Design Infrastructure Solutions

360 soru

Soru 181Soru

An energy exploration company is designing the Azure compute virtualization infrastructure for a seismic modeling platform. The platform consists of two primary workloads:

* Database Engine: A stateful, steady-state data store containing sensitive telemetry data. It must run on physical hardware isolated at the host level to meet compliance requirements. It requires a high memory-to-vCPU ratio and must maintain an uptime SLA of 99.99%.
* Simulation Pipeline: A massive batch-oriented parallel simulation runner. The pipeline is stateless, highly fault-tolerant, can resume from checkpoints, and must run at the lowest possible cost.

Which two compute virtualization 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 the Database Engine on Azure Dedicated Hosts using Esv5-series virtual machines allocated across multiple Availability Zones.; Deploy the Simulation Pipeline on Azure Spot Virtual Machines using Dsv5-series instances.

Cevap

Deploy the Database Engine on Azure Dedicated Hosts using Esv5-series virtual machines allocated across multiple Availability Zones, and deploy the Simulation Pipeline on Azure Spot Virtual Machines using Dsv5-series instances.
Deploying the Database Engine on Azure Dedicated Hosts with Esv5-series VMs across multiple Availability Zones guarantees host-level isolation, provides the required memory-to-vCPU ratio, and satisfies the 99.99% availability SLA. Deploying the Simulation Pipeline on Azure Spot VMs using Dsv5-series instances satisfies the requirement for the lowest cost compute, since the workload is stateless and capable of handling capacity eviction.

Adım Adım Çözüm

1
Analyze host isolation and memory requirements for the database workload.
Azure Dedicated Hosts are required to meet physical host isolation. E-series (such as Esv5) virtual machines must be used because they are memory-optimized.
This satisfies both the compliance requirement for hardware isolation and the technical requirement for a high memory-to-vCPU ratio.
2
Determine the high availability layout for the database engine to meet the SLA.
Distribute the Azure Dedicated Hosts across multiple Availability Zones.
Deploying dedicated hosts across multiple zones guarantees a 99.99% uptime SLA for the virtual machines running on those hosts.
3
Analyze the workload characteristics and cost requirements of the simulation pipeline.
Recommend Azure Spot VMs (e.g., using general-purpose Dsv5-series instances) for the Simulation Pipeline.
Since the simulation pipeline is stateless, fault-tolerant, and must run at the lowest possible cost, Spot VMs provide the optimal cost-saving mechanism despite their eviction model.

Anahtar Kavram

Selecting and configuring Azure compute virtualization components (Dedicated Hosts, Spot VMs, and VM series) to meet physical isolation, high availability SLA, hardware-profile, and cost constraints.
Soru 182Soru

A healthtech platform is designing an Azure architecture to ingest and analyze genomic sequencing datasets. The solution must support the following workloads:

* Workload A: An API endpoint that receives webhook notifications from external partners. The workload must scale dynamically from zero to handle high bursts of traffic, support custom domain names, and connect securely to an Azure SQL Database using virtual network integration.

* Workload B: A CPU-intensive file processing application packaged as a container image. Each processing run takes between 20 to 45 minutes depending on the file size. The compute resource must scale to zero when no files are available for processing, and it must minimize administrative overhead.

Which two Azure hosting services should you include in the design to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Azure Functions on a Flex Consumption plan for Workload A; Azure Container Apps Jobs for Workload B

Cevap

The hosting services that should be included are Azure Functions on a Flex Consumption plan for Workload A, and Azure Container Apps Jobs for Workload B.
Azure Functions on a Flex Consumption plan is correct for Workload A because it supports fast scaling, virtual network integration, and low cold starts. Azure Container Apps Jobs is correct for Workload B because it is designed for containerized, run-to-completion execution paths that run for hours (bypassing function timeout limits) and scale to zero when not active, without the overhead of AKS.

Adım Adım Çözüm

1
Analyze the scaling, networking, and security requirements for Workload A.
Workload A needs to scale dynamically from zero to handle bursts, support custom domains, and connect securely to Azure SQL Database using virtual network integration.
Virtual network integration is a key security requirement for accessing the database privately.
2
Evaluate hosting options for Workload A.
The standard Consumption plan for Azure Functions does not support virtual network integration. Flex Consumption supports both scale-to-zero and virtual network integration, satisfying all criteria for Workload A.
Choosing Flex Consumption meets the requirement of serverless scaling and private networking.
3
Analyze the execution duration, packaging, and management requirements for Workload B.
Workload B runs as a containerized application, takes between 20 and 45 minutes, must scale to zero when idle, and must minimize administrative overhead.
The 45-minute duration is a strict constraint that rules out standard serverless function timeouts.
4
Evaluate hosting options for Workload B.
Azure Functions on Consumption (10 minutes) and Elastic Premium (30 minutes) plans will timeout. Azure Kubernetes Service (AKS) supports the execution but violates the low administrative overhead constraint. Azure Container Apps Jobs supports run-to-completion containers, executes up to 24 hours, scales to zero, and has minimal administrative overhead.
Selecting Azure Container Apps Jobs provides the correct execution environment without exceeding timeout limits or adding excessive operational overhead.

Anahtar Kavram

Selecting serverless and container hosting solutions in Azure based on execution timeouts, networking needs, and operational overhead.
Soru 183Soru

A smart utilities company is designing a production telemetry processing system on Azure. The system will ingest continuous data streams from regional water meters and place them in an Azure Service Bus queue. A containerized backend application will retrieve the messages and perform complex data analysis.

The system must meet the following requirements:
* Scale container instances dynamically based on the queue length using Kubernetes Event-driven Autoscaling (KEDA).
* Support execution times of up to 25 minutes per data analysis task.
* Maintain continuous availability for this critical workload without risk of unexpected eviction.
* Minimize administrative and operational infrastructure overhead.

Which compute solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps

Cevap

Azure Container Apps
Azure Container Apps is the ideal solution because it is a serverless container platform that natively supports Kubernetes Event-driven Autoscaling (KEDA) out of the box, allowing container instances to scale dynamically based on the queue length. It minimizes administrative and operational overhead by removing the need to manage nodes, control planes, or cluster upgrades. It also supports long-running execution times beyond 10 minutes and provides stable, continuous availability suitable for production workloads without the eviction risks associated with Spot VM priority.

Adım Adım Çözüm

