Free AZ-400 Exam Braindumps
Designing and Implementing Microsoft DevOps Solutions Questions 23–27 (page: 18)

Updated On: 16-Nov-2026

You have an Azure key vault named KV1 and three web servers.
You plan to deploy an app named App1 to the web servers.
You need to ensure that App1 can retrieve a secret from KV1. The solution must meet the following requirements:
-Minimize the number of permission grants required.
-Follow the principle of least privilege.
What should you include in the solution?

  1. role-based access control (RBAC) permission
  2. a system-assigned managed identity
  3. a user-assigned managed identity
  4. a service principal

Answer(s): C



DRAG DROP (Drag and Drop is not supported)
You have a GitHub organization that contains three users named User1, User2, and User3. You have a project that contains a repository named repo1.
You need to configure permissions for repo1. The solution must meet the following requirements:
-Ensure that User1 can actively push to repo1.
-Ensure that User2 can manage issues and pull requests for repo1.
-Ensure that User3 can manage repo1.
-Prevent User3 from accessing sensitive data in repo1.
Which role should you assign to each user? To answer, drag the appropriate roles to the correct users. Each role 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: Write
Ensure that User1 can actively push to repo1.
Write: Recommended for contributors who actively push to your project
Box 2: Triage
Ensure that User2 can manage issues and pull requests for repo1.
Triage: Recommended for contributors who need to proactively manage issues, discussions, and pull requests without write access
Box 3: Maintain
Ensure that User3 can manage repo1.
Prevent User3 from accessing sensitive data in repo1.
Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
Note: Repository roles for organizations
You can give organization members, outside collaborators, and teams of people different levels of access to repositories owned by an organization by assigning them to roles. Choose the role that best fits each person or team's function in your project without giving people more access to the project than they need.
From least access to most access, the roles for an organization repository are:
Read: Recommended for non-code contributors who want to view or discuss your project
Triage: Recommended for contributors who need to proactively manage issues, discussions, and pull requests without write access
Write: Recommended for contributors who actively push to your project
Maintain: Recommended for project managers who need to manage the repository without access to sensitive or destructive actions
Admin: Recommended for people who need full access to the project, including sensitive and destructive actions like managing security or deleting a repository


Reference:

https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/repository-r oles-for-an-organization



Note: This question is part of a series of questions that present the same scenario. Each question in the series contains a unique solution that might meet the stated goals. Some question sets might have more than one correct solution, while others might not have a correct solution.
After you answer a question in this section, you will NOT be able to return to it. As a result, these questions will not appear in the review screen.
You plan to update the Azure DevOps strategy of your company.
You need to identify the following issues as they occur during the company’s development process:
-Licensing violations
-Prohibited libraries
Solution: You implement continuous deployment.
Does this meet the goal?

  1. Yes
  2. No

Answer(s): B

Explanation:

Correct:
* You implement automated security testing.
Incorrect:
* You implement continuous deployment.
* You implement continuous integration
* You implement pre-deployment gates.
Note:
You can use Mend Bolt with Azure DevOps to automatically detect alerts on vulnerable open source components, outdated libraries, and license compliance issues in your code.
Azure DevOps integration with Mend Bolt will enable you to:
Detect and remedy vulnerable open source components.
* Generate comprehensive open source inventory reports per project or build.
*-> Enforce open source license compliance, including dependencies’ licenses.
* Identify outdated open source libraries with recommendations to update.
Note 2: WhiteSource is the leader in continuous open source software security and compliance management.
WhiteSource integrates into your build process, irrespective of your programming languages, build tools, or development environments. It works *automatically*, continuously, and silently in the background, checking the security, licensing, and quality of your open source components against WhiteSource constantly-updated definitive database of open source repositories.


Reference:

https://azuredevopslabs.com/labs/vstsextend/whitesource/



You manage code by using GitHub.
You plan to use Dependabot to scan for code dependencies.
You need to identify when scanning will be triggered automatically.
Which two actions will trigger a scan? Each correct answer presents a complete solution.
Note: Each correct solution is worth one point.

  1. A new advisory is added.
  2. A pull request is created.
  3. A branch is forked.
  4. Any commit is pushed.
  5. The dependency graph of a repository changes.

Answer(s): A,E

Explanation:

About Dependabot alerts, Detection of insecure dependencies
Dependabot performs a scan of the default branch of your repository to detect insecure dependencies, and sends Dependabot alerts when:
A new advisory is added to the GitHub Advisory Database.
Note: Only advisories that have been reviewed by GitHub will trigger Dependabot alerts.
The dependency graph for a repository changes. For example, when a contributor pushes a commit to change the packages or versions it depends on, or when the code of one of the dependencies changes.


Reference:

https://docs.github.com/en/code-security/dependabot/working-with-dependabot/automating-dependabot-with-gi thub-actions



You have an Azure Resource Manager template that deploys a multi-tier application.
You need to prevent the user who performs the deployment from viewing the account credentials and connection strings used by the application.
What should you use?

  1. Azure Key Vault
  2. a Web.config file
  3. an Appsettings.json file
  4. an Azure Storage table
  5. an Azure Resource Manager parameter file

Answer(s): A

Explanation:

When you need to pass a secure value (like a password) as a parameter during deployment, you can retrieve the value from an Azure Key Vault. You retrieve the value by referencing the key vault and secret in your parameter file. The value is never exposed because you only reference its key vault ID. The key vault can exist in a different subscription than the resource group you are deploying to.


Reference:

https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-manager-keyvault-parameter



Viewing page 18 of 81
Viewing questions 86 - 90 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!