Design Infrastructure Solutions

360 soru

Soru 121Soru

An enterprise is designing a hub-and-spoke virtual network topology in Azure. The hub virtual network, `vnet-hub-weur` (10.200.0.0/1610.200.0.0/16), contains a Virtual Network Gateway connected to an on-premises network. A spoke virtual network, `vnet-spoke-prod` (10.201.0.0/1610.201.0.0/16), contains a workload subnet named `snet-app` (10.201.1.0/2410.201.1.0/24). A pair of network virtual appliances (NVAs) is deployed in the hub and sits behind an internal load balancer at 10.200.4.10010.200.4.100.

The Virtual Network Gateway receives BGP route advertisements from on-premises, including a summary route of 172.16.0.0/12172.16.0.0/12 and a specific database subnet prefix of 172.16.50.0/24172.16.50.0/24. To inspect all on-premises bound traffic, you associate a route table named `rt-spoke-app` with the `snet-app` subnet and add a user-defined route (UDR) for 172.16.0.0/12172.16.0.0/12 pointing to the load balancer at 10.200.4.10010.200.4.100. Gateway route propagation is enabled on `rt-spoke-app`.

During testing, you observe that traffic from `snet-app` to the database tier (172.16.50.10172.16.50.10) bypasses the NVAs and goes directly to the Virtual Network Gateway. Which action should you recommend to ensure all on-premises bound traffic is inspected by the NVAs?

Cevabı ve açıklamayı göster

Cevap: Disable gateway route propagation on the `rt-spoke-app` route table.

Cevap

Disable gateway route propagation on the `rt-spoke-app` route table.
Disabling gateway route propagation on the spoke subnet's route table prevents the BGP-learned routes from on-premises from being dynamically injected into the spoke subnet. This removes the specific BGP route for the database tier. Consequently, traffic to the database subnet matches the user-defined route for the summarized prefix, forcing it to route through the network virtual appliance (NVA) first.

Adım Adım Çözüm

1
Analyze how BGP routes propagate to the spoke subnet.
Since gateway route propagation is enabled, the BGP routes 172.16.0.0/12172.16.0.0/12 and 172.16.50.0/24172.16.50.0/24 are dynamically added to the subnet's effective route table with the next hop set to Virtual Network Gateway.
This establishes the baseline routing table of the spoke subnet before user overrides.
2
Evaluate the route selection logic for database traffic (172.16.50.10172.16.50.10).
The destination matches both the BGP route (172.16.50.0/24172.16.50.0/24) and the UDR (172.16.0.0/12172.16.0.0/12). In Azure, routes are evaluated using the Longest Prefix Match (LPM) rule. Because a /24 prefix is longer (more specific) than a /12 prefix, the BGP route takes precedence over the UDR, directing traffic directly to the gateway.
This identifies why the current routing configuration fails to meet the inspection requirement.
3
Determine the configuration change needed to force traffic through the NVA.
Disabling gateway route propagation on the spoke's route table removes the propagated BGP routes from its effective route table. Traffic to the on-premises database tier will then fall back to the UDR for 172.16.0.0/12172.16.0.0/12, sending it to the NVA load balancer. The NVAs, located in the hub, still have route propagation enabled and can forward the traffic to the gateway after inspection.
This establishes the correct architectural remediation path.

Anahtar Kavram

Azure Virtual Network routing precedence, BGP route propagation, and transit NVA design
Soru 122Soru

A meteorological modeling company is designing the Azure compute virtualization infrastructure for two distinct workloads:

* Workload 1: A weather simulation model that runs daily. The model requires Message Passing Interface (MPI) support with sub-millisecond node-to-node latency, high CPU performance, and cannot tolerate interruptions during its four-hour execution window.
* Workload 2: A public-facing web API providing real-time weather alerts that requires a minimum availability SLA of 99.99% and must scale automatically to handle sudden traffic spikes.

Which two virtual machine configurations should you recommend to meet the requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy Workload 1 on HBv3-series virtual machines within a proximity placement group.; Deploy Workload 2 using Virtual Machine Scale Sets in Flexible orchestration mode spread across multiple Availability Zones.

Cevap

Deploy Workload 1 on HBv3-series virtual machines within a proximity placement group, and deploy Workload 2 using Virtual Machine Scale Sets in Flexible orchestration mode spread across multiple Availability Zones.
The correct configurations are deploying the weather simulation on HBv3-series virtual machines in a proximity placement group, and deploying the API on Virtual Machine Scale Sets in Flexible orchestration mode across multiple Availability Zones. HBv3-series provides the InfiniBand networking and high compute capacity needed for MPI simulation workloads, and the proximity placement group ensures lowest possible latency by placing VMs physically close. Virtual Machine Scale Sets in Flexible orchestration mode distributed across multiple Availability Zones provide the autoscaling functionality and meet the 99.99% VM SLA requirement.

Adım Adım Çözüm

1
Analyze Workload 1 requirements for MPI support, sub-millisecond node-to-node latency, and no tolerance for interruptions.
Identify that HBv3-series virtual machines (HPC-optimized with InfiniBand) are required, and a proximity placement group must be used to keep latency minimal. Spot VMs must be avoided because they can be evicted, which violates the zero-interruption constraint.
Ensures that the compute selection matches the networking and performance requirements of the simulation model.
2
Analyze Workload 2 requirements for a 99.99% availability SLA and autoscaling capability.
Determine that achieving a 99.99% VM SLA in Azure requires distributing virtual machines across multiple Availability Zones in the same region. Virtual Machine Scale Sets with Flexible orchestration mode provide both auto-scaling capabilities and zonal redundancy.
Ensures the high-availability and scale targets are met using Azure best practices.
3
Select the two options that match the identified configurations.
Choose the configurations recommending HBv3-series with proximity placement groups, and Virtual Machine Scale Sets in Flexible orchestration mode across multiple zones.
Provides the complete recommended architecture satisfying all business and technical constraints.

Anahtar Kavram

Designing compute virtualization solutions in Azure requires matching VM series capabilities (such as HPC-optimized HBv3-series with InfiniBand for MPI workloads) and architectural patterns (such as multi-zone Virtual Machine Scale Sets in Flexible orchestration mode for high-availability SLAs) to workload constraints.
Soru 123Soru

An enterprise is designing the network routing topology for an Azure environment. The topology includes the following components:
- A hub virtual network named `vnet-hub-cus` (10.100.0.0/1610.100.0.0/16) containing an Azure Firewall with the private IP address 10.100.2.410.100.2.4 and an ExpressRoute virtual network gateway.
- A production spoke virtual network named `vnet-prod-spoke` (10.110.0.0/1610.110.0.0/16) with a subnet named `snet-prod-app` (10.110.1.0/2410.110.1.0/24).
- A shared services spoke virtual network named `vnet-shared-spoke` (10.120.0.0/1610.120.0.0/16) with a subnet named `snet-shared-db` (10.120.1.0/2410.120.1.0/24).

The virtual networks `vnet-prod-spoke` and `vnet-shared-spoke` are peered directly with `vnet-hub-cus` but are not peered with each other.

The design must meet the following requirements:
- All traffic between `snet-prod-app` and `snet-shared-db` must be routed through the Azure Firewall for inspection.
- Virtual machines in `snet-prod-app` must be able to communicate with the on-premises network (172.16.0.0/12172.16.0.0/12) via the ExpressRoute gateway.
- Traffic between virtual machines within the same subnet (`snet-prod-app`) must remain local and bypass the Azure Firewall.

