Microsoft Microsoft Certifications AZ-400 Questions & Answers

• Question 251:

  You manage source code control and versioning by using GitHub.

  You need to ensure that a PowerShell script is executed automatically before rebase operations are performed.

  What should you use?

  A. a package

  B. GitHub Copilot

  C. a webhook

  D. a gist

  Correct Answer: C

• Question 252:

  You need to the merge the POC branch into the default branch. The solution must meet the technical requirements. Which command should you run?

  A. git rebase

  B. git merge --squash

  C. git push

  D. git merge --allow-unrelated-histories

  Correct Answer: A

  The commit history of the POC branch must replace the history of the default branch.

  Rebasing is the process of moving or combining a sequence of commits to a new base commit. Rebasing is most useful and easily visualized in the context of a feature branching workflow.

  Note: The primary reason for rebasing is to maintain a linear project history. For example, consider a situation where the main branch has progressed since you started working on a feature branch. You want to get the latest updates to the

  main branch in your feature branch, but you want to keep your branch's history clean so it appears as if you've been working off the latest main branch. This gives the later benefit of a clean merge of your feature branch back into the main

  branch. Why do we want to maintain a "clean history"? The benefits of having a clean history become tangible when performing Git operations to investigate the introduction of a regression.

  Incorrect:

  Not B: git-merge - Join two or more development histories together.

  Squash merging is a merge option that allows you to condense the Git history of topic branches when you complete a pull request. Instead of each commit on the topic branch being added to the history of the default branch, a squash merge

  adds all the file changes to a single new commit on the default branch.

  Not D: git merge --allow-unrelated-histories

  By default, git merge command refuses to merge histories that do not share a common ancestor. This option can be used to override this safety when merging histories of two projects that started their lives independently. As that is a very rare

  occasion, no configuration variable to enable this by default exists and will not be added.

  Reference:

  https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase

• Question 253:

  You manage projects by using Azure Boards.

  You have a current work item name itemA that is dependant on a work item named itemB.

  You need to define the dependency for itemA.

  What should you do in the web portal for Azure DevOps?

  A. From Backlogs, open the context menu, select Add link and then select itemB. Set Link type to Related and add the ID of itemA

  B. From itemA open the Links tab, and then select Add link. Set Link type to Successor and add the ID of itemB.

  C. From Queries, open the context menu, select Add link, and then select Existing item. Set Link type to Affected By and add the ID of itemB.

  D. From itemA, open the Links tab, and then select Add link. Set Link type to References and add the ID Of itemB.

  Correct Answer: B

• Question 254:

  You have a project in Azure DevOps named Project1 that references an Azure Artifacts feed named Feed1. You have a package named Package1 that has the versions shown in the following table.

  

  You need to perform a build of Project1. Which version of Package1 will be used?

  A. 1.0.3

  B. 1.4.0

  C. 2.0.0

  D. 2.3.1

  Correct Answer: D

• Question 255:

  You use Azure DevOps processes to build and deploy code.

  You need to compare how much time is spent troubleshooting issues found during development and how much time is spent troubleshooting issues found in released code.

  Which KPI should you use?

  A. defect escape rate

  B. unplanned work rate

  C. defect rate

  D. rework rate

  Correct Answer: A

  Explanation:

  Defect escape rate

  Regardless of how experienced your DevOps team is, errors happen -- particularly as changes are being made. Software development requires innovation and defects should be expected and planned for as part of the process.

  The defect escape rate is a metric that assesses the collective quality of software releases by evaluating how often errors are discovered and rectified in the pre-production process versus during production.

  Incorrect:

  *

  Rework rate

  Rework rate (RWR) relates to the effort to address issues brought up in tickets.

  *

  unplanned work rate

  Unplanned Work

  How much time is dedicated to unexpected efforts? The unplanned work rate (UWR) tracks this in relation to time spent on planned work. Ideally, the unplanned work rate (UWR) will not exceed 25 percent.

  A high UWR may reveal efforts wasted on unexpected errors that were likely not detected early in the workflow. The UWR is sometimes examined alongside the rework rate (RWR), which relates to the effort to address issues brought up in tickets.

  Reference: https://www.appdynamics.com/topics/devops-metrics-and-kpis https://phoenixnap.com/blog/devops-metrics-kpis

