Examkin

Design Infrastructure Solutions

360 soru

Tüm türler360Çoktan seçmeli189Çoklu seçim171
Soru 341Soru →

A university plans to migrate its student enrollment application from an on-premises VMware vSphere environment to Azure. The application consists of multiple web servers, application servers, and a backend SQL Server database that utilizes cross-database queries. You need to design an assessment strategy that identifies all inter-server network dependencies while avoiding the installation of software agents on the VMs. Which action should you recommend?

Cevabı ve açıklamayı göster

Cevap: Configure agentless dependency analysis by deploying the Azure Migrate appliance and configuring vCenter Server credentials.

Cevap

Configure agentless dependency analysis by deploying the Azure Migrate appliance and configuring vCenter Server credentials.
Deploying the Azure Migrate appliance and configuring agentless dependency analysis is the correct approach. It permits the discovery of network connection details directly through the hypervisor using vCenter Server credentials, ensuring zero agent installation overhead on the target virtual machines.

Adım Adım Çözüm

1
Analyze the constraints and architectural requirements of the migration.
The migration targets an on-premises VMware vSphere environment and requires mapping server connections without installing agents.
Allows selecting a dependency mapping mechanism that meets the agentless requirement.
2
Evaluate the capability of Azure Migrate dependency analysis options.
Agentless dependency analysis for VMware is identified as the solution since it collects data directly from the hypervisor.
Ensures that VM guest-level changes or agents are not required.
3
Determine the configuration steps for agentless discovery.
Deploying the Azure Migrate appliance and providing vCenter Server credentials enables the required metadata and dependency mapping.
Establishes the integration needed to map the application components and network paths.

Anahtar Kavram

Evaluating and designing an agentless dependency assessment strategy using Azure Migrate for VMware workloads.
Tahmini Süre:2m 0s
Soru 342Soru →

A company is designing a regional web-based application in the North Europe region. The application is hosted on five Azure Virtual Machines, each configured with a Basic SKU public IP address for administrative access. You need to design a load balancing solution to distribute incoming HTTP and HTTPS traffic across these virtual machines. The solution must meet the following requirements:
- Route traffic based on the URL path (e.g., `/api/*` and `/web/*` to different backend pools).
- Terminate SSL/TLS sessions at the load balancer level to offload decryption overhead.
- Keep the existing virtual machines and their Basic SKU public IP configurations without modification.
- Restrict all traffic distribution to the regional level.

Which Azure load balancing service should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Application Gateway (Standard v2)

Cevap

Azure Application Gateway (Standard v2)
Azure Application Gateway (Standard v2) is the correct service because it is a regional Layer 7 load balancer that fully supports path-based routing (e.g., `/api/*`) and SSL/TLS termination. Since it communicates with the backend virtual machines using their private IP addresses within the virtual network, the VMs' existing Basic SKU public IP configurations will not cause any SKU mismatch validation conflicts.

Adım Adım Çözüm

1
Analyze the layer routing and protocol requirements.
The application requires HTTP/HTTPS routing, SSL/TLS termination, and URL path-based routing. This necessitates a Layer 7 (application-layer) load balancer, ruling out Layer 4 load balancers (Azure Load Balancer) and DNS-based routers (Azure Traffic Manager).
URL path-based routing and SSL termination are only available on Layer 7 load balancing services.
2
Analyze the regionality and network scope.
The application must be restricted to the regional level (North Europe). Azure Application Gateway is a regional service, which fits this requirement.
Azure Front Door is a global service and would not satisfy the regional restriction constraint.
3
Evaluate the backend SKU compatibility constraints.
The backend virtual machines have Basic SKU public IP addresses. While Azure Standard Load Balancer prevents backend pool membership for VMs with Basic SKU public IPs, Azure Application Gateway routes traffic using private IP addresses within the virtual network. Thus, Application Gateway avoids the SKU mismatch validation error and allows the VMs to retain their Basic SKU public IPs.
Application Gateway connects to backends via private IP addresses, bypassing any public IP SKU mismatch constraints.

Anahtar Kavram

Selecting between Azure Layer 4 and Layer 7 load balancing solutions while respecting SKU compatibility constraints.
Tahmini Süre:2m 0s
Soru 343Soru →

An organization is designing a regional load balancing solution for a web application in the West US 2 region. The application runs on Azure Virtual Machines that require direct inbound Internet access for administrative tasks and are configured with Basic SKU public IP addresses. The new load balancer must meet the following requirements:
- Distribute traffic within the West US 2 region only.
- Support SSL/TLS termination at the load balancer level.
- Route requests to different backend pools based on the URL path.
- Avoid configuration or validation errors when integrating with the existing virtual machines.

Which load balancing solution should you design?

Cevabı ve açıklamayı göster

Cevap: Azure Application Gateway (Standard v2) configured to target the backend virtual machines using their private IP addresses.

Cevap

Azure Application Gateway (Standard v2) configured to target the backend virtual machines using their private IP addresses.
Azure Application Gateway (Standard v2) is a regional Layer 7 load balancer that supports SSL/TLS termination and URL path-based routing. By configuring the backend pool to target the virtual machines' private IP addresses, the application gateway bypasses any configuration or validation conflicts related to the Basic SKU public IP addresses on the virtual machines' network interfaces.

Adım Adım Çözüm

