Microsoft AZ-400 Practice Test 25

Question 240

An engineer pushes a private key to a shared fork, then assumes a force-push alone eliminates copies held by collaborators. Choose TWO measures that implement and verify an effective Azure DevOps response to this specific situation. (Choose TWO.)

Revoke and rotate exposed credentials, assess distribution, and use controlled history remediation where warranted.
Confirm credential revocation, search reachable refs and forks, and verify no operational workflow still depends on the leaked key.
Declare removing committed secrets from git and rotating credentials successful solely from a green pipeline status and skip checking its actual control outcome.
Bypass review and testing for removing committed secrets from git and rotating credentials whenever the release deadline is urgent, applying the change to production immediately.
Dismiss the known risk for removing committed secrets from git and rotating credentials and keep no evidence or accountable owner after deployment.

Explanation

Correct Answers

A:

Revoke and rotate exposed credentials, assess distribution, and use controlled history remediation where warranted. Removing a secret from current source does not invalidate leaked credentials or guarantee prior copies disappeared. A leaked credential can remain exploitable after superficial cleanup of the latest branch contents.

B:

Confirm credential revocation, search reachable refs and forks, and verify no operational workflow still depends on the leaked key. Removing a secret from current source does not invalidate leaked credentials or guarantee prior copies disappeared.

Incorrect Answers

C:

Declare removing committed secrets from git and rotating credentials successful solely from a green pipeline status and skip checking its actual control outcome. It conflicts with the stated operating condition: Removing a secret from current source does not invalidate leaked credentials or guarantee prior copies disappeared.

D:

Bypass review and testing for removing committed secrets from git and rotating credentials whenever the release deadline is urgent, applying the change to production immediately. It conflicts with the stated operating condition: Removing a secret from current source does not invalidate leaked credentials or guarantee prior copies disappeared.

E:

Dismiss the known risk for removing committed secrets from git and rotating credentials and keep no evidence or accountable owner after deployment. It conflicts with the stated operating condition: Removing a secret from current source does not invalidate leaked credentials or guarantee prior copies disappeared.

Question 241

A .NET team exposes every package build to production consumers before dependency security testing finishes. Which solution should be prioritized to resolve the stated failure?

Separate internal and public feed priorities, protect namespaces, and enforce provenance for dependent packages.
Publish uniquely identified pipeline artifacts and reuse the same tested run output across all environments.
Configure upstream sources and caching policies that preserve authenticated provenance and pinned dependency versions.
Publish artifacts to controlled Azure Artifacts feeds and promote verified package versions through appropriate feed views.

Explanation

Correct Answer

D:

Publish artifacts to controlled Azure Artifacts feeds and promote verified package versions through appropriate feed views. Feed views and package versions distinguish validated consumable assets from untested build outputs. Unreviewed dependencies can be consumed by production services despite passing their own source-control checks.

Incorrect Answers

A:

Separate internal and public feed priorities, protect namespaces, and enforce provenance for dependent packages.

B:

Publish uniquely identified pipeline artifacts and reuse the same tested run output across all environments.

C:

Configure upstream sources and caching policies that preserve authenticated provenance and pinned dependency versions.

Question 242

A .NET team exposes every package build to production consumers before dependency security testing finishes. Which evidence would BEST demonstrate that the fix operates as intended?

Resolve a package using production feed permissions and verify only the reviewed immutable version is available.
Recreate a clean agent restore and verify package URL, publisher, hash, and expected feed resolution.
Rebuild a recorded release against the approved feed and compare exact package versions and checksums.
Use contract tests across dependent applications and compare package API changes with approved version increments.

Explanation

Correct Answer

A:

Resolve a package using production feed permissions and verify only the reviewed immutable version is available. Feed views and package versions distinguish validated consumable assets from untested build outputs.

Incorrect Answers

B:

Recreate a clean agent restore and verify package URL, publisher, hash, and expected feed resolution.

C:

Rebuild a recorded release against the approved feed and compare exact package versions and checksums.

D:

Use contract tests across dependent applications and compare package API changes with approved version increments.

Question 243

A .NET team exposes every package build to production consumers before dependency security testing finishes. Which design distinction is MOST relevant in these conditions?

Dependency-resolution order and namespace trust can allow an external package to impersonate a private library.
Package registries need separately managed publish and consume permissions, not blanket source repository ownership.
An upstream cache improves availability only if package identity and namespace trust remain consistent.
Feed views and package versions distinguish validated consumable assets from untested build outputs.