• Question 256:

  You have a project in Azure DevOps named Project1.

  You implement a Continuous Integration/Continuous Deployment (CI/CD) pipeline that uses PowerShell Desired State Configuration (DSC) to configure the application infrastructure.

  You need to perform a unit test and an integration test of the configuration before Project1 is deployed.

  What should you use?

  A. the PSScriptAnalyzer tool

  B. the Pester test framework

  C. the PSCodeHealth module

  D. the Test-DscConfiguration cmdlet

  Correct Answer: B

  Explanation:

  Pester is a testing and mocking framework for PowerShell.

  Pester provides a framework for writing and running tests. Pester is most commonly used for writing unit and integration tests, but it is not limited to just that. It is also a base for tools that validate whole environments, computer deployments,

  database configurations and so on.

  Example: Building a Continuous Integration and Continuous Deployment pipeline with DSC

  This example demonstrates how to build a Continuous Integration/Continuous Deployment (CI/CD) pipeline by using PowerShell, DSC, and Pester.

  IntegrationTests: Runs the Pester integration tests.

  UnitTests: Runs the Pester unit tests.

  Incorrect:

  * PSScriptAnalyzer PSScriptAnalyzer is a static code checker for PowerShell modules and scripts. PSScriptAnalyzer checks the quality of PowerShell code by running a set of rules. The rules are based on PowerShell best practices identified by PowerShell Team and the community. It generates DiagnosticResults (errors and warnings) to inform users about potential code defects and suggests possible solutions for improvements.

  PSScriptAnalyzer ships with a collection of built-in rules that check various aspects of PowerShell code such as:

  The presence of uninitialized variables Use of PSCredential type Use of Invoke-Expression And many more

  Reference: https://pester.dev/docs/quick-start/#what-is-pester https://learn.microsoft.com/en-us/azure/devops/pipelines/release/dsc-cicd https://github.com/PowerShell/PSScriptAnalyzer

• Question 257:

  You have a project in Azure DevOps named Project1.

  You need to ensure that all new pipelines in Project1 execute three specific tasks during pipeline execution.

  What should you create?

  A. a task group

  B. a JSON template

  C. a YAML template

  D. a PowerShell task

  Correct Answer: A

  Explanation:

  A task group allows you to encapsulate a sequence of tasks, already defined in a build or a release pipeline, into a single reusable task that can be added to a build or release pipeline, just like any other task. You can choose to extract the

  parameters from the encapsulated tasks as configuration variables, and abstract the rest of the task information.

  The new task group is automatically added to the task catalog, ready to be added to other release and build pipelines. Task groups are stored at the project level, and are not accessible outside the project scope.

  Task groups are a way to standardize and centrally manage deployment steps for all your applications. When you include a task group in your definitions, and then make a change centrally to the task group, the change is automatically

  reflected in all the definitions that use the task group. There is no need to change each one individually.

  Reference:

  https://learn.microsoft.com/en-us/azure/devops/pipelines/library/task-groups

• Question 258:

  You use Calendar Versioning (CalVer) for code assets.

  You need to store an optional tag of beta as part of the version.

  Which part of the version should you use for the tag?

  A. minor

  B. major

  C. micro

  D. modifier

  Correct Answer: D

  Explanation:

  Calendar Versioning

  There are multiple calendar versioning schemes, long used by projects big and small. Rather than declaring a single scheme to be CalVer, it's important to recognize the practicality of each and design the scheme to fit the project. First, the

  parts of the version:

  Major - The first number in the version. 2 and 3 are Python's famous major versions. The major segment is the most common calendar-based component.

  Minor - The second number in the version. 7 is the most popular minor version of Python.

  Micro - The third and usually final number in the version. Sometimes referred to as the "patch" segment.

  Modifier - An optional text tag, such as "dev", "alpha", "beta", "rc1", and so on.

  Reference: https://calver.org/

• Question 259:

  You use Azure Pipelines to build and test a React.js application.

  You have a pipeline that has a single job.

  You discover that installing JavaScript packages from npm takes approximately five minutes each time you run the pipeline.

  You need to recommend a solution to reduce the pipeline execution time.

  Solution: You recommend using pipeline artifacts.

  Does this meet the goal?

  A. Yes

  B. No

  Correct Answer: B

• Question 260:

  You use GitHub for source control of .NET applications.

  You need to deploy a documentation solution that meets the following requirements:

  Documents will be written in Markdown as developers make code changes. Changes to the documents will trigger the recompilation of a static website. Users will access the documents from the static website.

  Documents will be stored in a GitHub repository.

  Which two tools can you use to compile the website? Each correct answer presents a complete solution.

  NOTE: Each correct selection is worth one point.

  A. Word Press

  B. Jekyll

  C. DocFX

  D. caret

  E. Medium

  Correct Answer: BC