1
Analyze the scaling and infrastructure management requirements.
Identify that the solution must scale based on queue length using KEDA and minimize operational overhead.
This narrows the candidate services to managed container platforms that support event-driven scaling via KEDA.
2
Evaluate the execution timeout constraint against serverless options.
Determine that Azure Functions on a Consumption plan is ruled out due to its 10-minute maximum timeout since tasks can take up to 25 minutes.
Ensures the selected service can support long-running tasks without interruption.
3
Assess availability requirements and SLA constraints.
Rule out Azure Spot Virtual Machines because they do not guarantee continuous availability and are subject to eviction.
Ensures the workload is hosted on stable compute resources appropriate for production workloads.
4
Select the compute service that minimizes administrative overhead while meeting all technical requirements.
Azure Container Apps is selected over Azure Kubernetes Service (AKS) because AKS introduces excessive management overhead.
Aligns with Microsoft best practices for serverless container workloads when custom Kubernetes API access is not required.

Anahtar Kavram

Selecting container-based hosting solutions based on operational overhead, scaling, and execution duration
Tahmini Süre:1m 30s
Soru 184Soru

A healthcare provider is designing the Azure compute virtualization infrastructure for a clinical trial analysis application that processes sensitive patient data. The solution must satisfy the following requirements:

* Confidentiality: The patient data must be encrypted in memory during processing to prevent access by hypervisor administrators or other tenants.
* Resilience: The application virtual machines must be distributed across multiple physical hardware racks (fault domains) within an Azure region to guarantee high availability without allocating dedicated physical servers.
* Availability: The compute tier must support a 99.95%99.95\% availability SLA.
* Storage: The application requires high-performance disk storage supporting at least 5,000 IOPS5,000\text{ IOPS} per virtual machine instance for transaction logging.
* Licensing Costs: The solution must leverage existing Windows Server licenses to minimize operational expenses.

Which of the following compute virtualization designs should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy a Virtual Machine Scale Set in Flexible orchestration mode using DCasv5-series confidential virtual machines with Premium SSD disks, and enable Azure Hybrid Benefit.

Cevap

Deploy a Virtual Machine Scale Set in Flexible orchestration mode using DCasv5-series confidential virtual machines with Premium SSD disks, and enable Azure Hybrid Benefit.
The correct design uses a Virtual Machine Scale Set in Flexible orchestration mode with DCasv5-series confidential VMs and Premium SSD disks. The DCasv5-series virtual machines provide hardware-based memory encryption using AMD SEV-SNP to meet the confidentiality requirement. Flexible orchestration mode allows distributing virtual machines across multiple physical fault domains to ensure high availability without the overhead of renting dedicated physical hardware. Premium SSDs satisfy the storage requirement of 5,000 IOPS5,000\text{ IOPS} for transaction logging, and Azure Hybrid Benefit allows the reuse of existing Windows Server licenses to minimize operational costs.

Adım Adım Çözüm

1
Evaluate the confidentiality and licensing requirements to select the appropriate virtual machine configuration.
Select DCasv5-series confidential virtual machines and enable Azure Hybrid Benefit.
DCasv5-series VMs utilize AMD SEV-SNP to provide hardware-based memory encryption. Azure Hybrid Benefit allows the customer to reuse existing Windows Server licenses to minimize compute costs.
2
Determine the scale-out compute structure and resilience requirements.
Choose a Virtual Machine Scale Set (VMSS) in Flexible orchestration mode.
Flexible orchestration mode allows spreading VMs across fault domains without dedicated physical hardware, providing a 99.95%99.95\% SLA for individual VM instances, which meets the resilience and availability targets.
3
Evaluate the disk performance parameters.
Select Premium SSD storage.
Premium SSDs support the required 5,000 IOPS5,000\text{ IOPS} target with low latency, unlike Standard HDDs which fail to meet the performance threshold.

Anahtar Kavram

Designing secure, high-availability virtualized workloads on Azure using Virtual Machine Scale Sets in Flexible orchestration mode and Confidential VMs (DCasv5-series).
Soru 185Soru

An enterprise is designing a hub-and-spoke virtual network topology in Azure. The transit hub virtual network, `vnet-hub-transit` (172.16.0.0/16172.16.0.0/16), contains a firewall subnet, `AzureFirewallSubnet` (172.16.0.0/24172.16.0.0/24), hosting an Azure Firewall with a private IP address of 172.16.0.4172.16.0.4. The application virtual network, `vnet-spoke-app` (172.17.0.0/16172.17.0.0/16), is peered with `vnet-hub-transit` and contains two subnets: `snet-web` (172.17.1.0/24172.17.1.0/24) and `snet-biz` (172.17.2.0/24172.17.2.0/24). Another virtual network, `vnet-spoke-db` (172.18.0.0/16172.18.0.0/16), contains the database tier and is also peered with `vnet-hub-transit`.

You need to configure a route table associated with `snet-web`. The routing configuration must meet the following requirements:
- Route all outbound internet traffic from `snet-web` through the Azure Firewall.
- Route all database-bound traffic from `snet-web` to `vnet-spoke-db` through the Azure Firewall.
- Ensure that VMs within `snet-web` can communicate directly with VMs in `snet-biz` without routing traffic through the firewall.

Which route configuration should you apply to the route table associated with `snet-web`?

Cevabı ve açıklamayı göster

Cevap: A route for 0.0.0.0/00.0.0.0/0 pointing to the virtual appliance at 172.16.0.4172.16.0.4, and a route for 172.18.0.0/16172.18.0.0/16 pointing to the virtual appliance at 172.16.0.4172.16.0.4.

Cevap

Configure a route for 0.0.0.0/00.0.0.0/0 pointing to the virtual appliance at 172.16.0.4172.16.0.4, and a route for 172.18.0.0/16172.18.0.0/16 pointing to the virtual appliance at 172.16.0.4172.16.0.4.
The correct configuration applies two specific User Defined Routes (UDRs) to the route table for the web subnet. The first route (0.0.0.0/00.0.0.0/0 to 172.16.0.4172.16.0.4) handles all default egress to the internet. The second route (172.18.0.0/16172.18.0.0/16 to 172.16.0.4172.16.0.4) targets the peered database network. Because no user-defined route is configured for the local virtual network range (172.17.0.0/16172.17.0.0/16), the default local system route remains active. This allows traffic between the web and business subnets to route directly without traversing the firewall, satisfying all requirements.

Adım Adım Çözüm

