Examkin

Tüm alıştırma soruları

1198 soru

Tüm türler1,198Çoktan seçmeli617Çoklu seçim502Eşleştirme65Sıralama14
Soru 501Soru →

A logistics company is designing an analytical data platform to track fleet vehicles in real time. The platform must meet the following requirements:
- Ingest GPS telemetry from 50,00050,000 vehicles transmitting data every 55 seconds (approximately 10,00010,000 events per second).
- Store all raw telemetry data in Azure Data Lake Storage (ADLS) Gen2 in Parquet format for long-term historical analysis.
- Perform near-real-time analysis of the incoming streams to detect route deviations, with an end-to-end latency of under 22 seconds.
- Minimize administrative and operational overhead.
- Ensure the data platform can survive a primary datacenter outage.

Which two Azure services or configurations should you recommend to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Azure Event Hubs to ingest the streaming vehicle telemetry; Azure Stream Analytics to analyze the telemetry stream and output data to Azure Data Lake Storage (ADLS) Gen2

Cevap

The logistics company should use Azure Event Hubs to ingest the streaming vehicle telemetry and Azure Stream Analytics to analyze the telemetry stream and output data to Azure Data Lake Storage (ADLS) Gen2.
Azure Event Hubs is designed for high-throughput streaming ingestion from millions of devices, while Azure Stream Analytics offers a serverless engine to analyze streams and write to storage with sub-second latency, satisfying the business requirements.

Adım Adım Çözüm

1
Determine the ingestion requirements.
Azure Event Hubs is identified as the optimal ingestion service due to its ability to ingest millions of events per second with minimal latency and low operational overhead.
The platform needs to ingest 10,00010,000 events per second with low latency.
2
Select the stream processing and storage integration service.
Azure Stream Analytics is selected to process the stream with sub-second latency and write to ADLS Gen2 in Parquet format.
Stream Analytics is fully managed, serverless, and satisfies the sub-22-second end-to-end latency constraint while outputting raw data to ADLS Gen2.
3
Evaluate storage redundancy and security constraints.
Identify that Locally Redundant Storage (LRS) is insufficient for regional outages, and long-lived SAS tokens without access policies pose a significant security risk.
The system must survive a datacenter outage and maintain a secure authentication mechanism.

Anahtar Kavram

Selecting streaming ingestion and analytical storage components matching throughput, latency, redundancy, and security requirements.
Tahmini Süre:2m 0s
Soru 502Soru →

An organization is designing a high-availability global infrastructure across the East US and West US regions for two key services:

* Service A: An HTTPS-based web portal requiring URL path-based routing (e.g., `/api/*` to an API cluster and `/static/*` to storage), SSL offloading, and client session stickiness.
* Service B: A proprietary database synchronization engine running on custom TCP port 14330 that requires low-latency routing to the nearest region, with a strict failover detection and client redirection time of under 10 seconds.

Which global traffic routing and failover strategy should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy Azure Front Door for Service A to handle SSL offloading and path-based routing. Deploy a cross-region Azure Load Balancer (Global tier) for Service B with a TCP health probe configured with a 5-second interval and 2 failures.

Cevap

Deploy Azure Front Door for the HTTP/S portal and a cross-region Azure Load Balancer for the custom TCP service.
The correct strategy combines Azure Front Door for the Layer 7 HTTPS workload and a cross-region Azure Load Balancer (Global tier) for the custom TCP workload. Azure Front Door handles SSL offloading and path-based routing natively at the edge. The cross-region Load Balancer acts at Layer 4, supporting custom TCP port 14330, and provides deterministic failover under 10 seconds via Anycast routing, avoiding DNS caching issues that affect Traffic Manager.

Adım Adım Çözüm

1
Analyze protocol requirements for both services.
Service A requires HTTPS (Layer 7) features including path-based routing and SSL offloading. Service B requires custom TCP port 14330 (Layer 4).
This establishes the layer at which each routing solution must operate.
2
Evaluate global load balancing options for the HTTP/S workload.
Azure Front Door is selected for Service A because it is an Anycast-based global Layer 7 load balancer that handles SSL offloading, URL path-routing, and session affinity.
This directly satisfies all requirements of Service A.
3
Evaluate global load balancing and failover requirements for the custom TCP workload.
A cross-region Azure Load Balancer is selected for Service B because it operates at Layer 4, supports custom TCP ports, uses Anycast IP addresses, and provides near-instantaneous failover by bypassing DNS cache limitations. Traffic Manager cannot guarantee the sub-10 second failover requirement due to client-side DNS caching.
This satisfies the protocol and low-latency/fast-failover requirements of Service B.

Anahtar Kavram

Selecting the correct global load balancer based on Layer 4 vs. Layer 7 capabilities, protocol support, and failover latency constraints.
Soru 503Soru →

An enterprise designs a hub-and-spoke network topology in Azure. The topology consists of:
- A hub virtual network named `vnet-weur-hub` (10.100.0.0/1610.100.0.0/16) containing an Azure Firewall with the private IP address 10.100.4.410.100.4.4.
- A spoke virtual network named `vnet-weur-spoke1` (10.101.0.0/1610.101.0.0/16) that contains a subnet named `snet-workload1` (10.101.1.0/2410.101.1.0/24).
- A spoke virtual network named `vnet-weur-spoke2` (10.102.0.0/1610.102.0.0/16) that contains a subnet named `snet-workload2` (10.102.1.0/2410.102.1.0/24).

Both spoke virtual networks are peered directly with the hub virtual network. The security team requires that all traffic destined for the internet and all traffic between the two spoke virtual networks must be routed through the Azure Firewall in the hub. However, traffic between resources within `vnet-weur-spoke1` must remain local and route directly without passing through the firewall.

You need to design a route table for `snet-workload1` that meets these requirements with the minimum number of user-defined routes (UDRs).

Which route configuration should you specify in the route table?

Cevabı ve açıklamayı göster

Cevap: A single route with the address prefix 0.0.0.0/0, next hop type Virtual Appliance, and next hop address 10.100.4.4

Cevap

A single route with the address prefix 0.0.0.0/0, next hop type Virtual Appliance, and next hop address 10.100.4.4
The correct configuration uses a single route with the prefix 0.0.0.0/0 pointing to the Azure Firewall at 10.100.4.4. Since Azure uses the longest prefix match algorithm, traffic to the local network (10.101.0.0/16) will match the system route and bypass the firewall, whereas inter-spoke and internet traffic will match the default route and go through the firewall.

