Examkin

All practice questions

65 questions

All types1,198Multiple choice617Multiple select502Matching65Ordering14
Question 61Question →

An organization is modernizing its application portfolio and migrating its data tier to Azure Cosmos DB. You need to recommend the appropriate Azure Cosmos DB API for each application workload based on their technical requirements. Match the application workloads on the left to the correct Azure Cosmos DB APIs on the right.

Click a left item, then click its matching right item

Items

A telemetry system currently running on a wide-column store that must continue using CQL-based client drivers and tools.
A new customer order management system requiring flexible JSON document storage and queries using structured SQL syntax.
A fraud detection system that analyzes networks of transactions, accounts, and devices to identify suspicious relationship patterns.
A legacy catalog system built with the Mongoose ODM framework that must be migrated with minimal application code modifications.

Matches

Show answer & explanation

Answer

Match the wide-column telemetry system using CQL to API for Cassandra; match the new customer order management system using SQL syntax to API for NoSQL; match the fraud detection system analyzing relationship patterns to API for Gremlin; and match the legacy content management system using Mongoose to API for MongoDB.
Matching the wide-column telemetry workload to API for Cassandra allows the reuse of CQL drivers. Matching the new JSON SQL-based workload to API for NoSQL aligns with native Cosmos DB capabilities. Matching the network-relationship fraud detection workload to API for Gremlin facilitates graph traversals. Matching the Mongoose ODM catalog workload to API for MongoDB ensures compatibility with MongoDB drivers.

Step-by-Step Solution

1
Analyze the telemetry workload requiring CQL driver compatibility.
Identify that CQL is the Cassandra Query Language, pointing to the API for Cassandra.
This minimizes rewrites for Cassandra-based applications.
2
Analyze the customer order management workload requiring JSON storage and SQL-like queries.
Identify that Azure Cosmos DB's native SQL API is the API for NoSQL.
API for NoSQL provides optimal performance and features for document-based workloads querying with SQL syntax.
3
Analyze the fraud detection workload analyzing transaction networks and relationships.
Identify that graph relationships are best managed via a graph database model using Gremlin.
API for Gremlin supports graph traversals and relationship modeling.
4
Analyze the legacy content management system workload utilizing Mongoose ODM.
Identify that Mongoose is a popular MongoDB ODM framework, mapping to the API for MongoDB.
API for MongoDB supports MongoDB wire protocols, allowing Mongoose to function with minimal config adjustments.

Key Concept

Azure Cosmos DB API selection based on workload requirements and legacy system compatibility.
Question 62Question →

Match each architectural routing and failover requirement with the most appropriate Azure load balancing or traffic routing service.

Click a left item, then click its matching right item

Items

A global web application requires path-based routing, SSL offloading, and web application firewall protection at the edge before traffic enters Azure regions.
A gaming platform needs to route low-latency UDP traffic globally to regional backends using a single static IP address acting as the entry point.
A legacy retail application in a single region requires cookie-based session affinity to ensure users stay connected to the same backend virtual machine instance.
An enterprise requires global failover for a hybrid environment where traffic must be directed to external non-Azure endpoints without proxying the network payload.

Matches

Show answer & explanation

Answer

The architectural requirements match as follows: Global SSL offloading and WAF routing maps to Azure Front Door; global UDP routing via a single static IP maps to Azure Cross-region Load Balancer; single-region cookie session affinity maps to Azure Application Gateway; and DNS-based hybrid routing to external endpoints without proxying maps to Azure Traffic Manager.
Each matching pair aligns a specific application layer, scope, and feature requirement with the correct Azure service. Azure Front Door handles global HTTP/HTTPS with SSL offloading and WAF. Azure Cross-region Load Balancer provides global Layer 4 Anycast routing for TCP/UDP. Azure Application Gateway provides regional Layer 7 capabilities like session affinity. Azure Traffic Manager provides DNS-based redirection, making it suitable for hybrid endpoints without proxying.

Step-by-Step Solution