Explanation

Correct Answer

D:

Feed views and package versions distinguish validated consumable assets from untested build outputs. Unreviewed dependencies can be consumed by production services despite passing their own source-control checks.

Incorrect Answers

A:

Dependency-resolution order and namespace trust can allow an external package to impersonate a private library.

B:

Package registries need separately managed publish and consume permissions, not blanket source repository ownership.

C:

An upstream cache improves availability only if package identity and namespace trust remain consistent.

Question 244

A .NET team exposes every package build to production consumers before dependency security testing finishes. Which ongoing guardrail would BEST prevent this problem from recurring?

Audit upstream-source changes and implement dependency lock files and package provenance checks.
Require changelog review and compatibility validation before publishing shared package versions.
Review workflow permission scopes and package visibility after repository transfers or organization changes.
Require package promotion approvals and restrict feed publish and view management permissions.

Explanation

Correct Answer

D:

Require package promotion approvals and restrict feed publish and view management permissions. Unreviewed dependencies can be consumed by production services despite passing their own source-control checks.

Incorrect Answers

A:

Audit upstream-source changes and implement dependency lock files and package provenance checks.

B:

Require changelog review and compatibility validation before publishing shared package versions.

C:

Review workflow permission scopes and package visibility after repository transfers or organization changes.

Question 245

A .NET team exposes every package build to production consumers before dependency security testing finishes. Which risk is directly created by the described failure?

Production may contain software not covered by earlier quality and security gates.
Excessive package credentials may permit supply-chain tampering or leak proprietary dependencies to unrelated teams.
Unreviewed dependencies can be consumed by production services despite passing their own source-control checks.
Consumers may silently adopt breaking updates and experience preventable production failures.

Explanation

Correct Answer

C:

Unreviewed dependencies can be consumed by production services despite passing their own source-control checks. This is the directly relevant business or security consequence of azure artifacts feed views for verified package promotion. Root cause: Feed views and package versions distinguish validated consumable assets from untested build outputs.

Incorrect Answers

A:

Production may contain software not covered by earlier quality and security gates. That risk is relevant to pipeline artifact identity and cross-stage immutability, but the specific unresolved condition here concerns azure artifacts feed views for verified package promotion and has a different direct consequence.

B:

Excessive package credentials may permit supply-chain tampering or leak proprietary dependencies to unrelated teams. That risk is relevant to github packages access using least-privilege workflow credentials, but the specific unresolved condition here concerns azure artifacts feed views for verified package promotion and has a different direct consequence.

D:

Consumers may silently adopt breaking updates and experience preventable production failures. That risk is relevant to semantic versioning for shared api contract packages, but the specific unresolved condition here concerns azure artifacts feed views for verified package promotion and has a different direct consequence.

Question 246

A release consumes a prerelease NuGet library from the default feed even though only packages approved by QA may be deployed. Which implementation BEST addresses the operational issue?

Publish uniquely identified pipeline artifacts and reuse the same tested run output across all environments.
Publish artifacts to controlled Azure Artifacts feeds and promote verified package versions through appropriate feed views.
Configure upstream sources and caching policies that preserve authenticated provenance and pinned dependency versions.
Separate internal and public feed priorities, protect namespaces, and enforce provenance for dependent packages.

Explanation

Correct Answer

B:

Publish artifacts to controlled Azure Artifacts feeds and promote verified package versions through appropriate feed views. Feed views and package versions distinguish validated consumable assets from untested build outputs. Unreviewed dependencies can be consumed by production services despite passing their own source-control checks.

Incorrect Answers

A:

Publish uniquely identified pipeline artifacts and reuse the same tested run output across all environments.

C:

Configure upstream sources and caching policies that preserve authenticated provenance and pinned dependency versions.

D:

Separate internal and public feed priorities, protect namespaces, and enforce provenance for dependent packages.

Question 247

A release consumes a prerelease NuGet library from the default feed even though only packages approved by QA may be deployed. How should the team validate the intended result?

Resolve a package using production feed permissions and verify only the reviewed immutable version is available.
Use contract tests across dependent applications and compare package API changes with approved version increments.
Recreate a clean agent restore and verify package URL, publisher, hash, and expected feed resolution.
Rebuild a recorded release against the approved feed and compare exact package versions and checksums.

Explanation

Correct Answer

A:

