A cloud engineer creates an IaC repository to deploy an application to a specific region.

Option D is the best approach because it applies Infrastructure as Code (IaC) and Configuration as Code (CaC) principles to enable repeatable, scalable, and maintainable multi-region deployments. In Cloud+ CV0-004, IaC implementations should be parameterized so the same templates/modules can be reused across environments, regions, and accounts with minimal change. Using region-specific variable files (for example, per-region parameters such as CIDR ranges, availability zones, service endpoints, or sizing) keeps the core IaC code consistent while allowing controlled differences where needed. This supports version control, reduces configuration drift, and makes CI/CD automation simpler—one pipeline can loop through variable sets or deploy via a matrix strategy.

By contrast, creating branches per region (A or C) increases operational overhead, complicates merges, and risks inconsistent infrastructure definitions. Creating separate repositories per region (B) is even harder to govern and maintain, and it fragments change control and security reviews. Therefore, variable files + IaC provides the most efficient and scalable solution for ten-region deployment.