Tüm alıştırma soruları

1198 soru

Soru 701Soru

A company is designing a global traffic routing and failover solution for a web application deployed in the East US and West Europe regions. The application must support SSL termination at the global tier and must route traffic to different backend pools based on the URL path. If a regional outage occurs, the solution must fail over to the remaining healthy region in less than 30 seconds. Which two components should you include in the design to meet these requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure Front Door to manage global Anycast-based routing, SSL termination, and path-based routing rules.; Azure Application Gateway in each region to manage regional Layer 7 load balancing and secure the web servers.

Cevap

Azure Front Door and Azure Application Gateway
Azure Front Door is a global Layer 7 service that provides Anycast-based routing, SSL offloading, and URL path-based routing rules. Azure Application Gateway is a regional Layer 7 load balancer that handles regional routing, local SSL termination, and secures the workloads locally.

Adım Adım Çözüm

1
Analyze the requirement for global traffic routing with SSL offloading and path-based routing.
Identify that a global Layer 7 load balancer is required. Azure Front Door supports Anycast-based routing, SSL termination, and path-based routing rules, whereas Azure Traffic Manager operates at the DNS level and cannot terminate SSL or inspect URL paths.
This determines the global routing service choice.
2
Evaluate the failover time requirement of less than 30 seconds.
Azure Front Door uses Anycast routing and split TCP to direct traffic to the nearest healthy backend instantly, with fast failover. Azure Traffic Manager relies on DNS TTL, which is subject to client and ISP caching, making sub-30 second failover unreliable.
This confirms the suitability of Azure Front Door over DNS-based routing.
3
Identify the regional Layer 7 load balancing requirement.
Azure Application Gateway can be deployed in each region to manage regional Layer 7 routing, local SSL termination, and provide Web Application Firewall (WAF) protection closer to the backend servers.
This establishes the regional routing layer.

Anahtar Kavram

Selecting and configuring Azure load balancing services based on layer, protocol, global/regional scope, and failover capabilities.
Soru 702Soru

An organization is designing a business continuity and disaster recovery strategy for an enterprise web application deployed in the East US and West US regions.

The application must meet the following requirements:
- Route incoming HTTP requests to the closest healthy region based on latency.
- Support SSL offloading at the network edge and route traffic based on URL paths.
- Maximize availability by routing traffic away from an unhealthy region within seconds without relying on client-side DNS cache expiration.
- Provide automatic failover for the backend Azure SQL Database to the secondary region using a single connection string listener.

Which architecture solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy Azure Front Door to manage global traffic routing and Azure SQL Database auto-failover groups for database replication and failover.

Cevap

Deploy Azure Front Door to manage global traffic routing and Azure SQL Database auto-failover groups for database replication and failover.
The combination of Azure Front Door and Azure SQL Database auto-failover groups meets all requirements. Azure Front Door uses Anycast to route HTTP traffic based on latency, terminates SSL at the edge, performs URL path-based routing, and detects backend failures using fast health probes to redirect traffic within seconds, avoiding DNS caching delays. Azure SQL Database auto-failover groups provide a read-write listener endpoint that automatically fails over the database layer.

Adım Adım Çözüm

1
Evaluate the global traffic routing requirements: SSL offloading at the edge, URL path-based routing, and immediate failover bypassing DNS caching.
Azure Front Door is selected because it is an Anycast-based Layer 7 service that supports SSL offloading, URL path-based routing, and fast failover via health probes, whereas Traffic Manager is a DNS-based Layer 4 service that cannot meet these requirements.
Traffic Manager operates at the DNS level and cannot inspect HTTP application layer features like URL paths or SSL headers, and failover is limited by DNS client-side caching.
2
Evaluate the database replication and failover requirements: automatic failover using a single connection string listener.
Azure SQL Database auto-failover groups are selected over active geo-replication.
Auto-failover groups provide a read-write listener endpoint that remains constant during a failover, and support automatic failover policies, whereas basic active geo-replication requires manual failover and connection string updates.
3
Combine the valid traffic routing and database replication strategies into a single architecture.
The final architecture uses Azure Front Door at the edge and Azure SQL Database auto-failover groups at the data layer.
This configuration meets all constraints for low failover latency, SSL offloading, path-based routing, and automated database failover.