1
Identify the destinations that require transit through the Azure Firewall.
Internet traffic corresponds to prefix 0.0.0.0/00.0.0.0/0. Traffic to the database virtual network corresponds to prefix 172.18.0.0/16172.18.0.0/16. Both require a next hop of the virtual appliance IP 172.16.0.4172.16.0.4.
This establishes the necessary forwarding rules to send the external traffic to the firewall.
2
Analyze how local subnet-to-subnet traffic within the application virtual network is routed.
By default, Azure creates a system route for the local virtual network prefix (172.17.0.0/16172.17.0.0/16 -> Local) which allows subnets like `snet-web` and `snet-biz` to communicate directly.
Understanding default system routes helps determine if any user-defined routes will interfere with them.
3
Evaluate user-defined routes to ensure they do not overlap with and override the local system route.
The configured routes (0.0.0.0/00.0.0.0/0 and 172.18.0.0/16172.18.0.0/16) do not overlap with the local 172.17.0.0/16172.17.0.0/16 address space. Therefore, local communication between `snet-web` and `snet-biz` remains direct and does not go to the firewall.
Ensures the design meets the requirement to keep local traffic direct and avoid firewall overhead.

Anahtar Kavram

Azure route selection behavior, User Defined Routes (UDR) override precedence, and Longest Prefix Match (LPM) logic for local virtual network traffic.
Tahmini Süre:1m 30s
Soru 186Soru

An administrator is configuring a high-availability backend pool for a Standard SKU Azure Load Balancer. The backend pool contains several Azure Virtual Machines, but each virtual machine currently has a Basic SKU public IP address associated with its network interface. During deployment, the administrator encounters a validation failure. Which of the following configuration changes can resolve this validation mismatch? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Upgrade the public IP addresses of the virtual machines to the Standard SKU.; Remove the Basic SKU public IP addresses from the network interfaces of the virtual machines.

Cevap

To resolve the validation failure, you must either upgrade the virtual machines' public IP addresses to the Standard SKU or remove the Basic SKU public IP addresses from their network interfaces entirely.
The Standard Azure Load Balancer requires that all virtual machines in its backend pool use Standard SKU public IP addresses or have no public IP addresses assigned at all. Therefore, upgrading the virtual machines' public IPs to the Standard SKU or removing the Basic SKU public IPs entirely satisfies the SKU alignment constraints and resolves the validation failure.

Adım Adım Çözüm

1
Identify the cause of the validation failure
The failure is due to a SKU mismatch between the Standard Load Balancer and the Basic SKU public IPs attached to the backend virtual machines.
Standard Azure Load Balancer backend pools require all member virtual machines to use either Standard SKU public IPs or no public IPs at all.
2
Determine valid resolution methods that maintain the Standard Load Balancer
We can either upgrade the public IPs to the Standard SKU to match the load balancer, or disassociate the Basic public IPs from the virtual machines.
These actions satisfy the Standard SKU constraints of the Azure Load Balancer.

Anahtar Kavram

Azure Load Balancer SKU alignment constraints
Soru 187Soru

A digital marketing agency is designing the compute infrastructure for a new campaign analytics platform. The platform must support two distinct workloads:

1. **Workload 11**: A public-facing REST API that collects clickstream events from active marketing campaigns. The API is containerized, requires outbound virtual network (VNet) integration to access an Azure SQL Database via private endpoints, and experiences highly unpredictable demand, scaling down to 00 instances during off-peak hours to eliminate idle costs. Minimal infrastructure management is a key priority.
2. **Workload 22**: A data processing worker that aggregates campaign metrics daily. The worker is packaged as a container, runs as a single batch job that executes for approximately 4040 minutes, and requires access to local scratch disk storage for temporary data processing.

Which compute hosting architecture should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps for Workload 11, and Azure Container Apps Jobs for Workload 22.

Cevap

Azure Container Apps for Workload 11, and Azure Container Apps Jobs for Workload 22
The compute architecture recommending Azure Container Apps for Workload 11 and Azure Container Apps Jobs for Workload 22 is correct because Azure Container Apps provides a serverless platform that supports scaling to 00 instances, VNet integration, and minimum administrative overhead. Azure Container Apps Jobs is purpose-built for run-to-completion, long-running (up to several hours) containerized execution, fully accommodating the 4040-minute duration of the daily aggregation job.

Adım Adım Çözüm

1
Analyze the scaling and cost constraints of Workload 11.
Workload 11 requires containerized hosting, outbound VNet integration, minimal management overhead, and must scale to 00 instances during idle periods to avoid costs.
This rules out Azure App Service Premium v 33 because it does not scale to zero cost, and rules out Azure Kubernetes Service (AKS) due to high administrative overhead.
2
Analyze the execution duration and environment constraints of Workload 22.
Workload 22 runs as a single batch container for 4040 minutes and requires scratch disk space.
This rules out Azure Functions on a Consumption plan because its maximum execution duration is restricted to 1010 minutes.
3
Identify the service combinations that satisfy both workloads.
Azure Container Apps (ACA) satisfies Workload 11's requirements. Azure Container Apps Jobs (ACA Jobs) supports long-running (up to several hours) containerized batch execution and local storage, satisfying Workload 22.
Combining ACA and ACA Jobs delivers a fully serverless, containerized solution with minimal management overhead, VNet support, and scale-to-zero capabilities for both components.

Anahtar Kavram

Selecting optimal serverless and web hosting architectures in Azure based on execution timeouts, scaling constraints, and operational overhead.
Tahmini Süre:2m 0s
Soru 188Soru

An organization is designing a hub-and-spoke virtual network topology in Azure. The hub virtual network, `vnet-neure-hub-01` (10.240.0.0/1610.240.0.0/16), contains an Azure Route Server in the `RouteServerSubnet` (10.240.2.0/2410.240.2.0/24) and a pair of Network Virtual Appliances (NVAs) in `snet-nva` (10.240.1.0/2410.240.1.0/24) that establish BGP sessions with the Route Server. The NVAs advertise on-premises network routes (192.168.0.0/16192.168.0.0/16). You peer a spoke virtual network named `vnet-neure-spoke-app` (10.241.0.0/2410.241.0.0/24) with `vnet-neure-hub-01`. You must ensure that virtual machines in `vnet-neure-spoke-app` can dynamically learn the routes advertised by the NVAs via Azure Route Server, without using User-Defined Routes (UDRs). Which two configurations should you implement?

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

Cevabı ve açıklamayı göster

