Identity and data access
A fictional publisher grants a workload Reader on a storage account, but it needs to read blob contents. What is missing? Identify the principal, the data action and the narrow resource scope. A management-plane role isn’t a substitute for the required data permission. Then inspect inherited access before claiming least privilege.
Allocation and recovery
A survey VM is stopped after a batch. Is stopped the same as deallocated? No. Read the allocation state before making a compute-cost claim. Retained disks have their own lifecycle. Separately verify that the batch committed a durable result; a power-state change doesn’t prove the work finished safely.
Staging and production
An application has a staging build and a slot-sticky DATABASE setting. What must remain with production during a release? Explain which configuration moves and which stays with its environment. If the release changes shared data or schema, reversing the application swap may not undo that change. Describe the compatibility and recovery plan.
Incident population
An incident report requests failed dispatch calls in the last hour. Why can a plausible total still be wrong? Check the clock, workspace, service filter and aggregation grain. The same route name may occur in another service. An empty result also needs an ingestion check before it can support a healthy-service conclusion.
Preview and apply
A change review asks for a template what-if. Does creating the proposed resource satisfy that review? No. A preview reports intended changes while leaving the target untouched. Inspect scope, parameters and current state. The local Bicep subset isn’t Microsoft’s compiler, and a local preview doesn’t establish provider acceptance.
Practice these boundaries in the Azure course and the independent Azure Interview Hub. Use the certification guide when preparing for a named exam. None of these local results measures a production service or proves a real restore succeeds.
Compare provider tradeoffs in the cloud architect interview guide, then defend one write authority and a tested recovery path.