Which TWO configurations should you implement to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: In the route table associated with the `snet-prod-app` subnet, add a route for 10.120.0.0/1610.120.0.0/16 with the next hop set to the Virtual Appliance IP address 10.100.2.410.100.2.4.; Configure the virtual network peering between `vnet-hub-cus` and `vnet-prod-spoke` to enable gateway transit on the hub virtual network and use the remote virtual network's gateway on the spoke virtual network.

Cevap

To meet the requirements, you must add a User Defined Route (UDR) for the shared services spoke network prefix (10.120.0.0/1610.120.0.0/16) pointing to the Azure Firewall's private IP (10.100.2.410.100.2.4) as the next hop in the subnet's route table, and configure the peering between the hub and production spoke to enable gateway transit on the hub virtual network while utilizing the remote gateway on the spoke virtual network.
The correct configurations involve implementing a specific User Defined Route (UDR) for the destination spoke virtual network (10.120.0.0/1610.120.0.0/16) pointing to the Azure Firewall (10.100.2.410.100.2.4) as a Virtual Appliance. This redirects spoke-to-spoke traffic through the firewall. Additionally, configuring the virtual network peering to use the hub's gateway for transit allows BGP route propagation for on-premises routes to reach the spoke subnet, securing transit connectivity to the on-premises network.

Adım Adım Çözüm

1
Analyze virtual network peering requirements for on-premises connectivity.
Determine that spoke virtual networks must utilize the ExpressRoute gateway in the hub virtual network by enabling gateway transit on the hub side of the peering and enabling remote gateway usage on the spoke side of the peering.
This allows the spoke virtual network to dynamically learn routes advertised by the gateway via BGP and send on-premises traffic (172.16.0.0/12172.16.0.0/12) through the hub gateway.
2
Configure routing for spoke-to-spoke traffic while preserving local routing behavior.
Determine that a route for the remote spoke's address prefix (10.120.0.0/1610.120.0.0/16) must be added to the route table associated with the production subnet pointing to the Azure Firewall (10.100.2.410.100.2.4) as a Virtual Appliance next hop.
Because the local VNet route (10.110.0.0/1610.110.0.0/16) is more specific than the UDR or is managed by the default local VNet system route, local traffic remains inside the spoke VNet and bypasses the firewall, while traffic to the other spoke is successfully redirected to the firewall.

Anahtar Kavram

Azure Virtual Network peering gateway transit and User-Defined Routes (UDR) precedence over default system routes.
Tahmini Süre:3m 0s
Soru 124Soru

An organization is planning to migrate their on-premises VMware vSphere virtual machines (VMs) to Azure using Azure Migrate. Before scheduling the migration, they want to analyze the network connections and dependencies between their servers to ensure no critical connections are broken. Which two methods can they use to perform dependency analysis in Azure Migrate? (Choose two.)

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

Cevabı ve açıklamayı göster

Cevap: Perform agentless dependency analysis by using the Azure Migrate appliance to collect TCP connection data.; Perform agent-based dependency analysis by installing the Dependency agent and the Log Analytics agent on each VM.

Cevap

The two valid methods are agentless dependency analysis using the Azure Migrate appliance and agent-based dependency analysis using agents installed on each VM.
Azure Migrate provides two primary methods for dependency mapping: agentless analysis, which requires no software installation on the VMs, and agent-based analysis, which uses the Log Analytics agent and Dependency agent to gather granular process-level connection data.

Adım Adım Çözüm

1
Determine the migration discovery and assessment options in Azure Migrate.
Identify that Azure Migrate provides two distinct modes for assessing virtual machine network dependencies: agentless and agent-based.
Understanding the options allows you to align the assessment strategy with the organization's security and deployment guidelines.
2
Evaluate the agentless option.
The agentless method relies on the Azure Migrate appliance to query vCenter Server APIs and collect network metadata.
This configuration avoids the administrative overhead of managing agent installations on target VMs.
3
Evaluate the agent-based option.
The agent-based method requires installing the Log Analytics agent and the Dependency agent on target systems.
This is chosen when deeper process-level detail is needed or when hypervisor-level metadata collection is restricted.

Anahtar Kavram

Azure Migrate dependency analysis methodologies
Soru 125Soru

An enterprise is designing the network security for a two-tier application in Azure. The design includes:

* A virtual network named VNet1 containing two subnets: WebSubnet and DataSubnet.
* WebSubnet hosts web server virtual machines (VMs) that do not have public IP addresses.
* DataSubnet hosts a Private Endpoint for an Azure SQL Database named sql-db1.
* WebSubnet is associated with a Network Security Group (NSG) named NSG-Web.
* DataSubnet is associated with an NSG named NSG-Data.

The design must meet the following requirements:
* The web servers must connect to sql-db1 securely over its private IP address.
* All outbound traffic from WebSubnet to the internet must be blocked.
* Outbound traffic from WebSubnet must be restricted so that the web servers can only communicate with the Private Endpoint of sql-db1 and no other resources in VNet1.
* The design must minimize administrative effort by avoiding the use of individual, hardcoded IP addresses in NSG rules.

Which two configurations should you include in the design? (Choose two.)

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

Cevabı ve açıklamayı göster

Cevap: Associate the network interface of the Private Endpoint for sql-db1 with an Application Security Group (ASG), and reference this ASG as the destination in an outbound security rule for NSG-Web.; Enable network policies for private endpoints on DataSubnet.

Cevap

The correct configurations are to associate the Private Endpoint's network interface with an Application Security Group (ASG) and reference it in the outbound NSG rule, and to enable network policies for private endpoints on the subnet hosting the Private Endpoint.
To secure traffic to a Private Endpoint using Network Security Groups (NSGs) or Application Security Groups (ASGs), you must first enable network policies for private endpoints on the subnet where the Private Endpoint is deployed (DataSubnet). Once enabled, you can associate the Private Endpoint's network interface with an ASG and reference that ASG in the outbound security rules of the source subnet's NSG (NSG-Web). This dynamically permits traffic to the Private Endpoint without needing to hardcode private IP addresses, minimizing administrative overhead.

Adım Adım Çözüm

1
Enable network policies for private endpoints on DataSubnet.
Network security rules (including NSG and ASG policies) are now enforced on traffic flowing to the Private Endpoint in DataSubnet.
By default, Azure does not enforce NSG or ASG policies on Private Endpoints. Enabling this setting on the subnet is required to apply security rules to the Private Endpoint.
2
Associate the Private Endpoint's network interface with an ASG and reference it in the NSG-Web outbound rule.
Outbound traffic from WebSubnet is successfully restricted to only the Private Endpoint without using hardcoded IP addresses.
This minimizes administrative effort compared to manually configuring individual IP addresses, while still providing the required isolation.
3
Analyze and eliminate incorrect options.
The service tag and service endpoint options are ruled out because they do not apply to the private IP path of the Private Endpoint.
The Sql service tag only represents public IP ranges, and Service Endpoints route traffic to public endpoints. The VirtualNetwork service tag is too broad as it allows traffic to all VNet resources.

Anahtar Kavram

Enforcing network security policies on Private Endpoints using subnet settings and Application Security Groups.
Soru 126Soru

An enterprise is designing a hub-and-spoke network topology in Azure to host a secure multi-tier application. The architecture consists of:

* A hub virtual network named `vnet-hub-core` (10.100.0.0/1610.100.0.0/16) that hosts a central firewall Network Virtual Appliance (NVA) at IP address 10.100.2.410.100.2.4.
* A spoke virtual network named `vnet-prod-spoke` (10.150.0.0/1610.150.0.0/16) that contains two subnets: `snet-web` (10.150.1.0/2410.150.1.0/24) and `snet-db` (10.150.2.0/2410.150.2.0/24).
* Virtual network peering established between `vnet-hub-core` and `vnet-prod-spoke` with gateway transit and remote gateway options enabled.

