Microsoft AZ-400 Exam Questions

Step 1: Sign Up for Azure DevOps

Navigate to Azure DevOps.

Click onStart Free.

Enter the credentials:

Email: UserUsefl-42147509@ExamUsers.com

Password: eWrSalD2!

Follow the prompts to complete the sign-up process using the default settings.

Step 2: Create an Azure DevOps Organization

Once signed in, you will be prompted to create a new organization.

Enter a name for your organization and select your region.

Click onContinueto create the organization.

Step 3: Create a Private Project

In your new organization, click onNew Project.

Name the projectProject1.

Set the visibility toPrivate.

Click onCreate.

Step 4: Add an External User as a Stakeholder

Go to theOrganization Settings.

UnderGeneral, selectUsers.

Click onAdd users.

Enter the email address: Usfrr2-42147S09@ExamUsers.com.

Set the access level toStakeholder.

Add the user to the most restrictive group, which is typically theReadersgroup.

Click onAddto complete the process.

Step 5: Verify the User Addition

Ensure that the external user has been added successfully by checking theUserslist.

Confirm that the user has theStakeholderaccess level and is part of theReadersgroup.

By following these steps, you should be able to complete the task successfully. If you encounter any issues, feel free to ask for further assistance!

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

Step 1: Initialize the Default Main Branch

Navigate to Azure DevOps:

Go toAzure DevOpsand 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 branch1.

Step 2: Install the Microsoft Security DevOps Extension

Navigate to Extensions:

In Azure DevOps, click on theShopping Bagicon in the top right corner and selectBrowse Marketplace.

Search for the Extension:

Search forMicrosoft Security DevOps.

Install the Extension:

Click onGet it free.

Select your organization (User1-42147509) and clickInstall.

Follow the prompts to complete the installation2.

Step 3: Create a New Starter Pipeline

Navigate to Pipelines:

Go toPipelines>New pipeline.

Select the Repository:

ChooseAzure Repos Gitand select the relevant repository.

Configure the Pipeline:

SelectStarter pipelineand replace the default YAML with the following starter code:

trigger:

- starter

pool:

vmImage: 'windows-latest'

steps:

- task: MicrosoftSecurityDevOps@1

inputs:

command: 'run'

policy: 'azuredevops'

publish: true

Save the Pipeline:

Click onSaveand enterstarteras the branch name.

Click onSave and runto save the pipeline to the new branch namedstarter3.

By following these steps, you will have successfully initialized the main branch, installed the Microsoft Security DevOps extension, and created a new starter pipeline namedstarter1that includes the specified task

To ensure that your Azure Web App named az400-38443478-main supports rolling upgrades and only 10 percent of users connect to the updated version of the app, you can use deployment slots with the following steps:

Create a Deployment Slot:

Navigate to the Azure Portal.

Go to your Web App az400-38443478-main.

Select Deployment slots in the menu.

Click on Add Slot.

Name the slot (e.g., staging) and if needed, clone settings from the production slot.

Configure the Traffic Percentage:

In the Deployment Slots menu, you will see a column for Traffic %.

Set the traffic percentage to 10% for the staging slot1.

This will route only 10% of the traffic to the updated version of the app in the staging slot.

Deploy the Updated App to the Staging Slot:

Deploy your updated application to the staging slot.

Test the application in the staging slot to ensure it's working as expected.

Complete the Rolling Upgrade:

Once you're satisfied with the performance and stability of the app in the staging slot, you can gradually increase the percentage of traffic until you're ready to swap with the production slot.

To swap slots, go to the Deployment slots menu and click on Swap with the production slot.

By using deployment slots, you can achieve rolling upgrades with minimal administrative effort, as it allows you to test the new version on a subset of users before fully releasing it. Remember to adjust the traffic percentage and monitor the application's performance throughout the process.