Adım Adım Çözüm

1
Analyze the prefix matching behavior of Azure routing.
Azure evaluates routing tables using the longest prefix match. The system route for the local virtual network is 10.101.0.0/16.
Understanding how Azure determines path priority is necessary to avoid unnecessary routes.
2
Evaluate the default route (0.0.0.0/0) behavior.
A UDR of 0.0.0.0/0 redirects all traffic not matching a more specific route to the specified next hop (10.100.4.4). Local traffic (10.101.0.0/16) remains direct because 16 is a longer prefix match than 0.
Using 0.0.0.0/0 minimizes the route table complexity while capturing internet and inter-spoke traffic.
3
Determine if additional routes are required for local VNet traffic.
No additional route is required. Adding a local VNet prefix route to the UDR table would override the direct path and force local traffic through the firewall.
This avoids the overlapping route misconception that breaks local VNet traffic.

Anahtar Kavram

Azure routing utilizes the longest prefix match algorithm, allowing broad User Defined Routes like 0.0.0.0/0 to redirect external traffic to virtual appliances without overriding more specific local system routes.

Alternatif Yöntem

While configuring a single 0.0.0.0/0 route is the most optimal approach, an alternative but more complex configuration would involve defining separate routes for internet-bound traffic (0.0.0.0/0) and spoke-bound traffic (10.102.0.0/16) both pointing to the firewall. This achieves the same routing logic but requires maintaining additional routes.
Tahmini Süre:1m 30s
Soru 504Soru →

Vanguard Global Shipping is designing an identity security and access strategy for its Microsoft Entra ID tenant. The tenant is synchronized with an on-premises Active Directory Domain Services (AD DS) domain.

The design must satisfy the following requirements:
- Minimize the on-premises infrastructure required for user authentication.
- Enforce Multi-Factor Authentication (MFA) for all users with privileged administrative roles.
- Ensure that administrators can access the tenant even if a misconfiguration or third-party service outage affects Entra ID MFA.

Which solution should you recommend to meet the requirements?

Cevabı ve açıklamayı göster

Cevap: Configure Password Hash Synchronization (PHS) as the hybrid identity authentication method, implement a Conditional Access policy requiring MFA for all administrative roles, and exclude a dedicated emergency access account from the policy.

Cevap

Configure Password Hash Synchronization (PHS) as the hybrid identity authentication method, implement a Conditional Access policy requiring MFA for all administrative roles, and exclude a dedicated emergency access account from the policy.
The correct solution uses Password Hash Synchronization (PHS) to satisfy the requirement of minimizing on-premises infrastructure while maintaining authentication capabilities in the cloud. It secures privileged access by enforcing Multi-Factor Authentication (MFA) via a Conditional Access policy. Crucially, it excludes a dedicated emergency access account from this MFA policy, preventing the organization from being locked out of the tenant if there is a regional or global outage affecting Entra ID MFA services.

Adım Adım Çözüm

1
Evaluate the hybrid identity authentication method that minimizes on-premises infrastructure.
Select Password Hash Synchronization (PHS) as it requires minimal infrastructure compared to Active Directory Federation Services (AD FS).
AD FS requires deploying and maintaining federation servers, proxy servers, and certificates, which increases infrastructure and administrative overhead, whereas PHS performs authentication directly in the cloud.
2
Design the Conditional Access policies to secure administrative access while preventing lockout.
Enforce MFA for all admin roles using a Conditional Access policy, and explicitly exclude a dedicated emergency access account.
Excluding a dedicated emergency access account (break-glass account) is a Microsoft best practice to ensure access is maintained during service outages or policy misconfigurations.
3
Validate the governance configuration for administrative access.
Avoid permanently active administrative assignments in Privileged Identity Management (PIM).
Roles should be configured as eligible rather than permanently active to enforce just-in-time access and reduce the attack surface.

Anahtar Kavram

Microsoft Entra ID Authentication and Conditional Access
Soru 505Soru →

A company is migrating a legacy stateful application to Azure. The application runs on a single Azure Virtual Machine (VM) and requires high-performance block storage for its database. The database does not support application-level replication. The storage solution must meet the following requirements:
- Maintain read and write availability if a single Azure datacenter or availability zone fails.
- Experience zero data loss (RPO = 0) in the event of a zone outage.
- Provide high-performance storage suitable for database transaction logs.

Which disk configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Premium SSD Managed Disks configured with Zone-Redundant Storage (ZRS)

Cevap

Premium SSD Managed Disks configured with Zone-Redundant Storage (ZRS)
Premium SSD Managed Disks configured with Zone-Redundant Storage (ZRS) provide the necessary high performance for database transaction logs while replicating data synchronously across three availability zones in the primary region. This ensures that the storage remains accessible and suffers zero data loss if a single availability zone goes offline.

Adım Adım Çözüm

1
Analyze performance requirements.
Database transaction logs require high-performance block storage, ruling out Standard HDD storage due to performance limitations.
Databases need high IOPS and throughput to prevent performance bottlenecks.
2
Evaluate availability and data loss constraints.
The storage must survive a single availability zone failure with zero data loss (RPO = 0). This eliminates Locally Redundant Storage (LRS) since it is confined to a single datacenter.
LRS does not replicate data across availability zones.
3
Check capability support for Azure Managed Disks.
Azure Managed Disks only support LRS and ZRS natively. Geo-Redundant Storage (GRS) is not supported for managed disks, eliminating GRS.
Azure Managed Disks do not have native geo-replication options at the disk configuration tier.

Anahtar Kavram

Selecting the appropriate storage redundancy tier for Azure Managed Disks based on performance, availability, and capability support constraints.
Soru 506Soru →

ApexGlow Media is designing a business continuity solution for its content delivery application. The application's metadata is stored in Azure Blob Storage. The primary region is East US, and the secondary region is West US. The design requirements are as follows:
- During normal operations, the application in the secondary region must have read-only access to the replicated metadata.
- In the event of a primary region outage, the application must be able to fail over to the secondary region and resume write operations.
- The Recovery Point Objective (RPO) must be less than 1515 minutes.
- The solution must minimize cost and avoid active-active compute configurations.

Which storage replication and failover design should you recommend?

Cevabı ve açıklamayı göster

Cevap: Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). In the event of a primary region outage, initiate a customer-managed failover, and then redirect the application's write operations to the primary storage endpoint.