1
Analyze the layer and scope for the first scenario.
The requirement involves global HTTP/HTTPS traffic, path-based routing, SSL offloading, and WAF protection. This indicates a Layer 7 global service, which matches Azure Front Door.
Azure Front Door is the only service that combines global scope, Layer 7 HTTP/HTTPS features, SSL termination, and native WAF integration.
2
Analyze the protocol and IP configuration for the second scenario.
The requirement involves low-latency UDP traffic globally using a single static IP address. This points to a Layer 4 global load balancing solution.
Azure Cross-region Load Balancer uses Anycast IP to route Layer 4 (TCP/UDP) traffic globally with ultra-low latency.
3
Analyze the regional requirements for the third scenario.
The requirement is for a single-region HTTP/HTTPS application needing cookie-based session affinity for backend virtual machines.
Azure Application Gateway is a regional Layer 7 load balancer that provides cookie-based session affinity, unlike global services which route between regions.
4
Analyze the routing mechanism for the fourth scenario.
The requirement is global failover for a hybrid environment to external endpoints without proxying the network payload.
Azure Traffic Manager uses DNS-based routing to return client endpoints directly, bypassing the network proxy layer and supporting external hybrid endpoints.

Key Concept

Selecting the appropriate global or regional Azure load balancing service based on protocol (Layer 4 vs Layer 7), routing method (DNS vs Anycast), and features (session affinity, SSL offloading, WAF).
Question 63Question →

A cloud architect needs to select appropriate Azure networking services to satisfy load balancing and failover requirements for different application types. Match each operational scenario to the optimal Azure service that meets the requirements.

Click a left item, then click its matching right item

Items

A global HTTP/S application requiring URL path-based routing, TLS offloading, and immediate failover via Anycast IP routing.
A global TCP-based gaming application on port 7777 requiring client traffic redirection to the nearest region using DNS name resolution.
A regional web service requiring cookie-based session affinity, TLS offloading, and URL path-based routing within a virtual network.
A global application requiring Layer 4 load balancing to route non-HTTP TCP/UDP traffic to different regions using a single static Anycast IP.

Matches

Show answer & explanation

Answer

The correct matches are: 1) The global HTTP/S application matches Azure Front Door. 2) The global TCP-based gaming application matches Azure Traffic Manager. 3) The regional web service matches Azure Application Gateway. 4) The global Layer 4 Anycast application matches Azure Cross-region Load Balancer.
The correct matches map the specific technical characteristics (layer, scope, protocol) of each scenario to the capabilities of Azure's load balancing services.

Step-by-Step Solution

1
Analyze the scope (global vs. regional) and protocol layer (Layer 4, Layer 7, or DNS) for each scenario.
Two scenarios are global Layer 7/DNS HTTP/S, one is regional Layer 7 HTTP/S, and two are global Layer 4 TCP/UDP.
Categorizing the requirements by network layer and geographic scope immediately filters down the available Azure load balancing services.
2
Differentiate the Layer 7 requirements based on regional vs. global requirements.
The regional HTTP/S requirement inside a virtual network maps to Azure Application Gateway. The global HTTP/S application requiring fast failover and Anycast maps to Azure Front Door.
Azure Application Gateway operates within a region and virtual network, whereas Azure Front Door operates at the edge globally.
3
Differentiate the global Layer 4/DNS requirements.
The TCP port 7777 scenario requiring DNS resolution maps to Azure Traffic Manager. The global TCP/UDP scenario requiring a static Anycast IP maps to Azure Cross-region Load Balancer.
Azure Traffic Manager uses DNS redirection and supports custom TCP ports, while Azure Cross-region Load Balancer operates at Layer 4 using Anycast IP routing.

Key Concept

Selecting the correct Azure load balancing service involves evaluating regional vs. global scope, Layer 4 vs. Layer 7 routing capabilities, and DNS vs. Anycast IP architectures.
Question 64Question →

An organization is designing a high-availability and disaster recovery architecture for various workloads deployed in Azure. You need to select the appropriate load balancing and traffic routing services. Match each application routing requirement with the optimal Azure service.

Click a left item, then click its matching right item

Items

Route global HTTPS traffic to web applications across multiple regions with path-based routing, SSL offload, and fast Anycast failover.
Load balance non-HTTP TCP traffic globally across multiple Azure regions with low latency using Anycast IP address advertising.
Distribute HTTP(S) traffic within a single Azure region using URL path-based rules and cookie-based affinity.
Load balance global TCP/UDP endpoints using DNS-based name resolution with weighted or priority-based routing policies.

Matches

Show answer & explanation

Answer