Resolve a package using production feed permissions and verify only the reviewed immutable version is available. Feed views and package versions distinguish validated consumable assets from untested build outputs.

Incorrect Answers

B:

Use contract tests across dependent applications and compare package API changes with approved version increments.

C:

Recreate a clean agent restore and verify package URL, publisher, hash, and expected feed resolution.

D:

Rebuild a recorded release against the approved feed and compare exact package versions and checksums.

Question 248

A release consumes a prerelease NuGet library from the default feed even though only packages approved by QA may be deployed. Which design distinction is MOST relevant in these conditions?

Dependency-resolution order and namespace trust can allow an external package to impersonate a private library.
Feed views and package versions distinguish validated consumable assets from untested build outputs.
An upstream cache improves availability only if package identity and namespace trust remain consistent.
Package registries need separately managed publish and consume permissions, not blanket source repository ownership.

Explanation

Correct Answer

B:

Feed views and package versions distinguish validated consumable assets from untested build outputs. Unreviewed dependencies can be consumed by production services despite passing their own source-control checks.

Incorrect Answers

A:

Dependency-resolution order and namespace trust can allow an external package to impersonate a private library.

C:

An upstream cache improves availability only if package identity and namespace trust remain consistent.

D:

Package registries need separately managed publish and consume permissions, not blanket source repository ownership.

Question 249

A release consumes a prerelease NuGet library from the default feed even though only packages approved by QA may be deployed. Which ongoing guardrail would BEST prevent this problem from recurring?

Review workflow permission scopes and package visibility after repository transfers or organization changes.
Audit upstream-source changes and implement dependency lock files and package provenance checks.
Require package promotion approvals and restrict feed publish and view management permissions.
Require changelog review and compatibility validation before publishing shared package versions.

Explanation

Correct Answer

C:

Require package promotion approvals and restrict feed publish and view management permissions. Unreviewed dependencies can be consumed by production services despite passing their own source-control checks.

Incorrect Answers

A:

Review workflow permission scopes and package visibility after repository transfers or organization changes.

B:

Audit upstream-source changes and implement dependency lock files and package provenance checks.

D:

Require changelog review and compatibility validation before publishing shared package versions.

Question 250

A release consumes a prerelease NuGet library from the default feed even though only packages approved by QA may be deployed. Which risk is directly created by the described failure?

Excessive package credentials may permit supply-chain tampering or leak proprietary dependencies to unrelated teams.
Production may contain software not covered by earlier quality and security gates.
Consumers may silently adopt breaking updates and experience preventable production failures.
Unreviewed dependencies can be consumed by production services despite passing their own source-control checks.

Explanation

Correct Answer

D:

Unreviewed dependencies can be consumed by production services despite passing their own source-control checks. This is the directly relevant business or security consequence of azure artifacts feed views for verified package promotion. Root cause: Feed views and package versions distinguish validated consumable assets from untested build outputs.

Incorrect Answers

A:

Excessive package credentials may permit supply-chain tampering or leak proprietary dependencies to unrelated teams. That risk is relevant to github packages access using least-privilege workflow credentials, but the specific unresolved condition here concerns azure artifacts feed views for verified package promotion and has a different direct consequence.

B:

Production may contain software not covered by earlier quality and security gates. That risk is relevant to pipeline artifact identity and cross-stage immutability, but the specific unresolved condition here concerns azure artifacts feed views for verified package promotion and has a different direct consequence.

C:

Consumers may silently adopt breaking updates and experience preventable production failures. That risk is relevant to semantic versioning for shared api contract packages, but the specific unresolved condition here concerns azure artifacts feed views for verified package promotion and has a different direct consequence.

Microsoft AZ-400 Exam Dumps, Practice Test Questions

Question 240

Explanation

Correct Answers

Incorrect Answers

Question 241

Explanation

Correct Answer

Incorrect Answers

Question 242

Explanation

Correct Answer

Incorrect Answers

Question 243

Explanation

Correct Answer

Incorrect Answers

Question 244

Explanation

Correct Answer

Incorrect Answers

Question 245

Explanation

Correct Answer

Incorrect Answers

Question 246

Explanation

Correct Answer

Incorrect Answers

Question 247

Explanation

Correct Answer

Incorrect Answers

Question 248

Explanation

Correct Answer

Incorrect Answers

Question 249

Explanation

Correct Answer

Incorrect Answers

Question 250

Explanation

Correct Answer

Incorrect Answers