AZ-400 Compliance & Governance 3

Question 1

What is the primary benefit of integrating Azure Key Vault with Azure Pipelines for secrets management?

Accepted Answer

It allows pipelines to retrieve sensitive values at runtime without hardcoding them in pipeline code or plain-text variables

Answer

Azure Key Vault integration allows secrets to be fetched at runtime, preventing sensitive values like passwords and connection strings from being stored in pipeline code or plain-text variable groups.

Question 2

In compliance-focused Azure DevOps implementations, why should service connections used for development environments be kept separate from those used for production?

Accepted Answer

Separation enforces least-privilege access and prevents development pipelines from accidentally modifying production resources

Answer

Separating service connections by environment enforces the principle of least privilege, ensuring development or test pipelines cannot access or modify production infrastructure.

Question 3

What Azure DevOps capability enables end-to-end traceability from requirements to deployment by linking commits, builds, and releases to specific work items?

Accepted Answer

Work item traceability through linked commits, builds, and deployments

Answer

Azure DevOps provides end-to-end traceability by linking commits, builds, and releases back to work items, creating a full audit trail from requirement through to production deployment.

Question 4

What does the concept of 'immutable artifacts' ensure in a compliance-focused DevOps pipeline?

Accepted Answer

The exact binary tested in one environment is promoted and deployed to all subsequent environments unchanged

Answer

Immutable artifacts ensure the exact package tested in a lower environment is the same one promoted to production, providing verifiable consistency and a clear compliance audit trail.

Question 5

What Azure DevOps setting controls which users can create, manage, and run pipelines within a project?

Accepted Answer

Pipeline permissions combined with Azure DevOps RBAC roles

Answer

Azure DevOps uses role-based access control (RBAC) combined with pipeline-level permissions to control who can create, edit, queue, and administer pipelines within a project.

AZ-400 Practice Test

AZ-400 Practice Test

AZ-400 Compliance & Governance 3