Cevap

Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS). In the event of a primary region outage, initiate a customer-managed failover, and then redirect the application's write operations to the primary storage endpoint.
The correct option satisfies the requirement of read access to the secondary region during normal operations by utilizing Read-Access Geo-Redundant Storage (RA-GRS). It also correctly handles the primary region outage by initiating a customer-managed failover, which promotes the secondary region to the new primary, changes the storage account replication to Locally Redundant Storage (LRS), and allows writes to proceed on the storage endpoint.

Adım Adım Çözüm

1
Analyze read requirements during normal operations
Since read-only access to the secondary region is required during normal operations, Geo-Redundant Storage (GRS) is ruled out because it does not support reads from the secondary region unless a failover occurs. Read-Access Geo-Redundant Storage (RA-GRS) is required.
GRS keeps the secondary region completely offline to users until a failover, whereas RA-GRS provides a secondary endpoint for read access.
2
Evaluate write capabilities in the secondary region during an outage
Determine that write operations cannot be directed to the secondary endpoint directly because RA-GRS only supports read access on the secondary endpoint prior to failover.
Directing writes to the secondary endpoint before failover results in write failures.
3
Determine the correct failover strategy to enable writes
Initiate a customer-managed failover. This action promotes the secondary region to become the new primary region, switches the storage configuration to Locally Redundant Storage (LRS), and enables write access on the primary endpoint.
Customer-managed failover is required to swap the primary and secondary roles and allow write operations to resume on the storage account.

Anahtar Kavram

Azure Storage Geo-Replication Failover Behavior
Tahmini Süre:2m 0s
Soru 507Soru →

A multinational retail corporation is designing the storage architecture for its global inventory ledger application. The application stores ledger files in a General Purpose v2 storage account. The solution must satisfy the following requirements:

* In the primary region, the data must be replicated across three separate physical facilities (availability zones) to protect against datacenter-level failures.
* In the event of a primary region disaster, the application must be able to perform read operations on the inventory ledger files in the secondary paired region immediately, without waiting for a customer-managed or Microsoft-managed failover.
* Write operations to the secondary region are not required during a primary region outage.

Which redundancy option should you recommend for the storage account?

Cevabı ve açıklamayı göster

Cevap: Read-access geo-zone-redundant storage (RA-GZRS)

Cevap

Read-access geo-zone-redundant storage (RA-GZRS)
Read-access geo-zone-redundant storage (RA-GZRS) replicates data across three separate availability zones in the primary region (satisfying the zone-resiliency requirement) and replicates it to a secondary region. Crucially, the read-access feature enables immediate read capability from the secondary region endpoint without requiring a failover operation.

Adım Adım Çözüm

1
Analyze primary region redundancy requirement.
The requirement states that data must be replicated across three separate physical facilities (availability zones) in the primary region. This narrows the primary region storage type to Zone-Redundant Storage (ZRS) or Geo-Zone-Redundant Storage (GZRS). Locally Redundant Storage (LRS) and Geo-Redundant Storage (GRS) are eliminated because they replicate within a single facility.
Eliminate options that fail primary region resiliency requirements.
2
Analyze disaster recovery and secondary region read requirements.
The solution requires the ability to read from the secondary paired region immediately during a primary outage without initiating a failover. This requires a read-access (RA) suffix, narrowing the choices to RA-GRS or RA-GZRS.
Eliminate options that do not allow immediate read access to the secondary region without failover.
3
Combine primary zone redundancy and secondary read-access requirements.
Combining the requirement for ZRS in the primary region (from Step 1) with Read-Access to the secondary region (from Step 2) yields Read-access geo-zone-redundant storage (RA-GZRS).
Identify the storage tier that satisfies all constraints.

Anahtar Kavram

Selecting the optimal Azure storage redundancy tier based on zonal, regional, and read-access requirements.
Tahmini Süre:2m 0s
Soru 508Soru →

Your company uses an Azure Files share to store critical application configuration files. You are designing a backup solution to meet the following requirements:
- Recover files deleted within the last 14 days with a near-zero recovery time objective (RTO) using share snapshots.
- Retain historical backup copies for 90 days in a separate security boundary to protect against accidental or malicious deletion of the source storage account.
- Ensure the vaulted backup data is resilient against a primary region outage.

Which backup configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Create a Backup vault with Geo-redundant storage (GRS). Configure a backup policy with snapshot retention set to 14 days and vault retention set to 90 days.

Cevap

Create a Backup vault with Geo-redundant storage (GRS). Configure a backup policy with snapshot retention set to 14 days and vault retention set to 90 days.
The correct configuration uses a Backup vault with Geo-redundant storage (GRS) and a backup policy retaining local snapshots for 14 days and vault backups for 90 days. This separates the operational snapshot tier (which provides near-zero RTO restores) from the vaulted tier (which provides a separate security boundary to protect against storage account deletion), while GRS ensures that the vault remains available in the event of a regional outage.

Adım Adım Çözüm

1
Determine the local snapshot retention requirement.
Snapshot-tier retention must be set to 14 days.
Near-zero RTO restores rely on local share snapshots in the source storage account. Restoring from the vaulted tier takes longer because the data must be transferred back.
2
Identify the correct vault type and security boundary configuration.
Use a Backup vault and configure vaulted backup.
Vaulted backup copies data to a separate security boundary, protecting it from storage account deletion. Recovery Services vaults do not support vaulted backups for Azure Files.
3
Select the backup storage redundancy model.
Configure the Backup vault with Geo-redundant storage (GRS).
To survive a primary region outage, the vault's storage redundancy must be geo-redundant.

Anahtar Kavram

Azure Files vaulted backup separates snapshot-level operational recovery (for low RTO) from vault-level long-term retention (for security boundaries and regional resilience).
Soru 509Soru →

An organization has a financial analysis application deployed in the East Asia region. The application consists of two Azure virtual machines: `AppWeb-VM01` (web tier) and `AppDB-VM01` (database tier running SQL Server).

You are designing a disaster recovery (DR) solution to the Southeast Asia region. The solution must meet the following requirements:
* The database tier must have a recovery point objective (RPO) of 10 minutes10\text{ minutes} and a recovery time objective (RTO) of 1 hour1\text{ hour}.
* The web tier must have an RPO of 4 hours4\text{ hours} and an RTO of 2 hours2\text{ hours}.

