A compliance auditor asks Cascade Regional Airlines' platform team to show every ARM template deployment made against a specific outstation resource group over the past quarter, including which template and parameter values were used each time. Where in Azure should the team look first to answer this without needing external logging?
Select an answer to reveal the explanation.
Short Explanation
Every resource group keeps its own running record of what was deployed to it and when. That Deployments blade is the first place to look for exactly this kind of "what was deployed, and with what inputs" audit question.
Full Explanation
The Deployments blade on a resource group lists every ARM deployment made against it, including the template and the parameter values supplied, along with a correlation ID and timestamp for each run. This built-in history is the direct answer to an audit question about what was deployed and when, without needing a separate logging system. A Bicep module registry, where one exists, is a store for publishing and sharing reusable modules; it has no concept of logging every place a module was ever invoked across resource groups, so it cannot answer this question. Export template generates a fresh template from current resource state on demand; it does not keep a log of past exports and has nothing to do with deployment history. What-if is a one-time preview of a hypothetical future deployment run interactively before deploying; it does not cache or retain results from prior actual deployments. A useful next step for the auditor's request is opening a specific entry in the deployment history to view its full parameter values and correlation ID for cross-referencing against change tickets.