Cevap: Configure the peering from `vnet-neure-spoke-app` to `vnet-neure-hub-01` to use the remote virtual network's gateway or Route Server.; Configure the peering from `vnet-neure-hub-01` to `vnet-neure-spoke-app` to use this virtual network's gateway or Route Server.

Cevap

Configure the peering from `vnet-neure-spoke-app` to `vnet-neure-hub-01` to use the remote virtual network's gateway or Route Server, and configure the peering from `vnet-neure-hub-01` to `vnet-neure-spoke-app` to use this virtual network's gateway or Route Server.
The correct configurations involve enabling gateway and Route Server transit on both ends of the Virtual Network Peering. Specifically, you must configure the peering from the spoke VNet to the hub VNet to use the remote virtual network's gateway or Route Server, and configure the peering from the hub VNet to the spoke VNet to use this virtual network's gateway or Route Server. These settings allow the routing table of the spoke VNet to be dynamically updated with the BGP routes exchanged between the Route Server and the NVAs.

Adım Adım Çözüm

1
Analyze Azure Route Server routing requirements for spoke virtual networks.
Identify that spoke VNets peered with a hub VNet containing Azure Route Server do not automatically receive advertised BGP routes unless transit peering settings are enabled.
By default, Route Server does not propagate learned routes to spoke virtual networks unless transit routing settings are configured on the virtual network peering.
2
Configure the spoke-to-hub peering properties.
Enable 'Use the remote virtual network's gateway or Route Server' on the peering configuration from the spoke VNet to the hub VNet.
This allows the spoke VNet to consume the routing services provided by the Azure Route Server located in the peered hub VNet.
3
Configure the hub-to-spoke peering properties.
Enable 'Use this virtual network's gateway or Route Server' on the peering configuration from the hub VNet to the spoke VNet.
This grants permission for the hub VNet to propagate its gateway and Route Server routes to the peered spoke VNet.

Anahtar Kavram

Azure Route Server facilitates dynamic route exchange between NVAs and virtual networks using BGP. To allow peered spoke VNets to dynamically learn routes propagated by the Route Server in a hub VNet, transit options must be enabled on both sides of the VNet peering (specifically `useRemoteGateways` on the spoke side and `allowGatewayTransit` on the hub side).
Soru 189Soru

A company is modernizing a web application that will be hosted in a single Azure region. The solution must meet the following requirements:
- Support SSL/TLS termination at the load balancer.
- Support URL path-based routing (HTTP/HTTPS).
- Provide regional zone-redundant high availability.
- Ensure the configuration does not fail validation due to SKU mismatches.

Which load balancing configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Application Gateway (Standard v2) with backend virtual machines distributed across multiple Availability Zones

Cevap

Azure Application Gateway (Standard v2) with backend virtual machines distributed across multiple Availability Zones
The correct configuration is the Azure Application Gateway (Standard v2) with backend virtual machines distributed across multiple Availability Zones. This service operates at Layer 7, providing the required SSL/TLS termination and URL path-based routing. Distributing the virtual machines across multiple Availability Zones satisfies the zone-redundant high availability requirement.

Adım Adım Çözüm

1
Identify the protocol and routing requirements.
The application requires HTTP/HTTPS routing, SSL/TLS termination, and path-based routing, which necessitates a Layer 7 load balancer.
Layer 4 load balancers like Azure Load Balancer and DNS-based service routing like Traffic Manager do not inspect HTTP/HTTPS payloads.
2
Evaluate the high availability and regional constraints.
The solution must be regional and zone-redundant, meaning backend virtual machines must be distributed across multiple Availability Zones.
Placing all instances in a single Availability Zone fails zone-redundancy requirements.
3
Check validation and SKU constraints.
Avoid mixing Basic and Standard SKU configurations.
A Standard Load Balancer cannot connect to resources with Basic SKU public IP addresses, whereas Application Gateway v2 works seamlessly with standard configurations.

Anahtar Kavram

Application Load Balancing and Delivery
Soru 190Soru

A healthcare technology provider is designing a SaaS application on Azure that will process patient telemetry data across two different regions: Germany and the United States.

The solution must meet the following requirements:
- Host a containerized processing microservice that scales dynamically based on the queue depth of an Azure Service Bus queue.
- Separate the logging and monitoring data of patient events to comply with strict regional data sovereignty laws in each country.
- Minimize administrative effort and infrastructure management overhead.

Which two components should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps to host the processing microservice; Separate Azure Log Analytics workspaces in Germany and the United States to isolate monitoring data

Cevap

Azure Container Apps to host the processing microservice, and separate Azure Log Analytics workspaces in Germany and the United States to isolate monitoring data.
The correct design incorporates Azure Container Apps because it natively integrates with KEDA to scale workloads based on queue metrics without the administrative overhead of managing a Kubernetes cluster. Additionally, separate Log Analytics workspaces in each region ensure strict regional data isolation to meet sovereignty compliance regulations.

Adım Adım Çözüm

1
Evaluate compute options for hosting containerized microservices scaling on queue depth with minimal administrative effort.
Identify that Azure Container Apps supports KEDA scaling out-of-the-box and handles underlying infrastructure management, making it superior to Azure Kubernetes Service for low-overhead needs.
This meets the requirement of hosting containers with dynamic scaling while minimizing administrative effort.
2
Evaluate monitoring options for strict regional data sovereignty across Germany and the United States.
Determine that separate Log Analytics workspaces are required in each region to ensure physical boundary separation and compliance.
This meets the strict compliance and data sovereignty rules by avoiding co-mingling patient logs in a single central workspace.

Anahtar Kavram

Selecting container hosting and monitoring strategies that balance scaling capabilities, operational overhead, and compliance constraints in Azure.
Soru 191Soru

An enterprise is designing a serverless data processing pipeline in Azure to support a telemetry analysis system. The solution must host the following workloads:

- Workload 1: An event-driven API endpoint that ingests telemetry data. The workload must scale rapidly from 00 to handle unpredictable traffic spikes, incur 00 cost when idle, and route outbound traffic through an Azure Virtual Network to securely access a private database.
- Workload 2: A batch processing job that runs containerized custom simulation code triggered by telemetry events. The job must run for up to 4545 minutes per execution and dynamically scale down to 00 instances when no simulations are active.

The architecture must minimize operational management overhead and monthly hosting costs.

Which two compute solutions should you recommend? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure Functions on a Flex Consumption plan for Workload 1; Azure Container Apps Jobs for Workload 2

Cevap

