AZ-900 Describe cloud concepts 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.

• ✓

  Step 1: Access Azure Cost Management in the portal. Step 2: Create a budget with scope and amount. Step 3: Set up alerts for budget thresholds. Step 4: Monitor spending and adjust budget as needed.

  Why this is correct

  Accessing Azure Cost Management in the portal is the prerequisite entry point because the budget creation workflow, cost analysis charts, and alert configuration all live within this blade. Creating a budget with a scope (subscription, resource group, management group) and an amount establishes the monetary limit against which actual costs are measured. Alerts are then attached to that budget to notify on percentage thresholds (e.g., 50%, 90%, 100%). Finally, monitoring spending in Cost Management and comparing it to the budget enables you to adjust the budget amount or scope based on actual usage trends.

• ✗

  Step 1: Create a budget with scope and amount. Step 2: Access Azure Cost Management in the portal. Step 3: Set up alerts for budget thresholds. Step 4: Monitor spending and adjust budget as needed.

  Why it's wrong here

  Jumping directly to budget creation before opening Azure Cost Management is invalid because the 'Add budget' action is exposed only through the Cost Management blade, which includes the 'Budgets' section under 'Cost management'. To create a budget, you must first navigate to the correct scope and access the portal interface. Without Step 1 providing the entrance and context, Step 2 cannot be executed from the Azure portal. The rest of the sequence is correct after that misplaced first step, but the reversal makes the whole workflow impossible.

• ✗

  Step 1: Set up alerts for budget thresholds. Step 2: Access Azure Cost Management in the portal. Step 3: Create a budget with scope and amount. Step 4: Monitor spending and adjust budget as needed.

  Why it's wrong here

  Configuring threshold alerts before any budget exists is inherently impossible because Azure budget alerts are a property of a budget object; they reference the budget's defined amount and scope. The alert rule consumes the budget's percentage threshold settings (such as 50% or 100%) and requires that budget to be created first. Thus Step 1 cannot be performed until after Steps 2 and 3 (access and create budget) are completed. Placing alert setup at the beginning ignores the dependency chain and yields no alert targets.

• ✗

  Step 1: Monitor spending and adjust budget as needed. Step 2: Access Azure Cost Management in the portal. Step 3: Create a budget with scope and amount. Step 4: Set up alerts for budget thresholds.

  Why it's wrong here

  Monitoring spending and adjusting the budget are iterative management tasks that presuppose a defined budget with alert thresholds; early in the lifecycle neither a budget nor its alerts exist for monitoring. Cost Management's daily or weekly monitoring compares actual spend against the budgeted amount, so the budget must already be created. Similarly, adjusting an amount or scope is done in response to alerts or cost analysis, making it the final step. Starting with Step 4 before any budget infrastructure exists makes the entire workflow untenable.

Go deeper

Related to this question