1
Analyze the protocol and routing requirements.
The solution requires Layer 7 capabilities (SSL/TLS termination and URL path-based routing). This rules out Layer 4 load balancers (Azure Load Balancer) and DNS-based routing (Azure Traffic Manager).
SSL/TLS termination and URL-based routing are application-layer features.
2
Analyze the regional and SKU constraints.
The solution must be regional, which points to Azure Application Gateway. The backend VMs have Basic SKU public IPs. To avoid SKU mismatch validation errors, the load balancer should communicate with the VMs using their private IP addresses.
Standard SKU load balancing resources cannot be associated directly with Basic SKU public IP resources on the same network interfaces.
3
Select the compliant Azure load balancing service and configuration.
Configure Azure Application Gateway (Standard v2) with a Standard SKU public IP for its frontend and reference the backend VMs using their private IP addresses.
This configuration satisfies all Layer 7 requirements, regional scope, and avoids SKU mismatch conflicts.

Anahtar Kavram

Selecting the appropriate regional Layer 7 load balancer (Application Gateway) and avoiding SKU mismatches by utilizing private IP backend routing.
Soru 344Soru →

A company plans to migrate a legacy inventory application from their on-premises datacenter to Azure. The application consists of several physical Windows servers and a database tier running on SQL Server. The database tier relies on SQL Server Agent jobs for nightly processing and performs cross-database queries across two databases on the same server instance. The company's security policy strictly prohibits the installation of any monitoring agents or software on the production servers. Additionally, you must synchronize on-premises user identities to Microsoft Entra ID with minimal administrative effort and no extra on-premises infrastructure.

You need to design a migration assessment and target architecture strategy.

Which strategy should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy the Azure Migrate appliance to perform agentless discovery and agentless dependency mapping, recommend Azure SQL Managed Instance as the target database tier, and use Microsoft Entra Connect with Password Hash Synchronization (PHS).

Cevap

Deploy the Azure Migrate appliance to perform agentless discovery and agentless dependency mapping, recommend Azure SQL Managed Instance as the target database tier, and use Microsoft Entra Connect with Password Hash Synchronization (PHS).
The correct strategy combines the Azure Migrate appliance for agentless discovery and dependency mapping, Azure SQL Managed Instance for SQL Server Agent and cross-database query support, and Password Hash Synchronization (PHS) for low-overhead identity synchronization. The Azure Migrate appliance uses credentials to perform agentless dependency mapping on physical servers, ensuring compliance with the policy of not installing agents. Azure SQL Managed Instance matches the legacy SQL Server features required. PHS synchronizes on-premises AD DS user accounts without requiring additional federation servers.

Adım Adım Çözüm

1
Evaluate the database tier requirements to determine the target Azure service.
Since the legacy SQL Server databases rely on SQL Server Agent jobs and cross-database queries, Azure SQL Managed Instance is identified as the correct target service because Azure SQL Database single database does not support these instance-scoped features.
Choosing the correct SQL deployment option ensures compatibility and avoids costly application refactoring.
2
Select the assessment and dependency mapping method based on organizational security policies.
Because security policies prohibit the installation of agents on production servers, agentless discovery and agentless dependency mapping via the Azure Migrate appliance must be selected.
This allows the collection of dependency data (such as network connections) using server credentials without deploying local agents on the target physical servers.
3
Determine the hybrid identity synchronization mechanism.
Password Hash Synchronization (PHS) is selected because it meets the requirement of minimal administrative effort and requires no additional on-premises servers.
Using Active Directory Federation Services (AD FS) would introduce unnecessary infrastructure complexity and administrative overhead.

Anahtar Kavram

Azure Migrate physical server assessment, SQL tier compatibility, and hybrid identity selection.
Soru 345Soru →

A logistics company plans to migrate its legacy dispatching and routing platform to Azure. The on-premises environment consists of 12 physical Windows Server servers and 8 VMware vSphere virtual machines (VMs). The database backend runs on SQL Server 2016 and heavily relies on SQL Server Agent, CLR integration, and cross-database queries. Currently, users authenticate against an on-premises Active Directory Domain Services (AD DS) domain.

The company has the following requirements for the migration:
1. Identify all active network connections and dependencies between the application servers to minimize post-migration latency.
2. Recommend an Azure SQL database hosting model that supports all SQL Server 2016 features with minimal management overhead.
3. Integrate the on-premises AD DS with Microsoft Entra ID to allow users to sign in with their existing credentials, while keeping infrastructure complexity and cost to a minimum.

Which of the following migration assessment and strategy designs meets all the requirements?

Cevabı ve açıklamayı göster

Cevap: Perform dependency analysis using the Azure Migrate appliance to visualize server connections, recommend migrating the databases to Azure SQL Managed Instance, and configure Microsoft Entra Connect with Password Hash Synchronization (PHS).

Cevap

Perform dependency analysis using the Azure Migrate appliance to visualize server connections, recommend migrating the databases to Azure SQL Managed Instance, and configure Microsoft Entra Connect with Password Hash Synchronization (PHS).
The correct option is the one that recommends using the Azure Migrate appliance for dependency mapping, migrating to Azure SQL Managed Instance, and configuring Microsoft Entra Connect with Password Hash Synchronization (PHS). Azure SQL Managed Instance is the only fully managed relational database service in Azure that provides near 100% compatibility with on-premises SQL Server databases, supporting features like CLR, SQL Server Agent, and cross-database queries. Password Hash Synchronization (PHS) provides a simple and low-cost solution for hybrid identity compared to AD FS. Using the Azure Migrate appliance for dependency analysis before migrating ensures that all dependent servers are grouped together, preventing network latency or connectivity problems.

Adım Adım Çözüm

