What is the difference between an Azure subscription and a resource group?
Assesses fundamental understanding of Microsoft Azure conventions, runtime behavior, and memory/performance considerations.
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
A subscription is a billing and access boundary; a resource group is a logical container for related resources.
- Subscription: defines quotas, billing, and a trust boundary for RBAC and policy. You can have multiple subscriptions under a management group hierarchy for governance and cost separation.
- Resource group: groups resources that share a lifecycle, permissions, and deployment. Every resource belongs to exactly one resource group, and deleting the group deletes everything in it.
az group create --name rg-app-prod --location eastus
az deployment group create --resource-group rg-app-prod --template-file main.bicep
Good practice is to separate resource groups by environment or workload, apply tags for cost reporting, and scope RBAC at the narrowest level. Use management groups to apply policy across many subscriptions.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.