Microsoft AZ-400 Practice Test - Questions Answers, Page 36

You can add the text "AB#<WORKITEMNUMBER>" to the title or description of the pull request in GitHub, which will automatically link the request to an existing Azure Boards work item with that number.

Reference:

Azure DevOps Docs: Link a work item to a pull request https://docs.microsoft.com/enus/azure/devops/repos/git/pull-requests?view=azure-devops#link-a-work-item-to-a-pull-request GitHub Docs: Creating a pull request https://docs.github.com/en-us/github/collaborating-withissues-and-pull-requests/creating-a-pull-request

By creating a feed view named "release" and setting it as the default view, packages that are published to the feed will not be immediately available for consumption. After the npm packages are tested successfully, you can configure a release pipeline that promotes a package to the @release view. This ensures that only tested packages are available for consumption and minimizes development effort as it doesn't require any additional steps to be taken by the consumer of the feed.

Reference:

Azure DevOps Docs: Create a feed and views https://docs.microsoft.com/enus/azure/devops/artifacts/feeds/create-feed?view=azure-devops Azure

DevOps Docs: Promote a package https://docs.microsoft.com/enus/azure/devops/artifacts/feeds/promote-package?view=azure-devops

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions "We strongly recommend that you include the version of the action you are using by specifying a get ref, SHA, or Docker tag. If you don't specify a version, it could break your workflows or cause unexpected behavior when the action owner publishes an update. Using the commit SHA of a released action version is the safest for stability and security. If the action publishes major version tags, you should expect to receive critical fixes and security patches while still retaining compatibility. Note that this behavior is at the discretion of the action's author. Using the default branch of an action may be convenient, but if someone releases a new major version with a breaking change, your workflow could break."

Pipeline artifacts are a way to persist build outputs, test results, and other files generated during a pipeline run. They allow you to share data between stages, jobs, and pipelines, and to persist data for longer than the lifetime of a pipeline run. While artifacts can be useful for sharing data between pipeline runs and reducing the time required to download dependencies, they are not a solution for reducing the time required to install JavaScript packages from npm during a pipeline run.

The solution of reducing the pipeline execution time could be achieved by using package caching, which allows you to store and reuse npm packages from previous pipeline runs. There are several package caching options available for Azure Pipelines, including the npm task, the npm cache task, and the npm ci task. All of these options allow you to configure caching for your npm packages, which can significantly reduce the time required to install packages during subsequent pipeline runs. Another solution could be using a dedicated agent that has those packages already installed, this way the pipeline doesn't have to install them again. You can find more information on package caching by following this link

https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/package/npm-cache?view=azuredevops

https://docs.microsoft.com/en-us/azure/active-directory/develop/app-objects-and-serviceprincipals "When you've completed the app registration, you've a globally unique instance of the app (the application object) which lives within your home tenant or directory. You also have a globally unique ID for your app (the app or client ID). In the portal, you can then add secrets or certificates and scopes to make your app work, customize the branding of your app in the sign-in dialog, and more."

You should use the Pester test framework to perform a unit test and an integration test of the configuration before Project1 is deployed. The Pester test framework is a PowerShell testing framework that can be used to validate PowerShell DSC configurations.