Azure Functions on a Flex Consumption plan should be recommended for Workload 1, and Azure Container Apps Jobs should be recommended for Workload 2.
Azure Functions on a Flex Consumption plan is the correct choice for the event-driven ingestion workload because it combines event-driven serverless scaling and scale-to-zero capabilities with native virtual network integration. Azure Container Apps Jobs is the correct choice for the batch simulation workload because it is serverless, scales to zero when no jobs are active, supports custom containerized runtimes, and allows jobs to execute for up to 2424 hours, which easily accommodates the 4545-minute runtime without timeout failures.

Adım Adım Çözüm

1
Evaluate the requirements for Workload 1.
Workload 1 requires rapid scale-out from 00, zero cost when idle, and outbound virtual network integration to reach a private database. Azure Functions on a Flex Consumption plan meets all these needs.
Standard Consumption plans lack virtual network integration, while App Service plans do not scale to zero or scale out as rapidly.
2
Evaluate the requirements for Workload 2.
Workload 2 requires containerized execution, dynamic scale-to-zero behavior, and support for a 4545-minute execution duration. Azure Container Apps Jobs meets these constraints.
Azure Functions on Consumption plans are limited by a 1010-minute timeout, and deploying an Azure Kubernetes Service cluster would introduce excessive operational management overhead.
3
Select the correct combination.
Azure Functions on a Flex Consumption plan for Workload 1 and Azure Container Apps Jobs for Workload 2.
This combination satisfies all networking, execution duration, and cost/overhead constraints.

Anahtar Kavram

Selecting serverless compute resources based on scaling behaviors, networking requirements, execution timeouts, and operational overhead.
Soru 192Soru

An organization has deployed a virtual network named `vnet-prod-uswest` (10.110.0.0/1610.110.0.0/16) that contains two subnets: `subnet-web` (10.110.1.0/2410.110.1.0/24) and `subnet-data` (10.110.2.0/2410.110.2.0/24). A Network Virtual Appliance (NVA) is deployed in a peered hub virtual network at 10.120.1.410.120.1.4.

The organization needs to inspect all traffic sent from `subnet-web` to `subnet-data` using the NVA. The solution must ensure that virtual machines within `subnet-web` can still communicate directly with each other without routing through the NVA.

Which route should be added to the route table associated with `subnet-web`?

Cevabı ve açıklamayı göster

Cevap: Address prefix: 10.110.2.0/2410.110.2.0/24, Next hop type: Virtual appliance, Next hop address: 10.120.1.410.120.1.4

Cevap

Address prefix: 10.110.2.0/2410.110.2.0/24, Next hop type: Virtual appliance, Next hop address: 10.120.1.410.120.1.4
The correct route uses the destination prefix 10.110.2.0/2410.110.2.0/24, which matches only the database subnet. Because Azure uses the Longest Prefix Match algorithm, traffic destined for the database subnet will match this route and be forwarded to the NVA. Traffic destined for other resources within the same web subnet (10.110.1.0/2410.110.1.0/24) will not match this route and will instead use the system-defined local route (10.110.0.0/1610.110.0.0/16) with next hop 'Virtual Network', keeping the local communication direct.

Adım Adım Çözüm

1
Identify the destination subnet of the traffic that requires inspection.
The target traffic is destined for `subnet-data` which uses the prefix 10.110.2.0/2410.110.2.0/24.
Routing policies in Azure should target the most specific prefix possible to avoid affecting unrelated traffic paths.
2
Evaluate the priority and behavior of Azure system routes versus User-Defined Routes (UDRs).
Azure uses Longest Prefix Match (LPM) to select routes. If a UDR and a system route have identical prefixes, the UDR is preferred.
Understanding route selection order ensures the custom route is selected over the default system route.
3
Create a route that targets only the destination subnet and routes it to the NVA IP address.
A route with prefix 10.110.2.0/2410.110.2.0/24 pointing to next hop 10.120.1.410.120.1.4 is associated with `subnet-web`.
Traffic to `subnet-data` (10.110.2.0/2410.110.2.0/24) matches the UDR and goes to the NVA. Traffic within `subnet-web` (10.110.1.x10.110.1.x) does not match the UDR prefix and falls back to the system route (10.110.0.0/1610.110.0.0/16, next hop Virtual Network), keeping local traffic direct.

Anahtar Kavram

Azure route precedence rules and Longest Prefix Match (LPM) behavior with User-Defined Routes (UDRs)
Tahmini Süre:1m 30s
Soru 193Soru

An organization is designing a hub-and-spoke network topology in Azure. The hub virtual network, `vnet-hub-shared`, has an address space of 10.100.0.0/1610.100.0.0/16 and contains an Azure VPN Gateway in `GatewaySubnet` (10.100.0.0/2410.100.0.0/24) and a Network Virtual Appliance (NVA) at IP address 10.100.10.410.100.10.4. The spoke virtual network, `vnet-spoke-app`, has an address space of 10.101.0.0/1610.101.0.0/16. The networks are connected via virtual network peering.

The design must meet the following requirements:
- Spoke virtual machines must route all internet-bound traffic through the NVA in the hub.
- Spoke virtual machines must communicate with an on-premises network (172.16.0.0/12172.16.0.0/12) through the VPN Gateway.
- Spoke virtual machines must communicate directly with resources in the hub virtual network (10.100.0.0/1610.100.0.0/16) without passing through the NVA.

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

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

Cevabı ve açıklamayı göster

Cevap: Configure the virtual network peering to allow gateway transit on `vnet-hub-shared` and use the remote virtual network's gateway on `vnet-spoke-app`.; Create a route table associated with the subnets in `vnet-spoke-app` that contains a route for 0.0.0.0/00.0.0.0/0 with the next hop set to the virtual appliance at 10.100.10.410.100.10.4.

Cevap

Configure virtual network peering to allow gateway transit on the hub and use remote gateways on the spoke, and create a route table associated with the spoke subnets containing a route for 0.0.0.0/00.0.0.0/0 with the next hop set to the virtual appliance.
The correct configurations involve setting up virtual network peering to allow gateway transit and use remote gateways, combined with a user-defined default route (0.0.0.0/00.0.0.0/0) pointing to the network virtual appliance (NVA). Gateway transit allows the spoke virtual network to learn on-premises routes via BGP propagation. The default route redirects internet-bound traffic to the NVA. Because the peering system route for the hub (10.100.0.0/1610.100.0.0/16) and the propagated BGP routes for the on-premises network (172.16.0.0/12172.16.0.0/12) are more specific than the default route, they take precedence under Azure's longest prefix match algorithm, ensuring direct traffic to the hub and correct routing to the VPN gateway.