Anahtar Kavram

Contrasting Layer 7 Anycast routing (Azure Front Door) with Layer 4 DNS-based routing (Traffic Manager) and configuring database failover mechanisms.
Soru 703Soru

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 704Soru

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 705Soru

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 706Soru

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 707Soru

A healthcare provider stores patient diagnostic reports in an Azure Blob Storage General-purpose v2 (GPv2) account. The reports must be managed according to the following requirements:
- Reports are frequently accessed and updated during the first 14 days after creation.
- Between 15 and 180 days, reports are accessed occasionally. When requested, they must be available for immediate, sub-second retrieval.
- After 180 days, reports are rarely accessed, but must be retained for 7 years (2,555 days) to meet regulatory compliance. For these reports, a retrieval latency of several hours is acceptable.
- All reports must be deleted after 7 years.

You need to design a lifecycle management policy to minimize storage costs while meeting the access and retention requirements.

Which two actions should you include in the lifecycle management policy? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Transition blobs to cool storage 14 days after modification.; Transition blobs to archive storage 180 days after modification.

Cevap

Include the actions to transition blobs to cool storage 14 days after modification and transition blobs to archive storage 180 days after modification.
The lifecycle policy must transition the blobs to cool storage 14 days after modification to save costs while keeping them immediately accessible, and then transition them to archive storage 180 days after modification to achieve the lowest storage cost for the remainder of the 7-year retention period where retrieval latency is acceptable.

Adım Adım Çözüm

1
Analyze access frequency and latency requirements for the first phase (0-14 days).
Reports are frequently accessed and modified, requiring the default Hot storage tier.
Hot tier provides the lowest access costs for active data.
2
Analyze requirements for the second phase (15-180 days).
Reports must be retrieved immediately (sub-second latency) but are accessed occasionally, matching the Cool storage tier.
Transitioning to the Cool tier after 14 days reduces storage costs while maintaining immediate availability.
3
Analyze requirements for the third phase (after 180 days).
Reports are rarely accessed, can tolerate hours of retrieval latency, and must be stored for 7 years (2,555 days), matching the Archive storage tier.
Transitioning to the Archive tier after 180 days minimizes the cost of long-term compliance retention.

Anahtar Kavram

Azure Blob Storage lifecycle management policy design balancing retrieval latency and storage cost optimization.
Tahmini Süre:1m 30s
Soru 708Soru

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 709Soru

A healthcare provider is designing the compute topology for a critical telehealth video orchestration application on Azure. The workload will run on 44 Azure Virtual Machines (VMs) that perform real-time transcoding and routing. The application has the following design requirements:

- The VMs must achieve an SLA of 99.99%99.99\% for virtual machine uptime.
- Network latency between the VMs must be minimized to ensure sub-millisecond synchronization of media feeds.
- The design must protect against localized datacenter failures.

Which two actions should you include in the design to meet the requirements? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy the virtual machines across multiple Availability Zones in the target Azure region.; Group the virtual machines within a Proximity Placement Group.

Cevap

Deploy the virtual machines across multiple Availability Zones in the target Azure region and group the virtual machines within a Proximity Placement Group.
Deploying the virtual machines across multiple Availability Zones is required to achieve a 99.99%99.99\% uptime SLA and protect against localized datacenter failures. To minimize network latency between these virtual machines, they should be grouped within a Proximity Placement Group to ensure physical proximity.

Adım Adım Çözüm

1
Determine the configuration required to meet the 99.99%99.99\% uptime SLA.
Identify that Azure virtual machines must be deployed across multiple Availability Zones in the same region to achieve a 99.99%99.99\% uptime SLA.
Azure SLA guarantees 99.99%99.99\% virtual machine connectivity only when two or more instances are deployed across two or more Availability Zones in the same region.
2
Determine the configuration required to meet the low-latency placement requirement.
Identify that a Proximity Placement Group must be used.
A Proximity Placement Group is an Azure logical grouping capability that keeps virtual machines physically close to each other, minimizing network latency.
3
Evaluate and eliminate incorrect configurations.
Eliminated the options for Availability Sets in a single zone and Spot VMs.
An Availability Set inside a single zone fails to protect against datacenter outages and only offers a 99.95%99.95\% uptime SLA. Spot VMs can be evicted at any time and offer no uptime SLA.

