問題文
A platform team wants application teams to create their own database instances without filing a ticket, while still guaranteeing that every instance ends up with the organization's required encryption, backup, and tagging settings. Which property of an infrastructure-as-code approach makes this possible?
選択肢
- The tool refuses to create any resource whose settings differ from the organization's baseline standard, so no additional module structure is needed.
- The required settings can be encoded once in a reusable module definition, and the application teams supply only the values that legitimately differ between their services.
- The tool applies the organization's tagging policy to every resource that it creates, independently of what the definition says.
- Every application team can read the platform team's definitions in the repository, so they can copy the required encryption, backup, and tagging settings into their own configuration before they apply it.