A route table named `rt-web-tier` is associated with `snet-web` and contains a user-defined route (UDR) for 10.150.2.0/2410.150.2.0/24 with a next hop pointing to the NVA (10.100.2.410.100.2.4) to inspect all database-bound traffic. However, when web servers in `snet-web` attempt to establish database connections to VMs in `snet-db`, the connections time out. The database servers are verified as active, and Network Security Groups (NSGs) allow the traffic.

Which of the following routing configurations is the most appropriate solution to resolve the connectivity issue?

Cevabı ve açıklamayı göster

Cevap: Create a new route table with a UDR for 10.150.1.0/2410.150.1.0/24 pointing to the NVA (10.100.2.410.100.2.4) as the next hop, and associate it with `snet-db`.

Cevap

Create a new route table with a UDR for 10.150.1.0/2410.150.1.0/24 pointing to the NVA (10.100.2.410.100.2.4) as the next hop, and associate it with `snet-db`.
The correct option is to create a new route table with a UDR for the web subnet's IP range pointing to the NVA, and associate it with the database subnet. Because the database subnet does not have a route table, it defaults to the system local route for the virtual network, bypassing the NVA on the return path. This causes asymmetric routing, which leads the stateful NVA to drop the traffic. Enforcing the return path through the NVA resolves the timeout issue.

Adım Adım Çözüm

1
Analyze the outbound path from the web tier to the database tier.
Traffic from `snet-web` (10.150.1.0/2410.150.1.0/24) to `snet-db` (10.150.2.0/2410.150.2.0/24) matches the UDR for 10.150.2.0/2410.150.2.0/24 in `rt-web-tier` and is successfully forwarded to the NVA (10.100.2.410.100.2.4).
Verify that the outbound packets are correctly routed to the security appliance.
2
Analyze the return path from the database tier back to the web tier.
Since `snet-db` has no associated route table, return traffic destined for `snet-web` (10.150.1.0/2410.150.1.0/24) uses the default system route for the virtual network (10.150.0.0/1610.150.0.0/16 -> Local) and bypasses the NVA.
Identify the cause of connection timeouts, which is asymmetric routing. Stateful firewalls drop connection tracking packets (like TCP SYN-ACK) if they do not observe the initial handshake request.
3
Select a solution that ensures symmetric traffic flow through the firewall.
Create a route table containing a UDR for 10.150.1.0/2410.150.1.0/24 pointing to the NVA and associate it with `snet-db`. This forces the return traffic to flow through the NVA, completing the symmetric path.
Ensure that the stateful firewall tracks both directions of the connection, enabling communication to succeed.

Anahtar Kavram

Stateful network virtual appliances (NVAs) require symmetric routing to monitor and allow TCP handshakes. When routing traffic between subnets through an NVA, User-Defined Routes must be applied to both the source and destination subnets to prevent return packets from bypassing the NVA via the default local system route.
Tahmini Süre:1m 30s
Soru 127Soru

Your company is assessing the migration of an on-premises Microsoft SQL Server database to Azure. The database relies on cross-database queries and SQL Server Agent jobs to perform nightly transactional processing. Which Azure SQL deployment option should you select to support these features with minimal modification to the database or application code?

Cevabı ve açıklamayı göster

Cevap: Azure SQL Managed Instance

Cevap

Azure SQL Managed Instance
Azure SQL Managed Instance is designed for migrating on-premises SQL Server instances to Azure with minimal migration effort. It provides near-complete compatibility with the on-premises SQL Server database engine, including support for instance-level features such as SQL Server Agent, SQL Server Database Mail, Service Broker, and cross-database queries.

Adım Adım Çözüm

1
Identify the key technical requirements from the assessment phase.
The requirements are native support for SQL Server Agent jobs and cross-database queries.
These are specific features used by the database that must be supported in the target environment.
2
Evaluate the capabilities of Azure SQL Database vs. Azure SQL Managed Instance.
Azure SQL Database (single databases, elastic pools, serverless) does not natively support SQL Server Agent or cross-database queries. Azure SQL Managed Instance supports these instance-level features.
This determines which deployment option minimizes code modification.
3
Select the option that meets the requirements with minimal modification.
Azure SQL Managed Instance is selected.
It offers near-complete compatibility with SQL Server, directly supporting the identified features.

Anahtar Kavram

Selecting the appropriate Azure SQL deployment option during migration assessment based on database dependencies and instance-level features.
Soru 128Soru

An enterprise is designing a hub-and-spoke virtual network topology in Azure to support a multi-tier application. The topology consists of the following components:
- A hub virtual network named `vnet-hub-eus` (10.100.0.0/1610.100.0.0/16) that contains an Azure Firewall at IP address `10.100.1.4` and a Virtual Network Gateway connected to an on-premises environment via ExpressRoute.
- A spoke virtual network named `vnet-prod-spoke` (10.101.0.0/1610.101.0.0/16) containing a subnet named `snet-web` (10.101.1.0/2410.101.1.0/24).
- A virtual network peering connection between `vnet-hub-eus` and `vnet-prod-spoke` with gateway transit configured to allow the spoke to use the hub's gateway.

The on-premises network advertises specific subnets including `192.168.10.0/24` and `192.168.20.0/24` via BGP. You associate a new route table named `rt-prod-web` with the `snet-web` subnet.

You need to design a routing solution that meets the following requirements:
- All traffic from `snet-web` to the internet and to the on-premises subnets must be routed through the Azure Firewall.
- All traffic within the `vnet-prod-spoke` virtual network must route directly between resources and must not go through the Azure Firewall.
- The solution must minimize administrative overhead and avoid configuring individual routes for each on-premises subnet.

Which two actions should you perform to meet the requirements?

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

Cevabı ve açıklamayı göster

Cevap: Disable virtual network gateway route propagation on the rt-prod-web route table.; Add a route for 0.0.0.0/0 with the next hop set to Virtual Appliance and the next hop address 10.100.1.4 to the rt-prod-web route table.

Cevap

To meet the requirements, you must disable virtual network gateway route propagation on the route table associated with the spoke subnet, and add a default route (0.0.0.0/0) pointing to the Azure Firewall IP address (10.100.1.4).
Disabling virtual network gateway route propagation on the spoke subnet's route table prevents the specific on-premises routes advertised via BGP from being dynamically injected into the subnet's routing table. Consequently, all traffic destined for the on-premises networks and the internet will match the default route (0.0.0.0/0) pointing to the Azure Firewall. Since the local virtual network prefix (10.101.0.0/16) has a more specific system route, local traffic bypasses the default route and remains routed directly within the virtual network.

Adım Adım Çözüm

1
Identify BGP route propagation impact
By default, BGP-propagated routes from the Virtual Network Gateway (like 192.168.10.0/24 and 192.168.20.0/24) are added to the subnet's routing table. Because these prefixes are more specific than a default route (0.0.0.0/0), traffic destined for these ranges will bypass the Azure Firewall.
Azure routing prefers the longest prefix match (LPM).
2
Disable route propagation on spoke subnet
Disabling virtual network gateway route propagation on the route table associated with the spoke subnet prevents these specific BGP routes from being populated in the spoke subnet's routing table.
This removes the more specific BGP paths from the local routing table, allowing wider UDRs to intercept the traffic.
3
Add a default route to Azure Firewall
Define a default route (0.0.0.0/0) pointing to the Azure Firewall (10.100.1.4). Since the BGP routes are no longer present in the subnet's routing table, all traffic destined for the internet and the on-premises subnets will match the default route and be forwarded to the Azure Firewall.
The firewall subnet still has gateway route propagation enabled, so it will successfully forward the inspected traffic to the virtual network gateway.
4
Verify local VNet routing
The local VNet route (10.101.0.0/16 with next hop 'Virtual Network') remains in the routing table and takes precedence over 0.0.0.0/0 because it is more specific.
This ensures intra-spoke traffic does not route through the firewall, fulfilling the second requirement.