Anahtar Kavram

Designing compute high availability in Azure by combining Availability Zones for regional resiliency and Proximity Placement Groups for low latency.
Soru 710Soru

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 711Soru

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 712Soru

A research institution stores daily climate simulation datasets in a General-purpose v2 (GPv2) Azure Blob Storage account. The datasets are initially written to the Hot storage tier. You are designing a lifecycle management policy to meet the following requirements:

* The datasets are frequently and actively analyzed for the first 60 days after they are generated.
* After 60 days, the datasets are rarely accessed but must be retained for exactly 7 years (2,555 days) to comply with data retention regulations.
* Any rare data retrieval after 60 days must be completed within a maximum of 15 hours.
* Storage costs must be minimized.

Which two actions should you include in the lifecycle management policy? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Transition the datasets to the Archive tier 60 days after creation.; Delete the datasets 2,555 days after creation.

Cevap

To satisfy the requirements, the lifecycle policy must transition the datasets to the Archive tier 60 days after creation, and delete the datasets 2,555 days after creation.
Transitioning the datasets to the Archive tier 60 days after creation ensures they remain in the Hot tier during the active analysis period while minimizing long-term storage costs. Since the latency tolerance after 60 days is 15 hours, the Archive tier's standard rehydration time is acceptable. Deleting the datasets 2,555 days (7 years) after creation ensures compliance is met without paying for storage indefinitely.

Adım Adım Çözüm

1
Analyze the active usage window and tier requirements.
The datasets are actively analyzed for the first 60 days, requiring them to remain in the Hot tier to avoid retrieval latency and transaction costs.
Ensures immediate access performance is maintained for the active 60-day analysis period.
2
Evaluate the archival transition point and latency constraints.
Transition the datasets to the Archive tier after 60 days.
Since standard rehydration takes up to 15 hours and matches the 15-hour retrieval tolerance, transitioning directly to the Archive tier after 60 days minimizes storage costs without violating latency limits.
3
Determine the lifecycle deletion schedule.
Configure a deletion action to execute 2,555 days after creation.
Ensures the 7-year retention rule is precisely met, avoiding any ongoing storage charges once the retention period ends.

Anahtar Kavram

Azure Blob Storage Lifecycle Management Tiers and Latency Requirements
Soru 713Soru

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 714Soru

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
Soru 715Soru

An organization named Apex Bioscience is designing a secure networking architecture for a high-performance computing workload. The workload runs on Azure Virtual Machines deployed in a subnet named AnalysisSubnet within a virtual network named VNet1. The virtual machines must read and write data to multiple company-owned Azure Storage accounts located in the East US region. The security architecture must satisfy the following technical constraints:
- Outbound network traffic from AnalysisSubnet to the Azure Storage accounts must remain on the Microsoft backbone network and never traverse the public internet.
- Virtual machines must be prevented from exfiltrating data to any unauthorized or external Azure Storage accounts.
- The solution must minimize administrative overhead to implement and maintain as new company-owned storage accounts are provisioned in the East US region.

Which security component should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Virtual Network service endpoint policies applied to AnalysisSubnet that permit access to the company's Azure subscriptions.

Cevap

Virtual Network service endpoint policies applied to AnalysisSubnet that permit access to the company's Azure subscriptions.
Virtual Network service endpoint policies allow you to filter egress virtual network traffic to Azure Storage accounts. By configuring a policy that permits access only to the company's Azure subscriptions, you ensure that virtual machines in the subnet can only connect to authorized storage accounts, thereby preventing data exfiltration to external accounts. Traffic to these service endpoints remains on the Microsoft backbone network and does not traverse the public internet. Since the policy applies to the entire subscription level, any newly provisioned storage accounts within those subscriptions are automatically covered without requiring updates to the network configuration, which minimizes administrative overhead.

