A regional library system needs twenty nearly identical Azure environments for branch sites and finds portal-only builds too slow and inconsistent. What approach matches the scale need?
Select an answer to reveal the explanation.
Short Explanation
Twenty lookalike branch stacks are a stamp-and-repeat problem, and infrastructure as code is the stamp. Portal-clicking twenty times invites twenty different mistakes.
Full Explanation
Infrastructure as code supports repeatable multi-environment deployment from a shared definition, which scales better than manual portal-only builds for many similar sites. A regional library system can stamp branch environments from one reviewed template instead of reinventing each site by hand. Consistency and speed both improve as the number of sites grows. Claiming identical environments are impossible ignores the point of templated deployment.