1
Evaluate the database tier requirements.
Since the legacy SQL Server databases require SQL Server Agent, CLR integration, and cross-database queries, Azure SQL Managed Instance must be selected instead of Azure SQL Database, which does not support these features natively.
Choosing the correct SQL hosting option ensures application compatibility while keeping management overhead low compared to running SQL Server on Azure VMs.
2
Determine the identity synchronization method.
Password Hash Synchronization (PHS) is selected.
PHS allows users to authenticate using their on-premises credentials with minimal complexity and cost, avoiding the deployment of high-overhead Active Directory Federation Services (AD FS) servers.
3
Select the dependency assessment approach.
Perform dependency analysis using the Azure Migrate appliance before the migration starts.
Identifying dependencies beforehand ensures that interconnected servers are grouped into the same migration wave, avoiding network performance and latency issues.

Anahtar Kavram

Selecting migration hosting targets, dependency assessments, and hybrid identity solutions in Azure.
Tahmini Süre:1m 30s
Soru 346Soru →

An investment firm plans to migrate a legacy portfolio management system from an on-premises VMware vSphere environment to Azure. The system consists of three web servers and a Microsoft SQL Server database server that hosts multiple databases with active cross-database queries. You need to design a migration assessment strategy that identifies all application dependencies and evaluates database compatibility with Azure. Which two actions should you include in the assessment strategy? (Choose two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Deploy the Azure Migrate appliance to perform agentless dependency analysis on the virtual machines.; Assess the database compatibility for Azure SQL Managed Instance by using the Azure Migrate: Discovery and assessment tool.

Cevap

To perform a successful migration assessment, you should deploy the Azure Migrate appliance to perform agentless dependency analysis on the virtual machines, and assess the database compatibility for Azure SQL Managed Instance by using the Azure Migrate: Discovery and assessment tool.
The correct actions are deploying the Azure Migrate appliance for agentless dependency analysis and performing a database assessment targeting Azure SQL Managed Instance. Agentless dependency analysis helps map all connections between the web servers and database without guest agent overhead, which is critical for planning migration waves. Selecting Azure SQL Managed Instance for assessment is correct because the database uses cross-database queries, which is a feature not supported by Azure SQL Database single databases or elastic pools.

Adım Adım Çözüm

1
Analyze application dependencies to identify workload boundaries.
Identify all communication paths and group the web servers with the SQL Server.
This ensures that no dependent systems are left behind or experience high latency due to split-workload states.
2
Analyze database requirements to select the correct migration destination.
Identify cross-database query usage on the SQL Server.
Cross-database queries are not supported in Azure SQL Database single database/elastic pools, requiring Azure SQL Managed Instance.
3
Run a database-specific assessment using Azure Migrate.
Verify compatibility and identify any potential migration blockers or remediation steps for Azure SQL Managed Instance.
An assessment provides SQL Server-specific migration recommendations and readiness status.

Anahtar Kavram

Migration Assessment and Dependency Strategy for Relational Workloads
Tahmini Süre:2m 0s
Soru 347Soru →

A healthcare provider is redesigning the network architecture for a patient portal application hosted on Azure Virtual Machines in the East US region. The portal requires:

* Path-based routing to direct /imaging/* request traffic to a dedicated backend pool.
* SSL/TLS termination at the load balancing tier.
* High-availability load balancing for a backend database tier using TCP port 1433.

The Virtual Machines currently have Basic SKU Public IP addresses assigned to their Network Interface Cards (NICs) for direct administrative access. You need to design the regional load balancing solution while ensuring compatibility across all tiers.

Which TWO actions should you recommend? (Select TWO)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Deploy an Azure Application Gateway to handle the portal's path-based routing and SSL/TLS termination.; Upgrade the Public IP addresses assigned to the virtual machine NICs to the Standard SKU to support integration with a Standard Load Balancer backend pool.

Cevap

Deploy an Azure Application Gateway to handle the portal's path-based routing and SSL/TLS termination, and upgrade the Public IP addresses assigned to the virtual machine NICs to the Standard SKU to support integration with a Standard Load Balancer backend pool.
Azure Application Gateway is a regional Layer 7 load balancer that supports path-based routing and SSL/TLS termination. For the database tier (TCP 1433), a Standard Load Balancer is required. To prevent validation failures due to SKU mismatch, any public IPs attached to the virtual machines in the Standard Load Balancer's backend pool must be upgraded from the Basic SKU to the Standard SKU.

Adım Adım Çözüm

1
Identify the Layer 7 requirements for the web portal
The requirements of path-based routing for /imaging/* and SSL/TLS termination necessitate a Layer 7 load balancer like Azure Application Gateway.
Layer 4 load balancers cannot inspect HTTP paths or terminate SSL sessions.
2
Determine the requirements for the database tier load balancing
TCP port 1433 load balancing is a Layer 4 workload, which is best served by Azure Load Balancer.
Standard Load Balancer provides low-latency Layer 4 load balancing for TCP protocols like SQL Server.
3
Analyze SKU compatibility between the virtual machines and the Standard Load Balancer
Virtual machines with Basic SKU Public IPs on their NICs cannot join the backend pool of a Standard Load Balancer. They must be upgraded to Standard SKU Public IPs or have their Basic Public IPs removed.
Mixing Basic and Standard SKUs in a load balancer configuration causes validation failures.

Anahtar Kavram

Selecting and integrating Azure load balancing solutions based on protocol, routing, and SKU compatibility constraints.
Soru 348Soru →

An organization is designing a regional high-availability solution in the East US region. The architecture requires deploying a Standard Load Balancer to distribute inbound traffic across three Azure Virtual Machines that are deployed across different Availability Zones. The virtual machines currently have Basic SKU Public IP addresses assigned to their network interfaces for direct administrative access. During validation of the backend pool configuration, the deployment fails.

To ensure the virtual machines can be successfully added to the Standard Load Balancer's backend pool while maintaining zone redundancy, which of the following actions should the architect recommend?

Cevabı ve açıklamayı göster

Cevap: Upgrade the public IP addresses of the virtual machines to the Standard SKU.

Cevap

Upgrade the public IP addresses of the virtual machines to the Standard SKU.
The correct action is to upgrade the public IP addresses of the virtual machines to the Standard SKU. A Standard Load Balancer strictly requires that all virtual machines in its backend pool use the Standard SKU for any associated public IP addresses. This solution enables successful backend validation and retains support for Availability Zones and high availability.

Adım Adım Çözüm

1
Analyze the load balancer SKU and its requirements.
The design utilizes a Standard Load Balancer, which requires that any public IP addresses associated with backend pool virtual machines must also be of the Standard SKU.
Standard SKU resources must be consistently used throughout the load balancer boundary to prevent configuration and validation failures.
2
Evaluate the requirement for zone redundancy.
A Standard Load Balancer and Standard SKU public IPs support Availability Zones, whereas Basic SKU load balancers and Basic public IPs do not.
To satisfy the high-availability and zone redundancy requirements, the architecture must remain on the Standard SKU.
3
Identify the remediation action.
Upgrading the virtual machines' public IP addresses from Basic to Standard SKU satisfies both the Standard Load Balancer validation and the zone redundancy constraints.
This alignment allows the virtual machines to be members of the Standard Load Balancer's backend pool without losing zone redundancy features.

Anahtar Kavram

Standard SKU load balancers require all backend resources with public IP addresses to use the Standard SKU to ensure compatibility and support features like Availability Zones.
Soru 349Soru →

A healthcare provider plans to migrate a medical imaging portal and archiving application from an on-premises Hyper-V environment to Azure. The application architecture includes a front-end IIS web portal, an application tier, a SQL Server database cluster utilizing cross-database queries, and a network file share. To ensure a successful migration, you must identify all active network connections, ports, and dependencies between the application components and external systems before grouping servers into migration waves.

Which approach should you include in the migration assessment strategy?

Cevabı ve açıklamayı göster

Cevap: Deploy the Azure Migrate appliance to the Hyper-V host, configure agentless dependency analysis to discover network connections, and recommend Azure SQL Managed Instance as the target for the database tier.

Cevap

Deploy the Azure Migrate appliance to the Hyper-V host, configure agentless dependency analysis to discover network connections, and recommend Azure SQL Managed Instance as the target for the database tier.
Deploying the Azure Migrate appliance to perform agentless dependency analysis is the correct approach to discover active connections and ports without VM agent installation overhead. Furthermore, Azure SQL Managed Instance is the correct migration target for the SQL Server cluster because it natively supports legacy features like cross-database queries.

Adım Adım Çözüm

1
Select the discovery tool and deployment model
The Azure Migrate appliance is deployed to the on-premises Hyper-V host to discover virtual machines and collect metadata.
An appliance-based discovery is required to scan Hyper-V environments and gather performance data and dependency metrics agentlessly.
2
Analyze workload network dependencies
Agentless dependency analysis is enabled to identify active TCP connections, ports, and communication paths between tiers.
This ensures that dependent servers (like the application tier and network file share) are grouped into the same migration wave, minimizing post-migration latency and service disruption.
3
Map database features to target Azure services
Azure SQL Managed Instance is chosen as the target database tier rather than Azure SQL Database.
Azure SQL Managed Instance provides near 100% compatibility with the SQL Server database engine, supporting cross-database queries required by the application.

Anahtar Kavram

Azure Migrate dependency assessment and target tier selection for SQL Server migration
Tahmini Süre:2m 0s
Soru 350Soru →

An enterprise is designing a high-performance, multi-region web application that will be hosted in Azure. The design must satisfy the following requirements:
- Route incoming HTTPS user traffic to the nearest regional deployment to minimize latency.
- Perform SSL/TLS termination at the global edge to reduce handshake latency, but enforce end-to-end SSL encryption to the backend servers.
- Inspect and filter web traffic using a Web Application Firewall (WAF) at both the global entry point and the regional boundaries.
- Direct traffic to different backend web pools based on the URL path (e.g., routing /images/* to storage and /api/* to application servers).

Which two services should you recommend to meet these requirements? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Azure Front Door; Azure Application Gateway

Cevap

Azure Front Door and Azure Application Gateway
Azure Front Door and Azure Application Gateway are the correct services. Azure Front Door operates at the global edge to provide SSL/TLS termination closest to the user, global HTTP/HTTPS routing, and WAF protection. Azure Application Gateway operates at the regional level, providing URL path-based routing and regional WAF inspection before directing traffic to backend application pools.

Adım Adım Çözüm

1
Analyze global routing and edge security requirements.
Identify that global latency optimization, SSL/TLS termination at the edge, and global WAF require Azure Front Door.
Azure Front Door is Azure's global web load balancer that handles Layer 7 traffic at edge locations.
2
Analyze regional routing and backend integration requirements.
Identify that regional URL path-based routing and regional WAF require Azure Application Gateway.
Azure Application Gateway is a regional Layer 7 load balancer that handles application-level routing within a virtual network.
3
Evaluate other options against Layer 7 and security capabilities.
Reject Azure Traffic Manager (L3/DNS only) and Azure Load Balancer (L4 only) as they lack SSL/TLS termination, path-based routing, and WAF support.
Traffic Manager and Azure Load Balancer do not operate at the application layer (Layer 7).

Anahtar Kavram

Combining global and regional Layer 7 load balancing services to meet latency, security, and path-routing requirements.
Soru 351Soru →

An organization is migrating a legacy high-throughput inventory application to Azure. The application uses a custom TCP-based protocol on port 8080. The architecture requires deploying three virtual machines (VMs) in a single Azure region, distributed across multiple Availability Zones to ensure zone redundancy. The VMs are currently associated with Basic SKU Public IP addresses. You need to design a load balancing solution to distribute the client TCP traffic to the VMs.

Which design action should you recommend?

Cevabı ve açıklamayı göster

Cevap: Reassociate the virtual machines with Standard SKU public IP addresses and deploy a Standard Load Balancer.

Cevap

Reassociate the virtual machines with Standard SKU public IP addresses and deploy a Standard Load Balancer.
To support virtual machines distributed across multiple Availability Zones, a Standard Load Balancer is required because a Basic Load Balancer does not support zone-redundant backend pools. Additionally, Azure requires SKU consistency, meaning virtual machines in a Standard Load Balancer's backend pool must be associated with Standard SKU public IP addresses rather than Basic SKU public IP addresses.

Adım Adım Çözüm

1
Identify the protocol and zonal requirements.
The application uses a custom TCP protocol on port 8080, and the VMs are distributed across multiple Availability Zones.
Layer 7 load balancers like Azure Application Gateway or Azure Front Door are not suitable for non-HTTP/S custom TCP protocols. An Azure Load Balancer (Layer 4) is required.
2
Evaluate the required Load Balancer SKU for Availability Zones.
A Standard Load Balancer is selected because the Basic Load Balancer does not support backend pools containing VMs in multiple Availability Zones.
Only the Standard SKU Azure Load Balancer supports zone-redundant backend configurations.
3
Resolve IP address SKU mismatch constraints.
The VMs must have their Basic SKU Public IP addresses changed to Standard SKU.
Azure enforces strict SKU alignment; a Standard Load Balancer cannot target backend network interfaces associated with Basic SKU Public IP resources.

Anahtar Kavram

Azure Load Balancer SKU compatibility and Availability Zone support constraints.
Tahmini Süre:2m 0s
Soru 352Soru →

An organization is designing a high-availability infrastructure in a single Azure region for a suite of services hosted on Azure Virtual Machines. The VMs currently utilize Standard SKU public IP addresses. The infrastructure must meet the following requirements:

- Handle web application traffic (HTTPS) with support for URL-path routing and SSL/TLS termination.
- Load balance incoming custom TCP traffic on port 9500 to a separate backend pool of virtual machines.
- Avoid mixing Basic and Standard SKU resources to prevent validation errors.

Which two load balancing services should you include in the design?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Azure Application Gateway (Standard v2 SKU); Azure Load Balancer (Standard SKU)

Cevap

The load balancing design should include Azure Application Gateway (Standard v2 SKU) for Layer 7 web traffic and Azure Load Balancer (Standard SKU) for Layer 4 TCP traffic.
Azure Application Gateway (Standard v2 SKU) is correct because it operates at Layer 7, providing the required SSL/TLS termination and URL-path routing for HTTPS traffic. Azure Load Balancer (Standard SKU) is correct because it operates at Layer 4, providing high-throughput load balancing for custom TCP traffic on port 9500. Additionally, since the backend VMs use Standard SKU public IP addresses, using the Standard SKU Load Balancer avoids validation errors associated with mixing Basic and Standard SKUs.

Adım Adım Çözüm

1
Analyze the web traffic requirements (HTTPS, URL-path routing, and SSL/TLS termination).
Determine that the HTTPS web traffic requires a Layer 7 load balancer. Identify Azure Application Gateway as the regional load balancer that supports SSL/TLS offloading and path-based routing.
Azure Application Gateway operates at the application layer (Layer 7) and supports URL-path routing and SSL offloading.
2
Analyze the custom TCP traffic on port 9500.
Determine that the TCP traffic requires a Layer 4 load balancer since it does not utilize HTTP/S protocols.
Azure Load Balancer is a high-throughput, low-latency Layer 4 load balancer that handles TCP/UDP traffic.
3
Evaluate the SKU compatibility requirements.
Select the Standard SKU for the Azure Load Balancer because the virtual machines are configured with Standard SKU public IP addresses.
Azure enforces strict SKU matching rules where Basic SKU and Standard SKU resources cannot be mixed in the same configuration.

Anahtar Kavram

Selecting and combining Azure load balancing services based on layer features (Layer 4 vs Layer 7) and SKU compatibility requirements.
Soru 353Soru →

A retail company plans to host a customer-facing web portal on Azure Virtual Machines in the West Europe region. The architecture requires a load balancing solution that can perform SSL/TLS termination, route traffic to different backend virtual machines based on the incoming request path (such as /checkout and /products), and support cookie-based session affinity. The backend virtual machines currently have network interfaces associated with Basic SKU public IP addresses.

Which load balancing solution should the company implement to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Azure Application Gateway Standard v2 utilizing the private IP addresses of the virtual machines in the backend pool

Cevap

Azure Application Gateway Standard v2 utilizing the private IP addresses of the virtual machines in the backend pool
The correct option is the choice recommending Azure Application Gateway Standard v2. It operates at Layer 7, fulfilling the requirements for SSL/TLS termination, path-based routing, and cookie-based session affinity. Because Application Gateway targets the private IP addresses of the backend virtual machines, it avoids the validation failures that occur when mixing Basic SKU public IP addresses with Standard SKU load balancing resources.

Adım Adım Çözüm

1
Analyze the application layer requirements
The requirements for SSL/TLS termination, URL path-based routing, and cookie-based session affinity dictate a Layer 7 load balancer.
Layer 4 balancers (like Azure Load Balancer) and DNS-based routing (like Traffic Manager) do not inspect application headers and cannot perform these functions.
2
Evaluate the IP SKU constraints of the backend virtual machines
The backend virtual machines have Basic SKU public IP addresses associated with their network interfaces.
This prevents them from being placed in the backend pool of a Standard SKU Load Balancer directly due to the SKU mismatch rule.
3
Select the appropriate regional Layer 7 service that avoids SKU mismatch
Azure Application Gateway Standard v2 connects to backends via private IP addresses, bypassing public IP SKU restrictions.
Since Application Gateway operates in a virtual network and routes to the private IPs of the VMs, it does not conflict with their Basic SKU public IPs.

Anahtar Kavram

Selecting Azure Application Gateway to satisfy Layer 7 routing and SSL requirements while avoiding public IP SKU mismatch constraints on backend virtual machines
Soru 354Soru →

A company plans to deploy a high-performance backend application on five Azure Virtual Machines in the East US region. Each virtual machine has a dedicated public IP address utilizing the Basic SKU for direct management. You need to design a load balancing solution to distribute inbound TCP traffic across these virtual machines using a regional load balancer. The design must support availability zones and provide a 99.99% SLA. Which load balancing configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy an Azure Standard Load Balancer, and upgrade the public IP addresses of the virtual machines to the Standard SKU.

Cevap

Deploy an Azure Standard Load Balancer, and upgrade the public IP addresses of the virtual machines to the Standard SKU.
Deploying an Azure Standard Load Balancer and upgrading the virtual machine public IPs to the Standard SKU is the correct design. The Standard Load Balancer is required to meet the 99.99% SLA and support availability zones. Azure requires that any public IP address assigned to a virtual machine network interface (NIC) in the backend pool of a Standard Load Balancer must match the load balancer's SKU (Standard SKU). Therefore, upgrading the virtual machines' public IPs to the Standard SKU satisfies both compatibility and service-level requirements.

Adım Adım Çözüm

1
Analyze SLA and availability zone requirements
Standard SKU is required for Azure Load Balancer to support availability zones and the 99.99% SLA.
Basic SKU Load Balancers do not offer availability zone redundancy or the required SLA.
2
Evaluate compatibility of the backend pool resources
The virtual machines have Basic SKU public IPs attached to their NICs, which are incompatible with the Standard Load Balancer's backend pool.
Azure enforces that all public IP resources associated with network interfaces in a Standard Load Balancer's backend pool must be of the Standard SKU.
3
Formulate the remediation plan
Upgrade the public IP addresses of the virtual machines to the Standard SKU and deploy a Standard Load Balancer.
This allows the virtual machines to be added to the Standard Load Balancer's backend pool while maintaining direct public IP management.

Anahtar Kavram

Load Balancer SKU compatibility and backend pool IP SKU matching constraints
Soru 355Soru →

You are designing the networking architecture for an enterprise web application hosted on Azure Virtual Machines in the East US region. The design must meet the following requirements:
- Support Layer 7 load balancing with SSL/TLS termination and URL path-based routing (routing `/static/*` and `/api/*` to separate backend VM pools).
- Support internal Layer 4 load balancing of TCP traffic on port 8080 for backend synchronization.
- Ensure the entire architecture supports availability zones for high availability and regional resiliency.
- The virtual machines in the backend pools are currently configured with Basic SKU Public IP addresses.

Which two actions should you recommend to meet these requirements? (Select two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Deploy Azure Application Gateway (Standard v2) to manage the HTTP/S traffic, handle SSL/TLS termination, and execute path-based routing.; Upgrade the virtual machine Public IP addresses from Basic SKU to Standard SKU to allow them to be associated with an internal Azure Standard Load Balancer.

Cevap

Deploy Azure Application Gateway (Standard v2) to manage HTTP/S routing and upgrade the virtual machine Public IP addresses to Standard SKU to support an internal Azure Standard Load Balancer.
Deploying Azure Application Gateway (Standard v2) provides the required Layer 7 features (SSL termination, path-based routing) and supports availability zones. Upgrading the VM Public IP addresses from Basic to Standard SKU is necessary to allow them to connect to the internal Azure Standard Load Balancer for Layer 4 TCP traffic, ensuring SKU consistency and enabling availability zones.

Adım Adım Çözüm

1
Evaluate the Layer 7 requirements for SSL/TLS termination and URL path-based routing.
Select Azure Application Gateway (Standard v2) because it is a regional Layer 7 load balancer that natively supports SSL termination, path-based routing rules, and availability zones.
Alternative Layer 4 services or DNS-based routing cannot inspect HTTP/S paths or decrypt traffic for routing decisions.
2
Evaluate the Layer 4 requirements for internal TCP port 8080 traffic and availability zones.
Select an internal Azure Standard Load Balancer, as the Standard SKU is required to support zone redundancy.
Basic Load Balancers do not offer zone-redundancy features, making Standard Load Balancer the correct architectural choice.
3
Address resource SKU compatibility constraints.
Identify that the virtual machines currently utilize Basic SKU Public IP addresses. Recommend upgrading these Public IP addresses to Standard SKU to allow integration with the internal Standard Load Balancer.
Azure enforces SKU alignment. A Standard Load Balancer cannot serve backend virtual machines that are associated with Basic SKU Public IP addresses; attempting to do so results in a configuration mismatch error.

Anahtar Kavram

Azure load balancer SKU compatibility and Layer 7 vs Layer 4 routing capabilities
Tahmini Süre:2m 0s
Soru 356Soru →

An organization is designing the load balancing architecture for a multi-tier web application in the East US region. The solution must meet the following requirements:
- Web Tier: Requires global distribution, SSL/TLS termination, and HTTP/S URL-path-based routing to support different backend services.
- Database Tier: Requires regional load balancing of TCP port 14331433 traffic across database Virtual Machines (VMs) distributed across three availability zones. The VMs currently utilize Basic SKU Public IP addresses for legacy remote access.

You are designing the database tier load balancing solution. Which configuration should you recommend to meet the database tier requirements while preventing validation errors?

Cevabı ve açıklamayı göster

Cevap: Upgrade the VM Public IP addresses to Standard SKU and deploy an Azure Standard Load Balancer.

Cevap

Upgrade the VM Public IP addresses to Standard SKU and deploy an Azure Standard Load Balancer.
Upgrading the VM Public IP addresses to Standard SKU and deploying an Azure Standard Load Balancer is correct because the Standard Load Balancer is required to achieve zone-redundancy and support the distribution of TCP traffic across three availability zones. However, Azure enforces SKU consistency; standard-tier resources cannot be mixed with basic-tier resources in the backend configuration. Therefore, the VMs' existing Basic SKU Public IP addresses must be upgraded to Standard SKU to match the Standard Load Balancer, avoiding validation failures during deployment.

Adım Adım Çözüm

1
Identify the protocol and high-availability requirements of the database tier.
The database tier requires TCP port 14331433 load balancing (Layer 4) with zone-redundancy.
This narrows down the potential load balancing services to those supporting regional Layer 4 load balancing and availability zones.
2
Evaluate Azure load balancer SKU capabilities for zone-redundancy.
Azure Standard Load Balancer supports zone-redundant frontends, whereas Azure Basic Load Balancer does not.
This establishes that a Standard Load Balancer must be used to meet the high availability requirements.
3
Resolve the SKU mismatch between the selected load balancer and the database VM configurations.
Identify that the database VMs have Basic SKU Public IPs, which are incompatible with a Standard Load Balancer's backend pool. The VM Public IPs must be upgraded to Standard SKU.
Azure requires SKU consistency within the load balancing path to prevent validation errors.

Anahtar Kavram

Azure Load Balancer SKU alignment and availability zone support.
Soru 357Soru →

An enterprise is designing a multi-region web application deployment on Azure Virtual Machines. The design must satisfy the following architectural requirements:

* Provide global HTTP/S load balancing with SSL/TLS termination and Web Application Firewall (WAF) protection at the network edge.
* Enable regional routing within each Azure region to distribute traffic to separate backend pools based on the URL path (such as routing `/api/*` and `/static/*` differently).
* Ensure compatibility with backend virtual machines that are configured with Standard SKU public IP addresses.

Which two load balancing services should you include in the architectural design?

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Azure Front Door; Azure Application Gateway

Cevap

Azure Front Door and Azure Application Gateway
To satisfy all requirements, the design must use Azure Front Door for global Layer 7 traffic routing, SSL/TLS termination, and WAF protection at the edge. It must also use Azure Application Gateway at the regional level to inspect URL paths and direct traffic to the appropriate backend pools. Both services support integration with backend VMs using Standard SKU resources.

Adım Adım Çözüm

1
Analyze the global load balancing requirement.
Azure Front Door is selected for global Layer 7 traffic routing, providing edge SSL/TLS termination and WAF capabilities.
Global routing with HTTP/S offloading requires an edge service that supports Layer 7 features.
2
Analyze the regional routing requirement.
Azure Application Gateway is selected to perform regional URL path-based routing inside each region.
URL path-based routing requires a regional Layer 7 load balancer that can inspect HTTP request paths.
3
Verify SKU compatibility with the backend virtual machines.
Ensure Standard SKU resources are used consistently.
Azure Application Gateway and Azure Front Door do not impose Basic SKU load balancer constraints, keeping the Standard SKU public IP virtual machines compatible.

Anahtar Kavram

Combining global and regional Layer 7 load balancing services while maintaining SKU compatibility.
Soru 358Soru →

A financial services startup is modernizing a regional mobile banking API hosting solution in the North Europe region. The API is hosted on a pool of Azure Virtual Machines deployed within a private subnet of a virtual network.

The solution must satisfy the following technical requirements:
- Distribute incoming HTTPS traffic based on the URL path (e.g., routing `/accounts/*` and `/transfers/*` to different backend pools).
- Perform SSL/TLS termination at the load balancer level to offload decryption overhead from the virtual machines.
- Ensure the backend virtual machines remain isolated from the public internet by using only private IP addresses for backend pool communication.
- Prevent any validation or connectivity issues related to the virtual machines, which currently have Basic SKU Public IP addresses associated with their network interfaces for administrative troubleshooting.

Which load balancing solution should you design?

Cevabı ve açıklamayı göster

Cevap: Deploy an Azure Application Gateway in the virtual network.

Cevap

Deploy an Azure Application Gateway in the virtual network.
The correct design is to deploy an Azure Application Gateway. As a regional Layer 7 load balancer, it supports the required HTTP/HTTPS routing features, including URL path-based routing and SSL/TLS termination. Because the Application Gateway communicates with the backend virtual machines using their private IP addresses inside the virtual network, the existing Basic SKU Public IP addresses on the virtual machines' network interfaces do not cause any compatibility or SKU validation errors.

Adım Adım Çözüm

1
Identify the application layer requirements.
The requirements demand URL path-based routing and SSL/TLS termination, which are Layer 7 (application layer) capabilities.
Layer 4 load balancers (TCP/UDP) cannot inspect the HTTP/HTTPS request headers or paths to perform routing or decryption.
2
Evaluate regional vs global load balancing options.
The solution is regional (North Europe) and requires backend isolation within a private subnet.
Global load balancers like Azure Front Door or Traffic Manager are optimized for multi-region entry points and typically require public backend endpoints unless integrated with complex private services.
3
Analyze backend virtual machine SKU compatibility.
The virtual machines have Basic SKU Public IPs. Using an Application Gateway routes traffic using private IPs and avoids SKU mismatch conflicts.
Standard Load Balancers fail validation when combined with Basic SKU resources. Application Gateway integrates using internal private IPs, bypassing public IP SKU restrictions.

Anahtar Kavram

Selecting Azure load balancing services based on Layer 7 requirements (SSL termination, path-based routing) and backend SKU compatibility.
Tahmini Süre:1m 30s
Soru 359Soru →

An enterprise is designing a global web application that will be deployed across the East US and West Europe regions. The application requires global HTTP/S load balancing with SSL/TLS termination at the edge, along with regional path-based routing and Web Application Firewall (WAF) protection inside each regional virtual network. Additionally, the regional ingress points must be provisioned using a public IP configuration that is compatible with the regional load balancing service SKU. Which two services and configurations should you include in the design to meet these requirements? (Choose two.)

Geçerli olan tümünü seçin

Cevabı ve açıklamayı göster

Cevap: Azure Front Door; Azure Application Gateway V2 associated with a Standard SKU public IP address

Cevap

The correct design should include Azure Front Door to handle global traffic routing and SSL/TLS termination at the edge, and Azure Application Gateway V2 configured with a Standard SKU public IP address to handle regional path-based routing and WAF protection.
The combination of Azure Front Door and Azure Application Gateway V2 with a Standard SKU public IP address satisfies all design constraints. Azure Front Door handles global Layer 7 traffic routing and SSL/TLS termination at the edge. Within each region, Azure Application Gateway V2 provides localized path-based routing, WAF capabilities, and SSL/TLS termination closer to the backend resources. Using a Standard SKU public IP address is mandatory for Application Gateway V2, preventing deployment errors.

Adım Adım Çözüm

1
Analyze the global routing requirements.
Identify that the application requires global HTTP/S load balancing, edge SSL/TLS termination, and routing across multiple regions. Azure Front Door fits this layer.
Azure Front Door is a global Layer 7 load balancer that handles HTTP/S traffic and SSL termination at the edge.
2
Analyze the regional routing and security requirements.
Identify that the application requires WAF protection, localized path-based routing, and SSL termination within the virtual network. Azure Application Gateway V2 fits this layer.
Azure Application Gateway is a regional Layer 7 load balancer providing path-based routing, SSL termination, and WAF integration.
3
Evaluate SKU compatibility for the public IP endpoints.
Confirm that Azure Application Gateway V2 requires a Standard SKU public IP. Using a Basic SKU public IP will fail deployment validation.
Azure resource rules forbid mixing Basic SKU public IPs with Standard SKU/V2 resources like Application Gateway V2.

Anahtar Kavram

Multi-tier global and regional application load balancing using Azure Front Door and Azure Application Gateway V2 while adhering to SKU compatibility requirements.
Tahmini Süre:2m 0s
Soru 360Soru →

An enterprise is modernizing a regional application hosted on a backend pool of Azure Virtual Machines in the East US region. The solution requires Layer 44 load balancing for incoming TCP traffic, regional distribution, and high availability across Availability Zones. The design does not require SSL/TLS termination or URL-path-based routing. The virtual machines are currently configured with Basic SKU public IP addresses directly on their network interfaces. You need to recommend a load balancing configuration that meets these requirements. Which configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy an Azure Standard Load Balancer and upgrade the virtual machines' public IP addresses to Standard SKU.

Cevap

Deploy an Azure Standard Load Balancer and upgrade the virtual machines' public IP addresses to Standard SKU.
Deploying an Azure Standard Load Balancer meets the requirements because it operates at Layer 44 (TCP/UDP) and supports Availability Zones for high availability. However, to add the virtual machines to its backend pool, any public IP addresses assigned directly to their network interfaces must match the load balancer's SKU. Therefore, upgrading the virtual machines' public IP addresses from Basic to Standard SKU is required to avoid configuration and validation failures.

Adım Adım Çözüm

1
Analyze the traffic and routing requirements.
The application requires Layer 44 regional TCP load balancing and Availability Zones support without SSL/TLS termination or HTTP path-based routing.
This identifies Azure Load Balancer as the appropriate service, specifically the Standard SKU since Basic Load Balancer does not support Availability Zones.
2
Evaluate the existing virtual machine configurations.
The virtual machines have Basic SKU public IP addresses assigned to their network interfaces.
Azure Standard Load Balancer requires all public IP addresses associated with backend virtual machines to be of the Standard SKU to avoid configuration mismatch.
3
Formulate the final load balancer and IP address configuration.
An Azure Standard Load Balancer is selected, and the virtual machines' public IPs are upgraded to Standard SKU.
This ensures the configuration passes validation and satisfies the zone-redundancy and SKU compatibility requirements.

Anahtar Kavram

Azure Load Balancer SKU requirements and availability zone support.
ÖncekiSayfa 18 / 18