Adım Adım Çözüm

1
Analyze the requirements for network path isolation.
Traffic must remain on the Microsoft backbone network and must not traverse the public internet, which rules out routing traffic via the default internet gateway.
Ensures compliance with the data transit security policy.
2
Evaluate mechanisms to prevent data exfiltration to unauthorized Azure Storage accounts.
Standard NSG service tags for Storage allow access to all storage accounts in the region, which is insufficient. We must be able to scope access to only specific authorized accounts, subscriptions, or resource groups.
Ensures that data cannot be copied to external or personal storage accounts.
3
Determine the solution with the lowest administrative overhead.
Virtual Network service endpoint policies scoped to the company's subscriptions allow automatic access to newly created company storage accounts without manual updates. Managing individual IP rules in NSGs or individual routes in UDRs requires high administrative effort.
Supports scalability and satisfies the administrative constraint.

Anahtar Kavram

Virtual Network service endpoint policies allow you to filter egress virtual network traffic to Azure Storage accounts, preventing data exfiltration while keeping traffic on the Microsoft backbone network.
Tahmini Süre:2m 0s
Soru 716Soru

Your company is designing a secure network architecture in Azure. You have a virtual network named VNet1 containing a subnet named AppSubnet. Virtual machines in AppSubnet must connect to Azure Key Vault and Azure Storage.

The security team has the following requirements:
- Direct public internet connectivity from AppSubnet must be blocked.
- Administrative overhead for maintaining IP address changes of Azure services must be minimized.
- Communication with Azure Storage and Azure Key Vault must be allowed, while all other outbound traffic is denied.

You decide to use a Network Security Group (NSG) associated with AppSubnet to control outbound traffic.

Which two configurations should you recommend for the Network Security Group (NSG) outbound rules? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: An outbound security rule that allows traffic to the Storage service tag.; An outbound security rule that allows traffic to the AzureKeyVault service tag.

Cevap

Configure an outbound security rule that allows traffic to the Storage service tag, and configure an outbound security rule that allows traffic to the AzureKeyVault service tag.
To satisfy the requirements of securing outbound communication to Azure Storage and Azure Key Vault while avoiding administrative overhead, you should use Azure Service Tags in the Network Security Group. A service tag represents a group of IP address prefixes from a given Azure service. Microsoft manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change, minimizing administrative effort.

Adım Adım Çözüm

1
Identify the target Azure services that the virtual machines in AppSubnet need to access.
The target services are Azure Storage and Azure Key Vault.
This establishes the scope of traffic that must be explicitly permitted through the security controls.
2
Evaluate the mechanism that minimizes administrative overhead for maintaining changing service IP addresses.
Azure Service Tags represent groups of IP address prefixes managed entirely by Microsoft.
Using Service Tags like 'Storage' and 'AzureKeyVault' eliminates the need to manually track and update rule IP addresses when Azure updates service endpoints.
3
Formulate the outbound rules for the Network Security Group.
Add two high-priority outbound rules to allow the Storage and AzureKeyVault service tags as destinations, combined with a default or lower-priority rule to block all other outbound internet traffic.
This satisfies the security requirement to block general internet access while allowing access only to the authorized Azure services.

Anahtar Kavram

Azure Network Security Group Service Tags
Soru 717Soru

An enterprise designs a hub-and-spoke virtual network topology in Azure. The hub virtual network is `vnet-hub-prod` (10.10.0.0/1610.10.0.0/16) and hosts an Azure Firewall at 10.10.1.410.10.1.4. The spoke virtual network is `vnet-spoke-app` (10.20.0.0/1610.20.0.0/16) and contains two subnets: `subnet-web` (10.20.1.0/2410.20.1.0/24) and `subnet-db` (10.20.2.0/2410.20.2.0/24). The virtual networks are connected via Virtual Network Peering.

