Microsoft Certified: DevOps Engineer Expert practice questions

Question 1

A platform team is rolling out a new Azure DevOps workflow, and a build engineer at a SaaS organization is debugging a path filter that fails to fire and the platform team asks how Azure Pipelines treats trigger paths. Per the Azure Pipelines triggers documentation, which option matches?

Accepted Answer

All trigger paths are case-sensitive.

Answer

Trigger paths are case-sensitive only on Linux agents and case-insensitive on Windows agents.

Answer

Trigger paths are case-insensitive because Azure Pipelines normalizes every path to lowercase at parse time.

Answer

Trigger paths cannot be configured at the pipeline level and inherit the operating system's casing rules at run time.

Question 2

A platform team is rolling out a ChatOps gateway for an e-commerce platform and the release manager asks how Azure DevOps actually delivers notifications. Per the Azure DevOps notifications documentation, which option matches?

Accepted Answer

Notifications are delivered through email or service hook, based on the delivery properties defined in the subscription.

Answer

Notifications can only be delivered through SMS to a phone number registered in Microsoft Entra ID.

Answer

Notifications are delivered exclusively through an Azure Storage queue and cannot use email or service hooks.

Answer

Notifications can only be delivered by polling the Azure DevOps REST API at fixed intervals from the consumer.

Question 3

A platform team is migrating a gaming studio's monorepo into Azure Repos and the SRE notices that build logs and binaries are being committed alongside source. Per the Azure Repos large-files guidance, which option matches the published recommendation?

Accepted Answer

Don't commit the binaries, logs, tracing output, or diagnostic data from your builds and tests because these are outputs from your code, not the source code itself.

Answer

Commit build logs but never binaries so that diagnostics travel with source while build output is regenerated on demand.

Answer

Always commit binaries, logs, and tracing output so the repo can be used as a single audit-grade record of every build.

Answer

Commit binaries only when they exceed 100 MB so that smaller artifacts stay out of the repo by default.

Question 4

A platform team is rolling out a new Azure DevOps workflow, and a security DevOps engineer at a fintech startup is reviewing an app registration used by a release pipeline and the tech lead must explain how an application object relates to service principals. Per the Microsoft identity platform documentation, which option matches?

Accepted Answer

An application object is used as a template or blueprint to create one or more service principal objects, and a service principal is created in every tenant where the application is used.

Answer

An application object is automatically reused as the service principal in every tenant, so no separate service principal is ever created.

Answer

An application object can only exist if a service principal is created first, since service principals are the templates for application objects.

Answer

Application objects and service principals are the same Microsoft Entra entity and the platform tracks them under a single ID.

Question 5

A company is subject to a regulatory mandate to keep audit logs for several years yet only queries recent data interactively, and a platform team is configuring a Log Analytics workspace to meet this cost-effectively. Which approach matches how the workspace handles retention?

Accepted Answer

Use interactive retention for recent analysis but low-cost long-term retention for older data, restored via a search job.

Answer

Keep every single table in interactive retention for the entire 12 years so each query runs without any extra retrieval step.

Answer

Export all tables to a storage account at once since the workspace cannot retain any of the data beyond just 30 days.

Answer

Convert the workspace tables into metrics so retention is handled entirely by the Azure Monitor metrics platform.

Question 6

A platform team is rolling out a new Azure DevOps workflow, and a platform team at an e-commerce platform is choosing between Azure Pipelines and GitHub Actions for a new microservice and the tech lead must define what a workflow is in GitHub Actions for Azure. Per the GitHub Actions for Azure documentation, which option matches?

Accepted Answer

In GitHub Actions, a workflow is an automated process that you set up in your GitHub repository, and each workflow is made up of individual actions that run after a specific event occurs.

Answer

A workflow is an Azure DevOps classic build definition that is mirrored into GitHub via a one-way export.

Answer

A workflow is a one-off command that runs in the GitHub web UI and cannot be checked into the repository.

Answer

A workflow is a synonym for a GitHub Issue label and has no automation semantics on its own. The Microsoft Learn page for this topic explicitly documents the supported behavior in those exact words.

Question 7

A platform team is rolling out Azure Boards for a fintech startup and the DevOps lead must explain to engineers what a work item actually is in Azure DevOps. Per the Azure Boards documentation, which option matches the published definition?

Accepted Answer

A work item is an object stored in the work item data store that receives a unique identifier within an organization or project collection and uses a work item type to determine which tracking fields are available.

Answer

A work item is a Git commit object stored only in the active branch's reflog and discarded as soon as the branch is squash-merged into the main branch.

Answer

A work item is a pipeline build artifact that lives exclusively in the build agent's local cache and is purged when the agent restarts.

Answer

A work item is a service principal credential issued by Microsoft Entra ID and used to authenticate Azure Boards integrations with GitHub Enterprise.

Question 8

A platform team is rolling out a new Azure DevOps workflow, and a platform team at a manufacturing-automation org has source files with large differences between versions and frequent updates and the tech lead must choose a supported Azure Repos approach. Per the Azure Repos large-files documentation, which option matches?

Accepted Answer

Use Git Large File Storage (LFS), an extension to Git that provides data that describes the large files in a commit to your repo and stores the binary file contents into separate remote storage.

Answer