Anahtar Kavram

Azure Virtual Network Routing Precedence and Gateway Route Propagation
Tahmini Süre:2m 30s
Soru 129Soru

A financial services firm is modernizing its payment processing platform by migrating key workloads to Azure. The architecture team is designing a load balancing and traffic delivery solution that must meet the following requirements:

* External client transactions over HTTPS must be routed globally to regional endpoints using path-based rules (e.g., routing `/process` and `/refund` requests to dedicated backend services) with SSL/TLS termination performed at the edge.
* The internal backend database tier, which communicates over TCP port 14331433, must be load-balanced regionally across virtual machines in a virtual network.
* The database virtual machines currently have legacy Basic SKU Public IP addresses assigned for administrative access.
* The solution must support high-availability configurations for all load balancers without validation or deployment failures.

Which architecture configuration should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy Azure Front Door to manage global HTTP/S routing and SSL/TLS termination. Upgrade the public IP addresses of the database virtual machines to Standard SKU, and deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic.

Cevap

Deploy Azure Front Door to manage global HTTP/S routing and SSL/TLS termination. Upgrade the public IP addresses of the database virtual machines to Standard SKU, and deploy a Standard Load Balancer to load balance the regional TCP port 1433 traffic.
The correct architecture combines Azure Front Door for global HTTP/S delivery (providing edge SSL/TLS termination and path-based routing) with a Standard Azure Load Balancer to distribute the TCP port 14331433 database traffic within the region. Because Standard Load Balancers require all associated network interfaces and public IP addresses to use the Standard SKU, the legacy Basic SKU public IP addresses on the database virtual machines must be upgraded to Standard SKU to avoid validation failures.

Adım Adım Çözüm

1
Analyze global HTTP/S routing requirements.
Identify that Azure Front Door is required for global routing, SSL/TLS termination, and path-based URL matching.
Azure Front Door is a global Layer 7 load balancer designed specifically for HTTP/S web traffic, whereas Traffic Manager only operates at the DNS level (Layer 4) and Application Gateway is regional.
2
Analyze regional database tier load balancing requirements.
Select Azure Load Balancer (Standard SKU) to handle the database traffic on TCP port 14331433.
Azure Load Balancer is a regional Layer 4 load balancer that handles TCP/UDP protocols, making it suitable for SQL Server database traffic.
3
Evaluate VM Public IP SKU compatibility with the selected Load Balancer.
Determine that the database virtual machines' public IP addresses must be upgraded from Basic SKU to Standard SKU.
Standard Load Balancers require all backend resources to use Standard SKU IP configurations. Mixing Basic SKU Public IPs with a Standard Load Balancer will cause a validation error.

Anahtar Kavram

Designing a multi-tier load balancing architecture using Azure Front Door and Standard Load Balancer while adhering to SKU alignment rules.
Soru 130Soru

An organization is designing a secure hybrid network environment in Azure. A subnet named Subnet-App in VNet1 hosts virtual machines that must connect to the following resources:
- An Azure Key Vault named vault1 via a Private Endpoint deployed in Subnet-PE (IP range 10.0.2.0/24) in VNet1.
- An Azure Storage account named storage1 via a Private Endpoint deployed in Subnet-PE.
- Microsoft Entra ID for authentication.
- A public partner API (api.partner.com).

The design must satisfy the following requirements:
- Minimize administrative effort when Azure public IP addresses change.
- Route all public internet traffic (including api.partner.com) through an Azure Firewall in a peered hub virtual network.
- Restrict outbound traffic from Subnet-App using a Network Security Group (NSG) to block all outbound traffic by default, except for the minimum necessary traffic required to meet the connectivity requirements.

Which configuration should you recommend for the route table and NSG outbound rules on Subnet-App?

Cevabı ve açıklamayı göster

Cevap: Associate a route table with a route of 0.0.0.0/0 pointing to the Azure Firewall private IP. Configure NSG rules that allow outbound traffic to 10.0.2.0/24 on port 443, allow outbound traffic to the AzureActiveDirectory service tag on port 443, allow outbound traffic to the Internet service tag on port 443, and deny all other outbound traffic.

Cevap

Associate a route table with a route of 0.0.0.0/0 pointing to the Azure Firewall private IP. Configure NSG rules that allow outbound traffic to 10.0.2.0/24 on port 443, allow outbound traffic to the AzureActiveDirectory service tag on port 443, allow outbound traffic to the Internet service tag on port 443, and deny all other outbound traffic.
The correct configuration routes all outbound internet-bound traffic (0.0.0.0/0) to the Azure Firewall. To allow the traffic to leave the subnet and reach the firewall, the NSG must allow outbound traffic to the Internet service tag, as the packet's destination IP is the public IP of the partner API. The NSG must also explicitly allow traffic to the private IP range of the Private Endpoint subnet (10.0.2.0/24) to permit secure access to Key Vault and Storage, while using the AzureActiveDirectory service tag to allow token acquisition with minimal administrative effort.

Adım Adım Çözüm

1
Determine how to route public internet traffic through the Azure Firewall.
Create a route table associated with Subnet-App with a user-defined route (UDR) of 0.0.0.0/0 pointing to the private IP of the Azure Firewall as the next hop.
This forces all traffic destined for the public internet to go through the firewall for inspection and filtering.
2
Determine the destination addresses for Private Endpoint traffic in the NSG rules.
Use the private subnet range (10.0.2.0/24) where the Private Endpoints are deployed as the destination in the NSG rule.
Private Endpoints use private IP addresses from the virtual network. Service tags like AzureKeyVault and Storage represent public IP ranges and do not match private VNet IPs.
3
Determine how to permit traffic to Microsoft Entra ID while minimizing administrative effort.
Use the built-in AzureActiveDirectory service tag in the NSG rule.
Service tags automatically manage and update the IP ranges associated with Azure services, removing the need for manual IP maintenance.
4
Determine the NSG rule required for the public partner API traffic when routed through Azure Firewall.
Configure an NSG rule allowing outbound traffic to the Internet service tag (or the specific API endpoint IP if static).
Because NSGs evaluate the packet's final destination IP (the public IP of api.partner.com) rather than the next hop IP (the private IP of the firewall), an outbound deny rule for the Internet service tag would drop the packets before they reach the Azure Firewall.

Anahtar Kavram

NSG rules evaluate final destination IPs, not next hop IPs, meaning internet-bound traffic routed through a firewall must still be allowed to the 'Internet' destination in the NSG. Additionally, Private Endpoints use private IPs, so public service tags do not apply to them.
Tahmini Süre:3m 0s
Soru 131Soru

An enterprise is designing a hybrid network architecture to connect an on-premises datacenter to an Azure virtual network named `VNet1` using an ExpressRoute connection. A subnet in `VNet1` named `Subnet1` hosts virtual machines that must access an Azure SQL Database.

The design must meet the following requirements:
- The Azure SQL Database must not expose a public endpoint and must be accessible only via a private IP address within `VNet1`.
- On-premises applications must be able to resolve the database's fully qualified domain name (FQDN) to its private IP address.
- Outbound traffic from `Subnet1` to the database must be restricted at the network layer using Network Security Groups (NSGs).
- Administrative effort for managing DNS routing and network security rules must be minimized.

