DP-900 Describe core data 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: Select SQL Database service, Step 2: Configure server (create new server), Step 3: Configure database settings (name, pricing tier, compute+storage), Step 4: Review and create

  Why this is correct

  This is the correct order because you must first choose the SQL Database service, then set up the server that will host the database, then define database-specific settings like name and tier, and finally review and deploy.

• ✗

  Step 1: Configure server (create new server), Step 2: Select SQL Database service, Step 3: Configure database settings (name, pricing tier, compute+storage), Step 4: Review and create

  Why it's wrong here

  Attempting to create a server before selecting the SQL Database service reverses the logical flow in the Azure portal. The 'Create SQL Database' workflow has the server configuration (new server name, admin login, location) as the second pane after the Basics tab, which is only reached by first choosing the SQL Database resource type. A standalone logical server cannot be provisioned from the same blade; it exists as a parent container that is created in tandem with the database. Thus, this ordering fails because the service selection is the mandatory entry point for the entire provisioning process.

• ✗

  Step 1: Select SQL Database service, Step 2: Configure database settings (name, pricing tier, compute+storage), Step 3: Configure server (create new server), Step 4: Review and create

  Why it's wrong here

  Selecting the SQL Database service and then immediately jumping to database settings skips the required server configuration pane. In the portal's creation flow, after you choose 'Create' on a SQL Database, the Basics tab collects server details first, because the database is bound to a logical server that provides its connection endpoint and authentication. Only once the server is established does the portal present options for database name, compute tier, and storage; these settings are scoped to that server. Therefore, placing server configuration after database settings is invalid.

• ✗

  Step 1: Configure database settings (name, pricing tier, compute+storage), Step 2: Select SQL Database service, Step 3: Configure server (create new server), Step 4: Review and create

  Why it's wrong here

  Starting the sequence with database settings before selecting the SQL Database service is impossible because no creation context exists yet; the Azure portal does not expose a generic database-settings form outside a resource creation flow. The workflow requires you to initiate from the 'Create a resource' menu and choose 'Azure SQL,' which then guides you through the mandatory steps of server creation before database name, tier, and storage are available. Attempting to configure database-level options first would be operating on a nonexistent resource. Hence, this ordering cannot be executed in the portal.

Go deeper

Related to this question