A grants office must show auditors who changed which cloud resources and when. Which cloud benefit theme does that need map to?
Select an answer to reveal the explanation.
Short Explanation
Auditors love a paper trail — cloud governance is that trail for who touched what resource. Auditability and standards enforcement sit under the governance benefit, not overnight function pricing. Zones and gaming latency are different conversations.
Full Explanation
Governance benefits include control, auditability, and standards enforcement over cloud resources. A grants office that must show who changed which resources and when is asking for that audit trail—activity history, change accountability, and policy consistency—not for a different Domain 1 theme dressed up as compliance theater. Cloud platforms expose logging and control planes that make those questions answerable when configured and retained properly. High availability across availability zones addresses uptime design and fault isolation, not change accountability for auditors. Serverless pricing for idle functions overnight is a cost and compute model concern unrelated to “who changed what.” Geographic replication chosen only for lower latency gaming targets performance geography, not auditor evidence for grant-funded systems. Exam caveat: governance here is the cloud-benefit theme (control and audit), not a deep Azure Policy authoring exercise—AZ-900 stays at recognize-and-describe depth. Operational check: confirm activity or change logs retain who modified grant-related resources, that retention meets auditor expectations, and that access to those logs is limited to appropriate municipal roles before the next review.