ARM Templates (Infrastructure as Code)
← Back to DP-420 Terminology Reference
Category: Maintenance & Security
Summary: Declarative, version-controlled provisioning of Cosmos DB resources as code.
Overview
Azure Resource Manager (ARM) templates (and equivalents like Bicep) allow you to declaratively define and provision Azure Cosmos DB resources — accounts, databases, containers, throughput settings, and indexing policies — as code, enabling repeatable, version-controlled deployments as part of a DevOps process, as opposed to imperative, manual configuration through the Azure portal or CLI commands.
More Info & Links
DP-420 Style Practice Questions
Q1. What is the main advantage of provisioning Azure Cosmos DB resources using ARM templates instead of the Azure portal?
- A. Declarative, repeatable, and version-controlled infrastructure as code
- B. Lower RU cost for provisioned throughput
- C. Automatic point-in-time restore
- D. Elimination of the need for a partition key
Q2. Which of these can be maintained in production using ARM templates, per the DP-420 objectives?
- A. Indexing policies
- B. The account's region priority list only
- C. The change feed estimator
- D. The integrated cache
Answer Key
Answers are listed at the very end so you can attempt the questions first.
- Q1 (ARM Templates (Infrastructure as Code)): A. Declarative, repeatable, and version-controlled infrastructure as code — ARM templates provide declarative, repeatable infrastructure-as-code deployments suitable for DevOps pipelines.
- Q2 (ARM Templates (Infrastructure as Code)): A. Indexing policies — The DP-420 objectives specifically call out maintaining indexing policies in production using ARM templates.
DP-420: Designing and Implementing Cloud-Native Applications Using Microsoft Azure Cosmos DB — term detail page