Which design should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy a Private Endpoint for the Azure SQL Database in a dedicated subnet. Enable private endpoint network policies on the subnet. Configure an Azure DNS Private Resolver with an inbound endpoint in VNet1, and link a private DNS zone named privatelink.database.windows.net to VNet1. Configure the on-premises DNS servers to forward queries for database.windows.net to the inbound endpoint IP.

Cevap

Deploy a Private Endpoint for the Azure SQL Database in a dedicated subnet, enable private endpoint network policies, configure an Azure DNS Private Resolver with an inbound endpoint, link the private DNS zone, and configure on-premises DNS servers to forward queries to the inbound endpoint IP.
The correct option addresses the requirements by using a Private Endpoint to ensure the Azure SQL Database is not publicly exposed. It enables network policies on the subnet so that NSG rules can successfully apply to the Private Endpoint. Finally, it uses an Azure DNS Private Resolver with an inbound endpoint, allowing on-premises clients to resolve the database's private IP address using standard DNS forwarders with minimal administrative effort.

Adım Adım Çözüm

1
Address the private access requirement
Using an Azure Private Endpoint assigns a private IP address from the virtual network to the Azure SQL Database and allows disabling its public endpoint, fulfilling the primary security requirement.
Service Endpoints still use the public IP of the service and do not allow complete removal of the public endpoint.
2
Implement secure filtering on the Private Endpoint
Enable private endpoint network policies on the subnet hosting the Private Endpoint, which allows Network Security Groups (NSGs) to evaluate and filter traffic destined for the Private Endpoint.
By default, network policies are disabled for private endpoints, meaning NSGs do not filter traffic flowing to them.
3
Configure hybrid DNS resolution with minimal administrative overhead
Link the private DNS zone `privatelink.database.windows.net` to `VNet1` and deploy an Azure DNS Private Resolver with an inbound endpoint. Configure on-premises DNS to conditionally forward queries to the inbound endpoint's IP address.
Azure default DNS (168.63.129.16168.63.129.16) is not routable from on-premises, and manually managing static A records increases administrative overhead.

Anahtar Kavram

Azure Private Endpoint Security and Hybrid DNS Integration
Soru 132Soru

A healthcare provider is deploying a multi-tier clinical application across two Azure regions: East US 2 and West US 2.

The architecture team specifies the following technical requirements for the application:
1. Global Traffic Ingress: Client traffic must be dynamically routed to the closest healthy region based on latency. The ingress layer must support SSL/TLS termination, URL path-based routing (routing `/api/*` traffic to API clusters and `/static/*` traffic to static assets), and Web Application Firewall (WAF) protection at the network edge.
2. Regional Backend Load Balancing: In each region, internal services communicating over TCP port 5005 must be load balanced across a backend pool of virtual machines. The load balancer must support High Availability (HA) ports.
3. Administrative Access: During a temporary transition phase, the backend virtual machines must maintain their existing direct administrative access using Basic SKU public IP addresses attached to their network interfaces.

You need to design a load balancing and delivery solution that satisfies all of the application's requirements while ensuring the deployment passes Azure validation.

Which two of the following components or configurations should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Deploy Azure Front Door to manage global traffic routing, terminate SSL/TLS sessions, and enforce WAF policies at the edge.; Upgrade the public IP addresses of the backend virtual machine network interfaces (NICs) to the Standard SKU, and deploy a Standard SKU Azure Load Balancer for regional backend load balancing.

Cevap

Deploy Azure Front Door to manage global traffic routing, terminate SSL/TLS sessions, and enforce WAF policies at the edge; and upgrade the public IP addresses of the backend virtual machine network interfaces (NICs) to the Standard SKU, and deploy a Standard SKU Azure Load Balancer for regional backend load balancing.
Deploying Azure Front Door satisfies the global ingress requirements because it is a global, layer-7 load balancer that supports latency-based routing, SSL/TLS termination, path-based routing, and WAF integration. Additionally, using a Standard SKU Azure Load Balancer is required to support High Availability (HA) ports for internal TCP traffic. Because Standard Load Balancers cannot have backend resources with Basic SKU public IP addresses, the existing Basic SKU public IPs on the virtual machine NICs must be upgraded to the Standard SKU to avoid validation failures.

Adım Adım Çözüm

1
Evaluate global ingress requirements including SSL/TLS termination, path-based routing, latency-based routing, and WAF rules.
Determine that Azure Front Door is the correct global layer-7 delivery service, as Azure Traffic Manager only works at the DNS level and lacks these layer-7 application capabilities.
Selects the global service matching layer-7 routing and security requirements.
2
Evaluate regional load balancing requirements for TCP port 5005 with HA ports capability.
Determine that a Standard SKU Azure Load Balancer is required, as High Availability (HA) ports are not supported by the Basic SKU Azure Load Balancer.
Ensures the regional load balancer meets protocol and HA ports criteria.
3
Analyze backend virtual machine public IP requirements for validation compatibility.
Identify that the VMs have Basic SKU public IPs. Since a Standard Load Balancer requires all attached public IPs of backend resources to be of the Standard SKU, these IPs must be upgraded to Standard SKU.
Avoids validation failures caused by mixing Basic and Standard SKU resources in the load balancer backend pool.

Anahtar Kavram

Selecting and configuring Azure global and regional load balancing services based on layer-4 and layer-7 protocols, feature support (HA ports, SSL offloading, WAF), and resource SKU compatibility.
Soru 133Soru

An enterprise has a hub-and-spoke network topology in Azure to support a multi-tier application. The topology contains the following configurations:

* Hub VNet (`vnet-hub-weur`): Address space 10.100.0.0/1610.100.0.0/16. It contains an Azure Route Server and a Network Virtual Appliance (`nva-core` at 10.100.1.410.100.1.4) that dynamically advertises the prefix 192.168.10.0/24192.168.10.0/24 via BGP.
* Spoke VNet (`vnet-prod-spoke`): Address space 10.101.0.0/1610.101.0.0/16. It contains a subnet named `subnet-prod` (10.101.1.0/2410.101.1.0/24). The spoke VNet is peered with the hub VNet with gateway transit enabled so that it receives the routes propagated by the Route Server.
* **Security Scanner (`nva-scan` at 10.100.2.410.100.2.4)**: Deployed in the hub VNet for inspecting traffic destined to specific security zones.

You need to design a routing solution for resources in `subnet-prod` to ensure that all traffic destined for the 192.168.10.0/24192.168.10.0/24 network is routed through the security scanner (`nva-scan`) instead of the core NVA (`nva-core`).

Which of the following configurations should you recommend?

Cevabı ve açıklamayı göster

Cevap: Associate a route table with `subnet-prod` and add a user-defined route for 192.168.10.0/24192.168.10.0/24 with a next hop type of Virtual Appliance pointing to 10.100.2.410.100.2.4.

Cevap

Associate a route table with the subnet and add a user-defined route for the exact prefix pointing to the security scanner IP address.
The correct configuration is to associate a route table with the spoke subnet and add a UDR for the exact destination prefix pointing to the security scanner. When Azure evaluates routing options, it first looks at the prefix length (Longest Prefix Match). If the prefix lengths are identical, User-Defined Routes take precedence over BGP routes. Therefore, a UDR for the exact prefix overrides the BGP route propagated by the Route Server.

Adım Adım Çözüm

