SIMULATION
You have several apps that use an Azure SQLDatabase named db1.
You need to ensure that queries to db1 are tuned by Azure over time. The solution must only apply to db1.
To complete this task, sign in to the Microsoft Azure portal.
1. To enable automatictuning on a single database, navigate to the database in the Azure portal and select Automatic tuning.
2. Select the automatic tuning options you want to enable and select Apply.
Note: Individual automatic tuning settings can be separately configuredfor each database. You can manually configure an individual automatic tuning option, or specify that an option inherits its settings from the server.
https://docs.microsoft.com/en-us/azure/azure-sql/database/automatic-tuning-enable
You have a GitHub repository that uses GitHub Actions and stores access keys by using GitHub encrypted secrets.
You plan to update the secrets by using the GitHub REST API.
You need to wrap the secrets before adding them to a REST-based call.
Which encryption library should you are that you use?
SIMULATION
Task 7
Initialize the default main branch, if it does not exist already
In the User 1-42147509 organization, you need to install the Microsoft Security DevOps extension.
Next, create a new starter pipeline named starter1 that will use the following starter code.
Ensure that starter! includes a task that executes the extension and uses the following input*:
* Command: run
* Policy aruredevops
* Publish: true
Save the pipeline to a new branch named starter
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.
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.
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.
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:
You have an Azure DevOpsorganization named Contoso.
You need to recommend an authentication mechanism that meets the following requirements:
* Supports authentication from Get
* Minimizes the need to provide credentials during authentication
What should you recommend?
Personal access tokens (PATs) give you access to Azure DevOps and Team Foundation Server (TFS), without using your username and password directly. These tokens have an expiration date from when they're created. You can restrict the scope of the data they can access. Use PATs to authenticate if you don't already have SSH keys set up on your system or if you need to restrict the permissions that are granted by the credential.
https://docs.microsoft.com/en-us/azure/devops/repos/git/auth-overview
Xuan
21 days agoDwight
27 days agoGarry
1 months agoIzetta
2 months agoEdison
2 months agoDino
2 months agoJamey
3 months agoVilma
3 months agoTwanna
3 months agoTawna
3 months agoWilliam
4 months agoRicki
4 months agoKattie
4 months agoGeoffrey
4 months agoDulce
4 months agoCherelle
4 months agoBillye
5 months agoAmber
5 months agoTula
5 months agoThea
5 months agoBrittani
6 months agoRoy
6 months agoEttie
6 months agoJannette
6 months agoLindsay
6 months agoBev
7 months agoGwenn
7 months agoGlendora
7 months agoVernell
7 months agoAlison
7 months agoMarguerita
8 months agoLacresha
8 months agoSalley
9 months agoJanae
9 months agoYoulanda
10 months agoAmber
10 months agoTyisha
10 months ago