DRAG DROP (Drag and Drop is not supported)You need to find and isolate shared code. The shared code will be maintained in a series of packages.Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.Select and Place:
Answer(s): A
Step 1: Create a dependency graph for the applicationBy linking work items and other objects, you can track related work, dependencies, and changes made over time. All links are defined with a specific link type. For example, you can use Parent/Child links to link work items to support a hierarchical tree structure. Whereas, the Commit and Branch link types support links between work items and commits and branches, respectively.Step 2: Group the related components.Packages enable you to share code across your organization: you can compose a large product, develop multiple products based on a common shared framework, or create and share reusable components and libraries.Step 3: Assign ownership to each component graph
https://docs.microsoft.com/en-us/azure/devops/boards/queries/link-work-items-support-traceability?view=azure -devops&tabs=new-web-form https://docs.microsoft.com/en-us/visualstudio/releasenotes/tfs2017-relnotes
DRAG DROP (Drag and Drop is not supported)You have a large repository named Repo1 that contains a directory named directory1.You plan to modify files in directory1.You need to create a clone of Repo1. The solution must minimize the amount of transferred data.How should you complete the script? To answer, drag the appropriate values to the correct targets. Each value may be used once, more than once, or not at all. You may need to drag the split bar between panes or scroll to view content.Note: Each correct selection is worth one point.Select and Place:
Box 1: scalar clone scalar clone optimizes cloning large repositories by minimizing the initial data transfer.Box 2: git sparse-checkout git sparse-checkout set directory1 limits the working directory to the specified folder, avoiding unnecessary file downloads.
https://devblogs.microsoft.com/devops/introducing-scalar/https://git-scm.com/docs/scalar
SIMULATIONInitialize the default main branch, if it does not exist already.For Project1, you need to implement branch merging restrictions to enable squash merge for all changes merged into the main branch.
See explanation below.Phase 1. Select the correct branchStep 1: To manage branch policies, select Repos > Branches to open the Branches page in the web portal.(You can also get to branch policy settings with Project Settings > Repository > Policies > Branch Policies > <Branch Name>.)Step 2: To set branch policies, locate the branch you want to manage. You can browse the list or search for your branch in the Search branch name box at upper right. [Select the default main branch]Select the More options icon next to the branch, and then select Branch policies from the context menu.Phase 2: Limit merge typesAzure Repos has several merge strategies, and by default, all of them are allowed. You can maintain a consistent branch history by enforcing a merge strategy for PR completion.Step 3: Set Limit merge types to On to limit which merge types to allow in your repo.Step 4: Select Squash merge, deselect the other Allowed Merge types.Squash merge creates a linear history with a single commit in the target branch with the changes from the source branch. Learn more about squash merging and how it affects branch history.
https://learn.microsoft.com/en-us/azure/devops/repos/git/branch-policies
HOTSPOT (Drag and Drop is not supported)You have a project in Azure DevOps named Project1 and an Azure Repos repository named Repo1. Project1 contains a team named Team1.You need to ensure that all pull requests to the main branch from the feature/* branches are reviewed by the members of Team1 before the pull requests can be merged.Which two settings should you configure in the Azure DevOps portal? To answer, select the appropriate settings in the answer area.Note: Each correct answer is worth one point.Hot Area:
Box 1: Require a minimum number of reviewersTo configure branch policies in Azure DevOps, go to Project Settings > Repos > Repositories, select your repository, navigate to the Policies tab, then select the main branch to open its policy settings. Enable "Require a minimum number of reviewers" and "Automatically include reviewers" to enforce a review by the specific team before merging from feature/* branches.Box 2: Automatically include reviewers
You have an Azure Automation account that contains a runbook. The runbook is used to configure the application infrastructure of an Azure subscription.You have a project in Azure DevOps named Project1. Project1 contains a repository that stores code for the runbook.You need to ensure that every committed change to the code will update automatically and publish the runbook to Azure Automation.What should you configure?
Answer(s): C
Source control integration in Azure Automation supports single-direction synchronization from your source control repository. Source control allows you to keep your runbooks in your Automation account up to date with scripts in your GitHub or Azure DevOps source control repository. This feature makes it easy to promote code that has been tested in your development environment to your production Automation account.Source control integration lets you easily collaborate with your team, track changes, and roll back to earlier versions of your runbooks. For example, source control allows you to synchronize different branches in source control with your development, test, and production Automation accounts.Note:1. Configure source control in Azure portal2. Use this procedure to configure source control using the Azure portal.3. In your Automation account, select Source Control and click Add.Etc.
https://docs.microsoft.com/en-us/azure/automation/source-control-integration
Post your Comments and Discuss Microsoft AZ-400 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-400 content, but please register or login to continue.