1
Analyze the existing route sources in the spoke subnet.
The spoke subnet receives a dynamic BGP route for 192.168.10.0/24192.168.10.0/24 pointing to the core NVA (10.100.1.410.100.1.4) via Azure Route Server.
Understanding the baseline routing behavior is necessary to design an override mechanism.
2
Compare routing priority and prefix length rules in Azure.
Azure evaluates routing in order: Longest Prefix Match (LPM) first, and then route source precedence (UDR > BGP > System routes) when prefixes are identical.
This establishes that any override route must have a prefix length at least as specific as 192.168.10.0/24192.168.10.0/24.
3
Select the correct target IP and prefix for the User-Defined Route (UDR).
Creating a UDR for 192.168.10.0/24192.168.10.0/24 pointing to the security scanner (10.100.2.410.100.2.4) matches the prefix length and overrides the BGP route due to UDR precedence.
This configuration satisfies the business requirements while adhering to Azure routing rules.

Anahtar Kavram

Azure routing precedence and Longest Prefix Match (LPM) for overriding dynamically propagated routes.
Soru 134Soru

An organization is designing the network security for an Azure environment. A subnet named Subnet1 in a virtual network named VNet1 hosts virtual machines that run batch processing jobs. The virtual machines must access Azure Key Vault and Azure SQL Database instances over their public endpoints. You need to configure a Network Security Group (NSG) associated with Subnet1 to restrict outbound traffic so that the virtual machines can access only these specific Azure services and are blocked from all other public internet destinations. The solution must minimize administrative overhead. Which two actions should you recommend?

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

Cevabı ve açıklamayı göster

Cevap: Create an outbound security rule in the NSG with the destination set to the AzureKeyVault Service Tag.; Create an outbound security rule in the NSG with the destination set to the Sql Service Tag.

Cevap

Create an outbound security rule in the NSG with the destination set to the AzureKeyVault Service Tag, and create an outbound security rule in the NSG with the destination set to the Sql Service Tag.
To securely allow outbound traffic to Azure Key Vault and Azure SQL Database over public endpoints while blocking all other public internet traffic, you should configure NSG outbound rules using the built-in Service Tags 'AzureKeyVault' and 'Sql'. Service Tags represent the IP address prefixes of these services and are automatically managed and updated by Microsoft, which minimizes administrative overhead.

Adım Adım Çözüm

1
Identify the destination services and their public endpoint access requirements.
The virtual machines must access Azure Key Vault and Azure SQL Database over public endpoints.
This determines the scope of outbound traffic that must be permitted.
2
Evaluate options for restricting outbound traffic while minimizing administrative overhead.
Service Tags represent IP address prefixes for specific Azure services and are managed automatically by Microsoft.
Using Service Tags avoids manually tracking and updating individual IP ranges for Azure services in NSG rules.
3
Formulate the correct NSG outbound rules.
Configure rules with destinations set to the AzureKeyVault and Sql Service Tags, and deny all other outbound internet traffic.
This fulfills the security requirement to block other public internet destinations while allowing Key Vault and SQL access.

Anahtar Kavram

Using Service Tags in Network Security Groups (NSGs) to manage outbound access to Azure services with minimal administrative overhead.
Tahmini Süre:1m 30s
Soru 135Soru

A logistics corporation is migrating a core ERP and dispatch system to Azure. The system has two distinct components:
1. An HTTP/HTTPS web application that requires cookie-based session affinity, SSL/TLS termination at the load balancer, and routing traffic to different backend pools based on the URL path.
2. A high-throughput database replication service that communicates over a custom TCP port 1445 and requires regional high availability.

All backend virtual machines (VMs) for both components are deployed within a single virtual network in the North Europe region. The VMs are currently associated with Basic SKU Public IP addresses. The entire load balancing architecture must support availability zones for zone redundancy and must not trigger deployment validation failures.

Which configuration should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy a Standard v2 Application Gateway for the web application, and deploy a Standard Load Balancer for the database replication service. Upgrade the existing Basic SKU Public IP addresses on the virtual machines to Standard SKU Public IP addresses.

Cevap

Deploy a Standard v2 Application Gateway for the web application, and deploy a Standard Load Balancer for the database replication service. Upgrade the existing Basic SKU Public IP addresses on the virtual machines to Standard SKU Public IP addresses.
The correct architecture uses a Standard v2 Application Gateway to satisfy the Layer 7 requirements (cookie affinity, SSL termination, path-based routing) and a Standard Load Balancer for the custom TCP port 1445 traffic. Both services support availability zones. To avoid validation failures, the existing Basic SKU Public IPs on the backend VMs must be upgraded to Standard SKU to match the Standard Load Balancer requirement.

Adım Adım Çözüm

1
Analyze the web application requirements.
Identify that cookie-based session affinity, SSL/TLS termination, and path-based routing require a Layer 7 load balancer. In Azure, this is addressed by Azure Application Gateway.
Layer 4 balancers cannot read HTTP headers, cookies, or URL paths.
2
Analyze the database replication service requirements.
Identify that custom TCP port 1445 load balancing requires a Layer 4 load balancer, which is addressed by Azure Load Balancer.
Application Gateway only supports HTTP, HTTPS, HTTP/2, and WebSocket protocols, not raw custom TCP ports.
3
Evaluate the resiliency and SKU constraint requirements.
To support Availability Zones, Standard v2 Application Gateway and Standard Load Balancer must be selected. Basic SKUs do not support zonal redundancy.
Zonal and zone-redundant deployments are exclusive features of Standard SKU load balancing resources.
4
Check VM IP configurations for SKU compatibility.
Note that backend VMs associated with a Standard Load Balancer backend pool must use Standard SKU Public IPs or no Public IPs. Thus, the Basic SKU Public IPs on the VMs must be upgraded to Standard SKU.
Mixing Basic and Standard SKUs in a Load Balancer backend pool triggers a validation failure.

Anahtar Kavram

Azure Load Balancer and Application Gateway SKU integration constraints
Tahmini Süre:3m 0s
Soru 136Soru

A company is designing a secure hub-and-spoke network topology in Azure. The hub virtual network contains an Azure Firewall with the private IP address 10.1.1.410.1.1.4. The spoke virtual network uses the address space 10.2.0.0/1610.2.0.0/16 and contains two subnets: `Prod-App-Subnet` (10.2.1.0/2410.2.1.0/24) hosting application virtual machines associated with the Application Security Group (ASG) `AppVM-ASG`, and `Prod-Db-Subnet` (10.2.2.0/2410.2.2.0/24) hosting a private endpoint for an Azure SQL Database with the private IP address 10.2.2.510.2.2.5.

The network security design must satisfy the following technical requirements:
1. All traffic from `Prod-App-Subnet` to the Azure SQL Database private endpoint must be routed through and inspected by the Azure Firewall.
2. The Network Security Group (NSG) associated with `Prod-App-Subnet` must allow outbound database traffic to the private endpoint while blocking all other outbound traffic to the public internet.
3. Administrative overhead for managing network rules and IP changes must be minimized.
4. Network security policies must be enforced on `Prod-Db-Subnet`.

Which configuration should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Associate a route table with `Prod-App-Subnet` containing a route for 10.2.2.5/3210.2.2.5/32 with a next hop of 10.1.1.410.1.1.4. In the NSG for `Prod-App-Subnet`, add an outbound rule allowing traffic from `AppVM-ASG` to destination 10.2.2.510.2.2.5 on port 14331433, and a rule denying outbound traffic to the `Internet` Service Tag. Enable private endpoint network policies on `Prod-Db-Subnet`.

Cevap

