A three-month proof of concept will create a virtual machine, a storage account, a virtual network and a web app. When it ends, everything it created must go, with nothing left quietly billing. What is the simplest way to arrange that up front?

Microsoft Certified: Azure Fundamentals (AZ-900), objective architecture-and-services. Azure architecture and services easy

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

Correct Create every resource in one dedicated resource group, and delete that resource group at the end

Correct. A resource belongs to exactly one resource group, and deleting the group deletes everything inside it, which is why a group per project turns cleanup into a single action.

Not correct Create a dedicated management group for the project

Wrong. Management groups organise subscriptions, not resources — you cannot place a virtual machine in one, and removing it would delete nothing.

Not correct Tag every resource with the project name and delete by tag at the end

Wrong as the primary mechanism. Tags are excellent for reporting and cost attribution, but there is no single delete-everything-with-this-tag operation, and anything created without the tag is silently missed.

Not correct Create a separate subscription for the work and cancel it afterwards

Wrong — an account-level action with its own process and timing, taken for a three-month experiment that a resource group already handles.

Why

The management hierarchy runs management group, subscription, resource group, resource, and each level exists for a different job. The resource group is the lifecycle unit: things with the same lifetime belong together, because that is what makes deletion, permissions and cost views line up with the work. A resource can be moved between groups later, but it is only ever in one at a time.

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

All questions on Azure architecture and services