Skip to main content
  1. Public practice questions
  2. AZ-900 Practice Exams | Azure Fundamentals
  3. Domain 2-Describe Azure architecture and services | AZ-900 Practice Exam | 399 Questions

Question 201 — Domain 2-Describe Azure architecture and services | AZ-900 Practice Exam | 399 Questions

Arrange the following Azure portal steps for creating an availability set in the correct order.

Instruction: Drag and drop the items into the correct order, starting with the first step at the top.

  1. Sign in to the Azure portal
  2. Submit the deployment
  3. Enter the availability set name, subscription, resource group, and region
  4. Start a new availability set configuration
  5. Search for and open Availability sets
  6. Set the fault domain and update domain values
  7. Review the configuration

Correct answers

  1. Sign in to the Azure portal
  2. Search for and open Availability sets
  3. Start a new availability set configuration
  4. Enter the availability set name, subscription, resource group, and region
  5. Set the fault domain and update domain values
  6. Review the configuration
  7. Submit the deployment

Explanations

Correct order

Sign in to the Azure portal

Search for and open Availability sets

Start a new availability set configuration

Enter the availability set name, subscription, resource group, and region

Set the fault domain and update domain values

Review the configuration

Submit the deployment

Signing in to the Azure portal is the mandatory entry point that establishes an authenticated session. From there, searching for and opening the Availability sets blade brings you to the dedicated resource area where availability sets are managed; without this step, no configuration can begin. Starting a new availability set configuration launches the creation form, which immediately requires the foundational details—name, subscription, resource group, and region—before anything else can be set. Only once these basics are filled in do the fault domain and update domain fields become meaningful and editable, as they are properties of the specific resource definition. After all values are entered, reviewing the configuration validates the inputs and surfaces any errors; you cannot submit without passing this review stage. Finally, submitting the deployment provisions the availability set based on the validated configuration. Each step is a strict prerequisite of the next, and the sequence never varies by environment, user role, or scenario—making it a fixed, unskippable workflow.