Associate a route table with the application subnet containing a specific /32 route for the private endpoint pointing to the Azure Firewall private IP. Configure the application subnet's NSG to allow outbound traffic to the private endpoint IP on port 1433 and block the Internet Service Tag. Finally, ensure that private endpoint network policies are enabled on the database subnet.
To force traffic destined for the database private endpoint through the Azure Firewall, you must define a custom route that is more specific than the system-defined local virtual network route (10.2.0.0/1610.2.0.0/16). A route pointing to 10.2.2.5/3210.2.2.5/32 with the next hop of the firewall private IP (10.1.1.410.1.1.4) successfully achieves this. Because private endpoints resolve to private IP addresses, the application subnet's NSG must allow outbound traffic targeting the specific private IP (10.2.2.510.2.2.5) instead of the public `Sql` Service Tag. Using the `Internet` Service Tag to deny outbound traffic blocks all other public web access while minimizing administrative overhead. Finally, enabling private endpoint network policies on the destination subnet ensures that traffic rules are correctly enforced.

Adım Adım Çözüm

1
Evaluate routing precedence between user-defined routes (UDRs) and default system routes.
A route to 10.2.2.5/3210.2.2.5/32 is more specific than the system route 10.2.0.0/1610.2.0.0/16 (Local), forcing traffic through the firewall. A route to 10.0.0.0/810.0.0.0/8 is less specific than 10.2.0.0/1610.2.0.0/16, which would cause the firewall to be bypassed.
Azure routing always selects the route with the longest prefix match (most specific route) first.
2
Analyze how NSG rules match traffic directed to Private Endpoints.
Since the private endpoint uses a private IP address within the VNet (10.2.2.510.2.2.5), public Service Tags like `Sql` will not match this traffic. The NSG rule must explicitly target the private IP address.
Service Tags only resolve to public IP ranges of Azure services, not private IPs allocated to private endpoints.
3
Apply the principle of least privilege and low administrative overhead for internet blocking.
Use the built-in `Internet` Service Tag to deny outbound traffic, rather than maintaining hundreds of individual rules for external public IP ranges.
Maintaining individual IP rules manually introduces massive administrative overhead and is prone to errors.
4
Verify database subnet policies.
Ensure private endpoint network policies are enabled on `Prod-Db-Subnet`.
If private endpoint network policies are disabled, NSGs and UDRs applied to the subnet hosting the private endpoint will not be enforced.

Anahtar Kavram

Enforcing custom routing and security rules on traffic destined for private endpoints in a hub-and-spoke VNet topology.
Soru 137Soru

A multinational finance company is designing a secure hybrid networking architecture in Azure. The architecture must connect their on-premises datacenter to an Azure virtual network (VNet1VNet1) via an ExpressRoute circuit. The company is deploying an Azure SQL Database named FinanceDB1FinanceDB1 and wants to ensure that:

- VMs in VNet1VNet1 and on-premises database client tools can access FinanceDB1FinanceDB1 privately.
- VMs in VNet1VNet1 are strictly blocked from accessing any other Azure SQL Database instances in any region (preventing database data exfiltration).
- The on-premises clients must resolve the private endpoint of FinanceDB1FinanceDB1 using their existing local DNS servers.
- Administrative overhead and maintenance of custom DNS forwarder virtual machines must be minimized.

Which two configurations should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Configure a Private Endpoint for FinanceDB1FinanceDB1 in VNet1VNet1, and apply a Network Security Group (NSG) to the VM subnet that permits outbound traffic to the Private Endpoint's private IP address and denies outbound traffic to the `Sql` service tag.; Deploy an Azure DNS Private Resolver in Azure with an inbound endpoint, and configure the on-premises DNS servers with a conditional forwarder for `privatelink.database.windows.net` pointing to the inbound endpoint's private IP address.

Cevap

To meet the requirements, the design must configure a Private Endpoint for the database and apply a Network Security Group to the VM subnet that allows outbound traffic to the Private Endpoint's private IP while blocking the Sql service tag. It must also deploy an Azure DNS Private Resolver with an inbound endpoint to resolve the private endpoint FQDN from the on-premises DNS servers.
The correct architecture combines Private Endpoints for private database access with NSGs that allow traffic to the private endpoint IP while blocking the Sql service tag, effectively preventing data exfiltration to other public SQL databases. For hybrid DNS resolution, an Azure DNS Private Resolver with an inbound endpoint allows on-premises DNS servers to forward queries for private link zones without the overhead of custom DNS VM forwarders.

Adım Adım Çözüm

1
Enable private access and prevent database data exfiltration.
Create a Private Endpoint for the database, and configure an NSG on the VM subnet that allows outbound traffic to the private IP address of the Private Endpoint but denies outbound traffic to the `Sql` service tag.
Traffic to the private endpoint uses the private IP address, which bypasses the `Sql` service tag block. This prevents VMs from accessing other Azure SQL databases via their public endpoints while maintaining access to the designated database.
2
Establish secure hybrid DNS resolution with minimal administrative effort.
Deploy an Azure DNS Private Resolver with an Inbound Endpoint in Azure, and configure a conditional forwarder on the on-premises DNS servers pointing to the resolver's private IP.
This avoids maintaining custom DNS forwarder virtual machines and enables on-premises DNS queries for the private link zone to be forwarded to Azure's internal DNS resolver.

Anahtar Kavram

Designing secure hybrid network access and private DNS resolution in Azure.
Tahmini Süre:3m 0s
Soru 138Soru

An enterprise has a hub-and-spoke virtual network topology in the West US 2 region. The hub virtual network, `vnet-usw2-hub` (10.200.0.0/1610.200.0.0/16), contains an Azure Route Server and a pair of active-active network virtual appliances (NVAs) in the subnet `snet-usw2-nva` (10.200.1.0/2410.200.1.0/24). The NVAs use BGP to peer with the Azure Route Server. The spoke virtual network, `vnet-usw2-spoke` (10.201.0.0/1610.201.0.0/16), contains a subnet named `snet-usw2-app` (10.201.1.0/2410.201.1.0/24) and is peered with `vnet-usw2-hub` with gateway transit enabled.

Initially, the NVAs advertise the on-premises range 172.16.0.0/12172.16.0.0/12 via BGP. To force all on-premises traffic from `snet-usw2-app` through the NVAs, a route table is associated with `snet-usw2-app` containing a user-defined route (UDR) for 172.16.0.0/12172.16.0.0/12 with the next hop set to the NVAs' internal load balancer IP address (10.200.1.10010.200.1.100).

A new branch office is added on-premises, and the Virtual Network Gateway in `vnet-usw2-hub` dynamically learns the specific subnet route 172.20.100.0/24172.20.100.0/24 via ExpressRoute BGP propagation. Azure Route Server propagates this route to `vnet-usw2-spoke`. Security audits show that traffic from `snet-usw2-app` destined for the new branch (172.20.100.0/24172.20.100.0/24) is bypassing the NVAs.

You need to ensure that traffic from `snet-usw2-app` to the new branch office is inspected by the NVAs.

What should you do?

Cevabı ve açıklamayı göster

Cevap: Add a user-defined route for 172.20.100.0/24172.20.100.0/24 with the next hop set to the Virtual Appliance IP address of 10.200.1.10010.200.1.100 in the route table associated with `snet-usw2-app`.

Cevap