During peak hours, the disk write churn rates are as follows:
* `AppWeb-VM01`: 1.5 MB/s1.5\text{ MB/s} total.
* `AppDB-VM01` OS disk: 1.8 MB/s1.8\text{ MB/s}.
* `AppDB-VM01` SQL Server data disk (Premium SSD v1): 27 MB/s27\text{ MB/s}.
* `AppDB-VM01` SQL Server TempDB disk (Premium SSD v1): 12 MB/s12\text{ MB/s}.

Which two actions should you include in the disaster recovery design?

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

Cevabı ve açıklamayı göster

Cevap: Replicate AppWeb-VM01 to the target region by using Azure Site Recovery.; Replicate the database tier by using SQL Server Always On Availability Groups to the target region.

Cevap

Replicate AppWeb-VM01 to the target region by using Azure Site Recovery, and replicate the database tier by using SQL Server Always On Availability Groups to the target region.
Replicating the web tier virtual machine with Azure Site Recovery is correct because its total write churn of 1.5 MB/s1.5\text{ MB/s} is well within ASR limits. Replicating the database tier with SQL Server Always On Availability Groups is correct because the database data disk write churn of 27 MB/s27\text{ MB/s} exceeds the 20 MB/s20\text{ MB/s} threshold supported by Azure Site Recovery for Premium SSD v1 disks, requiring an application-level replication strategy to maintain the 10-minute RPO.

Adım Adım Çözüm

1
Analyze Azure Site Recovery limits for Premium SSD v1.
The standard disk-level write churn limit for Azure Site Recovery is 10 MB/s10\text{ MB/s} per disk, which can be configured up to 20 MB/s20\text{ MB/s} per disk when the high-churn option is enabled.
This establishes the boundaries of what workloads can be protected using host-based replication with Azure Site Recovery.
2
Compare the virtual machines' disk write churn rates against the limits.
AppWeb-VM01 (1.5 MB/s1.5\text{ MB/s}) and the AppDB-VM01 OS disk (1.8 MB/s1.8\text{ MB/s}) are well below the limits. However, the database data disk write churn (27 MB/s27\text{ MB/s}) exceeds the absolute limit of 20 MB/s20\text{ MB/s}.
This identifies which virtual machines can be replicated using Azure Site Recovery and which cannot.
3
Select the appropriate disaster recovery strategy for the database tier.
Design native database replication using SQL Server Always On Availability Groups to replicate database transactions to a secondary server running in the target region.
Since Azure Site Recovery cannot replicate the high-churn data disk, native replication is required to achieve the 10-minute RPO.

Anahtar Kavram

Azure Site Recovery has strict write churn limits (10 MB/s10\text{ MB/s} standard, 20 MB/s20\text{ MB/s} high-churn per Premium SSD v1 disk). Workloads exceeding these limits must be replicated using application-native replication solutions such as SQL Server Always On Availability Groups.
Soru 510Soru →

An organization is designing the Azure container compute infrastructure for two new applications:

* Application 1 is a simple, public-facing microservice that experiences highly variable traffic. It must scale to zero when idle and minimize administrative effort.
* Application 2 is a stateful data processing engine that must run continuously and requires direct access to the Kubernetes API to manage Custom Resource Definitions (CRDs).

Which two services should you recommend to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps for Application 1; Azure Kubernetes Service (AKS) for Application 2

Cevap

To host Application 1, recommend Azure Container Apps to minimize administrative effort and support scaling to zero. For Application 2, recommend Azure Kubernetes Service (AKS) to provide direct access to the Kubernetes API for Custom Resource Definitions (CRDs).
The correct recommendation is to use Azure Container Apps for the first application and Azure Kubernetes Service (AKS) for the second application. Azure Container Apps is designed for microservices, scaling to zero, and low administrative effort. Azure Kubernetes Service is necessary when direct access to the Kubernetes control plane or API (such as for CRDs) is required.

Adım Adım Çözüm

1
Identify requirements for Application 1.
Application 1 requires a simple microservice host, scaling to zero, and minimal administrative effort.
Establishing application requirements determines the necessary level of control and orchestration.
2
Select container service for Application 1.
Recommend Azure Container Apps.
Azure Container Apps abstracts Kubernetes management, reducing overhead while supporting scale-to-zero microservices.
3
Identify requirements for Application 2.
Application 2 requires direct access to the Kubernetes API to manage Custom Resource Definitions (CRDs).
Direct access to the API plane limits hosting choices to options that expose Kubernetes controls.
4
Select container service for Application 2.
Recommend Azure Kubernetes Service (AKS).
AKS provides full access to the Kubernetes API control plane, which is required for custom CRDs, unlike serverless abstractions like Azure Container Apps.

Anahtar Kavram

Differentiating container hosting options in Azure based on operational overhead and Kubernetes API access requirements.
Soru 511Soru →

A retail company is designing an order processing system that runs containerized workloads. The system must process orders from an Azure Service Bus queue. The workload has the following requirements:
- Process batches of orders that can take up to 15 minutes to complete per batch.
- Scale dynamically from zero to hundreds of instances based on the volume of messages in the queue.
- Support Kubernetes Event-driven Autoscaling (KEDA) natively.
- Minimize the administrative and operational effort required to manage infrastructure, VM patching, and container orchestration.

Which Azure service should you recommend hosting the containerized order processing workload?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps

Cevap

Azure Container Apps
Azure Container Apps is a serverless container platform that natively integrates with KEDA (Kubernetes Event-driven Autoscaling). It allows containers to scale dynamically based on Azure Service Bus queue metrics, including scaling down to zero instances when no messages are present. It abstracts away the Kubernetes cluster management, node patching, and infrastructure maintenance, thereby minimizing operational overhead. Additionally, Azure Container Apps supports long-running execution limits that accommodate the 15-minute processing window.

Adım Adım Çözüm

1
Analyze the scaling and execution requirements
The application runs in containers, needs to scale from zero to hundreds based on queue metrics using KEDA, and has a processing runtime limit of 15 minutes.
This establishes the technical constraints for hosting candidate options.
2
Evaluate the administrative overhead constraint
Azure Kubernetes Service is eliminated due to its high management overhead for node maintenance, upgrades, and clustering.
The scenario explicitly requests minimizing administrative and operational effort.
3
Evaluate the execution timeout constraint
Azure Functions on a Consumption plan is eliminated because it enforces a hard 10-minute timeout.
The workload requires up to 15 minutes of execution time per batch.
4
Evaluate native scaling support
Azure Container Instances is eliminated as it lacks native KEDA event-driven scaling to zero.
ACI would require custom scripts or helper utilities to monitor the queue and trigger instances.
5
Determine the best fit
Azure Container Apps provides serverless container management, native KEDA integrations, scale-to-zero capabilities, and supports container runtime limits that accommodate the 15-minute window.
Azure Container Apps meets all criteria with the lowest administrative overhead.

