Two staging and production environments for a city portal are created from the same template and should match aside from parameters. Which IaC benefit is being pursued?
Select an answer to reveal the explanation.
Short Explanation
Same blueprint, different street addresses—that is the point of repeatable templates. Staging and production should look alike except for the knobs you deliberately turn.
Full Explanation
Repeatability means identically defined environments diverge only where parameters intentionally differ. Creating staging and production for a city portal from the same template pursues that IaC benefit so configuration drift between tiers is minimized except for planned parameter deltas. Unlimited free egress between every public endpoint fails as an unrelated and false benefit. Automatic exemption from all change-management reviews fails; IaC improves change quality but does not erase governance. Guaranteed single-AZ placement for every workload fails and may contradict availability goals. Exam caveat: name the IaC benefit the stem asks for—repeatability and consistency—not a grab-bag of cloud myths. Operational check: parameterize only true differences such as sizing, DNS names, and CIDRs, run the same pipeline stages for both tiers, and compare plan outputs to ensure accidental drift is not introduced for civic portal components. In municipal platform operations, record the chosen control and the rejected alternatives in the change record so future on-call engineers understand the failure modes avoided for citizen services. Re-check the decision after the next provider feature change or compliance update to ensure the same answer still holds for the city's estate.