Adım Adım Çözüm

1
Configure gateway transit settings on the virtual network peering connections.
The peering connection allows the spoke virtual network to route traffic through the hub's VPN gateway to access on-premises networks.
By default, peering connections do not allow gateway transit. Enabling 'allow gateway transit' on the hub and 'use remote gateways' on the spoke enables BGP route propagation from the gateway to the spoke.
2
Ensure BGP route propagation is enabled on the spoke's route table and add a default route (0.0.0.0/00.0.0.0/0) to the NVA.
All internet-bound traffic is redirected to the NVA, while on-premises traffic (172.16.0.0/12172.16.0.0/12) and local hub traffic (10.100.0.0/1610.100.0.0/16) route directly via BGP and peering system routes.
Azure's routing selection algorithm uses Longest Prefix Match (LPM). More specific routes (such as 10.100.0.0/1610.100.0.0/16 for the hub and 172.16.0.0/12172.16.0.0/12 for on-premises) will always take precedence over the default route (0.0.0.0/00.0.0.0/0) to the NVA.

Anahtar Kavram

Azure virtual network routing priority, virtual network peering gateway transit, and the longest prefix match algorithm.
Tahmini Süre:2m 0s
Soru 194Soru

An enterprise is designing a hub-and-spoke network topology in Azure for a multi-tier application. The architecture includes:

* A hub virtual network named `vnet-prod-hub` with an address space of 10.150.0.0/1610.150.0.0/16.
* `AzureFirewallSubnet` (10.150.1.0/2410.150.1.0/24) containing an Azure Firewall with private IP 10.150.1.410.150.1.4.
* `GatewaySubnet` (10.150.2.0/2410.150.2.0/24) containing a Virtual Network Gateway connected to on-premises via ExpressRoute.
* A spoke virtual network named `vnet-prod-spoke` with an address space of 10.160.0.0/1610.160.0.0/16.
* Subnet `snet-compute` (10.160.10.0/2410.160.10.0/24) hosting virtual machines.

The hub and spoke virtual networks are peered. The peering is configured to allow gateway transit on the hub and use remote gateways on the spoke.

The security requirements are:
1. All traffic from `snet-compute` destined for the internet must be routed through the Azure Firewall.
2. All traffic from `snet-compute` destined for the on-premises network (172.16.0.0/12172.16.0.0/12) must be routed through the Virtual Network Gateway.
3. All traffic from `snet-compute` destined for the hub virtual network (`vnet-prod-hub`) must be routed through the Azure Firewall for security inspection.

To implement these requirements, a network architect creates a route table named `rt-spoke-routing` with the following user-defined routes (UDRs):
* Route 1: 0.0.0.0/00.0.0.0/0 \rightarrow Next hop: Virtual appliance (10.150.1.410.150.1.4)
* Route 2: 10.150.0.0/1610.150.0.0/16 \rightarrow Next hop: Virtual appliance (10.150.1.410.150.1.4)

The architect associates `rt-spoke-routing` with the `snet-compute` subnet. To ensure symmetric inspection for return traffic, the architect also associates the same `rt-spoke-routing` route table with the `AzureFirewallSubnet`.

During post-deployment validation, VMs in `snet-compute` can successfully access the internet, but they cannot establish any connections to resources in the hub virtual network, and the Azure Firewall fails to pass traffic to the Gateway Subnet.

Which configuration change should the architect perform to resolve the connectivity issue while satisfying all design requirements?

Cevabı ve açıklamayı göster

Cevap: Remove the association of the `rt-spoke-routing` route table from the `AzureFirewallSubnet`, and allow the firewall to use default system routes for local hub destinations.

Cevap

Remove the association of the `rt-spoke-routing` route table from the `AzureFirewallSubnet`, allowing the firewall to rely on default system routes for local hub destinations.
The correct option is the one suggesting to remove the association of the route table from the firewall subnet. In Azure, User-Defined Routes (UDRs) override system-defined routes of the same prefix length. By applying the route table containing the 10.150.0.0/1610.150.0.0/16 prefix (pointing to the firewall itself as a virtual appliance) to the firewall's own subnet, a routing loop is created. Any packet the firewall attempts to forward to other subnets in the hub virtual network matches the UDR and is routed back to the firewall. Removing this association allows the firewall to use the default system route (10.150.0.0/1610.150.0.0/16 -> Virtual Network) to successfully route traffic to other hub subnets, while the spoke still routes hub-bound traffic to the firewall.

Adım Adım Çözüm

1
Analyze the route table configuration and its associations.
The route table `rt-spoke-routing` contains a route for 10.150.0.0/1610.150.0.0/16 pointing to the firewall at 10.150.1.410.150.1.4. This route table is associated with both the spoke subnet `snet-compute` and the hub `AzureFirewallSubnet`.
Understanding which subnets are bound to the routing rules determines how next hops are resolved for transit traffic.
2
Determine the impact of the UDR on the firewall's own subnet.
The firewall subnet resides within the 10.150.0.0/1610.150.0.0/16 VNet range. When the firewall tries to forward traffic to a hub destination (like the gateway at 10.150.2.x10.150.2.x), the matching route is the UDR 10.150.0.0/1610.150.0.0/16 pointing to 10.150.1.410.150.1.4.
Azure evaluates User-Defined Routes (UDRs) over default system routes of the same prefix length, which overrides the local VNet system route.
3
Identify the routing loop.
The next hop for the destination in the hub is resolved to the firewall itself (10.150.1.410.150.1.4), creating a loop where the packet repeatedly routes back to the firewall and is eventually dropped.
This explains why VMs in the spoke cannot communicate with resources in the hub and why firewall traffic fails to reach the gateway.
4
Select the correct remediation strategy.
Dissociate the `rt-spoke-routing` route table from the `AzureFirewallSubnet`. The firewall will now use default system routing, which contains a system route for 10.150.0.0/1610.150.0.0/16 pointing to 'Virtual Network'.
This allows the firewall to successfully forward traffic to other hub subnets while maintaining the required traffic inspection on the spoke subnet where the route table remains associated.

Anahtar Kavram

Azure User Defined Routes (UDR) precedence and routing loops in firewall subnets.
Tahmini Süre:3m 0s
Soru 195Soru