Anahtar Kavram

Selecting the appropriate Azure container hosting service based on scaling requirements, timeout constraints, and operational overhead.
Soru 512Soru →

A media company stores user activity logs in Azure Data Lake Storage (ADLS) Gen2 in CSV format. You need to design an analytical solution to meet the following requirements:
- Storage Volume: 8 TB8 \text{ TB} of historical CSV log files.
- Ingestion Velocity: Logs are uploaded hourly at a rate of 5 GB5 \text{ GB} per hour.
- Query Pattern: Data analysts perform ad-hoc, exploratory queries intermittently to identify user trends.
- Query Latency: Response times of up to 6060 seconds are acceptable.
- Resiliency: The analytical data must survive a primary datacenter outage within the region.
- Cost: Minimize compute cost when no queries are running.

Which combination of storage redundancy and query engine should you configure?

Cevabı ve açıklamayı göster

Cevap: Configure ADLS Gen2 with Geo-Redundant Storage (GRS) and use Azure Synapse Analytics Serverless SQL pools to query the CSV files.

Cevap

Configure ADLS Gen2 with Geo-Redundant Storage (GRS) and use Azure Synapse Analytics Serverless SQL pools to query the CSV files.
The correct solution uses Geo-Redundant Storage (GRS) to ensure that the data survives a primary datacenter outage, and queries the CSV files directly using Azure Synapse Serverless SQL pools. Serverless SQL pools charge only for data processed per query, making them highly cost-effective for ad-hoc, intermittent query patterns on files stored in a data lake.

Adım Adım Çözüm

1
Determine the appropriate query model based on query patterns and cost constraints.
Since the queries are ad-hoc, intermittent, and performed on CSV files in a data lake, Azure Synapse Serverless SQL pools are selected to minimize compute costs via pay-per-query pricing.
Dedicated SQL pools incur ongoing provisioned compute costs even when idle, which violates the requirement to minimize costs during periods of inactivity.
2
Evaluate the resiliency requirements for the underlying storage.
Select Geo-Redundant Storage (GRS) for Azure Data Lake Storage Gen2.
Locally Redundant Storage (LRS) only replicates data within a single datacenter, failing the requirement to survive a primary datacenter outage.
3
Ensure secure access configuration.
Avoid long-lived Shared Access Signature (SAS) tokens without stored access policies.
Ad-hoc SAS tokens with long lifetimes cannot be revoked easily, presenting a significant security risk.

Anahtar Kavram

Selecting the optimal Azure Synapse query model (Serverless vs. Dedicated) and storage redundancy based on cost, latency, and resiliency requirements.
Soru 513Soru →

An enterprise environment uses a hub-and-spoke topology. The hub virtual network is `vnet-hub-prod` (address space 10.1.0.0/1610.1.0.0/16) and hosts a network virtual appliance (NVA) at 10.1.0.410.1.0.4. Two spoke virtual networks are peered only to the hub: `vnet-spoke-web` (address space 10.2.0.0/1610.2.0.0/16) and `vnet-spoke-data` (address space 10.3.0.0/1610.3.0.0/16). You need to route all traffic between the two spokes through the NVA without overriding the default routing for communication within each spoke's own address space. Which two configurations should you implement?

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

Cevabı ve açıklamayı göster

Cevap: In the route table associated with the subnets in `vnet-spoke-web`, add a route for 10.3.0.0/1610.3.0.0/16 with a next hop of Virtual Appliance at 10.1.0.410.1.0.4.; In the route table associated with the subnets in `vnet-spoke-data`, add a route for 10.2.0.0/1610.2.0.0/16 with a next hop of Virtual Appliance at 10.1.0.410.1.0.4.

Cevap

To route inter-spoke traffic through the NVA, you must add a route for the remote spoke's address prefix (10.3.0.0/1610.3.0.0/16 in the web spoke, and 10.2.0.0/1610.2.0.0/16 in the data spoke) with a next hop pointing to the NVA's IP address. You must avoid creating user-defined routes for a spoke's own local address prefix, as doing so overrides the default system route for the local virtual network and disrupts internal communication.
To route transit traffic between the two spoke virtual networks through the NVA, you must define routes for the non-local spoke prefixes. Thus, the route table for the web spoke needs a route for the database spoke prefix (10.3.0.0/1610.3.0.0/16), and the route table for the database spoke needs a route for the web spoke prefix (10.2.0.0/1610.2.0.0/16). Both routes must point to the NVA's IP address at 10.1.0.410.1.0.4. This setup ensures that inter-spoke traffic is routed through the NVA, while local traffic within each spoke is handled by the default system route.

Adım Adım Çözüm

1
Identify the target address prefix for outbound inter-spoke traffic originating from the web spoke.
The target prefix is the database spoke's address space: 10.3.0.0/1610.3.0.0/16.
This target prefix is used to steer traffic destined for the other spoke towards the NVA.
2
Identify the target address prefix for outbound inter-spoke traffic originating from the database spoke.
The target prefix is the web spoke's address space: 10.2.0.0/1610.2.0.0/16.
This target prefix is used to steer traffic returning or originating from the database spoke towards the NVA.
3
Configure the next hop type and IP address for both route definitions.
The next hop type is set to Virtual Appliance, and the next hop IP address is set to 10.1.0.410.1.0.4.
This directs traffic to the NVA hosted in the hub virtual network instead of using default direct routing.

Anahtar Kavram

User-Defined Routes and Default System Route Overrides
Soru 514Soru →

ApexVault Pay is designing a disaster recovery strategy for its transaction ledger application. The ledger data is currently stored in a general-purpose v2 storage account configured with Read-Access Geo-Redundant Storage (RA-GRS), where West US 3 is the primary region and East US is the secondary region. The business continuity requirements specify:
- A Recovery Point Objective (RPO) of 15 minutes.
- A Recovery Time Objective (RTO) of 30 minutes.
- Read availability in the secondary region during a primary region outage must be immediate.
- Write availability must be restored in the secondary region within the RTO.
- Solution costs must be minimized by avoiding multi-region active-write configurations.

