You have an Azure DevOps organization that contains a group named Group1 and a project named Project1.You need to ensure that the members of Group1 can create and manage build pipelines in Project1. The solution must follow the principle of least privilege.To which group should you add Group1?
Answer(s): C
The group should be added to the built-in Build Administrators security group.The Build Administrators group is specifically scoped to pipeline management. Members of this group can: -> Create new build and release pipelines.-> Edit existing pipeline definitions.Manage build resources and retention policies.Delete build pipelines.By using this group, you avoid adding users to the Project Administrators group, which would grant unnecessary control over project settings, repository permissions, board configurations, and service connections.
https://learn.microsoft.com/en-us/azure/devops/pipelines/policies/set-permissions
You have an Azure Pipeline.You plan to provision a self-hosted Linux agent.Which authentication mechanism should you use to register the self-hosted agent?
Answer(s): A
Correct:To register a self-hosted Linux agent for Azure Pipelines, you have several authentication options.* device code flowYou can use the device code flow (referred to as AAD in the configuration script) if you want to authenticate interactively without generating a long-lived token yourself.* personal access token (PAT)Use a personal access token (PAT) if your Azure DevOps Server or TFS instance and the agent machine are not in a trusted domain. PAT authentication is handled by your Azure DevOps Server or TFS instance instead of the domain controller.Note: Authentication Methods for RegistrationWhen you run the ./config.sh script on your Linux machine, it will prompt you for an authentication type. The primary options are:Personal Access Token (PAT): The most common method. You generate a token in Azure DevOps with the Agent Pools (read, manage) scope and paste it when prompted.Device Code Flow (AAD): Select this by entering AAD at the prompt. The script will provide a code and a URL (e.g., https://microsoft.com/devicelogin). You enter the code in a browser on any device to sign in with your Entra ID (Azure AD) credentials.Service Principal (SP): Ideal for automated setup. You provide the Application (Client) ID, Tenant ID, and Client Secret.Incorrect:* Alternate credentials* certificate* SSH key
https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agent-authentication-options
HOTSPOT (Drag and Drop is not supported)You have a project in Azure DevOps that contains a team named Team1.You need to ensure that the members of Team1 can perform the following actions:-Execute builds from the command line.-Stop builds from the command line.-Specify the build number format.The solution must follow the principle of least privilege.Which two permissions should you assign to Team1? To answer, select the appropriate permissions in the answer area.Note: Each correct selection is worth one point.Hot Area:
To meet your requirements while maintaining the principle of least privilege, the team needs exactly two permissions: Queue builds and Edit build pipeline.Here is the breakdown of why these two specific permissions are required and sufficient.Box 1: Edit build pipelineEdit build pipeline: Defining or changing the build number format requires modifying the pipeline configuration itself (either via the YAML file definition or the classic UI editor settings).Scope: This permission allows users to save changes to the pipeline definition, which is required to update the name: property (YAML) or the Build Number Format field (Classic).Box 2: Queue buildsThe Queue builds permission allows team members to execute builds and stop builds from the command line (via the Azure DevOps CLI or REST API).Scope: It grants the necessary runtime control over build execution without allowing users to modify the structural configuration of the pipeline.
https://learn.microsoft.com/en-us/azure/devops/pipelines/policies/permissions?view=azure-devops
HOTSPOT (Drag and Drop is not supported)You have the GitHub repositories shown in the following table.You make changes to the code in RepoB.You need to integrate the changes to RepoC.How should you complete the command? To answer, select the appropriate options in the answer area.Note: Each correct selection is worth one point.Hot Area:
To integrate the changes made in RepoB into RepoC, the exact Git commands depend on how Repo3 manages its dependencies.Box 1: submoduleCase 1: If RepoB is a Git SubmoduleIf RepoC pulls in RepoB as a git submodule, run these commands inside the RepoC repository:git submodule update --remote RepoBgit add RepoBgit commit -m "Update RepoB dependency"Box 2: updateNote:Case 2: If RepoB is a Git SubtreeThe following command is used:git subtree pull --prefix=path/to/RepoB RepoB_remote_url main --squashCase 3: If using a Package ManagerYou update the package file and run the manager's update command:Node.js/npm: npm update repoBPython/pip: pip install --upgrade git+https://github.com
https://stackoverflow.com/questions/50278005/setting-up-multiple-git-repositories-for-multiple-projects-in-vsts
DRAG DROP (Drag and Drop is not supported)You use GitHub Enterprise Server as a source code repository.You create an Azure DevOps organization named Contoso.In the Contoso organization, you create a project named Project1.You need to link GitHub commits, pull requests, and issues to the work items of Project1. The solution must use OAuth-based authentication.Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of actions to the answer area and arrange them in the correct order.Select and Place:
Step 1: From Developer settings in GitHub Enterprise Server, register a new OAuth app.If you plan to use OAuth to connect Azure DevOps Services or Azure DevOps Server with your GitHub Enterprise Server, you first need to register the application as an OAuth AppStep 2: From Organization settings in Azure DevOps, add an OAuth configurationRegister your OAuth configuration in Azure DevOps Services.Note:1. Sign into the web portal for Azure DevOps Services.2. Add the GitHub Enterprise Oauth configuration to your organization.3. Open Organization settings>Oauth configurations, and choose Add Oauth configuration.4. Fill in the form that appears, and then choose Create.Step 3: From Project Settings in Azure DevOps, add a GitHub connection.Connect Azure DevOps Services to GitHub Enterprise ServerChoose the Azure DevOps logo to open Projects, and then choose the Azure Boards project you want to configure to connect to your GitHub Enterprise repositories.Choose (1) Project Settings, choose (2) GitHub connections and then (3) Click here to connect to your GitHub Enterprise organization.
https://docs.microsoft.com/en-us/azure/devops/boards/github/connect-to-github
Post your Comments and Discuss Microsoft AZ-400 exam prep with other Community members:
Our website is free, but we have to fight against AI bots and content theft. We're sorry for the inconvenience caused by these security measures. You can access the rest of the AZ-400 content, but please register or login to continue.