The administrator wants to route all traffic from `subnet-web` to `subnet-db` through the Azure Firewall for security inspection. To achieve this, the administrator creates a route table and associates it with `subnet-web`.

Which route configuration should be added to the route table to inspect traffic destined for `subnet-db` while ensuring that local traffic within `subnet-web` and traffic to other potential subnets in `vnet-spoke-app` continues to route directly within the virtual network?

Cevabı ve açıklamayı göster

Cevap: Address prefix: 10.20.2.0/2410.20.2.0/24; Next hop type: Virtual appliance; Next hop address: 10.10.1.410.10.1.4

Cevap

Configure a User Defined Route with an Address prefix of 10.20.2.0/2410.20.2.0/24, Next hop type of Virtual appliance, and Next hop address of 10.10.1.410.10.1.4.
The correct answer specifies a route for the specific database subnet prefix (10.20.2.0/2410.20.2.0/24) with a next hop type of Virtual appliance pointing to the firewall IP (10.10.1.410.10.1.4). By using a more specific prefix, Azure uses Longest Prefix Match (LPM) to route database traffic to the firewall, while traffic within the web subnet or to other subnets continues to use the less-specific system route (10.20.0.0/1610.20.0.0/16 -> Virtual Network).

Adım Adım Çözüm

1
Analyze the destination target prefix requirements.
The target subnet is `subnet-db` (10.20.2.0/2410.20.2.0/24), while the rest of the virtual network is `vnet-spoke-app` (10.20.0.0/1610.20.0.0/16).
Determining the correct prefix prevents over-routing and maintains local virtual network connectivity.
2
Determine the routing priority and longest prefix match (LPM) logic in Azure.
A route targeting 10.20.2.0/2410.20.2.0/24 is more specific than the default local system route of 10.20.0.0/1610.20.0.0/16.
Azure routes traffic using the longest prefix match. A route for 10.20.2.0/2410.20.2.0/24 will only affect traffic going to the database subnet, leaving traffic to 10.20.1.0/2410.20.1.0/24 or other parts of the spoke to follow the system route.
3
Select the correct next hop type and IP address for the firewall.
Next hop type should be Virtual appliance, and the next hop IP address should be the Azure Firewall's private IP (10.10.1.410.10.1.4).
Azure Firewall acts as a network virtual appliance (NVA) and routing to it requires the Virtual appliance next hop type.

Anahtar Kavram

Azure Route Selection and Longest Prefix Match (LPM)
Soru 718Soru

An insurance firm is deploying a core claims auditing application on Azure Virtual Machines. The application requires a virtual machine uptime SLA of at least 99.99%99.99\% to meet regulatory compliance. The auditing process runs continuously and must not be interrupted by eviction. Which compute topology should you recommend to meet the SLA and operational requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy the virtual machines across two or more Availability Zones in the Azure region.

Cevap

Deploy the virtual machines across two or more Availability Zones in the Azure region.
Deploying the virtual machines across two or more Availability Zones in the Azure region is the only configuration that provides a 99.99%99.99\% uptime SLA for Azure Virtual Machines, satisfying the high availability and compliance demands of the application.

Adım Adım Çözüm

1
Analyze the SLA requirement.
The application requires an uptime SLA of at least 99.99%99.99\%.
This establishes the minimum infrastructure standard needed, as only specific Azure configurations can guarantee a 99.99%99.99\% SLA.
2
Evaluate Azure SLA guarantees for compute topologies.
Deploying VMs across two or more Availability Zones provides a 99.99%99.99\% SLA, whereas Availability Sets provide a 99.95%99.95\% SLA and single-instance VMs provide up to 99.9%99.9\% SLA.
Determining which deployment strategies meet or exceed the 99.99%99.99\% target narrows the valid architectural options.
3
Evaluate the workload eviction constraint.
Spot VMs must be ruled out because they are subject to eviction and carry no SLA.
The scenario specifies that the process runs continuously and must not be interrupted by eviction.

Anahtar Kavram

Azure Virtual Machine High Availability SLA Requirements
Soru 719Soru