During a simulated regional outage of West US 3, the operations team needs to maintain business continuity. The application instance in East US must immediately be able to read existing ledger data. Additionally, the team plans to minimize data loss by performing a customer-managed failover to make East US the primary region.

Which of the following describes the write availability of the storage account during this recovery process?

Cevabı ve açıklamayı göster

Cevap: Write operations are unavailable in the secondary region until the customer-managed failover is completed, at which point the storage account is converted to locally redundant storage (LRS) in the new primary region and write capabilities are enabled.

Cevap

Write operations are unavailable in the secondary region until the customer-managed failover is completed, at which point the storage account is converted to locally redundant storage (LRS) in the new primary region and write capabilities are enabled.
The correct answer is correct because under RA-GRS, the secondary endpoint is read-only. To allow write operations in the secondary region during an outage, a customer-managed failover must be triggered. Once the failover completes, the secondary region becomes the new primary, the storage account replication tier is converted to Locally Redundant Storage (LRS), and write operations become available.

Adım Adım Çözüm

1
Analyze the capabilities of the Read-Access Geo-Redundant Storage (RA-GRS) secondary endpoint during a primary region outage.
Identify that the secondary endpoint is strictly read-only prior to initiating a failover, meaning writes cannot be sent directly to the secondary region.
This establishes that write access is unavailable in the secondary region during the initial phase of the outage.
2
Determine the impact of initiating and completing a customer-managed failover on the storage account configuration.
Recall that a customer-managed failover updates the DNS records so that the secondary region becomes the new primary, enabling write access, and changes the replication type to locally redundant storage (LRS).
This identifies the state of the storage account and the replication configuration after the failover completes.
3
Compare the results against the options to find the one that accurately describes both the pre-failover write restriction and post-failover LRS transition.
The option describing write unavailability prior to failover and the subsequent LRS conversion matches these characteristics.
This confirms the correct choice based on Azure Storage DR design rules.

Anahtar Kavram

Azure Storage customer-managed failover behavior and replication state changes for GRS/RA-GRS accounts.
Soru 515Soru →

A retail company is designing a container-based backend system for real-time inventory updates. The system consists of multiple microservices that process messages from Azure Service Bus queues. The solution must meet the following requirements:
- Scale container instances down to zero when there are no messages in the queue to minimize costs.
- Support event-driven auto-scaling based on the number of messages in the Service Bus queues.
- Prevent developers from managing Kubernetes APIs, control planes, or virtual machine node scaling.
- Consolidate application telemetry into a single repository, while strictly isolating sensitive transaction logs into a separate, dedicated repository for regulatory compliance.

Which architecture should you recommend to meet the requirements with the minimum amount of administrative effort?

Cevabı ve açıklamayı göster

Cevap: Deploy the microservices to Azure Container Apps. Configure the container apps to write telemetry to a shared Log Analytics workspace, and route transaction logs to a dedicated Log Analytics workspace.

Cevap

Deploy the microservices to Azure Container Apps. Configure the container apps to write telemetry to a shared Log Analytics workspace, and route transaction logs to a dedicated Log Analytics workspace.
The correct solution uses Azure Container Apps to host the microservices. This satisfies the event-driven scaling (via KEDA integration) and scale-to-zero requirements while completely abstracting the Kubernetes control plane and VM node scaling. To meet the compliance requirement, the solution isolates sensitive transaction logs into a dedicated Log Analytics workspace, keeping general application telemetry in a shared workspace.

Adım Adım Çözüm

1
Evaluate the compute hosting requirements against Azure options.
Azure Container Apps (ACA) is selected over Azure Kubernetes Service (AKS) because it is a serverless platform that natively supports KEDA-based scaling, scales to zero, and hides Kubernetes API/infrastructure management, which directly minimizes administrative effort.
The requirements state that developer management of Kubernetes APIs, control planes, and VM node scaling must be prevented, which rules out AKS.
2
Evaluate the logging and compliance requirements.
Two distinct Log Analytics workspaces are planned: one shared workspace for telemetry logs and one dedicated workspace for sensitive transaction logs.
Regulatory compliance mandates strict isolation of transaction logs from application telemetry, which cannot be achieved with a single consolidated workspace.
3
Synthesize compute and logging designs into a unified solution.
Recommend hosting the microservices on Azure Container Apps and configuring log split routing to two separate Log Analytics workspaces.
This combined architecture satisfies all business, technical, scaling, and compliance requirements with the lowest operational overhead.

Anahtar Kavram

Azure Container Apps provides serverless container hosting with native KEDA-based scaling and zero operational overhead compared to AKS, while log isolation requirements must be met by using separate Log Analytics workspaces.
Soru 516Soru →

NovaPeak Space Dynamics is designing an identity and access management strategy for its Microsoft Entra ID tenant. The tenant is synchronized with an on-premises Active Directory Domain Services (AD DS) domain. You need to design a solution that meets the following security requirements:

- Users must be able to sign in to cloud applications even if the on-premises network or domain controllers are unavailable.
- Administrators must not be locked out of the tenant in the event of an Azure Multi-Factor Authentication (MFA) service outage.

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: Exclude a dedicated emergency access account from all Conditional Access policies that require multi-factor authentication; Configure Password Hash Synchronization (PHS) as the hybrid authentication method

Cevap

Exclude a dedicated emergency access account from all Conditional Access policies that require multi-factor authentication, and configure Password Hash Synchronization (PHS) as the hybrid authentication method.
The correct configurations are using Password Hash Synchronization (PHS) and excluding emergency access accounts from Conditional Access policies. Password Hash Synchronization copies password hashes from on-premises Active Directory to Microsoft Entra ID, allowing users to sign in even if the on-premises infrastructure is unavailable. Excluding emergency access (break-glass) accounts from Conditional Access policies that require multi-factor authentication prevents administrative lockout if the Multi-Factor Authentication service experiences an outage.

Adım Adım Çözüm

