A city IT office wants production citizen services and a free-form sandbox for experiments kept apart so quotas, billing, and accidental changes do not collide. What Azure approach matches that goal?
Select an answer to reveal the explanation.
Short Explanation
Prod and playground should not share the same leash. Separate subscriptions give each side its own billing, quotas, and access story. That way a sandbox experiment cannot burn production limits or land on the wrong invoice.
Full Explanation
Azure subscriptions isolate billing, service limits (quotas), and access for the resources they contain. Splitting production and sandbox into different subscriptions reduces the chance that experimental workloads exhaust shared quotas or blur chargeback. Resource groups alone organize resources within a subscription; they do not provide the same isolation as a subscription boundary.