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
An operator cannot prove which source commit created the artifact deployed last month.
Which explanation best supports the needed implementation decision?
A release tag marks an intended commit, while signing and tag protection add evidence against unauthorized retargeting. The appropriate response is to create protected annotated or signed release tags linked to immutable build and artifact identifiers. The expected evidence is that a deployed package maps to an approved release tag and its precise source commit.
That explanation is about Required status checks: Server-enforced branch rules validate executable evidence before integration, independent of informal reviewer assurances.
This describes the mechanism for Repository least privilege: Least-privilege repository authorization minimizes the impact of a compromised user or automation token.
This reasoning pertains to Git LFS for binaries: Git LFS replaces eligible large file content in history with lightweight pointers and manages binary content separately.
A checkout API returns sporadic HTTP 500 errors but the team has only server heartbeat checks and no failed-request details.
What is the most appropriate action for this DevOps team?
Instrument the application with Application Insights request, dependency, exception and correlation telemetry. Application-level instrumentation exposes call outcomes and dependency contributions that basic host availability cannot explain. A useful check is that failed requests link to exceptions and dependencies with consistent operation correlation.
This would instead address Correlated distributed traces: Trace correlation connects related requests and dependencies across service boundaries to reveal end-to-end latency contributors.
That intervention fits Azure Pipelines run monitoring: CI observability complements application monitoring by identifying delivery-system availability and throughput issues.
This is designed for GitHub Actions workflow alert: Build failure signals have value only if owners receive timely actionable notifications rather than relying on manual inspection.
A nightly integration workflow has failed for three days, but the development team reviews run status only on Fridays.
Which explanation best supports the needed implementation decision?
Build failure signals have value only if owners receive timely actionable notifications rather than relying on manual inspection. The appropriate response is to configure workflow failure alerts and route them to the responsible operational channel with a run link. The expected evidence is that a simulated failed run generates one useful alert with repository, workflow and failure links.
This reasoning pertains to Azure Pipelines run monitoring: CI observability complements application monitoring by identifying delivery-system availability and throughput issues.
This describes the mechanism for Correlated distributed traces: Trace correlation connects related requests and dependencies across service boundaries to reveal end-to-end latency contributors.
This reasoning pertains to Azure Monitor diagnostic collection: Azure Monitor unifies service-specific telemetry needed to distinguish infrastructure faults from application and container behavior.
A developer accidentally merged a bad change to a shared branch used by many peers and wants a safe undo.
What is the most appropriate action for this DevOps team?
Use git revert to create a compensating commit on shared history rather than forcibly resetting the published branch. Revert preserves the published commit graph while negating the selected change through a new auditable commit. A useful check is that the reversal is visible in shared history and other collaborators can pull it without forced history reconciliation.
That intervention fits Git LFS for binaries: Git LFS replaces eligible large file content in history with lightweight pointers and manages binary content separately.
This is designed for Repository least privilege: Least-privilege repository authorization minimizes the impact of a compromised user or automation token.
That intervention fits Feature branching with reviews: Branch protection enables isolated contribution while enforcing a consistent integration gate before accepted code reaches the default branch.
An external consultant has Project Administrator access although they only need to view sprint status in Azure Boards.
What is the most appropriate action for this DevOps team?
Assign appropriate Azure DevOps access levels and group roles according to actual work responsibilities. Access levels govern available features while permissions and security groups govern allowed actions; both matter for least privilege. A useful check is that the consultant performs the approved board review but cannot edit build service connections or project security.
This is designed for Secret scanning in pull requests: Secret scanning detects known credential patterns before promotion and alerts owners to rotate any exposed credential.
This would instead address Managed identity versus service principal: Azure-managed workload identities authenticate Azure resources without an application-managed secret, with access granted through role assignments.
That intervention fits Workload identity federation: OIDC-based federation exchanges trusted workflow identity assertions for short-lived cloud access, reducing static credential exposure.
A third-party quality vendor can push directly to protected production branches even though it only needs to report issues.
Which explanation best supports the needed implementation decision?
Least-privilege repository authorization minimizes the impact of a compromised user or automation token. The appropriate response is to assign repository permissions by task and restrict branch write operations to approved roles and workflows. The expected evidence is that permission tests confirm the vendor can create required reports but cannot modify protected source or settings.
That explanation is about Feature branching with reviews: Branch protection enables isolated contribution while enforcing a consistent integration gate before accepted code reaches the default branch.
This describes the mechanism for Signed annotated release tags: A release tag marks an intended commit, while signing and tag protection add evidence against unauthorized retargeting.
This reasoning pertains to Remove leaked credential from Git: Deleting a current file does not remove earlier Git objects or copies; invalidating the credential is the immediate security control.
Two teams plan in Azure Boards and develop in GitHub, but a released bug fix has no connection to its Azure work item.
Which observation most directly confirms the required DevOps control is effective?
An auditor opens a work item and sees the linked GitHub pull request, associated commits and status. This shows that the control was implemented as intended: connect Azure Boards with GitHub and associate pull requests and commits with the corresponding work items. It matters because the Boards-GitHub integration surfaces development activity against the planning record, supporting end-to-end traceability across services.
This observation would support Bug quality feedback loop, where the relevant control is define a feedback loop that links production defects to work items, root-cause labels, tests and retrospective improvements.
That result would verify GitHub Flow work visibility, where the relevant control is establish GitHub Flow with short branches, reviewed pull requests, and explicit issue-to-commit and deployment links.
This observation would support Lead time versus cycle time, where the relevant control is use lead time and cycle time with clearly defined start and end timestamps to locate delivery delays.
A SaaS service sees identical defects re-opened after releases, while sprint metrics treat them as unrelated new tickets.
Which explanation best supports the needed implementation decision?
Tying operational feedback to original code and acceptance criteria exposes recurring failure patterns and supports process improvement. The appropriate response is to define a feedback loop that links production defects to work items, root-cause labels, tests and retrospective improvements. The expected evidence is that repeated defects lead to updated regression tests and documented follow-up changes visible from their work items.
This describes the mechanism for GitHub Flow work visibility: Linking issues, pull requests, commits, checks, and releases gives stakeholders traceability without requiring a long-lived branch per ticket.
This reasoning pertains to Azure Boards GitHub traceability: The Boards-GitHub integration surfaces development activity against the planning record, supporting end-to-end traceability across services.
This describes the mechanism for Versioned release notes: Releasing documented change history helps consumers and support understand compatible features, fixes and known constraints.
A payments application receives releases from multiple branches and needs only one production deployment to hold the environment lock.
Which observation most directly confirms the required DevOps control is effective?
Only one deployment holds the protected environment at a time and later runs follow the agreed queue policy. This shows that the control was implemented as intended: configure an exclusive environment lock or equivalent serialized deployment control. It matters because serialization prevents conflicting writes to the same mutable production target while allowing independent builds elsewhere.
That result would verify Artifacts retention policy, where the relevant control is apply lifecycle-based retention for artifacts and dependencies consistent with rollback and compliance needs.
This observation would support Date-based versioning, where the relevant control is use a documented CalVer scheme for chronological releases while separately tracking backward-compatibility obligations.
Such evidence would establish Agent image maintenance, where the relevant control is manage versioned hardened runner images with patch schedules and automated smoke validation.
A medical application team needs a security hotfix on the deployed version but the main branch contains unready features.
What is the most appropriate action for this DevOps team?
Maintain a controlled release branch for the supported version and cherry-pick reviewed fixes as appropriate. Release branches isolate stabilization and patching from ongoing development while still retaining traceable changes. A useful check is that the supported release receives only its approved hotfix and the change is reconciled with ongoing development.
This is designed for Feature branching with reviews: Branch protection enables isolated contribution while enforcing a consistent integration gate before accepted code reaches the default branch.
This would instead address Signed annotated release tags: A release tag marks an intended commit, while signing and tag protection add evidence against unauthorized retargeting.
That intervention fits Required status checks: Server-enforced branch rules validate executable evidence before integration, independent of informal reviewer assurances.
A design repository grows rapidly because every large media binary version is stored as a regular Git object.
Which risk most directly follows if the team leaves this problem unresolved?
Repository history becomes increasingly expensive to clone and unsuitable for normal source-control workflows. The failure follows from the described gap because git LFS replaces eligible large file content in history with lightweight pointers and manages binary content separately. Mitigate it by choosing to use Git LFS for large binaries with explicit patterns while leaving source code in ordinary Git storage.
That consequence is characteristic of Repository least privilege: Least-privilege repository authorization minimizes the impact of a compromised user or automation token. The present scenario instead leaves the git lfs for binaries requirement unresolved, which creates this more direct risk: repository history becomes increasingly expensive to clone and unsuitable for normal source-control workflows.
This risk is associated with Required status checks: Server-enforced branch rules validate executable evidence before integration, independent of informal reviewer assurances. The present scenario instead leaves the git lfs for binaries requirement unresolved, which creates this more direct risk: repository history becomes increasingly expensive to clone and unsuitable for normal source-control workflows.
That consequence is characteristic of Remove leaked credential from Git: Deleting a current file does not remove earlier Git objects or copies; invalidating the credential is the immediate security control. The present scenario instead leaves the git lfs for binaries requirement unresolved, which creates this more direct risk: repository history becomes increasingly expensive to clone and unsuitable for normal source-control workflows.
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.