Which TWO of these statements about subscriptions and management groups are true?
Microsoft Certified: Azure Fundamentals (AZ-900), objective architecture-and-services. Azure architecture and services medium
Machine-checked — no person has signed for it. This question was read against the source cited below by an automated pass, which found no contradiction. That is a weaker claim than it sounds: the same kind of process wrote the question, so it can confirm its own mistake.
Treat it as a good draft rather than as settled fact, and read the source below before you rely on it. It is not used in mock exams here — only questions a person has signed for are.
The options
Choose 2.
Correct A subscription is a billing boundary: the usage inside it is accumulated and invoiced together
True. Splitting an estate into subscriptions is one of the standard ways to separate what different departments or environments cost, without reconstructing it from tags afterwards.
Correct A subscription is also a scale boundary, because quotas and limits apply per subscription
True. A large estate can genuinely run out of headroom inside one subscription, and adding subscriptions is how you get more, which is why the boundary is described as both billing and scale.
Not correct One resource group can contain resources drawn from two different subscriptions
False. A resource group lives inside exactly one subscription, and everything in it belongs to that subscription. Moving a resource between subscriptions is a deliberate move operation, not a shared group.
Not correct A subscription can sit under two management groups at once, so two teams can each govern it
False. Each subscription has exactly one parent management group. If it had two, inherited policy and role assignments would have no unambiguous answer, which is why the hierarchy is a tree.
Not correct Deleting a management group deletes the subscriptions inside it
False. A management group with children cannot be deleted; you move the children out first. Nothing about that removes a subscription or anything billing inside one.
Why
A subscription is where billing, quotas and the boundary of most access control meet, which is why estates are usually split along organisational or environmental lines rather than arbitrarily. Above it, management groups exist purely to apply governance to many subscriptions at once, in a strict tree with a single root. Below it, resource groups gather resources that share a lifecycle — one subscription each, and no sharing between them.
Where this comes from
- Cited
- Microsoft AZ-900 study guide skill area architecture-and-services.core-architectural-components
Practise this
Reading one question is not practice. The trainer will draw a set from objective architecture-and-services and space the ones you get wrong.
Practise Microsoft Certified: Azure Fundamentals (AZ-900)
More questions on this objective
- An image-resizing routine runs for about two seconds whenever a file lands in a storage container — perhaps two hundred times on a busy day, and not at all on a quiet one. The team wants to pay for the work done and maintain no servers. Which compute option fits? machine-checked
- A fifteen-year-old accounting application needs a kernel-level driver, a scheduled task that edits the registry, and a runtime version nobody supports any more. The business wants it running in Azure this quarter with as few code changes as possible. Where does it go? machine-checked
- A team runs nine small services, each with its own conflicting library versions. They want each one packaged with its dependencies, starting in seconds, several to a host, without a separate operating system per service. Which compute type are they describing? machine-checked
- Which TWO of these statements about Azure compute types are true? machine-checked
- A public website runs on four identical virtual machines behind a load balancer. Traffic triples while a television advert airs and falls back an hour later. The team wants instances added and removed automatically against CPU, all built from one image, with nobody clicking. Which option is designed for that? machine-checked
- Three virtual machines form a quorum-based cluster in a region that has no availability zones. You want them placed so that neither a single rack losing power nor a single batch of planned host maintenance can take all three at once. What do you configure? machine-checked