You save $69.98
AZ-400 Premium Bundle
- Premium File 398 Questions & Answers
- Last Update: Nov 11, 2026
- Training Course 27 Lectures
- Study Guide 784 Pages
You save $69.98
A regulated insurer audits GitHub commits while approval and defect evidence resides only in Azure Boards.
What is the most appropriate action for this DevOps team?
Connect Azure Boards with GitHub and associate pull requests and commits with the corresponding work items. The Boards-GitHub integration surfaces development activity against the planning record, supporting end-to-end traceability across services. A useful check is that an auditor opens a work item and sees the linked GitHub pull request, associated commits and status.
This is designed for Wiki and process diagrams: Version-controlled documentation can evolve through ordinary review and makes dependencies inspectable by engineers and operators.
That intervention fits GitHub Flow work visibility: Linking issues, pull requests, commits, checks, and releases gives stakeholders traceability without requiring a long-lived branch per ticket.
This is designed for Cross-team workflow handoffs: An explicit work-item flow gives each team a shared view of readiness and blocked dependencies rather than separate informal queues.
A distributed payments team merges tickets without linking pull requests, so product managers cannot follow fixes from work items to deployments.
Which risk most directly follows if the team leaves this problem unresolved?
An unlinked production change can bypass review or be impossible to associate with its original requirement. The failure follows from the described gap because linking issues, pull requests, commits, checks, and releases gives stakeholders traceability without requiring a long-lived branch per ticket. Mitigate it by choosing to establish GitHub Flow with short branches, reviewed pull requests, and explicit issue-to-commit and deployment links.
That is a credible failure of Azure Boards GitHub traceability: The Boards-GitHub integration surfaces development activity against the planning record, supporting end-to-end traceability across services. The present scenario instead leaves the github flow work visibility requirement unresolved, which creates this more direct risk: an unlinked production change can bypass review or be impossible to associate with its original requirement.
This risk is associated with Webhooks for event integration: Event subscriptions push relevant changes to a receiver; delivery validation and idempotency are necessary for dependable automation. The present scenario instead leaves the github flow work visibility requirement unresolved, which creates this more direct risk: an unlinked production change can bypass review or be impossible to associate with its original requirement.
That is a credible failure of Bug quality feedback loop: Tying operational feedback to original code and acceptance criteria exposes recurring failure patterns and supports process improvement. The present scenario instead leaves the github flow work visibility requirement unresolved, which creates this more direct risk: an unlinked production change can bypass review or be impossible to associate with its original requirement.
A Kubernetes delivery flow trusts an image tag without checking OS libraries or image provenance.
What is the most appropriate action for this DevOps team?
Scan container images and dependencies before promotion, enforce risk-based gates and retain image provenance. Container scanning examines packaged runtime components that may not appear in application source analysis. A useful check is that a deliberately vulnerable image is blocked and the promoted digest maps to an acceptable scan result.
That intervention fits Dependabot dependency alerts: Dependency scanning connects known advisories to manifest and lockfile versions and can propose reviewed updates.
This is designed for CodeQL static analysis: Static code analysis can trace risky code patterns and data flow without relying on runtime exploitation to surface the flaw.
This would instead address Service connection scope: Service connections are privileged deployment identities, so resource RBAC and use restrictions should match actual blast radius.
A regulated service needs recent rollback packages and audit evidence but cannot retain all build logs forever.
Which observation most directly confirms the required DevOps control is effective?
Required release artifacts remain accessible through the mandated window and expired temporary objects are purged. This shows that the control was implemented as intended: apply lifecycle-based retention for artifacts and dependencies consistent with rollback and compliance needs. It matters because retention should balance recovery evidence, cost and governance rather than indiscriminately retaining or deleting every build.
That result would verify Feature flag dark launch, where the relevant control is use a controlled feature flag with scoped audience targeting and an audited kill switch.
This observation would support Agent cost management, where the relevant control is right-size agent pools and job concurrency using observed utilization, queue duration and workload demand.
Such evidence would establish Migrate classic to YAML, where the relevant control is inventory existing classic tasks and resource checks, migrate logic into versioned YAML and validate parity in parallel.
A deploy stage automatically reruns every failed script, including a non-idempotent database migration that can duplicate updates.
Which explanation best supports the needed implementation decision?
Retries are reliable only when repeated execution has a defined effect and partial failures are detectable. The appropriate response is to retry only safe idempotent operations and use checkpoints and explicit recovery for state-changing steps. The expected evidence is that a failed stage resumes or rolls back without duplicate schema changes or conflicting infrastructure resources.
This reasoning pertains to Build cache with correctness: Correct cache keys improve speed while preventing incompatible or stale cached outputs from silently changing builds.
This describes the mechanism for Test agent network isolation: An agent placed on an approved reachable network can exercise private services without exposing those services publicly.
This reasoning pertains to Agent cost management: Pool sizing is a tradeoff between capacity, execution delay and infrastructure or licensing cost.
An enterprise rolls out an agent to thousands of branches and wants to learn from low-risk cohorts first.
Which observation most directly confirms the required DevOps control is effective?
The pilot ring meets stability targets before subsequent rings receive the signed update. This shows that the control was implemented as intended: implement a ring-based rollout with ordered cohorts, monitoring and explicit promotion criteria. It matters because rings separate user populations for controlled exposure and detect population-specific problems before broad deployment.
This observation would support Unit tests fast feedback, where the relevant control is run fast deterministic unit tests early in CI and fail the build before slower stages on regressions.
Such evidence would establish Canary progressive exposure, where the relevant control is use a canary deployment with gradually increased traffic and health-based rollback thresholds.
This observation would support Database expand-contract migration, where the relevant control is use backward-compatible expand-and-contract schema changes before removing old fields.
A startup stores application code in GitHub and wants a native workflow for pull-request tests and container publishing.
Which explanation best supports the needed implementation decision?
Both GitHub Actions and Azure Pipelines can automate CI/CD, but repository integration and governance capabilities determine the appropriate fit. The appropriate response is to select the pipeline platform that integrates with repository hosting, required approvals and deployment environments. The expected evidence is that a pilot triggers from the intended repository, enforces approvals and deploys to the target environment with auditable identities.
This describes the mechanism for Extends security template: An extends template can constrain allowed pipeline steps, while checks on protected resources prevent easy removal of the requirement.
This reasoning pertains to Container image digest promotion: Image digests identify exact content, preserving supply-chain consistency across environments despite tag changes.
That explanation is about Trigger branch and path filters: Trigger rules map source changes to relevant pipelines and reduce unnecessary executions without weakening critical release checks.
A build needs a licensed proprietary compiler absent from Microsoft-hosted images and requires durable tool caching.
Which risk most directly follows if the team leaves this problem unresolved?
An unmanaged runner can become an unpatched privileged foothold or repeatedly fail for missing tools. The failure follows from the described gap because custom execution environments support private dependencies while making the organization responsible for patching, isolation and capacity. Mitigate it by choosing to provision managed self-hosted runners or agents with required toolchains, networking and hardened lifecycle controls.
This risk is associated with Reusable YAML template: Includes and parameterized templates centralize repeatable pipeline logic while keeping service-specific inputs explicit. The present scenario instead leaves the hosted versus self-hosted agents requirement unresolved, which creates this more direct risk: an unmanaged runner can become an unpatched privileged foothold or repeatedly fail for missing tools.
That consequence is characteristic of Cross-repository pipeline checkout: Explicit repository resources make multi-repository dependencies reproducible and subject to service-connection and permission checks. The present scenario instead leaves the hosted versus self-hosted agents requirement unresolved, which creates this more direct risk: an unmanaged runner can become an unpatched privileged foothold or repeatedly fail for missing tools.
That is a credible failure of Deployment scopes: Azure Resource Manager scopes determine where resources and policy assignments can be created, independently of template language. The present scenario instead leaves the hosted versus self-hosted agents requirement unresolved, which creates this more direct risk: an unmanaged runner can become an unpatched privileged foothold or repeatedly fail for missing tools.
A monorepo's infrastructure directory changes should run a provisioning pipeline but currently run every application test suite.
What is the most appropriate action for this DevOps team?
Set precise branch and path trigger filters, retaining broad protected-branch verification where needed. Trigger rules map source changes to relevant pipelines and reduce unnecessary executions without weakening critical release checks. A useful check is that representative commits run only expected pipelines and a security-sensitive main-branch change still executes its required gate.
That intervention fits Cross-repository pipeline checkout: Explicit repository resources make multi-repository dependencies reproducible and subject to service-connection and permission checks.
This would instead address Semantic versioning: SemVer communicates compatibility intent by distinguishing major breaks, compatible additions and backward-compatible fixes.
That intervention fits Hosted versus self-hosted agents: Custom execution environments support private dependencies while making the organization responsible for patching, isolation and capacity.
A pipeline maintains one broad credential for staging, production and audit systems with no rotation procedure.
Which explanation best supports the needed implementation decision?
Scoped identities and rehearsed rotation reduce the security impact and operational disruption of credential compromise. The appropriate response is to separate credentials by environment and purpose, use short lifetimes or federation, and test rotation and revocation. The expected evidence is that an old identity is revoked successfully while each pipeline continues using only its own authorized environment credentials.
This describes the mechanism for Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.
This reasoning pertains to Azure Pipelines secure files: Secure files are protected pipeline resources with permissions and checks, unlike publicly retrievable general artifacts.
This describes the mechanism for Key Vault runtime secret retrieval: A dedicated secret store provides access control, rotation and auditing while preventing credentials from becoming ordinary source artifacts.
A repository administrator grants all automation identities write access to every project for convenience.
Which risk most directly follows if the team leaves this problem unresolved?
A compromised low-trust account could change production code or repository governance. The failure follows from the described gap because least-privilege repository authorization minimizes the impact of a compromised user or automation token. Mitigate it by choosing to assign repository permissions by task and restrict branch write operations to approved roles and workflows.
That is a credible failure of Merge policy stale approval: Approvals should cover the final content actually merged, rather than an earlier snapshot of the branch. The present scenario instead leaves the repository least privilege requirement unresolved, which creates this more direct risk: a compromised low-trust account could change production code or repository governance.
This risk is associated with Recover one commit safely: Revert preserves the published commit graph while negating the selected change through a new auditable commit. The present scenario instead leaves the repository least privilege requirement unresolved, which creates this more direct risk: a compromised low-trust account could change production code or repository governance.
That consequence is characteristic of Git LFS for binaries: Git LFS replaces eligible large file content in history with lightweight pointers and manages binary content separately. The present scenario instead leaves the repository least privilege requirement unresolved, which creates this more direct risk: a compromised low-trust account could change production code or repository governance.
or Guarantee your success by buying the full version which covers the full latest pool of questions. (398 Questions, Last Updated on Nov 11, 2026)
Please check your mailbox for a message from support@examlabs.com and follow the directions.