Route global HTTPS traffic with path-based routing matches Azure Front Door; Load balance global TCP traffic using Anycast matches Azure Cross-region Load Balancer; Distribute regional HTTP(S) traffic with path-based rules matches Azure Application Gateway; Load balance global TCP/UDP endpoints using DNS matches Azure Traffic Manager.
The correct pairings are determined by matching the geographic scope (global vs. regional), the OSI layer (layer 4 TCP/UDP vs. layer 7 HTTP/S), and the routing mechanism (Anycast vs. DNS-based) of the requirements with the respective features of Azure Front Door, Azure Cross-region Load Balancer, Azure Application Gateway, and Azure Traffic Manager.

Step-by-Step Solution

1
Identify the geographical scope (global vs. regional) and network layer (layer 4 vs. layer 7) for each requirement.
Two requirements specify global HTTP(S) routing, one specifies global non-HTTP TCP/UDP routing, and one specifies regional HTTP(S) routing.
This helps categorize and filter the available Azure load balancing services.
2
Distinguish between the global services: Azure Front Door, Azure Traffic Manager, and Azure Cross-region Load Balancer.
Azure Front Door matches global layer 7 (HTTP/S) Anycast routing. Azure Traffic Manager matches DNS-based routing for generic endpoints. Azure Cross-region Load Balancer matches global layer 4 Anycast routing.
This pairs the global requirements with their corresponding services based on the routing mechanism and protocol requirements.
3
Identify the regional service matching the regional HTTP(S) requirement.
Azure Application Gateway is the regional layer 7 service that supports cookie-based affinity and path-based routing.
This resolves the final requirement by matching it to the regional application delivery controller.

Key Concept

Selecting the appropriate Azure load balancing and traffic routing services based on application protocol (HTTP/S vs. TCP/UDP), routing layer (Layer 4 vs. Layer 7), and geographic scope (Global vs. Regional).
Estimated Time:2m 0s
Question 65Question →

Match each application architecture scenario to the most appropriate Azure load balancing or traffic routing service. Each service may be used once, more than once, or not at all.

Click a left item, then click its matching right item

Items

A global web application that requires SSL offloading, URL path-based routing, and immediate failover using Anycast routing.
A global application using custom TCP ports that requires DNS-based routing to endpoints with configurable TTL for failover.
A web application restricted to a single region that requires URL-path routing, private backend IP addresses, and Web Application Firewall (WAF) protection.
A regional database cluster requiring high-throughput, ultra-low latency TCP load balancing for backend virtual machines.

Matches

Show answer & explanation

Answer

The global web application with SSL offloading and Anycast routing matches Azure Front Door. The global TCP application using DNS routing matches Azure Traffic Manager. The regional web application with private backend IPs and WAF matches Azure Application Gateway. The regional database cluster matches Azure Load Balancer.
The correct matches are based on mapping the architectural scope (global vs. regional) and the required networking layer (Layer 4 vs. Layer 7). Global Layer 7 routing with Anycast maps to Azure Front Door. Global DNS-based Layer 4 routing maps to Azure Traffic Manager. Regional Layer 7 routing with private IP backends and WAF maps to Azure Application Gateway. Regional Layer 4 high-performance TCP load balancing maps to Azure Load Balancer.

Step-by-Step Solution

1
Determine the scope (global vs. regional) for each application requirement.
The global web application and the global TCP application require global solutions. The regional web application and database cluster require regional solutions.
This narrows down the choices between global services (Front Door, Traffic Manager) and regional services (Application Gateway, Load Balancer).
2
Analyze the network layer requirements (Layer 4 vs. Layer 7) for the global services.
The global web application requires Layer 7 features (SSL offloading, URL routing) and maps to Azure Front Door. The global TCP application requires Layer 4/DNS routing and maps to Azure Traffic Manager.
Azure Front Door is a Layer 7 service, while Azure Traffic Manager works at the DNS layer (Layer 4/any protocol).
3
Analyze the network layer and security requirements for the regional services.
The regional web application requires Layer 7 features (URL routing, private backend IPs, WAF) and maps to Azure Application Gateway. The regional database requires high-performance Layer 4 load balancing and maps to Azure Load Balancer.
Azure Application Gateway provides regional Layer 7 capabilities, while Azure Load Balancer handles high-performance Layer 4 traffic.

Key Concept

Selecting Azure load balancing services based on geographical scope (global vs. regional) and protocol layer (Layer 4 vs. Layer 7).
PreviousPage 4 / 4
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin