DP-900 Practice Question: Describe considerations for working with non-relational data on Azure

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: Navigate to the Azure Cosmos DB account. Step 2: Under Settings, click 'Replicate data globally'. Step 3: Select the regions you want to add. Step 4: Enable multi-region writes (if desired). Step 5: Click Save.

  Why this is correct

  This sequence is correct because the 'Replicate data globally' blade is the sole portal location where geographic region coverage is configured. After adding the desired read and write regions, you set the account-level toggle for multi-region writes, which applies to the entire set of selected regions. Clicking Save then commits all changes in a single operation, avoiding a second configuration pass.

• ✗

  Step 1: Navigate to the Azure Cosmos DB account. Step 2: Under Settings, click 'Replicate data globally'. Step 3: Enable multi-region writes (if desired). Step 4: Select the regions you want to add. Step 5: Click Save.

  Why it's wrong here

  Selecting regions after enabling multi-region writes is invalid because the multi-region writes toggle is not a standalone setting; it operates on the region set you have already configured on the 'Replicate data globally' blade. If you toggle it before selecting any additional regions, the portal's validation cannot confirm that the setting is compatible with the final write region list, and the configuration may be saved with an unintended single-write region. The correct order ensures the toggle is applied to the exact regions you intend to add.

• ✗

  Step 1: Navigate to the Azure Cosmos DB account. Step 2: Enable multi-region writes (if desired). Step 3: Under Settings, click 'Replicate data globally'. Step 4: Select the regions you want to add. Step 5: Click Save.

  Why it's wrong here

  The second step, enabling multi-region writes from the account overview, is impossible because that toggle is not exposed on the Cosmos DB account overview page. It exists only inside the 'Replicate data globally' blade, which you must open first via 'Settings' in the left navigation. Therefore, this sequence attempts to perform an action before its required context is loaded, violating the portal's actual workflow.

• ✗

  Step 1: Navigate to the Azure Cosmos DB account. Step 2: Under Settings, click 'Replicate data globally'. Step 3: Select the regions you want to add. Step 4: Click Save. Step 5: Enable multi-region writes (if desired).

  Why it's wrong here

  Saving before toggling multi-region writes commits the account with only a single write region, because all changes on the 'Replicate data globally' blade are applied atomically when you click Save. Once saved, the initial configuration is finalized, and enabling multi-region writes afterward will require reopening the blade, changing the toggle, and saving a second time—an unnecessary extra operation that also delays the moment at which multi-region writes becomes active. This sequence therefore fails to leverage the blade's all-in-one configuration save.

Go deeper

Related to this question