Free AZ-400 Exam Braindumps
Designing and Implementing Microsoft DevOps Solutions Questions 116–120 (page: 25)

Updated On: 10-Mar-2026

Your development team is building a new web solution by using the Microsoft Visual Studio integrated development environment (IDE).

You need to make a custom package available to all the developers. The package must be managed centrally, and the latest version must be available for consumption in Visual Studio automatically.

Which three actions should you perform? Each correct answer presents part of the solution.

Note: Each correct selection is worth one point.

  1. Publish the package to a feed.
  2. Create a new feed in Azure Artifacts.
  3. Upload a package to a Git repository.
  4. Add the package URL to the Environment settings in Visual Studio.
  5. Add the package URL to the NuGet Package Manager settings in Visual Studio.
  6. Create a Git repository in Azure Repos.

Answer(s): A,B,E

Explanation:

B: By using your custom NuGet package feed within your Azure DevOps (previously VSTS) instance, you'll be able to distribute your packages within your organization with ease.
Start by creating a new feed.
A: We can publish, pack and push the built project to our NuGet feed.
E: Consume your private NuGet Feed
Go back to the Packages area in Azure DevOps, select your feed and hit "Connect to feed". You'll see some instructions for your feed, but it's fairly simple to set up.
Just copy your package source URL, go to Visual Studio, open the NuGet Package Manager, go to its settings and add a new source. Choose a fancy name, insert the source URL. Done.
Search for your package in the NuGet Package Manager and it should appear there, ready for installation.
Make sure to select the appropriate feed (or just all feeds) from the top right select box.


Reference:

https://medium.com/medialesson/get-started-with-private-nuget-feeds-in-azure-devops-8c7b5f022a68



You use GitHub for source control.

A file that contains sensitive data is committed accidentally to the Git repository of a project.

You need to delete the file and its history from the repository.

Which two tools can you use? Each correct answer presents a complete solution.

Note: Each correct selection is worth one point.

  1. the git filter-branch command
  2. BFG Repo-Cleaner
  3. the git rebase command
  4. GitHub Desktop

Answer(s): A,B

Explanation:

To entirely remove unwanted files from a repository's history you can use either the git filter-branch command or the BFG Repo-Cleaner open source tool.


Reference:

https://docs.github.com/en/github/authenticating-to-github/keeping-your-account-and-data-secure/removing- sensitive-data-from-a-repository



HOTSPOT (Drag and Drop is not supported)

Your company uses GitHub for source control. GitHub repositories store source code and store process documentation. The process documentation is saved as Microsoft Word documents that contain simple flow charts stored as .bmp files.

You need to optimize the integration and versioning of the process documentation and the flow charts. The solution must meet the following requirements:

Store documents as plain text.

Minimize the number of files that must be maintained.

Simplify the modification, merging, and reuse of flow charts.

Simplify the modification, merging, and reuse of documents.

Hot Area:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: Markdown (.md)
Github understands several text formats, including .txt and .md. .md stands for a file written in Markdown.

Box 2: Mermaid diagrams
Mermaid lets you create diagrams and visualizations using text and code. It is a Javascript based diagramming and charting tool that renders Markdown-inspired text definitions to create and modify diagrams dynamically.


Reference:

https://ourcodingclub.github.io/tutorials/git/

https://mermaid-js.github.io/mermaid/#/



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?

  1. the Service hooks settings for Project1
  2. the Connections settings for the Automation account
  3. the Source control settings for the Automation account
  4. the Service connections settings for Project1

Answer(s): C

Explanation:

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 portal
2. Use this procedure to configure source control using the Azure portal.
3. In your Automation account, select Source Control and click Add.
Etc.


Reference:

https://docs.microsoft.com/en-us/azure/automation/source-control-integration



DRAG DROP (Drag and Drop is not supported)

You have a GitHub repository named repo1 that stores the code of an app named App1.

You need deploy a workflow for repo1 by using GitHub Actions. The solution must meet the following requirements:

Scan on pushes to the main branch.

Scan on pull requests to the main branch.

Scan on pull requests to any branch that has a prefix of releases/.

Scan all the files in the subdirectories of the src directory.

Exclude scanning of markdown files.

How should you complete the code? 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:

  1. See Explanation section for answer.

Answer(s): A

Explanation:




Box 1: - 'releases/**'
Scan on pull requests to any branch that has a prefix of releases/.

Note: You can use special characters in path, branch, and tag filters.
*: Matches zero or more characters, but does not match the / character. For example, Octo* matches Octocat.
**: Matches zero or more of any character.

Box 2: - 'src/**'
Scan all the files in the subdirectories of the src directory.

Use the paths filter when you want to include file path patterns or when you want to both include and exclude file path patterns.

Box 3: - '**/*.md'
Exclude scanning of markdown files.

Use the paths-ignore filter when you only want to exclude file path patterns.


Reference:

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat- sheet



Viewing page 25 of 72
Viewing questions 193 - 200 out of 398 questions


Post your Comments and Discuss Microsoft AZ-400 exam prep with other Community members:

AI Tutor AI Tutor 👋 I’m here to help!