An organization is planning to migrate a business-critical application suite from an on-premises datacenter hosting physical servers and VMware vSphere virtual machines to Azure. During the assessment phase, the following technical requirements and constraints are identified:

* The backend database layer consists of multiple SQL Server databases on physical servers that perform cross-database queries, utilize SQL Server Agent for scheduled maintenance, and execute CLR assembly routines.
* The application servers are hosted on VMware vSphere VMs and have undocumented TCP connections to external partner APIs.
* For hybrid identity, users must authenticate against the on-premises Active Directory Domain Services (AD DS) in real time to meet security compliance, but the organization wants to minimize on-premises infrastructure footprint and administrative overhead.

Which combination of Azure Migrate assessment strategies, target database service tiers, and Microsoft Entra ID hybrid identity solutions should you recommend to meet all migration requirements?

Cevabı ve açıklamayı göster

Cevap: Enable Azure Migrate agent-based dependency analysis for all application servers, select Azure SQL Managed Instance as the database migration target, and implement Microsoft Entra Pass-through Authentication (PTA) with Seamless Single Sign-On (SSO).

Cevap

Enable Azure Migrate agent-based dependency analysis for all application servers, select Azure SQL Managed Instance as the database migration target, and implement Microsoft Entra Pass-through Authentication (PTA) with Seamless Single Sign-On (SSO).
The correct recommendation is to enable agent-based dependency analysis to map the undocumented connections to external partner APIs, use Azure SQL Managed Instance to support SQL Server Agent, cross-database queries, and CLR, and deploy Pass-through Authentication (PTA) with Seamless SSO to validate credentials against the on-premises directory in real time with minimal footprint.

Adım Adım Çözüm

1
Determine the database service tier required for the backend SQL databases.
Azure SQL Managed Instance
The databases require SQL Server Agent, cross-database queries, and CLR integration, which are not supported in Azure SQL Database single databases or elastic pools but are fully supported in Azure SQL Managed Instance.
2
Select the hybrid identity synchronization and authentication mechanism.
Microsoft Entra Pass-through Authentication (PTA) with Seamless SSO
PTA validates passwords directly against the on-premises AD DS in real time using lightweight agents, meeting compliance requirements without the heavy footprint and high administrative overhead of Active Directory Federation Services (AD FS).
3
Determine the dependency analysis strategy for the application servers.
Azure Migrate agent-based dependency analysis
Agent-based dependency analysis installs agents on the servers to capture all TCP connections, which is required to accurately map undocumented connections to external partner APIs where agentless discovery cannot retrieve connection details.

Anahtar Kavram

Selecting migration assessment and target service strategies based on legacy application compatibility, networking dependency mapping, and hybrid identity constraints.
Soru 720Soru

You are designing a serverless processing pipeline for an IoT platform. Devices upload binary log files to an Azure Storage account. A custom executable packaged in a Linux container must run to extract anomaly metrics from each log file. The extraction process takes approximately 12 minutes per file. The solution must scale automatically based on demand, scale to zero when no logs are uploaded, and avoid any running compute charges when idle. Which hosting option should you select to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps event-driven jobs

Cevap

Azure Container Apps event-driven jobs
Azure Container Apps event-driven jobs is the correct hosting option because it can run containerized tasks on demand, supports execution times longer than 10 minutes (up to 24 hours), and scales down to zero instances when idle, incurring no billing costs during idle periods.

Adım Adım Çözüm

1
Analyze execution duration and packaging requirements
The workload is packaged as a Linux container and takes 12 minutes to run.
This rules out hosting options with strict timeout limitations below 12 minutes.
2
Evaluate scale-to-zero and idle cost requirements
The hosting option must scale to zero and incur zero compute charges when idle.
This rules out plans that charge for pre-warmed or running instances when idle.
3
Select the service that meets all constraints
Azure Container Apps event-driven jobs meets all requirements.
It runs containerized tasks, supports executions exceeding 10 minutes, and scales to zero with zero idle cost.

Anahtar Kavram

Selecting serverless hosting options based on execution limits, packaging, and scale-to-zero capabilities.
ÖncekiSayfa 36 / 60Sonraki