AZ-400 Question 196
Single answerYou are a DevOps engineer at a fast-growing company that wants to adopt Azure Deployment Environments to enable multiple development teams to self-deploy ephemeral test environments on demand. The organization has standard resource naming conventions, cost management constraints, and RBAC policies that must be enforced for all environments. Which approach should you recommend to ensure consistency and minimal overhead in managing these requirements?
- A
Maintain a single environment catalog in Azure Deployment Environments referencing standardized templates (e.g., Bicep or Terraform) and grant each development team contributor rights to deploy from that catalog.
- B
Allow each development team to maintain its own environment definitions in completely separate catalogs without central enforcement of resource naming or cost-management policies.
- C
Rely on manual environment creation for each request, using the Azure portal and referencing an organizational naming policy document for team members to follow on their own.
- D
Use stand-alone scripts that each team can customize independently, with no shared standards or environment definitions.
Show answer and explanation
Correct answer: A
Explanation
Centralizing environment definitions in a shared environment catalog is a recommended pattern in Azure Deployment Environments, as documented in Microsoft� official guidance. This approach enforces organizational policies (naming, RBAC, cost constraints) and still empowers teams to self-deploy environments on demand. For more details, refer to Microsoft� documentation on Azure Deployment Environments and environment catalogs.
- A. Correct.
Correct. By maintaining a central environment catalog with standardized Bicep or Terraform templates, you enforce naming conventions, RBAC policies, and cost controls. Granting contributors the right to self-deploy from this catalog aligns with best practices for on-demand, consistent deployments in Azure Deployment Environments.
- B. Incorrect.
Incorrect. Allowing each team to maintain entirely separate catalogs without central enforcement disrupts consistency. This approach risks drifting resource naming standards, inconsistent cost management, and potential gaps in RBAC policies.
- C. Incorrect.
Incorrect. Relying on manual portal-based deployments for each request is error-prone and negates the main benefits of Azure Deployment Environments (consistent, automated on-demand creation). Manual processes cannot easily enforce standardized templates or cost policies.
- D. Incorrect.
Incorrect. Using individualized stand-alone scripts leads to a lack of standardization and makes it difficult to enforce organizational policies. Each team would interpret requirements differently, increasing management complexity and the risk of misconfiguration.