An administrator needs to configure a Network Security Group (NSG) to allow outbound traffic from an Azure Virtual Network subnet to Azure SQL Database. The IP addresses for Azure SQL Database might change over time. The solution must minimize administrative overhead. Which NSG rule configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Set the destination of the outbound security rule to the Sql service tag.

Cevap

Set the destination of the outbound security rule to the Sql service tag.
Using the Sql service tag as the destination in the Network Security Group (NSG) outbound rule allows access to the Azure SQL Database service. Service tags represent a group of IP address prefixes from a given Azure service and are managed automatically by Microsoft, which minimizes administrative overhead.

Adım Adım Çözüm

1
Identify the destination service that the virtual machines need to access.
Azure SQL Database
The virtual machines must establish outbound connections to Azure SQL Database.
2
Determine the network security mechanism to control outbound traffic with minimal administrative overhead.
Network Security Group (NSG) rule using a Service Tag.
Microsoft manages the IP prefixes associated with Service Tags, preventing the need to manually update rules when IPs change.
3
Select the specific Service Tag for Azure SQL Database.
The Sql service tag.
The Sql service tag represents Azure SQL Database, Azure SQL Managed Instance, and Azure Synapse Analytics.

Anahtar Kavram

Azure NSG Service Tags
Soru 196Soru

A logistics company is designing an event-driven system to generate end-of-day shipping manifests. The generation process reads transaction logs, formats reports, and takes between 12 and 18 minutes to complete per run. The process is triggered by a scheduler message in an Azure Service Bus queue. The company requires a compute solution that minimizes operational overhead and incurs costs only when executing. Which compute option should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps Jobs

Cevap

Azure Container Apps Jobs
Azure Container Apps Jobs are designed specifically for tasks that run to completion, support executions up to 24 hours, scale to zero when idle, and run as serverless resources with minimal operational overhead.

Adım Adım Çözüm

1
Analyze the execution duration requirement.
The workload runs for 12 to 18 minutes, which exceeds the 10-minute maximum execution timeout limit of the Azure Functions Consumption plan.
This rules out standard consumption-based Azure Functions.
2
Evaluate the cost and scaling requirements.
The solution must scale to zero and incur costs only during execution. Dedicated hosting plans are billed continuously and do not meet this constraint.
This rules out App Service plans and Dedicated Function plans.
3
Assess the operational overhead constraints.
Azure Container Apps Jobs manage container orchestration automatically and support long-running event-driven tasks, whereas Azure Kubernetes Service (AKS) requires managing nodes, clusters, and complex configurations.
This identifies Azure Container Apps Jobs as the option that minimizes operational overhead while meeting all timeout and cost requirements.

Anahtar Kavram

Selecting serverless compute hosting options based on execution timeout, scaling characteristics, and operational overhead constraints.
Tahmini Süre:1m 30s
Soru 197Soru

A financial firm is designing a secure network environment for a pool of virtual machines in a virtual network subnet named Subnet1. The design must meet the following requirements:
- The virtual machines must retrieve cryptographic keys from an Azure Key Vault.
- The virtual machines must be isolated behind a load balancer that distributes incoming traffic.
- All outbound traffic to the internet must be blocked except for connections to Azure Key Vault.
- The configuration must minimize administrative maintenance.

Which security and load balancing configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Configure an outbound security rule in the Network Security Group (NSG) that allows traffic to the AzureKeyVault Service Tag, and associate a Standard Load Balancer with Standard SKU public IP addresses.

Cevap

Configure an outbound security rule in the Network Security Group (NSG) that allows traffic to the AzureKeyVault Service Tag, and associate a Standard Load Balancer with Standard SKU public IP addresses.
The correct choice is to configure an outbound security rule allowing traffic to the AzureKeyVault Service Tag combined with a Standard Load Balancer utilizing Standard SKU public IP addresses. This minimizes administrative overhead because Azure manages the IP address updates for the Service Tag, and matches the SKUs required for the load balancer.

Adım Adım Çözüm

1
Identify the service tag requirement.
Azure Key Vault public endpoints are represented by the AzureKeyVault service tag, which updates automatically and eliminates the need for manual IP list maintenance.
This satisfies the requirement to minimize administrative maintenance.
2
Select the correct Load Balancer SKU combination.
Standard Load Balancer requires Standard SKU public IP addresses; mixing them with Basic SKU public IP addresses is not supported.
This ensures compatibility and successful resource deployment.
3
Verify routing requirements.
Avoid configuring custom routes that override system-defined local routes to ensure internal virtual network communications remain operational.
This prevents network connectivity loss within the VNet.

Anahtar Kavram

Configuring secure service access using Service Tags in NSGs while maintaining Standard SKU compatibility across network resources.
Soru 198Soru

An enterprise is designing a hub-and-spoke network topology in Azure. The hub virtual network, `vnet-weur-hub` (10.100.0.0/1610.100.0.0/16), contains an ExpressRoute Gateway in `GatewaySubnet`, an Azure Route Server in `RouteServerSubnet` (10.100.1.0/2410.100.1.0/24), and a pair of active-passive Network Virtual Appliances (NVAs) in `NvaSubnet` (10.100.2.0/2410.100.2.0/24). The spoke virtual network, `vnet-weur-spoke-prod` (10.101.0.0/1610.101.0.0/16), is peered directly with the hub.

To implement security inspection, all egress traffic to the internet (0.0.0.0/00.0.0.0/0) from both the spoke and the hub must be routed through the NVA (10.100.2.410.100.2.4). The NVA advertises the 0.0.0.0/00.0.0.0/0 route to the Azure Route Server via BGP.

Which two configurations must you implement to ensure routing functions correctly without routing loops or unsupported configurations?

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

Cevabı ve açıklamayı göster

Cevap: Associate a route table to the `NvaSubnet` containing a User Defined Route (UDR) for 0.0.0.0/00.0.0.0/0 with a next hop type of `Internet`.; Configure the virtual network peering on `vnet-weur-spoke-prod` to use the remote virtual network's gateway or route server, and configure the peering on `vnet-weur-hub` to allow gateway transit.

Cevap

