Get Microsoft AZ-400 Exam Dumps

Answer : A

Step 1: Navigate to Personal Access Tokens

Sign in to Azure DevOps:

Go toAzure DevOpsand sign in with your credentials.

Access User Settings:

Click on your profile picture in the top right corner.

SelectUser settings.

Open Personal Access Tokens:

In the user settings menu, selectPersonal access tokens.

Step 2: Create a New Personal Access Token

Create a New Token:

Click on+ New Token.

Configure the Token:

Name: EnterToken1.

Organization: Select the organization where you want to use the token.

Expiration: Set the expiration to60 days.

Set Scopes:

Code: SelectRead, Write, & Manage.

Build: SelectRead & Execute.

Release: SelectRead.

Create the Token:

Click onCreate.

Step 3: Save the Token

Copy the Token:

Once the token is created, copy it immediately as it will not be displayed again.

Store the token in a secure location.

By following these steps, you will have successfully created a personal access token namedToken1with the specified capabilities and a 60-day expiration

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.

By following these steps, you will have created a project wiki namedWiki1and used Mermaid syntax to render a diagram

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.

By following these steps, you will have successfully initialized the main branch and implemented an approval process that adheres to the four-eyes principle, ensuring that every iteration has at least one approval

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.

By following these steps, you will have a new team dashboard namedDashboard1that displays the members of the default project team forProject1

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.

By following these steps, you will have successfully created an action group namedDevOpsAGthat emails the specified users and notifies resource owners using the common alert schema