1
Evaluate the requirement for cloud authentication availability during on-premises downtime.
Password Hash Synchronization (PHS) is selected because it replicates password hashes to Microsoft Entra ID, allowing authentication directly in the cloud independent of on-premises domain controller availability.
On-premises identity providers like Active Directory Federation Services (AD FS) depend on active on-premises networks and domain controllers, which does not meet the resiliency requirement.
2
Evaluate the requirement to prevent administrator lockout during a multi-factor authentication (MFA) service outage.
A dedicated emergency access (break-glass) account is designed and excluded from all Conditional Access policies that require MFA.
Omitting exclusions for emergency access accounts risks permanent tenant lockout if Microsoft Entra MFA services are unreachable.
3
Ensure administrative role assignment alignment with security best practices.
Ensure the emergency access account is not configured with permanently active administrative roles in PIM, keeping assignments governed appropriately.
Permanent role assignment bypasses the security controls of Privileged Identity Management.

Anahtar Kavram

Designing resilient Microsoft Entra ID hybrid authentication and administrative access controls, including Password Hash Synchronization (PHS) for local outage resilience and emergency access account exclusions in Conditional Access policies to prevent lockout.
Soru 517Soru →

A financial services company is designing a new payment processing application on Azure. The architecture consists of a transaction processing API tier and a stateful database tier. The application design must satisfy the following requirements:

* The database tier requires at least 256 GB of memory and high temporary storage throughput. To minimize SQL Server core-based licensing costs, the operating system must only see 8 vCPUs, while the database continues to utilize the memory and I/O performance of a 32-core virtual machine size.
* The transaction processing API tier handles highly sensitive financial data in transit. It must run in a secure, hardware-isolated execution environment that protects data in memory from external access, including the host operating system, hypervisor, and cloud administrators.
* The database tier must remain highly available and survive a primary datacenter outage without unexpected interruptions or evictions.

Which two compute virtualization solutions or configurations should you recommend to meet these requirements?

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

Cevabı ve açıklamayı göster

Cevap: Deploy the database tier on E32-8ds_v5 constrained vCPU virtual machines; Deploy the transaction processing API tier on DC-series or EC-series confidential virtual machines

Cevap

Deploy the database tier on E32-8ds_v5 constrained vCPU virtual machines and deploy the transaction processing API tier on DC-series or EC-series confidential virtual machines.
Deploying the database tier on E32-8ds_v5 constrained vCPU virtual machines provides the required 256 GB of memory and storage throughput of the E32ds_v5 size while limiting active vCPUs to 8, which minimizes SQL Server licensing costs. Deploying the transaction processing API tier on DC-series or EC-series confidential virtual machines meets the security requirement by encrypting memory in use at the hardware level using AMD SEV-SNP or Intel SGX, preventing access from the hypervisor and cloud operators.

Adım Adım Çözüm

1
Analyze the database core licensing constraint.
Determine that a constrained vCPU virtual machine size is required to provide high memory (256 GB) and high I/O throughput while limiting the OS-visible vCPUs to 8 to minimize licensing costs.
Azure offers constrained vCPU VM sizes (such as E32-8ds_v5) specifically for database workloads where memory and storage performance are needed but licensing costs are bound to core counts.
2
Analyze the secure execution environment requirement for the API tier.
Determine that confidential virtual machines (such as DC-series or EC-series) are required to protect data in memory from external access, including the hypervisor and administrators.
Confidential computing uses hardware-based Trusted Execution Environments (TEEs) to encrypt memory in use.
3
Evaluate the database tier availability requirements.
Rule out Azure Spot VMs due to eviction risks, and rule out single-zone deployments due to lack of resilience against datacenter outages.
Production database workloads must run on standard VM tiers across multiple availability zones to satisfy high availability SLAs.

Anahtar Kavram

Azure compute virtualization selection, including constrained vCPUs for cost optimization, confidential computing for security in use, and high availability constraints.
Soru 518Soru →

You are an Azure Solutions Architect designing a data modernization strategy for a global retail enterprise. The architecture must achieve an SLA of 99.999%99.999\% availability for both reads and writes, and support global distribution across three regions: East US, West Europe, and Southeast Asia. The application suite consists of multiple workloads with different read-to-write ratios and data models:

- Workload 1: A recommendation engine that performs relationship-heavy queries (vertices and edges) to map user preferences, requiring a 70:3070:30 read-to-write ratio.
- Workload 2: A globally distributed telemetry processor migrated from an on-premises Apache Cassandra cluster, requiring a 10:9010:90 read-to-write ratio.
- Workload 3: A product catalog migrated from an existing MongoDB cluster that uses complex document aggregation pipelines, requiring an 80:2080:20 read-to-write ratio.
- Workload 4: A simple session-state store migrated from Azure Table Storage requiring high-throughput key-value lookups with a 50:5050:50 read-to-write ratio.

Match each workload description to the most appropriate Azure Cosmos DB API to meet these requirements.

Soldaki öğeye tıklayın, sonra eşleşen sağdaki öğeye tıklayın

Öğeler

A relationship-heavy recommendation engine that maps complex user connections using vertices and edges.
A high-write telemetry processor migrated from an Apache Cassandra cluster utilizing CQL.
A product catalog migrated from a MongoDB database using document aggregation pipelines.
A session-state key-value store migrated from Azure Table Storage.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Workload 1 matches Azure Cosmos DB for Apache Gremlin; Workload 2 matches Azure Cosmos DB for Apache Cassandra; Workload 3 matches Azure Cosmos DB for MongoDB; Workload 4 matches Azure Cosmos DB for Table.
The correct pairings align each workload with the appropriate Azure Cosmos DB API: the graph-based recommendation engine aligns with the Gremlin API, the Cassandra migration aligns with the Cassandra API, the MongoDB migration aligns with the MongoDB API, and the Table Storage migration aligns with the Table API. This alignment ensures protocol compatibility, query language support, and minimum code changes.

Adım Adım Çözüm

1
Analyze Workload 1 requirements for graph relationships.
The requirement specifies vertices and edges, which indicates a graph database. The matching API is Azure Cosmos DB for Apache Gremlin.
Gremlin is the standard graph API in Cosmos DB.
2
Analyze Workload 2 requirements for Cassandra CQL migration.
The workload is migrated from Apache Cassandra and uses CQL, which maps directly to Azure Cosmos DB for Apache Cassandra.
Cassandra API provides direct wire compatibility for Apache Cassandra workloads.
3
Analyze Workload 3 requirements for MongoDB aggregation pipeline migration.
The catalog data is migrated from MongoDB and uses its document aggregation pipelines, pointing to Azure Cosmos DB for MongoDB.
MongoDB API supports MongoDB query syntax and aggregation commands.
4
Analyze Workload 4 requirements for key-value Table Storage migration.
The session store needs a key-value structure and is migrated from Azure Table Storage, matching Azure Cosmos DB for Table.
Table API provides key-value storage capabilities compatible with SDKs for Azure Table Storage.