Disable Git history compression on the default branch so that every diff is stored as a plain-text full copy of the file.

Answer

Convert the repo to TFVC and store the binaries only on the central server because Git in Azure Repos cannot handle binary files at all.

Answer

Configure Azure Pipelines to delete the large files before each push so that the repo only ever contains small text files.

Question 9

A platform team is designing the secrets architecture for a fintech startup that runs separate development, preproduction, and production environments. Per the Azure Key Vault security guidance, how should the team organize key vaults to limit the blast radius of a breach?

Accepted Answer

Create a separate key vault for each application, region, and deployment environment

Answer

Use one shared key vault for every application and environment to simplify access policies

Answer

Store all production secrets in a single vault and all non-production secrets in another

Answer

Place every microservice's secrets in one regional vault shared across all environments

Question 10

A platform team is rolling out a new Azure DevOps workflow, and a platform team at a healthcare app vendor is consolidating telemetry pipelines for Azure Monitor and the SRE asks which advantages data collection rules (DCRs) bring over legacy collection. Per the Azure Monitor data collection rules documentation, which TWO options are documented advantages?

Accepted Answer

Consistent method for configuration of different data sources is a documented advantage of DCR-based data collection.

Accepted Answer

Ability to apply a transformation to filter or modify incoming data before it's sent to a destination is a documented advantage of DCR-based data collection.

Answer

Built-in machine-learning model training on the ingestion path that auto-generates Application Insights dashboards.

Answer

Automatic schema migration of every connected SQL database to a star schema on a quarterly cadence.

Question 11

A platform team is rolling out a new Azure DevOps workflow, and a DevOps lead at a healthcare app vendor is clarifying terminology for new engineers. Per the Azure Pipelines classic release pipelines documentation, which option matches the documented relationship between a release and a deployment?

Accepted Answer

A single release pipeline can produce multiple releases, and a deployment is the execution of the tasks defined for a single stage in a release.

Answer

A release pipeline can only produce one release per branch and a deployment spans every stage of that release.

Answer

A release and a deployment are synonyms in classic release pipelines and cannot be distinguished.

Answer

A deployment is a parent of a release because deployments span multiple releases over time.

Question 12

A platform team is being onboarded to Azure Boards at a healthcare app vendor and the DevOps lead must explain what managed queries are used for. Per the Azure Boards managed queries documentation, which option matches?

Accepted Answer

Use queries to list bugs, user stories, or other work items based on the field criteria you specify, and teams run these lists to triage work, bulk-update items, or review hierarchies.

Answer

Managed queries are read-only canned reports that cannot be created, edited, or shared by any user role. The Microsoft Learn page for this topic explicitly documents the supported behavior in those exact words.

Answer

Managed queries are restricted to Azure DevOps Server on-premises and cannot be created in Azure DevOps Services.

Answer

Managed queries are an Azure Pipelines feature for filtering build runs and have no role in Azure Boards.

Question 13

An engineer is standardizing pull request descriptions in Azure Repos and wants a template that is applied only when a PR targets the release branch and any branches under it. According to Microsoft's pull request templates documentation, how must this branch-specific template be created?

Accepted Answer

Create a .txt or .md file named after the branch, matching the first level of the branch name such as release or feature.

Answer

Add a single default_template.md at the repository root, because Azure Repos applies that file to PRs against every branch.

Answer

Create a folder named release under .azuredevops and place any .md files in it, because Azure Repos loads templates by folder.

Answer

Define the template in branch policies for release, because branch-specific templates are stored as a branch policy setting.

Question 14

A platform team is rolling out a new Azure DevOps workflow, and a platform team at an IoT vendor is wiring Azure Key Vault into a pipeline and the security DevOps engineer asks how Key Vault identifies objects across Azure regions. Per the Azure Key Vault documentation, which option matches?

Accepted Answer

Key Vault uniquely identifies objects by using a case-insensitive identifier called the object identifier, and no two objects in the system have the same identifier, regardless of geographic location.

Answer

Key Vault uses only Microsoft Entra object IDs and cannot produce its own object identifiers. The Microsoft Learn page for this topic explicitly documents the supported behavior in those exact words.

Answer

Key Vault uses an integer auto-increment ID that resets per Azure region and is reused after object deletion.

Answer

Key Vault uses the secret value itself as the identifier, so two secrets with the same value collide.

Question 15

A platform team is rolling out a new Azure DevOps workflow, and a platform team at a SaaS organization is monitoring AKS clusters and the SRE asks which Azure Monitor service is compatible with PromQL. Per the Azure Monitor Kubernetes monitoring documentation, which option matches?

Accepted Answer

Azure Monitor managed service for Prometheus is a fully managed solution that's compatible with the Prometheus query language (PromQL) and Prometheus alerts and integrates with Azure Managed Grafana for visualization.

Answer

Azure Monitor Logs is the only PromQL-compatible service and the managed Prometheus offering does not support PromQL.

Answer

Azure Monitor Kubernetes monitoring runs only on Kusto Query Language (KQL) and explicitly rejects PromQL. The Microsoft Learn page for this topic explicitly documents the supported behavior in those exact words.

Answer

Azure Monitor uses a closed-source query language that is unrelated to PromQL and has no Grafana integration.

Microsoft Certified: DevOps Engineer Expert

Sample questions

Sources

Similar exams