Correct Answer: @secure()
The @secure() decorator in Bicep (and ARM templates) tells the Azure Resource Manager deployment engine that the parameter value contains sensitive data. ARM will prevent the value...
Correct Answer
@secure()
Why This Answer Is Correct
The @secure() decorator in Bicep (and ARM templates) tells the Azure Resource Manager deployment engine that the parameter value contains sensitive data. ARM will prevent the value from being logged in the deployment history, printed to the console, or exposed in the portal.
This question evaluates your knowledge of Infrastructure as Code — a core concept tested in Microsoft Certified: DevOps Engineer Expert (AZ-400). Understanding Infrastructure as Code is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
You are using Azure Resource Manager (ARM) templates to deploy infrastructure. Your pipeline fails occasionally because developers introduce changes that inadvertently delete existing resources. You need to preview exactly what an ARM template deployment will create, modify, or delete before actually applying it. Which feature should you use?
Your team uses Terraform to deploy Azure infrastructure via Azure Pipelines. Multiple developers might trigger the pipeline simultaneously, which could lead to race conditions and corrupt the Terraform `.tfstate` file. What is the recommended way to prevent this?