Anahtar Kavram

Selecting Azure Cosmos DB APIs based on workload query models and migration compatibility requirements.
Tahmini Süre:2m 0s
Soru 519Soru →

An enterprise deploys a hub-and-spoke virtual network topology in Azure. The Hub Virtual Network (vnet-hub-prod, CIDR: 10.200.0.0/16) contains a subnet (snet-hub-nva, CIDR: 10.200.1.0/24) that hosts a firewall Network Virtual Appliance (NVA) at IP address 10.200.1.4. The Spoke Virtual Network (vnet-spoke-app, CIDR: 10.201.0.0/16) contains a subnet (snet-app-prod, CIDR: 10.201.1.0/24) hosting application servers. The virtual networks are peered.

The enterprise has the following requirements:
1. All outbound internet traffic from snet-app-prod must be routed through the NVA at 10.200.1.4 for security inspection.
2. Application servers in snet-app-prod must communicate directly with database servers in another subnet (snet-app-db, CIDR: 10.201.2.0/24) within the same virtual network without traversing the NVA, to minimize latency.
3. Access to public Azure Key Vault instances must go directly over the Azure backbone network using service tags.

A junior administrator creates a custom Route Table, associates it with snet-app-prod, and defines the following user-defined routes (UDRs):
- Route 1: Address prefix 0.0.0.0/0 -> Next hop: Virtual appliance (10.200.1.4)
- Route 2: Address prefix 10.201.0.0/16 -> Next hop: Virtual appliance (10.200.1.4)
- Route 3: Address prefix AzureKeyVault (Service Tag) -> Next hop: Internet

Following this configuration, application servers in snet-app-prod lose all connectivity to database servers in snet-app-db.

Which modification to the Route Table will restore the required network connectivity?

Cevabı ve açıklamayı göster

Cevap: Delete Route 2 from the Route Table so that traffic within the virtual network is handled by the default system-defined local route.

Cevap

Delete the user-defined route with the prefix 10.201.0.0/16 (Route 2) from the Route Table so that traffic within the virtual network is handled by the default system-defined local route.
Deleting the user-defined route with the prefix 10.201.0.0/16 allows the default system-defined local virtual network route to handle traffic within the virtual network. In Azure, UDRs with the exact same prefix as system routes will override them. Removing this route allows servers in the application subnet to communicate directly with the database subnet without going through the NVA, satisfying the latency constraint while keeping the security rules for internet and Key Vault traffic intact.

Adım Adım Çözüm

1
Analyze the current route table configuration and identify conflicts with requirements.
Route 2 has the address prefix 10.201.0.0/16, which matches the local virtual network's CIDR block.
Identify why traffic from the application subnet to the database subnet within the same virtual network is failing.
2
Evaluate the route selection logic in Azure.
User-defined routes (UDRs) with the same prefix length as system routes override the default system routes. Thus, Route 2 overrides the default '10.201.0.0/16 -> Local' route.
Determine how Route 2 affects traffic destined for resources inside the same virtual network.
3
Formulate a resolution that satisfies all design constraints.
By deleting Route 2, the system route '10.201.0.0/16 -> Local' becomes active again, allowing intra-virtual network traffic to bypass the NVA. Outbound internet traffic and Key Vault traffic still match Route 1 and Route 3 respectively.
Restore the default system local route while preserving forced tunneling for internet traffic and direct path access for Azure Key Vault.

Anahtar Kavram

Azure Route Selection and User Defined Route (UDR) Override Behaviors
Tahmini Süre:2m 0s
Soru 520Soru →

A biotechnology firm is designing a serverless container-based system on Azure to process genomic sequencing data. The architecture must support the following workloads:

* Workload 1: A research portal web application that accepts sequencing requests. The application must scale dynamically based on HTTP traffic, scale down to zero instances during idle periods to minimize costs, and support custom domain names with TLS termination.
* Workload 2: A sequencing analysis processor. Each execution is triggered by a new message in an Azure Service Bus queue, runs to completion, and can take up to three hours to finish. The processor must automatically scale its instances horizontally based on the number of messages in the queue.

You need to recommend the container compute solutions for both workloads. The solution must minimize administrative and operational overhead.

Which services should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps for Workload 1 and Azure Container Apps Jobs for Workload 2

Cevap

Azure Container Apps for Workload 1 and Azure Container Apps Jobs for Workload 2
The correct recommendation is to use Azure Container Apps for the web application (Workload 1) and Azure Container Apps Jobs for the batch sequencing analysis processor (Workload 2). Azure Container Apps is optimized for HTTP-based, serverless workloads that need to scale down to zero replicas. Azure Container Apps Jobs is designed specifically for run-to-completion tasks triggered by events (such as queue messages) and can run for up to 24 hours, satisfying the 3-hour requirement while natively supporting KEDA-based horizontal scaling to zero.

Adım Adım Çözüm

1
Analyze the requirements for Workload 1
Workload 1 is a web application requiring HTTP routing, TLS termination, auto-scaling to zero, and serverless compute. Azure Container Apps is a managed platform that natively supports these features with minimal administrative effort.
Identify the best serverless host for HTTP-triggered web portals without the overhead of AKS.
2
Analyze the requirements for Workload 2
Workload 2 is a queue-triggered, run-to-completion processor that can run for up to three hours and requires event-driven horizontal scaling.
Determine the execution patterns and runtime limitations of the workloads.
3
Evaluate candidate compute services for Workload 2 against runtime and scaling constraints
Azure Functions Consumption plan has a 10-minute execution limit, making it invalid. Azure Container Instances (ACI) lacks native auto-scaling on queue length, requiring custom orchestration. Azure Container Apps Jobs supports run-to-completion execution up to 24 hours and includes native KEDA scalers for Service Bus queues.
Select the option that satisfies the timeout and scaling requirements with the lowest operational overhead.

Anahtar Kavram

Selecting the appropriate Azure container hosting option (Azure Container Apps vs. Azure Container Apps Jobs vs. AKS vs. ACI) based on workload execution patterns, scaling behaviors, runtime timeouts, and operational overhead constraints.
ÖncekiSayfa 26 / 60Sonraki