AZ-204 Practice Question: Monitor, troubleshoot, and optimize Azure solutions

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Use Azure Application Gateway with Web Application Firewall

  Why it's wrong here

  Using Azure Application Gateway with Web Application Firewall is a regional solution designed to provide Layer 7 load balancing, SSL termination, and WAF capabilities within a single Azure region. While it enhances security and performance for applications deployed in that specific region, it does not address the fundamental problem of latency caused by geographic distance between global users and that single regional deployment. To reduce latency for a globally distributed user base, a solution must distribute traffic across multiple regions, which Application Gateway does not facilitate.

• ✗

  Scale up the App Service plan to a higher tier

  Why it's wrong here

  Scaling up an App Service plan to a higher tier increases the compute, memory, and storage resources available to a single App Service instance within a specific Azure region. This action improves the application's capacity to handle more requests or perform complex operations more efficiently, thereby reducing processing time on the server. However, scaling up does not reduce the physical network latency incurred when users are geographically distant from the single region where the App Service is hosted, as it does not bring the application closer to the users.

• ✓

  Use Azure Traffic Manager with performance routing

  Why this is correct

  Azure Traffic Manager is a DNS-based traffic load balancer that distributes incoming user requests across multiple Azure regions or external endpoints. When configured with performance routing, it intelligently directs users to the endpoint with the lowest latency, typically by resolving the DNS query to the closest available Azure region based on the user's DNS resolver location. This approach effectively minimizes the network round-trip time for users accessing a globally distributed application, significantly reducing perceived latency.

• ✗

  Enable multi-region writes on Azure Cosmos DB

  Why it's wrong here

  Enabling multi-region writes on Azure Cosmos DB allows applications to write data to any configured region, which can significantly reduce write latency for users geographically closer to a write region. This feature optimizes the database's write operations by allowing local writes and background replication. However, it primarily addresses write latency for the database layer and does not inherently reduce the overall application latency for read operations, static content delivery, or the initial connection to the application's compute layer, which are often larger contributors to global user experience latency.

• ✓

  Use Azure Front Door to route traffic to the nearest region

  Why this is correct

  Azure Front Door is a global, scalable entry-point that leverages the Microsoft global edge network to accelerate web traffic and provide global load balancing. Operating at Layer 7 (HTTP/HTTPS), it routes user requests to the fastest and most available application backend, often the one geographically closest to the user, by utilizing anycast IP and intelligent health probing. This not only reduces latency by bringing the application's entry point closer to the user but also enhances application availability and security by acting as a global reverse proxy with integrated WAF capabilities.

Go deeper

Related to this question