AZ-900 Describe Azure management and governance Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Azure Cost Management

  Why it's wrong here

  Azure Cost Management is a suite for monitoring, analyzing, and optimizing cloud spend, providing cost trends, budgets, and anomaly alerts based on billing data. It uses resource metadata to attribute costs, but its primary purpose is financial governance rather than providing a browsable, manage-able list of every deployed resource. You wouldn't use it to locate a specific VM or check its provisioning state; you'd use All Resources.

• ✓

  All Resources blade in the Azure portal

  Why this is correct

  The All Resources blade in the Azure portal provides a centralized list of every resource across all subscriptions and resource groups to which the user has read access, with filtering, grouping, and column customization. It is the correct answer because it is specifically designed to give an inventory of all deployed resources, whereas the other options serve different purposes. It allows you to search, filter by subscription/resource group/type/location, and manage resource properties from a single unified view.

• ✗

  Azure Service Health

  Why it's wrong here

  Azure Service Health is a personalized dashboard that surfaces service incidents, planned maintenance, and health advisories affecting Azure regions/services, not a list of your deployed resources. It helps you understand the impact of Azure platform issues on your workloads, but it does not enumerate or manage your resource instances. It's a monitoring/notifications service, not an inventory tool.

• ✗

  Azure Subscriptions blade

  Why it's wrong here

  The Subscriptions blade is an administrative view for managing billing, access control (RBAC), and subscription-level settings; it lists subscriptions but does not aggregate or display the actual deployed resources within them. To see all resources, you use All Resources, which queries the Azure Resource Manager across all subscriptions you have access to, providing a flat inventory of resource groups, resources, and their metadata. So it's wrong because it's not the correct tool for inventorying resources; it's for managing subscriptions.