SIMULATION
Task 6
Initialize the default main branch, if it does not exist already.
For Project 1, you need to implement branch merging restrictions to enable squash merge for all changes merged into the main branch.
Answer : A
Step 1: Initialize the Default Main Branch
Navigate to Azure DevOps:
Go to Azure DevOps and sign in with your credentials.
Select Your Project:
ChooseProject1from your list of projects.
Initialize the Main Branch:
Go toRepos>Files.
Step 2: Enable Squash Merge for the Main Branch
Navigate to Branch Policies:
Go toRepos>Branches.
Find themainbranch and click on the...(ellipsis) next to it.
SelectBranch policies.
Enable Squash Merge:
UnderPolicies, scroll down to theMerge strategysection.
SelectSquash mergeas the required merge strategy2.
Save Changes:
Click onSave changesto apply the policies.
Step 3: Verify the Squash Merge Policy
Create a Pull Request:
Make a change in a branch and create a pull request to merge it into the main branch.
Complete the Pull Request:
SIMULATION
Task 5
For Project1, you need to create a project wiki named Wiki1 that uses the Mermaid syntax to render a diagram A sample of the desired output is stored in C:\Resources\TCPHandshake.png.
Answer : A
Step 1: Create a Project Wiki
Navigate to Azure DevOps:
Go to Azure DevOps and sign in with your credentials.
Select Your Project:
ChooseProject1from your list of projects.
Create a Wiki:
In the left-hand menu, selectWiki.
Click onCreate project wiki.
Enter the nameWiki1and clickCreate.
Step 2: Add Mermaid Syntax to Render a Diagram
Open the Wiki Page:
Navigate to the newly createdWiki1.
Edit the Wiki Page:
Click onEditto start editing the wiki page.
Insert Mermaid Diagram:
Use the following Mermaid syntax to render a diagram. For example, to render a simple flowchart, you can use:
```mermaid
graph TD;
A-->B;
A-->C;
B-->D;
C-->D;
Save the Page:
Click onSaveto save your changes.
Step 3: Render the TCP Handshake Diagram
Convert TCPHandshake.png to Mermaid Syntax:
Since you have a sample diagram inC:\Resources\TCPHandshake.png, you need to convert this diagram into Mermaid syntax. Here's an example of how a TCP handshake might look in Mermaid syntax:
```mermaid
sequenceDiagram
participant Client
participant Server
Client->>Server: SYN
Server-->>Client: SYN-ACK
Client->>Server: ACK
Add the Diagram to the Wiki:
Replace the sample Mermaid syntax with the TCP handshake diagram syntax in the wiki page.
Save the Page:
Click onSaveto save your changes.
SIMULATION
Task 4
Initialize the default main branch, if it does not exist already.
In the Userl-42147509 Azure DevOps project, you need to implement an approval process for the default main branch.
The process must use the four-eyes principle and have at least one approval on every iteration.
Answer : A
Step 1: Initialize the Default Main Branch
Navigate to Azure DevOps:
Go to Azure DevOps and sign in with your credentials.
Select Your Project:
ChooseProject1from your list of projects.
Initialize the Main Branch:
Go toRepos>Files.
If the main branch does not exist, you will see an option to initialize it. Click onInitializeand follow the prompts to create the main branch.
Step 2: Implement an Approval Process for the Main Branch
Navigate to Branch Policies:
Go toRepos>Branches.
Find themainbranch and click on the...(ellipsis) next to it.
SelectBranch policies.
Enable Required Reviewers:
UnderPolicies, enableMinimum number of reviewers.
Set the minimum number of reviewers to2to enforce the four-eyes principle.
Add Required Reviewers:
Add the users who should review the changes. Ensure that at least one approval is required on every iteration.
Enable Reset Code Reviewer Votes:
Enable theReset code reviewer votes when there are new changesoption to ensure that any new changes require re-approval.
Save Changes:
Click onSave changesto apply the policies.
Step 3: Verify the Approval Process
Create a Pull Request:
Make a change in a branch and create a pull request to merge it into the main branch.
Review and Approve:
Ensure that the pull request requires at least two reviewers to approve it before it can be merged.
SIMULATION
Task 3
You need to create a new team dashboard named Dashboard1 for the default project team of Project1. The dashboard must display the members of the team
Answer : A
Step 1: Create a New Team Dashboard
Navigate to Azure DevOps:
Go toAzure DevOpsand sign in with your credentials.
Select Your Project:
ChooseProject1from your list of projects.
Access Dashboards:
In the left-hand menu, selectDashboards.
Create a New Dashboard:
Click onNew Dashboard.
Enter the nameDashboard1.
Ensure the dashboard type is set toTeam Dashboard.
ClickCreate.
Step 2: Add the Team Members Widget
Open the Widget Catalog:
After creating the dashboard, the widget catalog will open automatically. If it doesn't, click onAdd Widget.
Search for Team Members Widget:
In the widget catalog, search forTeam Members.
Add the Widget:
Click on theTeam Memberswidget and then clickAddto place it on your dashboard.
Configure the Widget:
Once added, you can resize and move the widget to your preferred location on the dashboard.
Step 3: Save and Share the Dashboard
Save the Dashboard:
Click onSaveto save your changes.
Share the Dashboard:
You can share the dashboard URL with your team members or set permissions to control who can view or edit the dashboard.
SIMULATION
Task 2
For the RG1 lod42147S09 resource group, you need to create an action group named DevOpsAG that can be triggered in any region by using Alerts.
The action group must email two users named admin1 @contoso.com and admin2@contoso.com and notify members of the Owner role for the resource.
Use only the common alert schema for notifying the resource owners.
Answer : A
Step 1: Create an Action Group
Navigate to Azure Portal:
Go to Azure Portal and sign in with your credentials.
Access Azure Monitor:
In the left-hand menu, selectMonitor.
Create Action Group:
UnderAlerts, selectAction groups.
Click on+ Create.
Configure Basic Settings:
Subscription: Select your subscription.
Resource Group: SelectRG1 lod42147S09.
Action Group Name: EnterDevOpsAG.
Display Name: Enter a display name for the action group.
Step 2: Define Actions
Add Email Notifications:
Click onAdd action.
Action Type: SelectEmail/SMS message/Push/Voice.
Action Name: Enter a name for the action (e.g.,EmailAdmins).
Email: Enteradmin1@contoso.comandadmin2@contoso.com.
ClickOK.
Notify Resource Owners:
Click onAdd actionagain.
Action Type: SelectEmail/SMS message/Push/Voice.
Action Name: Enter a name for the action (e.g.,NotifyOwners).
Email: SelectNotify all owners.
ClickOK.
Step 3: Enable Common Alert Schema
Common Alert Schema:
In theAdvancedtab, enable theCommon alert schemaoption1.
Step 4: Review and Create
Review:
Review all the settings you have configured.
Create:
Click onReview + createand thenCreate.
You have an Azure pipeline that is used to deploy an app named App1.
You need to ensure that new versions of App1 are released only if they exceed performance baselines. The solution must minimize administrative effort.
What should you configure?
Answer : C
You are developing an Azure Pipelines pipeline.
You need to configure a check in the pipeline that will query Azure Boards to ensure that there are no active work item issues before the pipeline deploys a build to production.
Which type of check should you implement?
Answer : C