AZ-305 Design data storage solutions 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.

• ✓

  Create profile, then add endpoints, then configure mapping, then update DNS, then test.

  Why this is correct

  This is the correct order because you must first create the Traffic Manager profile, then add endpoints to it, then configure the geographic routing mapping to associate regions with endpoints, then update DNS to point to the Traffic Manager domain, and finally test the configuration to verify routing.

• ✗

  Add endpoints, then create profile, then configure mapping, then update DNS, then test.

  Why it's wrong here

  A Traffic Manager profile is the parent Azure resource that owns all endpoint references; before the profile exists there is no DNS name, routing method, or endpoint configuration context on which to add endpoints. In any ARM hierarchy, child resources such as endpoints cannot be created independently of the parent profile. Attempting to add endpoints first would also fail because the API target for endpoint creation is profilename/endpoints. Therefore you must create the profile first, and only then add endpoint child resources to it.

• ✗

  Create profile, then configure mapping, then add endpoints, then update DNS, then test.

  Why it's wrong here

  Geographic mapping in Traffic Manager associates a specific region, country, or continent with an endpoint resource ID that Traffic Manager can route to. If you configure this mapping before endpoints are added, there is no endpoint object to bind to the region, so the portal's mapping UI or API call has nothing to attach. The Azure portal will not let you select an endpoint for a region if none exist, and REST or ARM would reject the configuration as invalid. Thus endpoints must be added first, so the mapping step that follows can reference actual endpoint resources.

• ✗

  Create profile, then add endpoints, then update DNS, then configure mapping, then test.

  Why it's wrong here

  Traffic Manager's geographic routing evaluates the configured region-to-endpoint mapping at the same time it answers DNS queries; if you update your production DNS record before configuring that mapping, clients may receive a response that fails to identify an endpoint for their geographical origin. The profile's routing method is already set to geographic, but without the mapping the resolver cannot consistently return the correct endpoint, which can cause 'endpoint not found' behavior or regional fallback to the default. Configuring mapping first ensures the geo policy is fully deployed before the traffic switch, avoiding an availability or performance blip. Therefore DNS update is the final step, not the fourth step.

Go deeper

Related to this question