Associate a User Defined Route (UDR) for 0.0.0.0/00.0.0.0/0 pointing to the next hop type of `Internet` on the `NvaSubnet` route table, and configure the virtual network peering on `vnet-weur-spoke-prod` to use the remote gateway/route server while allowing gateway transit on the `vnet-weur-hub` peering.
When an NVA advertises a default route (0.0.0.0/00.0.0.0/0) via BGP to Azure Route Server, the Route Server propagates this default route to all subnets in the hub VNet and peered spoke VNets. To prevent a routing loop where the NVA forwards traffic back to itself, you must override the BGP route on the NVA's subnet by associating a UDR for 0.0.0.0/00.0.0.0/0 with a next hop type of `Internet`. Additionally, for the spoke VNet to receive this dynamic default route from the Route Server in the hub VNet, the VNet peering must be configured to support gateway transit (allowing gateway transit on the hub VNet side and using the remote gateway or route server on the spoke VNet side).

Adım Adım Çözüm

1
Analyze the route propagation behavior of Azure Route Server (ARS).
ARS dynamically advertises BGP routes learned from the NVA (including the default route 0.0.0.0/00.0.0.0/0) to all subnets in the hub VNet and peered spoke VNets.
This is standard behavior of ARS to ensure dynamic routing propagation across the topology.
2
Identify potential routing loops at the NVA.
Since ARS propagates the 0.0.0.0/00.0.0.0/0 route to the NvaSubnet, the NVA would attempt to forward outgoing internet traffic to itself, causing a loop.
A more specific route or a local User Defined Route (UDR) is required to override the BGP-learned route on the NVA's own interface.
3
Apply a UDR to the NVA's subnet.
Create a route table with 0.0.0.0/00.0.0.0/0 pointing to the next hop type `Internet` and associate it with the `NvaSubnet`.
UDRs always take precedence over BGP routes, ensuring the NVA can send clean egress packets directly to Azure's physical internet boundary.
4
Configure the virtual network peerings for route transit.
Enable 'Use remote virtual network's gateways' on the spoke peering and 'Allow gateway transit' on the hub peering.
Without these peering settings enabled, ARS cannot propagate the dynamically learned routes to the peered spoke VNets, rendering the spoke isolated from the egress design.

Anahtar Kavram

Azure Route Server routing loop prevention and transit peering configuration.
Soru 199Soru

An organization is designing a secure network architecture in Azure. The design includes:
- A subnet named Subnet-App hosting virtual machines that run an application.
- An Azure Key Vault that stores cryptographic keys.
- A Private Endpoint for the Key Vault deployed in a subnet named Subnet-Private with a private IP address of 10.10.2.4.

A Network Security Group (NSG) associated with Subnet-App must allow the virtual machines to access the Key Vault via the Private Endpoint. To meet security compliance, you must block all other outbound traffic from Subnet-App to both the internet and other resources within the virtual network.

Which configuration should you specify for the destination in the NSG outbound security rule on Subnet-App to meet the requirements with the least administrative effort?

Cevabı ve açıklamayı göster

Cevap: The private IP address of the Private Endpoint (10.10.2.4)

Cevap

The private IP address of the Private Endpoint (10.10.2.4)
When accessing Azure services via Private Endpoints, all network traffic is directed to the private IP address of the endpoint. Therefore, any outbound Network Security Group (NSG) rule intended to permit this traffic must specify the Private Endpoint's private IP address as the destination. This allows the application subnet to communicate with the specific Private Endpoint while enabling other rules to block all other outbound traffic to the virtual network and the internet.

Adım Adım Çözüm

1
Analyze how client virtual machines communicate with an Azure service when a Private Endpoint is implemented.
Clients communicate with the service using the private IP address assigned to the Private Endpoint (10.10.2.4) within the virtual network.
Private Endpoints project the Azure service into the virtual network as a local resource with a private IP address.
2
Evaluate the behavior of Azure Service Tags in Network Security Groups (NSGs) for outbound rules.
Service tags such as AzureKeyVault represent the public IP ranges of Azure services and do not encompass private IP addresses.
This determines that service tags cannot be used to permit traffic destined for private endpoints.
3
Determine the rule destination that satisfies the security constraint of blocking all other outbound virtual network and internet traffic.
The destination must be restricted to the specific private IP address of the Private Endpoint (10.10.2.4). Using broader tags like VirtualNetwork would allow access to unintended internal resources.
This ensures the rule adheres to the principle of least privilege and satisfies all technical constraints.

Anahtar Kavram

Configuring NSGs for Private Endpoint Access
Tahmini Süre:2m 0s
Soru 200Soru

An enterprise is designing a multi-tier application in an Azure virtual network named VNet1. The application consists of web servers, application servers, and database servers.

You need to design a network security strategy using Network Security Groups (NSGs) to isolate the traffic between these tiers. The strategy must meet the following requirements:
- Allow web servers to communicate only with the application servers.
- Allow application servers to communicate only with the database servers.
- Minimize administrative effort as virtual machines (VMs) are added or removed from each tier.
- Avoid the use of individual IP addresses in the security rules.

Which two actions should you include in the design?

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

Cevabı ve açıklamayı göster

Cevap: Create Application Security Groups (ASGs) and associate the network interfaces of the virtual machines with their respective ASG.; Configure NSG rules that reference the Application Security Groups as the source and destination.

Cevap

Create Application Security Groups (ASGs), associate the network interfaces of the virtual machines with their respective ASG, and configure NSG rules that reference the ASGs as the source and destination.
Defining Application Security Groups (ASGs) and referencing them in Network Security Group (NSG) rules allows you to secure traffic between application tiers logically. As virtual machines are added or removed, associating their network interfaces with the correct ASG automatically applies the defined rules, satisfying all technical constraints and minimizing administrative overhead.

Adım Adım Çözüm

1
Define logical groupings for the multi-tier application.
Three Application Security Groups (ASGs) are planned: one for web servers, one for application servers, and one for database servers.
This establishes a logical boundary for each tier without relying on static IP addresses.
2
Associate VM network interfaces (NICs) with the appropriate ASGs.
NICs of the web, application, and database VMs are associated with their corresponding ASG.
This ensures that any security rule applied to the ASG automatically applies to the member network interfaces.
3
Create NSG rules referencing the ASGs as sources and destinations.
Outbound and inbound rules are configured to permit traffic only between the designated ASGs (Web to App, App to Database), while denying other inter-tier traffic.
This dynamically secures the traffic flow while minimizing administrative effort as VMs are added or removed.

Anahtar Kavram

Application Security Groups (ASGs) allow you to configure network security as a natural extension of an application's structure, grouping virtual machines and defining security policies based on those groups rather than individual IP addresses.
Tahmini Süre:1m 30s
ÖncekiSayfa 10 / 18Sonraki