Add a user-defined route for the specific branch subnet of 172.20.100.0/24172.20.100.0/24 pointing to the NVA internal load balancer (10.200.1.10010.200.1.100) on the route table associated with `snet-usw2-app`.
Adding a user-defined route for the specific branch subnet of 172.20.100.0/24172.20.100.0/24 pointing to the NVA internal load balancer is correct because Azure routing uses the Longest Prefix Match (LPM) algorithm. The dynamically learned BGP route for 172.20.100.0/24172.20.100.0/24 is more specific than the existing UDR for 172.16.0.0/12172.16.0.0/12. By creating an explicit UDR for 172.20.100.0/24172.20.100.0/24, the UDR overrides the BGP route of the same prefix length, directing the traffic to the NVAs.

Adım Adım Çözüm

1
Analyze the routing table of the subnet `snet-usw2-app`.
Identify that the routing table contains a UDR for 172.16.0.0/12172.16.0.0/12 pointing to 10.200.1.10010.200.1.100, and a propagated BGP route for 172.20.100.0/24172.20.100.0/24 pointing to the ExpressRoute gateway.
To understand why traffic to the new branch is bypassing the NVAs.
2
Apply the Azure routing priority rules, specifically Longest Prefix Match (LPM).
Determine that the 172.20.100.0/24172.20.100.0/24 prefix is longer and more specific than the 172.16.0.0/12172.16.0.0/12 prefix, meaning the BGP route to the gateway takes precedence over the broader NVA UDR.
To identify the root cause of the routing bypass.
3
Design a route modification that overrides the propagated BGP route without disrupting other dynamic on-premises routing.
Create a UDR for the specific prefix 172.20.100.0/24172.20.100.0/24 pointing to the NVA internal load balancer (10.200.1.10010.200.1.100). Since UDRs take precedence over BGP routes of the same prefix length, this forces the traffic through the NVAs.
To ensure that all traffic destined for the new branch office is inspected by the NVAs.

Anahtar Kavram

Azure Routing Precedence and Longest Prefix Match (LPM)
Tahmini Süre:2m 30s
Soru 139Soru

Your company, Aetheris Manufacturing, is designing a secure network architecture in Azure. The architecture consists of a Hub virtual network (VNet) and a Spoke VNet peered together. Subnet-App (10.20.1.0/2410.20.1.0/24) in the Spoke VNet hosts virtual machines running a production application. Subnet-PrivateLink (10.20.2.0/2410.20.2.0/24) in the Spoke VNet contains Private Endpoints for an Azure SQL Database (sqldb-prod.database.windows.net) and an Azure Key Vault (kv-prod.vault.azure.net). Public network access is disabled on both the SQL Database and the Key Vault. You must block all outbound traffic from Subnet-App to the public internet and ensure that the virtual machines can only communicate with the specific SQL Database and Key Vault instances. The solution must minimize administrative overhead. Which network security configuration should you recommend for Subnet-App?

Cevabı ve açıklamayı göster

Cevap: Configure outbound Network Security Group (NSG) rules on Subnet-App that allow destination traffic to the specific private IP addresses of the SQL Database and Key Vault private endpoints, followed by a rule that denies outbound traffic to the Internet service tag.

Cevap

Configure outbound Network Security Group (NSG) rules on Subnet-App that allow destination traffic to the specific private IP addresses of the SQL Database and Key Vault private endpoints, followed by a rule that denies outbound traffic to the Internet service tag.
The correct configuration uses outbound NSG rules targeting the specific private IP addresses of the SQL Database and Key Vault private endpoints, and then blocks all other outbound internet traffic using the Internet service tag. Because Private Endpoints utilize private IP addresses from the local VNet address space, NSG rules must target these private IPs rather than Service Tags, which only cover the public IP addresses of the services. Additionally, because the client subnet and the Private Endpoint subnet are in the same VNet, traffic is routed locally and bypasses default route table configurations pointing to a hub firewall.

Adım Adım Çözüm

1
Analyze how traffic to Private Endpoints is addressed and routed.
Private Endpoints receive private IP addresses from the subnet in which they are deployed (Subnet-PrivateLink, 10.20.2.0/24). Traffic destined for these endpoints is addressed to these private IPs, not to public IPs.
This determines how firewall rules, route tables, and NSGs will evaluate the destination addresses.
2
Evaluate the behavior of Service Tags in NSG rules and User Defined Routes (UDRs) for Private Endpoints.
Service tags (such as Sql or AzureKeyVault) represent public IP address ranges of Azure services. They do not match private IP addresses allocated to Private Endpoints.
This rules out solutions that attempt to filter or route Private Endpoint traffic using service tags.
3
Evaluate routing precedence for traffic within the same virtual network.
Traffic from Subnet-App (10.20.1.0/24) to Subnet-PrivateLink (10.20.2.0/24) is handled by the default local system route (10.20.0.0/16). A UDR for 0.0.0.0/0 is less specific and will not intercept this traffic.
This explains why routing through a central Azure Firewall using a default route fails to inspect or filter intra-VNet traffic to Private Endpoints.
4
Combine the findings to determine the correct and minimal security configuration.
Configure outbound NSG rules on Subnet-App to allow traffic to the specific private IPs of the Private Endpoints, and then deny outbound traffic to the Internet service tag to block all other outbound traffic.
This satisfies the requirement to allow only specific SQL Database and Key Vault traffic while blocking all other outbound internet traffic with minimal overhead.

Anahtar Kavram

Private Endpoint IP addressing bypasses public Service Tags and standard 0.0.0.0/0 UDRs for intra-VNet traffic, requiring NSG rules targeting specific private IPs to enforce network-level security boundaries.
Tahmini Süre:3m 0s
Soru 140Soru

A logistics company is designing the Azure compute virtualization infrastructure for its operations platform. The platform consists of two workloads:

* Workload A: A fleet telemetry ingestion service that runs continuously, requires a 99.99%99.99\% availability SLA, and cannot tolerate unexpected interruptions or evictions.
* Workload B: A monthly inventory forecasting simulation that can run asynchronously, can be paused and resumed, and must minimize costs as much as possible.

Which two compute configurations 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 Workload A on a Virtual Machine Scale Set in Flexible orchestration mode spread across multiple availability zones.; Deploy Workload B on Azure Spot Virtual Machines.

Cevap

Deploy Workload A on a Virtual Machine Scale Set in Flexible orchestration mode spread across multiple availability zones, and deploy Workload B on Azure Spot Virtual Machines.
Deploying the telemetry service on a Virtual Machine Scale Set in Flexible orchestration mode across multiple availability zones satisfies the high availability SLA and ensures continuous operation without eviction risk. Deploying the inventory forecasting simulation on Azure Spot VMs utilizes deeply discounted compute capacity that matches the workload's tolerance for pauses and interruptions.

Adım Adım Çözüm

1
Evaluate Workload A's availability and resilience requirements.
Identify that Workload A requires a 99.99%99.99\% SLA and cannot tolerate interruptions.
This rules out interruptible compute configurations and single-zone deployments.
2
Evaluate Workload B's operational flexibility and cost constraints.
Identify that Workload B can tolerate pauses, run asynchronously, and has a primary constraint of minimizing cost.
This makes Workload B an ideal candidate for discounted, interruptible compute options.
3
Map the evaluated workloads to their optimal Azure compute virtualization options.
Select Virtual Machine Scale Sets in Flexible orchestration mode across availability zones for Workload A to ensure SLA adherence, and select Spot VMs for Workload B to optimize costs.
This combination successfully meets all SLA, performance, and budget constraints.

Anahtar Kavram

Selecting Azure compute virtualization services based on availability, eviction tolerance, and cost constraints.
Tahmini Süre:2m 0s
ÖncekiSayfa 7 / 18Sonraki
Design Infrastructure Solutions Alıştırma Soruları — Microsoft Azure Solutions Architect (AZ-305) — Sayfa 7 | Examkin