Free AZ-400 Exam Braindumps
Designing and Implementing Microsoft DevOps Solutions Questions 181–185 (page: 38)

Updated On: 10-Mar-2026

You manage source control by using GitHub.

You have a file named Data.txt that contains sensitive data. A user pushes Data.txt to a repository.

You need to purge the file from the repository.

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

Note: Each correct solution is worth one point.

  1. git checkout git clean -d data.txt --force
  2. bfg --delete-files data.txt git push --force
  3. git revert -edit data.txt git push -force
  4. git filter-repo --invert-paths --path data.txt git push origin --force --all
  5. git rm data.txt git push --force
  6. git checkout git reset -hard -pathspec data.txt

Answer(s): D,E

Explanation:

E:
The Problem
How do I delete a file from a Git repository?
The Solution
We can do this using git rm:
git rm unwanted-file.txt
This command will delete the file and stage its deletion to be included in the next commit. If we want to remove a directory, we must include the -r (recursive) flag, as with the standard rm command.
D:
If the file we want to remove contains sensitive content, we will need either to create a new Git repository with a fresh history or to rewrite the history of our current repository using git filter-branch:
git filter-repo -f --index-filter 'git rm --cached --ignore-unmatch unwanted-file.tx Note that rewriting the commit history in this way is dangerous and will permanently alter your repository.
Additionally, git filter-branch is a slow operation, especially for large repositories with many commits. Double- check that the name of the file to be removed is correct before running this command.
After our commit history has been rewritten, we will need to force push the changes to remote repositories using a command such as the following:

git push --force -u origin main


Reference:

https://sentry.io/answers/delete-a-file-from-a-git-repository/



You manage projects by using Azure Boards.

You have a current work item named itemA that is dependent 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?

  1. From itemA, open the Links tab, and then select Add link. Set Link type to References and add the ID of itemB.
  2. From itemA, open the Links tab, and then select Add link. Set Link type to Successor and add the ID of item
  3. 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.
  4. From itemA, open the Links tab, and then select Add link. Set Link type to Related and add the ID of itemB.

Answer(s): B

Explanation:

Correct:
* From Backlogs, open the context menu, select Add link, and then select itemA. Set Link type to Successor and add the ID of itemB.
* From itemA, open the Links tab, and then select Add link. Set Link type to Successor and add the ID of itemB.
Set Link type to Successor, not to Affected by, References, or Related.
Incorrect:
* Add a Parent link to the user story of itemA.
* From Backlogs, open he context menu, select Add link, and then select itemA. Set Link type to References and add the ID of itemB.
* From Backlogs, open the context menu, select Add link, and then select itemB. Set Link type to Related and add the ID of itemA.
* From itemA, open the Links tab, and then select Add link. Set Link type to References and add the ID of itemB.
* From itemA, open the Links tab, and then select Add link. Set Link type to Related and add the ID of itemB.
* 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.
Note: Creating a Dependency
Dependencies can be created from the Links Tab
Dependencies can be created using the Predecessor and Successor links on the Links tab. A predecessor is the producer of the work item, or the item that must come first. A successor is the consumer of the work item, or the item that is dependent on the first item.


Reference:

https://learn.microsoft.com/en-us/azure/devops/extensions/dependency-tracker/create-new-dependency



You have a project in Azure DevOps named Project1. Project1 contains a published wiki.

You need to change the order of pages in the navigation pane of the published wiki in the Azure DevOps portal.

What should you do?

  1. At the root of the wiki, create a file named wiki.md that defines the page hierarchy.
  2. Drag and drop the pages in the navigation pane.
  3. At the root of the wiki, create a file named .order that defines the page hierarchy.
  4. Rename the pages in the navigation pane.

Answer(s): B

Explanation:

Reorder a wiki page
You can reorder pages within the wiki tree view to have pages appear in the order and hierarchy you want. You can drag-and-drop a page title in the tree view to do the following operations:
Change the parent-child relationship of a page
Change the order of the page within the hierarchy


Reference:

https://docs.microsoft.com/en-us/azure/devops/project/wiki/add-edit-wiki



You build a Node.js app named App1 by using GitHub.

You need to test App1. The solution must ensure that App1 meets the following requirements.

Works correctly with versions 10, 12, and 14 of Node.js

Works correctly with Ubuntu versions 22.04 and 20.04

Minimizes the runtime of the test stage

What should you use?

  1. environments
  2. matrices
  3. concurrency
  4. jobs

Answer(s): B

Explanation:

About matrix strategies
A matrix strategy lets you use variables in a single job definition to automatically create multiple job runs that are based on the combinations of the variables. For example, you can use a matrix strategy to test your code in multiple versions of a language or on multiple operating systems.
Using a matrix strategy
Use jobs.<job_id>.strategy.matrix to define a matrix of different job configurations. Within your matrix, define one or more variables followed by an array of values. For example, the following matrix has a variable called version with the value [10, 12, 14] and a variable called os with the value [ubuntu-latest, windows-latest]:
jobs:
example_matrix:
strategy:
matrix:

version: [10, 12, 14]
os: [ubuntu-latest, windows-latest]
A job will run for each possible combination of the variables. In this example, the workflow will run six jobs, one for each combination of the os and version variables.
Example: Using a multi-dimension matrix jobs:
example_matrix:
strategy:
matrix:
os: [ubuntu-22.04, ubuntu-20.04]
version: [10, 12, 14]
runs-on: ${{ matrix.os }}
steps:
- uses: actions/setup-node@v4
with:
node-version: ${{ matrix.version }}


Reference:

https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/running-variations-of- jobs-in-a-workflow



DRAG DROP (Drag and Drop is not supported)

You are implementing a new project in Azure DevOps.

You need to assess the performance of the project. The solution must identify the following metrics:

How long it takes to complete a work item

The percentage of defects found in production

Which DevOps KPI should you review for each metric? To answer, drag the appropriate KPIs to the correct metrics. Each KPI 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: Cycle time
How long it takes to complete a work item

Cycle time measures the time it takes for your team to complete work items once they begin actively working on them.

Lead time measures the total time elapsed from the creation of work items to their completion.

Box 2: Defect Escape Rate
The percentage of defects found in production

Defect Escape Rate: Each software deployment includes the risk of sparking new defects. These issues can be discovered with user acceptance testing but sometimes these errors are found by the end-user. Since errors are the natural part of the development process, the development team should plan to deal with these issues before the development process. Defect escape rate comes into play to deal with such scenarios. It monitors the reality by accepting that issues will arise and they should be discovered as early as possible. The defect escape rate checks how often defects are discovered in the preproduction phase versus during the production phase. This metric alone provides essential insights into the quality of software releases.


Reference:

https://learn.microsoft.com/en-us/azure/devops/report/dashboards/cycle-time-and-lead-time https://www.professional-devops.com/devops-metrics-kpis.html



Viewing page 38 of 72
Viewing questions 186 - 190 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!