1. A team is developing a complex application with several independent components, each residing in its own Git repository within the same Azure DevOps project. A build pipeline for the main application needs to checkout code from its primary repository and also from two other component repositories to compile and package the final application. The team wants to ensure that all required repositories are available at build time without manually cloning them in the script. Which feature should they use in their Azure Pipelines YAML definition?
Design and implement source control
A.Submodules
B.Package management feeds
C.Multi-repo checkout
D.Git Large File Storage (LFS)
Show answerAnswer
C. Multi-repo checkout
Azure Pipelines' multi-repo checkout feature allows a single pipeline to checkout multiple Git repositories. By defining additional repositories in the `resources.repositories` section and using the `checkout` step, all necessary codebases can be made available to the build agent automatically.
2. A company is setting up self-hosted build agents in an on-premises data center for Azure DevOps. These agents need to access internal network resources and build applications that require specific software (e.g., a proprietary compiler) not available on Microsoft-hosted agents. The agents should be configured to run as a service and securely communicate with Azure DevOps. Which steps are crucial during the agent installation and configuration?
Design and implement source control
A.Install Docker on the agent machine and pull the Azure DevOps agent image.
B.Install the Azure DevOps Server on the agent machine and register it as a build host.
C.Download the agent package, run 'config.cmd' (or 'config.sh'), and provide the Azure DevOps PAT and URL.
D.Configure a VPN connection from the agent machine to Azure DevOps and set up port forwarding.
Show answerAnswer
C. Download the agent package, run 'config.cmd' (or 'config.sh'), and provide the Azure DevOps PAT and URL.
Installing and configuring a self-hosted agent involves downloading the agent software, running the configuration script ('config.cmd' for Windows or 'config.sh' for Linux/macOS), and providing the Azure DevOps URL and a Personal Access Token (PAT) for authentication. This sets up the agent as a service and enables secure communication.
3. A company is using Azure DevOps to manage its software development lifecycle. They need to integrate an external security scanning tool into their release pipeline. This tool requires approval from a security team before deploying to production. The approval process involves reviewing the scan results and manually approving the deployment. The security team uses a separate ticketing system, and the approval status needs to be reflected in Azure DevOps. Which Azure DevOps feature should they use to manage this approval process effectively?
Design and implement source control
A.Pre-deployment approvals in release pipelines
B.Branch policies on the production branch
C.Service hooks to trigger an external approval system
D.Manual intervention tasks in release pipelines
Show answerAnswer
A. Pre-deployment approvals in release pipelines
Pre-deployment approvals in Azure DevOps release pipelines are specifically designed for this scenario. They pause the pipeline before deployment to an environment (like production) and require designated approvers to manually approve or reject the deployment. While service hooks or manual intervention tasks could be part of a larger solution, the direct and integrated way to enforce approval for deployment in Azure DevOps is through pre-deployment approvals.
4. A project team is setting up a new Git repository in Azure DevOps. They want to prevent large binary files (e.g., compiled executables, large datasets) from being committed directly into the repository, as this would inflate its size and negatively impact clone times. However, these files are necessary for some build processes and need to be tracked and versioned. Which Git feature should they integrate with their repository?
Design and implement source control
A.Git Large File Storage (LFS)
B.Azure Artifacts Universal Packages
C..gitignore file
D.Git hooks for pre-commit checks
Show answerAnswer
A. Git Large File Storage (LFS)
Git Large File Storage (LFS) is a Git extension that handles large files by replacing them with text pointers in the Git repository while storing the actual file contents on a remote server. This keeps the Git repository small and fast, while still allowing large files to be tracked and versioned.
5. A team is developing a new application that uses a combination of public open-source NuGet packages and internal proprietary NuGet packages. They are using Azure Artifacts for their private feeds. The team wants to ensure that when a developer builds the application, the build process first attempts to retrieve packages from the internal feed. If a package is not found in the internal feed, it should then attempt to retrieve it from nuget.org. This order of resolution is critical for security and performance. Which Azure Artifacts configuration should they implement?
Design and implement source control
A.Create a new feed view that filters public packages.
B.Manually add both internal and nuget.org feeds to the pipeline's NuGet.config.
C.Set up a separate proxy server for public NuGet packages.
D.Configure the internal feed to use nuget.org as an upstream source.
Show answerAnswer
D. Configure the internal feed to use nuget.org as an upstream source.
Configuring nuget.org as an upstream source for the internal Azure Artifacts feed allows the feed to act as a single point of access. When a package is requested, the feed first checks its own content (internal packages), then consults its upstream sources (nuget.org). This ensures the desired resolution order and simplifies the client's NuGet configuration to a single feed.
6. A software development company uses Azure DevOps for its source control. They have a large monorepo with several independent projects, each managed by a different team. They want to integrate a third-party code quality analysis tool that runs a scan whenever code is pushed to the `main` branch. This tool has a webhook that can be configured to receive notifications from Azure DevOps. The company needs to configure Azure DevOps to send specific events to this webhook. Which Azure DevOps feature should they use?
Design and implement source control
A.Service connections
B.Build pipeline triggers
C.Webhooks in repository settings
D.Service hooks
Show answerAnswer
D. Service hooks
Service hooks in Azure DevOps allow you to integrate with external services by sending notifications when specific events occur. You can configure a service hook to trigger on code pushes, pull request updates, or build completions, and then send a payload to a specified webhook URL, which is exactly what the third-party tool requires.
7. A team is developing a large application with several independent components, each residing in its own Git repository in Azure Repos. A build pipeline for the main application needs to access code from multiple repositories (e.g., common libraries, configuration files) during its execution. How should the pipeline be configured to efficiently check out code from these additional repositories?
Design and implement source control
A.Configure the pipeline to run on an agent that has all repositories pre-cloned.
B.Add multiple 'Get Sources' tasks to the pipeline, one for each repository.
C.Use the 'checkout' step with multiple repository resources in the YAML pipeline.
D.Manually clone each additional repository using Git commands in a script task.
Show answerAnswer
C. Use the 'checkout' step with multiple repository resources in the YAML pipeline.
Azure DevOps YAML pipelines support defining multiple repository resources and then checking them out using the 'checkout' step. This is the native and most efficient way to access code from multiple Git repositories within a single pipeline run.
8. A software development team is using Azure DevOps for their source control. They have a large monorepo containing several independent microservices. Each microservice has its own build pipeline. The team wants to optimize their CI/CD process so that a build pipeline for a specific microservice is only triggered when changes are pushed to files within that microservice's directory. Which feature should they configure in their build pipelines?
Design and implement source control
A.Path filters
B.Pipeline resource triggers
C.Branch policies
D.Scheduled triggers
Show answerAnswer
A. Path filters
Path filters allow you to specify which file paths within the repository should trigger a pipeline. By configuring path filters for each microservice's directory, pipelines will only run when relevant changes occur, optimizing build times and resource usage.
9. A company is migrating its existing on-premises Team Foundation Version Control (TFVC) repository to Azure Repos Git. The TFVC repository has a very large history, including numerous branches and merges, and it's essential to preserve the complete history and relationships accurately in Git. The development team is comfortable with command-line tools. Which tool is best suited for this full-fidelity migration?
Design and implement source control
A.Azure Migration Assistant
B.Azure DevOps Import Repository feature
C.Manual file copy and initial Git commit
D.Git-TFS command-line utility
Show answerAnswer
D. Git-TFS command-line utility
Git-TFS is a powerful command-line tool specifically designed for migrating TFVC repositories to Git while preserving full history, including branches, merges, and changesets accurately as Git commits. The Azure DevOps Import Repository feature is simpler but often doesn't handle complex history as robustly.
10. A company uses Azure DevOps to manage its software development lifecycle. They need to integrate their Azure DevOps pipelines with an external, on-premises quality gate system. This system performs static code analysis and security scans and must approve a build before it can proceed to deployment. How should they integrate the external system to pause the pipeline and await approval?
Design and implement source control
A.Implement an 'Invoke Azure Function' task to call the external system.
B.Define an Approval and Checks on the environment or resource the pipeline targets.
C.Configure a Service Hook to trigger the external system.
D.Use a REST API call within the pipeline to query the external system's status.
Show answerAnswer
B. Define an Approval and Checks on the environment or resource the pipeline targets.
Approvals and Checks on environments or resources are specifically designed to pause pipeline execution until external conditions are met or manual approvals are granted. This allows the external quality gate system to signal its approval (or rejection) via an API, which Azure DevOps then processes before proceeding.
11. A software development company is using Feature Branch Git workflow. They want to ensure that before any pull request (PR) can be merged into the 'main' branch, a build pipeline must successfully complete, and at least two reviewers must approve the changes. Additionally, the build pipeline should run automatically whenever a new commit is pushed to the feature branch associated with an active PR. Which combination of Azure DevOps branch policies and pipeline triggers should they configure?
Design and implement source control
A.Set up a build validation policy for all feature branches, require minimum 2 reviewers for 'main', and configure the build pipeline with a Scheduled trigger.
B.Require a successful build validation policy for 'main', use code review work items, and configure the build pipeline with a Manual trigger.
C.Require a successful build validation policy for 'main', require minimum 2 reviewers for 'main', and configure the build pipeline with a CI trigger on feature branches.
D.Require a successful build validation policy for 'main', require minimum 2 reviewers for 'main', and configure the build pipeline with a Pull Request trigger.
Show answerAnswer
D. Require a successful build validation policy for 'main', require minimum 2 reviewers for 'main', and configure the build pipeline with a Pull Request trigger.
To enforce a successful build and reviewer approvals before merging to 'main', branch policies are used. The 'Build validation' policy ensures a successful build, and 'Minimum number of reviewers' enforces approvals. To have the build run automatically on new commits in a PR, the build pipeline needs a Pull Request trigger, which starts a build when a PR is created or updated.
12. A company is implementing a new package management strategy using Azure Artifacts. They have a public upstream source (nuget.org) and also publish their own internal NuGet packages. They want to configure their feed to prioritize their internal packages over public packages when a package with the same name exists in both sources, and also ensure that all public packages are cached for faster access. Which configuration should they apply to their Azure Artifacts feed?
Design and implement source control
A.Use a single feed, adding nuget.org as an upstream source, and manually push all public packages to the feed.
B.Create two separate feeds: one for internal packages and one for cached public packages.
C.Set nuget.org as an upstream source with a view, and store internal packages in a separate feed.
D.Configure the feed to use 'Local packages first' behavior and add nuget.org as an upstream source.
Show answerAnswer
D. Configure the feed to use 'Local packages first' behavior and add nuget.org as an upstream source.
Configuring an Azure Artifacts feed with 'Local packages first' behavior ensures that packages published directly to the feed are prioritized over packages from upstream sources. Adding nuget.org as an upstream source allows public packages to be fetched and automatically cached when first requested, meeting both requirements.
13. A team is using Azure DevOps for their source control and build pipelines. They have several private NuGet feeds hosted in Azure Artifacts. Their build pipelines need to publish new NuGet packages to these private feeds and consume existing packages. To do this securely without hardcoding credentials, which type of Azure DevOps construct should be configured to allow the build pipeline to interact with Azure Artifacts feeds?
Design and implement source control
A.Service connection of type 'Azure DevOps Services'
B.Repository permissions
C.Variable group with feed URLs
D.Agent pool capabilities
Show answerAnswer
A. Service connection of type 'Azure DevOps Services'
A 'Service connection' of type 'Azure DevOps Services' is the correct construct. It allows a pipeline to securely authenticate and interact with other Azure DevOps resources within the same organization, including Azure Artifacts feeds, without exposing credentials.
14. A company is migrating its existing on-premises Subversion (SVN) repository to Git in Azure DevOps. The SVN repository has a long and complex history, including multiple branches and tags. The company requires a full-fidelity migration, preserving all commit history, author information, branch structures, and tag references. Which utility is best suited for this task?
Design and implement source control
A.Git-TFS utility
B.git-svn utility
C.Manual `git init` and `git remote add`
D.Azure DevOps Import Repository feature
Show answerAnswer
B. git-svn utility
The `git-svn` utility is a bidirectional bridge between a Subversion repository and Git. It is specifically designed to perform full-fidelity migrations from SVN to Git, preserving commit history, author information, branches, and tags, which aligns perfectly with the company's requirements.
15. An organization is moving from an on-premises build server to Azure DevOps build agents. They have several legacy applications that require specific, outdated compiler versions and custom command-line tools that are not available on Microsoft-hosted agents. Which type of build agent should they implement to support these legacy applications?
Design and implement source control
A.Microsoft-hosted agents with custom scripts
B.Self-hosted agents configured with required software
C.Containerized agents running on Azure Container Instances
D.Scale set agents within an Azure Virtual Machine Scale Set
Show answerAnswer
B. Self-hosted agents configured with required software
Self-hosted agents provide the flexibility to install any necessary software, tools, and dependencies, including specific compiler versions or custom command-line tools, directly onto the agent machine. This makes them ideal for building legacy applications with unique requirements.
16. A company is developing a machine learning application. Their build pipeline generates large model files (e.g., `.pkl`, `.h5`) that are too large to be stored efficiently in Git. These files are outputs of a training process and need to be versioned along with the code that generated them. The team wants to use Git for source control but needs a way to manage these large binary files without bloating the repository or degrading Git performance. Which solution should they implement?
Design and implement source control
A.Upload model files to Azure Blob Storage and store only URLs in Git.
B.Store model files directly in the Git repository and use shallow clones.
C.Exclude model files from Git using `.gitignore` and manage them separately.
D.Use Git Large File Storage (LFS) to track the large model files.
Show answerAnswer
D. Use Git Large File Storage (LFS) to track the large model files.
Git Large File Storage (LFS) is specifically designed to handle large binary files within a Git workflow. It replaces large files with small text pointers in Git, storing the actual file contents on a remote LFS server. This prevents repository bloat and maintains Git's performance while still allowing versioning of large files alongside code.
17. You are configuring an Azure DevOps build pipeline. This pipeline needs to securely access a private feed in Azure Artifacts to download internal NuGet packages. The pipeline runs on a Microsoft-hosted agent. You want to ensure that the pipeline uses the correct authentication without hardcoding credentials or using a personal access token (PAT) directly in the YAML. Which authentication mechanism is automatically available and recommended for this scenario?
Design and implement source control
A.Service principal authentication configured in a variable group.
B.User-managed personal access token (PAT) stored as a secure file.
C.OAuth token provided by the build service identity.
D.Basic authentication with username and password in pipeline variables.
Show answerAnswer
C. OAuth token provided by the build service identity.
Azure DevOps pipelines, by default, run under a 'Build Service' identity. This identity automatically receives an OAuth token that can be used to authenticate with other Azure DevOps services, including Azure Artifacts feeds within the same organization, without requiring explicit credential management in the pipeline YAML.
18. A team is developing a new application that uses a combination of public open-source NuGet packages and proprietary internal NuGet packages. They want to set up Azure Artifacts to manage these packages. They need to ensure that developers can consume both types of packages from a single feed, prioritizing internal packages when names conflict. Additionally, they want to automatically save any public packages consumed to their internal feed for reliability and auditing. Which Azure Artifacts configuration should they implement?
Design and implement source control
A.Create a single Azure Artifacts feed and use upstream sources to connect to NuGet.org, with the internal feed as the primary source.
B.Use a Universal Packages feed to store both types of packages, manually uploading public packages.
C.Set up two separate feeds, one for public and one for internal packages, and configure each project to use both.
D.Configure a Service Hook to copy public packages from NuGet.org to their internal feed whenever a new package is released.
Show answerAnswer
A. Create a single Azure Artifacts feed and use upstream sources to connect to NuGet.org, with the internal feed as the primary source.
Upstream sources in Azure Artifacts allow a single feed to consume packages from multiple sources (e.g., NuGet.org and other internal feeds). By configuring NuGet.org as an upstream source and setting the internal feed as the primary, it resolves conflicts in favor of internal packages. The 'save packages downloaded from upstream sources' feature automatically caches public packages, addressing reliability and auditing requirements.
19. A development team uses Azure DevOps for their source control and build pipelines. They maintain sensitive configuration values, such as API keys and database connection strings, that are required by their build and release pipelines. These values must be stored securely and be accessible to pipelines without being hardcoded in YAML files. The team also wants to manage these secrets centrally and integrate with Azure Key Vault for enhanced security. Which Azure DevOps feature should they use?
Design and implement source control
A.Pipeline variables
B.Service connections
C.Variable groups linked to Azure Key Vault
D.Secure files
Show answerAnswer
C. Variable groups linked to Azure Key Vault
Variable groups in Azure DevOps allow you to store values that can be shared across multiple pipelines. When linked to Azure Key Vault, these variable groups can securely retrieve secrets directly from Key Vault at runtime. This provides central, secure management of sensitive configuration values, preventing them from being hardcoded and leveraging Key Vault's security features.
20. A company uses Azure DevOps for its source control, build, and release pipelines. They have several build agents running on virtual machines in an on-premises data center. The IT department has a strict policy that requires all virtual machine operating systems to be patched and restarted monthly. This causes build agent downtime during patching. The development team wants to minimize this downtime and ensure that build capacity is always available, even during maintenance windows. Which type of build agent should they implement?
Design and implement source control
A.Self-hosted agents within an Azure Virtual Machine Scale Set
B.Self-hosted agents with a manual update process
C.Microsoft-hosted agents
D.Containerized self-hosted agents
Show answerAnswer
A. Self-hosted agents within an Azure Virtual Machine Scale Set
Self-hosted agents within an Azure Virtual Machine Scale Set (VMSS) provide elastic scaling and automatic agent lifecycle management. When VMs are patched or updated, new instances can be spun up automatically, ensuring continuous agent availability and minimizing downtime during maintenance. This directly addresses the need for continuous availability despite monthly patching.
21. A development team is using Azure DevOps for their source control and build pipelines. They have multiple build pipelines that share common steps, such as compiling code, running unit tests, and publishing artifacts. They want to ensure consistency and reusability of these common steps across all pipelines. Which Azure DevOps feature should they use to achieve this?
Design and implement source control
A.Deployment Groups
B.Task Groups
C.Service Connections
D.Variable Groups
Show answerAnswer
B. Task Groups
Task Groups allow you to encapsulate a sequence of tasks into a single reusable unit. This promotes consistency and reusability across multiple build or release pipelines.
22. A company is adopting a monorepo strategy for its microservices. Each microservice has its own folder within the single Git repository (e.g., /src/serviceA, /src/serviceB). They want to create a single Azure DevOps YAML pipeline that can build only the microservice whose code has changed in a given commit, rather than building all microservices every time. Which pipeline feature should they use to achieve this optimized build behavior?
Design and implement source control
A.Scheduled triggers for each microservice
B.Path filters in CI triggers
C.Conditional expressions in pipeline tasks
D.Multiple pipeline definitions, one per microservice
Show answerAnswer
B. Path filters in CI triggers
Path filters in Continuous Integration (CI) triggers allow a pipeline to be triggered only when changes occur in specific paths within the repository. By configuring a path filter for each microservice's directory, the pipeline can conditionally build only the affected microservice, optimizing build times in a monorepo.
23. A development team is migrating their existing on-premises Team Foundation Version Control (TFVC) repository to Azure DevOps Git. They have a large history with many branches and merges. The team wants to preserve all historical data, including branches, merges, and changesets, while ensuring a smooth transition with minimal disruption. Which migration strategy should they use?
Design and implement source control
A.Manually re-create all branches and commit history in a new Git repository.
B.Export the TFVC history to a flat Git repository without merge information.
C.Use the 'git-tfs' command-line tool to perform a full fidelity migration.
D.Utilize Azure DevOps' built-in 'Import repository' feature for TFVC without any pre-processing.
Show answerAnswer
C. Use the 'git-tfs' command-line tool to perform a full fidelity migration.
The 'git-tfs' tool is specifically designed for migrating TFVC repositories to Git while preserving full history, including branches, merges, and changesets, making it the most suitable option for a full fidelity migration.
24. A company is developing a machine learning application. The application's build process generates large model files (several GBs) that need to be packaged and made available for deployment. These model files are too large to be stored efficiently in Git and should not be part of the standard build artifacts. They need a robust way to store, version, and distribute these large files. Which Azure DevOps integrated solution should they use?
Design and implement source control
A.Azure Artifacts for Universal Packages
B.Azure Pipelines built-in artifact publishing
C.Azure Blob Storage directly
D.Git Large File Storage (LFS)
Show answerAnswer
A. Azure Artifacts for Universal Packages
Azure Artifacts Universal Packages are specifically designed for storing and versioning large, arbitrary files and packages (including machine learning models, installers, test data) that don't fit into traditional package types like NuGet or npm. They provide versioning, feed management, and integration with Azure DevOps pipelines for publishing and consuming.
25. A company is implementing a new package management strategy using Azure Artifacts. They have internal NuGet packages published to a private feed, and they also consume several public NuGet packages from nuget.org. Developers currently configure multiple package sources in their local NuGet.config files. The company wants to simplify this configuration and ensure that developers can resolve both internal and public packages from a single, unified feed without manually configuring each source. Which Azure Artifacts feature should they use?
Design and implement source control
A.Retention Policies
B.Views
C.Upstream Sources
D.Recycle Bin
Show answerAnswer
C. Upstream Sources
Upstream sources in Azure Artifacts allow you to consolidate multiple package feeds (both private and public) into a single feed. When a request comes for a package, the feed first checks its own packages, then queries its upstream sources in a defined order. This simplifies client configuration as developers only need to configure one feed.
A feature in Azure Pipelines that enables a single pipeline to checkout code from multiple Git repositories (within the same or different organizations) into the build agent's workspace.
Defined using `resources.repositories` in YAML.
Supports Git repositories from Azure Repos, GitHub, or other Git sources.
Each repository is checked out into a separate directory.
A feature in Azure DevOps release pipelines that pauses deployment to an environment and requires explicit approval from designated users or groups before proceeding.
Configured per environment in a release pipeline.
Supports multiple approvers and approval policies.
Can integrate with Azure AD groups for approver management.
A Git extension for versioning large files (binaries, audio, video, datasets) by storing pointers in the Git repository and the actual content on a remote LFS server.
Keeps Git repository size small and clone times fast.
Allows large files to be versioned alongside code.
Requires Git LFS client installation and configuration.
Upstream sources in Azure Artifacts allow a single feed to serve packages from multiple sources, with a default resolution order of local feed content first, then configured upstream sources.
Primary feed's packages are always resolved first.
Upstream sources are queried in the order they are listed if the package isn't found locally.
Caches packages from upstream sources for improved performance.
A mechanism in Azure DevOps to integrate with external services by sending notifications or payloads when specific events occur within Azure DevOps (e.g., code push, build completion, work item update).
Configured at the project level.
Supports various event types (code, build, work item, release).
Can send data to webhooks, Azure Functions, or other integrated services.
A feature in Azure DevOps YAML pipelines that allows a single pipeline to check out code from multiple Git repositories (both Azure Repos and external) into the agent's workspace.
Defined using `resources.repositories` in YAML.
Supports different repository types (Git, GitHub, Bitbucket).
Each repository is checked out into a specific directory.
A command-line tool that allows you to migrate a Team Foundation Version Control (TFVC) repository to Git, preserving the full commit history, branches, and merge relationships.
Enables full-fidelity TFVC to Git migration.
Handles complex branching and merging scenarios.
Requires installation on a machine with TFVC client installed.
Mechanisms in Azure DevOps pipelines that require certain conditions (manual approval, external system validation, etc.) to be met before a stage or job can start executing on a protected resource or environment.
Ensures compliance and quality gates.
Can integrate with external systems via REST APIs.
Applied to environments, service connections, agent pools, or variable groups.
Pull Request (PR) triggers in pipelines initiate builds when PRs are created or updated, while Branch Policies enforce conditions (e.g., successful build, reviewer approval) that must be met before a PR can be merged into a target branch.
PR triggers ensure builds run for every PR change.
Build validation policy prevents merging if the build fails.
Minimum reviewers policy enforces code review before merge.
Sources (e.g., nuget.org, npmjs.com, other Azure Artifacts feeds) that an Azure Artifacts feed can 'pull' packages from, automatically caching them upon first request.
Provides a single point of access for internal and external packages.
Automatically caches packages from upstream sources.
Supports different prioritization behaviors (e.g., 'Local packages first').
A secure way to connect Azure DevOps pipelines to external and internal services (like Azure Artifacts, Azure subscriptions, GitHub) without exposing sensitive credentials directly in pipeline definitions.
A Git command-line utility that provides a bidirectional gateway between a local Git repository and a remote Subversion repository, primarily used for migrating SVN history to Git.
Performs full-fidelity migration from SVN to Git.
Preserves commit history, author information, branches, and tags.
Build agents that you set up and manage on your own infrastructure (on-premises or cloud VMs), providing full control over the installed software and environment.
Provides full control over installed software and dependencies.
Required for specific hardware, custom tools, or outdated software not on Microsoft-hosted agents.
Requires manual management of agent updates and maintenance.
A built-in service identity (Project Collection Build Service / Project Build Service) that Azure DevOps pipelines run under, automatically providing an OAuth token for secure interaction with other Azure DevOps services.
Automatically generated for each project/organization.
Used for pipeline authentication to internal Azure DevOps resources.
Permissions can be managed like a regular user or group.
A feature in Azure DevOps that allows you to store reusable sets of variables and securely link them to secrets stored in Azure Key Vault, making them accessible to pipelines at runtime.
Centralized management of secrets and configuration values.
Secrets are retrieved from Key Vault at runtime, not stored in Azure DevOps.
Enhances security by leveraging Key Vault's access control and auditing.
Self-hosted agents deployed in an Azure Virtual Machine Scale Set, offering automatic scaling, lifecycle management, and high availability for build and release pipelines.
Automatically scales agent count based on demand.
VM instances can be automatically re-imaged or replaced.
Reduces administrative overhead for agent management.
A feature in Azure DevOps that allows encapsulating a sequence of tasks into a single reusable unit, promoting consistency and reusability across pipelines.
A configuration within a Continuous Integration (CI) trigger in Azure DevOps pipelines that specifies which file paths, when changed, should cause the pipeline to run.
Essential for optimizing builds in monorepos.
Prevents unnecessary builds of unaffected components.
The process of moving a Team Foundation Version Control (TFVC) repository to a Git repository while retaining all historical data, including branches, merges, and changesets.
Preserves complete history for auditing and context.
Often requires specialized tools like 'git-tfs'.
More complex than basic code migration but offers significant benefits.
A type of package in Azure Artifacts designed to store arbitrary files and folders, particularly useful for large assets like machine learning models, installers, or test datasets.
Supports large file sizes (up to 4TB).
Provides versioning and feed management.
Integrates with Azure DevOps pipelines for publishing and consuming.
A set of configurable rules in Azure DevOps Git repositories that enforce quality and workflow standards on branches, typically applied to pull requests before merging.
Enforce minimum number of reviewers.
Require successful build validation.
Integrate with external services for status checks (e.g., security scans).
Questions are original practice items written to match the published exam objectives. Step2Study is not affiliated with or endorsed by any certification body.