Tüm alıştırma soruları

1198 soru

Soru 641Soru

Solas Renewable Energy is designing an identity and access management solution for its Microsoft Entra ID tenant. The solution must meet the following requirements:

- Enforce multi-factor authentication (MFA) for all users assigned to privileged administrator roles when they access the Azure portal.
- Prevent administrative users from being permanently assigned to privileged roles, requiring them to activate roles on demand.
- Ensure that the tenant remains accessible to administrators even during a widespread Microsoft Entra MFA service outage.

Which of the following configurations should you include in the design? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Create a Conditional Access policy requiring multi-factor authentication for administrative roles, and exclude a dedicated, cloud-only emergency access account.; Configure eligible role assignments in Microsoft Entra Privileged Identity Management (PIM) for the administrative roles.

Cevap

Create a Conditional Access policy requiring multi-factor authentication for administrative roles, and exclude a dedicated, cloud-only emergency access account; and configure eligible role assignments in Microsoft Entra Privileged Identity Management (PIM) for the administrative roles.
To meet the security and reliability goals, you must enforce MFA using Conditional Access while excluding an emergency access account to prevent lockout during service outages. Additionally, to avoid permanent privileges, you must configure eligible assignments in Microsoft Entra Privileged Identity Management (PIM), which allows administrators to elevate their access on demand.

Adım Adım Çözüm

1
Identify the requirement to prevent permanent administrative assignment.
Determine that Microsoft Entra Privileged Identity Management (PIM) must be used with eligible assignments, not active assignments, to enforce just-in-time role activation.
Active assignments leave the privilege permanently assigned to the user.
2
Identify the requirement to enforce MFA for administrators while preventing tenant lockout during outages.
Determine that a Conditional Access policy must target administrative roles with MFA required, and exclude a dedicated, cloud-only emergency access account.
Excluding the emergency access account ensures admins can log in if Entra MFA is offline, avoiding a tenant lockout scenario.

Anahtar Kavram

Designing Microsoft Entra ID Conditional Access policies with emergency exclusions and integrating Privileged Identity Management (PIM) for just-in-time access.
Soru 642Soru

An automotive manufacturing corporation is designing a container-based telemetry and diagnostics platform on Azure. The platform will be deployed across two European regions. The design must meet the following requirements:
- A set of internal REST APIs must process incoming vehicle diagnostics data.
- A background analytics engine must process messages from an Azure Service Bus queue and scale to zero when no messages are present.
- A third-party security agent must run as a privileged DaemonSet on every container host node to inspect kernel-level system calls.
- Telemetry and logs collected from the workloads in each region must be isolated and stored only within that specific region to meet strict local data residency compliance.

You need to recommend the container hosting and monitoring architecture.

Which solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy Azure Kubernetes Service (AKS) in both regions with Kubernetes Event-driven Autoscaling (KEDA) configured for the background analytics engine. Configure a separate Azure Log Analytics workspace in each region to collect and store logs locally.

Cevap

Deploy Azure Kubernetes Service (AKS) in both regions with Kubernetes Event-driven Autoscaling (KEDA) configured for the background analytics engine. Configure a separate Azure Log Analytics workspace in each region to collect and store logs locally.
The correct solution recommends Azure Kubernetes Service (AKS) because running a privileged security agent as a DaemonSet to inspect host-level kernel calls requires access to the underlying VM host nodes, which is supported by AKS but not by serverless container environments like Azure Container Apps. The solution uses KEDA within AKS to natively support event-driven auto-scaling to zero based on Azure Service Bus metrics. To comply with strict regional data isolation rules, the architecture deploys separate Log Analytics workspaces in each region to ensure telemetry data is stored within its local geographic boundary.

Adım Adım Çözüm

1
Analyze the container node access requirement.
The security policy requires a third-party security agent to run as a DaemonSet to inspect kernel-level system calls on container host nodes.
This requirement indicates that the hosting platform must expose access to the underlying virtual machine host nodes. Serverless container offerings like Azure Container Apps and Azure Container Instances abstract host nodes away and do not support DaemonSets or kernel-level inspection.
2
Select the appropriate container hosting service.
Azure Kubernetes Service (AKS) is selected because it provides full control over the node configuration and natively supports DaemonSets.
AKS allows deploying DaemonSets onto the worker nodes to run security agents directly on each VM host, satisfying the security constraint.
3
Evaluate the scaling mechanism for the queue-based worker.
Configure Kubernetes Event-driven Autoscaling (KEDA) on the AKS clusters to scale the background pods based on Service Bus queue metrics.
KEDA allows Kubernetes workloads to scale to zero based on external event sources, meeting the requirement to scale to zero when no Service Bus messages are present.
4
Determine the monitoring and compliance architecture.
Deploy a separate Log Analytics workspace in each European region and route regional cluster logs to their respective local workspaces.
A single centralized Log Analytics workspace would aggregate data across regional boundaries, which violates the strict data residency and isolation compliance requirements.

Anahtar Kavram

Selecting Azure Kubernetes Service (AKS) vs. Azure Container Apps based on node-level control requirements, combined with regional log isolation design.
Tahmini Süre:2m 30s
Soru 643Soru

A manufacturing company is designing a container-based quality control system on Azure. The system will run image classification models on images uploaded by factory cameras. The workloads have the following requirements:
- Scale up rapidly in response to a sudden influx of images uploaded to an Azure Blob Storage container.
- Scale down to zero when there are no images to process to minimize idle compute costs.
- Support event-driven scaling using KEDA without requiring the team to manage Kubernetes APIs, node pools, or cluster upgrades.

Which compute solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps

Cevap

Azure Container Apps
Azure Container Apps is the recommended solution because it is a serverless container hosting service designed for microservices and event-driven applications. It supports native autoscaling using KEDA, allowing containers to scale to zero when idle, and manages all underlying Kubernetes infrastructure, APIs, and upgrades, thereby minimizing administrative effort.

Adım Adım Çözüm

1
Analyze the scaling and infrastructure management requirements.
The solution requires rapid scaling based on events (KEDA), scaling down to zero, and minimized administrative overhead.
This rules out solutions that require managing cluster infrastructure or lack native event-driven scaling mechanisms.
2
Compare candidate Azure container hosting services.
Azure Container Apps is fully managed, serverless, natively supports KEDA, and scales to zero. Azure Kubernetes Service (AKS) requires node and cluster administration. Azure Container Instances (ACI) lacks native KEDA autoscaling.
Choosing the service that balances KEDA scaling with low management overhead is key to meeting the design requirements.

Anahtar Kavram

Azure Container Apps provides a serverless platform for containerized applications, enabling KEDA-driven scaling and eliminating Kubernetes cluster management overhead.
Soru 644Soru

An organization is designing a serverless backend for an enterprise batch import system. The system must process files uploaded to an Azure Blob Storage container. The architectural design must satisfy the following technical constraints:

- Execution Time: The file processing logic is single-threaded and can take up to 15 minutes to complete for large payloads.
- Network Isolation: The compute resource must securely access an Azure SQL Database and storage accounts via private endpoints within an Azure Virtual Network (VNet).
- Cost Efficiency: The compute resource must automatically scale down to zero instances when there are no files to process, ensuring zero billing during idle periods.
- Operational Overhead: Minimize administrative overhead by avoiding the need to configure, build, or deploy custom Docker container images or manage container registries.

Which Azure compute hosting option should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Azure Functions on a Flex Consumption plan

Cevap

Azure Functions on a Flex Consumption plan
The correct option is the Azure Functions Flex Consumption plan. It supports fast virtual network integration through subnet delegation, scales to zero instances when idle to eliminate cold-start costs during inactive periods, allows configuring the execution duration timeout up to 30 minutes, and offers a code-first deployment path that avoids containerization overhead.

Adım Adım Çözüm

1
Evaluate the execution duration limit constraint.
The file processing tasks can take up to 15 minutes. This immediately rules out the standard Azure Functions Consumption plan, which has a hard maximum timeout of 10 minutes.
Choosing a plan that cannot support the maximum processing time will result in premature execution failures.
2
Evaluate the network isolation constraint.
The solution requires secure access to resources using private endpoints inside an Azure Virtual Network (VNet).
This rules out the standard Consumption plan as it lacks VNet integration support, but Elastic Premium, Flex Consumption, and AKS options remain viable.
3
Evaluate the cost constraint of scaling to zero billing during idle periods.
The compute hosting plan must scale to zero instances when idle to ensure no compute charges.
This rules out the Elastic Premium plan because it requires at least one active, pre-warmed instance, leading to continuous charges regardless of usage.
4
Evaluate the operational overhead and container management constraint.
The architecture must avoid container management, registry management, and custom Dockerfile creation.
This rules out Azure Kubernetes Service (AKS) with KEDA, as it introduces substantial containerization and cluster administration overhead.
5
Confirm the capabilities of the remaining option.
Azure Functions on a Flex Consumption plan natively supports up to 30-minute execution limits, fast subnet delegation VNet integration, scales down to zero instances when inactive, and allows code-first deployment without custom container images.
This matches all specific constraints of the scenario.

Anahtar Kavram

Selecting the optimal Azure Functions plan based on execution limits, virtual network integration, scale-to-zero capabilities, and administrative overhead.
Soru 645Soru

Verdant Power Solutions is designing a business continuity solution for an application that processes wind turbine telemetry data. The application continuously writes transactional log files to an Azure Storage account.

The solution must satisfy the following requirements:
- Recovery Point Objective (RPO): Less than 1515 minutes.
- Recovery Time Objective (RTO): Less than 3030 minutes.
- Read availability: Telemetry data must remain readable from a secondary region during a primary region outage.
- Write availability: Write capabilities must be restored in the secondary region within the RTO during a primary region outage.
- Cost: Storage costs must be minimized.

Which storage redundancy configuration and disaster recovery procedure should you recommend?

Cevabı ve açıklamayı göster

Cevap: Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS) and initiate a customer-managed failover to the secondary region during an outage.

Cevap

Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS) and initiate a customer-managed failover to the secondary region during an outage.
The correct answer configuration uses Read-Access Geo-Redundant Storage (RA-GRS) combined with customer-managed failover. RA-GRS ensures that data is geo-replicated and readable from the secondary region's secondary endpoint during a primary outage. Initiating a customer-managed failover promotes the secondary region to primary, restoring write capabilities within the required 30-minute RTO.

Adım Adım Çözüm

1
Analyze the read availability requirement during a primary region outage.
Standard Geo-Redundant Storage (GRS) does not allow read access to the secondary region during a primary outage unless a failover is initiated. Only Read-Access Geo-Redundant Storage (RA-GRS) provides a secondary read-only endpoint that remains accessible.
Ensures the solution satisfies the read availability requirement during an outage.
2
Analyze the write availability and RTO requirements.
To restore write availability in the secondary region within the 30-minute RTO, a customer-managed failover must be initiated. A Microsoft-managed failover does not guarantee a specific timeline and is reserved for major disasters.
Determines the correct procedure to resume write capabilities within the RTO envelope.
3
Evaluate the write capabilities of RA-GRS.
The secondary endpoint is read-only. Writes cannot be redirected to the secondary endpoint without completing a failover, which promotes the secondary region to the primary role.
Eliminates incorrect configuration proposals that attempt direct writes to the read-only secondary endpoint.

Anahtar Kavram

Azure Storage Disaster Recovery and Redundancy
Tahmini Süre:1m 30s
Soru 646Soru

Your company has an on-premises datacenter connected to an Azure Virtual Network (VNet) via a site-to-site VPN. You are designing a secure private access solution for a business-critical application running on virtual machines in the VNet. The application needs to connect to an Azure SQL Database. You must meet the following requirements:
- The Azure SQL Database must not accept connections from the public internet.
- The virtual machines must access the database using private IP addresses.
- On-premises database administrators must be able to manage the database using private IP addresses.
- On-premises DNS servers must resolve the database FQDN to its private IP address.
- Administrative overhead for security rule maintenance and DNS routing must be minimized.

Which network security design should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy a Private Endpoint for the Azure SQL Database. Configure an Azure DNS Private Resolver in the VNet, and set up conditional forwarding on the on-premises DNS servers to route database FQDN queries to the resolver's inbound endpoint. Apply a Network Security Group (NSG) utilizing the SQL Service Tag to secure database traffic.

Cevap

Deploy a Private Endpoint for the Azure SQL Database, configure an Azure DNS Private Resolver with conditional forwarding from on-premises DNS servers, and apply a Network Security Group utilizing the SQL Service Tag.
The correct answer provides a robust network security and private access design. A Private Endpoint ensures that the Azure SQL Database is only accessible via a private IP address, completely blocking public access. Deploying an Azure DNS Private Resolver allows on-premises DNS servers to forward queries to its inbound endpoint, ensuring on-premises clients can resolve the private IP address of the database. Finally, utilizing the SQL Service Tag within the Network Security Group (NSG) restricts outbound database traffic while avoiding the need to manually update rules when IP addresses change, minimizing administrative overhead.

Adım Adım Çözüm

1
Select Private Endpoint to satisfy private access and disable public access.
The Azure SQL Database is assigned a private IP address within the VNet, and public internet access can be completely disabled.
Meets the security requirements for private IP access and zero public internet exposure.
2
Deploy Azure DNS Private Resolver to enable hybrid DNS resolution.
On-premises DNS servers can use conditional forwarding to target the resolver's inbound endpoint to resolve the database FQDN to its private IP.
Provides seamless DNS resolution across hybrid connections without the administrative overhead of deploying and patching DNS forwarder VMs.
3
Use Service Tags in Network Security Groups (NSGs) for outbound control.
The NSG uses the SQL Service Tag rather than manually configured IP blocks.
Minimizes administrative overhead since Azure automatically maintains the IP address ranges associated with the Service Tag.

Anahtar Kavram

Designing secure hybrid name resolution and private access for Azure PaaS services using Private Endpoints and Azure DNS Private Resolver.
Tahmini Süre:2m 0s
Soru 647Soru

A media streaming company hosting its application in the Azure North Europe region wants to design a disaster recovery (DR) solution to the West Europe region. The application runs on two Azure virtual machines (VMs):

- `vm-web`: A web server VM with one Standard SSD disk that has a write churn rate of 3 MB/s3\text{ MB/s}.
- `vm-db`: A SQL Server database VM with two Premium SSD disks: a data disk with a write churn rate of 12 MB/s12\text{ MB/s} and a log disk with a write churn rate of 25 MB/s25\text{ MB/s}.

The disaster recovery solution must achieve a Recovery Point Objective (RPO) of 2 hours and a Recovery Time Objective (RTO) of 4 hours.

Which disaster recovery configuration should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Replicate `vm-web` using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the databases on `vm-db` to the West Europe region.

Cevap

Replicate `vm-web` using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the databases on `vm-db` to the West Europe region.
The correct configuration is to replicate the web server VM using Azure Site Recovery and to configure SQL Server Always On Availability Groups to replicate the database. This is because the database log disk write churn of 25 MB/s25\text{ MB/s} exceeds the maximum supported write churn limit of 20 MB/s20\text{ MB/s} per Premium SSD disk for Azure Site Recovery (even with enhanced high-churn support). Therefore, native SQL Server replication must be utilized for the database tier, while the web tier can be safely replicated using ASR since its disk churn of 3 MB/s3\text{ MB/s} is well within limits.

Adım Adım Çözüm

1
Analyze the write churn rates of each disk in the source environment.
The web VM has a single disk with 3 MB/s3\text{ MB/s} churn. The database VM has one disk with 12 MB/s12\text{ MB/s} churn and another with 25 MB/s25\text{ MB/s} churn.
Understanding the individual disk throughput requirements is necessary to verify compliance with Azure Site Recovery limits.
2
Compare disk churn rates against Azure Site Recovery (ASR) limits.
The web VM disk fits within standard and enhanced limits. However, the database log disk (25 MB/s25\text{ MB/s}) exceeds both the standard (10 MB/s10\text{ MB/s}) and enhanced/high-churn (20 MB/s20\text{ MB/s}) per-disk write churn limits of ASR.
Exceeding these limits causes replication lag, RPO violations, and replication health degradation.
3
Select alternative replication mechanisms for workloads exceeding ASR limits.
Use SQL Server Always On Availability Groups for the database tier to replicate data asynchronously to the target region, satisfying the 2-hour RPO. Use ASR for the web tier VM since its churn rate is well within supported limits.
This hybrid design ensures that database transaction logs are replicated natively without being blocked by ASR disk churn limits, while the web tier VM is replicated using ASR.

Anahtar Kavram

Azure Site Recovery limits require separating high-churn database workloads to native replication tools like SQL Server Always On Availability Groups when disk write churn exceeds supported limits.
Soru 648Soru

Your company has an Azure environment with a hub virtual network named `vnet-hub-prod` (10.10.0.0/1610.10.0.0/16) that contains a Virtual Network Gateway, and a spoke virtual network named `vnet-spoke-app` (10.20.0.0/1610.20.0.0/16). You configure Virtual Network Peering between `vnet-hub-prod` and `vnet-spoke-app`. You need to ensure that virtual machines in `vnet-spoke-app` can access your on-premises network through the gateway in `vnet-hub-prod`. Which two configuration settings should you select? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: On the peering configuration from vnet-hub-prod to vnet-spoke-app, select 'Use this virtual network's gateway or Route Server'.; On the peering configuration from vnet-spoke-app to vnet-hub-prod, select 'Use the remote virtual network's gateway or Route Server'.

Cevap

On the peering configuration from vnet-hub-prod to vnet-spoke-app, select 'Use this virtual network's gateway or Route Server', and on the peering configuration from vnet-spoke-app to vnet-hub-prod, select 'Use the remote virtual network's gateway or Route Server'.
To enable gateway transit in Azure Virtual Network Peering, you must configure both ends of the peering connection. In the hub virtual network (which contains the gateway), the peering to the spoke must be configured with 'Use this virtual network's gateway or Route Server' to allow the gateway to be shared. In the spoke virtual network, the peering to the hub must be configured with 'Use the remote virtual network's gateway or Route Server' to route outbound traffic through the remote gateway.

Adım Adım Çözüm

1
Configure the hub-to-spoke peering direction.
The peering configuration from vnet-hub-prod to vnet-spoke-app has 'Use this virtual network's gateway or Route Server' enabled.
This registers the hub's gateway as shareable with the peered spoke virtual network.
2
Configure the spoke-to-hub peering direction.
The peering configuration from vnet-spoke-app to vnet-hub-prod has 'Use the remote virtual network's gateway or Route Server' enabled.
This allows resources in the spoke virtual network to send traffic destined for on-premises through the hub's gateway.

Anahtar Kavram

Virtual Network Peering Gateway Transit allows peered virtual networks to share a VPN or ExpressRoute gateway, eliminating the need to deploy gateways in every spoke virtual network.
Tahmini Süre:1m 0s
Soru 649Soru

A telecommunications provider is designing an analytical data platform to process and query call detail record (CDR) log files. The platform must meet the following requirements:
- Ingest 50 GB50\text{ GB} of CDR files daily at a peak velocity of 200200 files per minute.
- Store the raw logs cost-effectively in Azure Data Lake Storage Gen2 (ADLS Gen2).
- Enable analysts to run ad-hoc, exploratory SQL queries directly on the raw files with a query latency of under 15 seconds15\text{ seconds}.
- Orchestrate a weekly batch transformation job that aggregates the CDR data, which typically takes 25 minutes25\text{ minutes} to run.
Which of the following Azure 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 Synapse serverless SQL pools to query the raw log files in Azure Data Lake Storage Gen2; Azure Data Factory pipelines to orchestrate the weekly batch transformation

Cevap

Azure Synapse serverless SQL pools to query the raw log files in Azure Data Lake Storage Gen2, and Azure Data Factory pipelines to orchestrate the weekly batch transformation
Azure Synapse serverless SQL pools are correct for ad-hoc exploratory queries because they allow querying unstructured or semi-structured data directly in Azure Data Lake Storage Gen2 using standard T-SQL without provisioning persistent resources. Azure Data Factory pipelines are correct for the weekly batch orchestration because they are built to manage complex data integration workflows with no runtime limits.

Adım Adım Çözüm

1
Analyze the requirement for ad-hoc, exploratory SQL queries on raw data stored in Azure Data Lake Storage Gen2 (ADLS Gen2).
Identify that Azure Synapse serverless SQL pools are designed specifically for querying files (such as CSV, JSON, Parquet) in place without needing to provision dedicated clusters, fitting the 1515-second latency and cost-effectiveness requirements.
Dedicated SQL pools require importing data into relational tables and provisioning continuous resources, which is inefficient for ad-hoc file exploration.
2
Analyze the requirement for orchestrating a weekly batch transformation job that takes 25 minutes25\text{ minutes} to run.
Select Azure Data Factory (or Synapse Pipelines) as the orchestration engine, which supports long-running batch workflows without execution time limitations.
Azure Functions on a Consumption plan has a 1010-minute execution limit, which would cause the 2525-minute run to time out.

Anahtar Kavram

Selecting appropriate Azure analytical and integration services based on query patterns, operational overhead, and execution limits
Soru 650Soru

An energy utility company is designing a smart grid monitoring platform on Azure. The system will ingest real-time telemetry from 10 million smart meters globally. The architecture has the following requirements:

* Raw telemetry payloads must be stored in an Azure Storage account. The storage account must survive a regional outage.
* A third-party auditing application must be granted temporary read-only access to the raw payloads for a maximum of 2 hours, with the ability to revoke access immediately if credentials are leaked.
* Metadata and event indexing records must be stored in Azure Cosmos DB for NoSQL. The database must sustain a write-heavy ingestion rate (90% writes, 10% reads) and achieve 99.999%99.999\% write availability.
* Telemetry records in Cosmos DB contain `meterId` (unique per meter), `readingDate` (daily format), `postalCode` (geographic region), and `usageValue`. Queries typically filter by `meterId` and `readingDate`.

You need to recommend the partition key for Azure Cosmos DB, the redundancy configuration for the storage account, and the security configuration for the auditing application.

Which combination should you recommend?

Cevabı ve açıklamayı göster

Cevap: Partition key: meterId; Storage redundancy: Geo-redundant storage (GRS); Security: A Service Shared Access Signature (SAS) associated with a Stored Access Policy configured for a 2-hour duration.

Cevap

Select meterId as the Cosmos DB partition key, configure the storage account with Geo-redundant storage (GRS), and use a Service Shared Access Signature (SAS) associated with a Stored Access Policy configured for 2 hours.
The correct recommendation is to use meterId as the Cosmos DB partition key, Geo-redundant storage (GRS) for storage account redundancy, and a Service SAS associated with a Stored Access Policy for temporary access. This combination successfully distributes Cosmos DB writes evenly across 10 million logical partitions, protects storage data against regional disaster, and provides revokable, limited-duration access to the auditing application.

Adım Adım Çözüm

1
Determine the Cosmos DB partition key to prevent hot partitions under heavy write ingestion.
Using meterId, which has high cardinality (10 million unique values), ensures even distribution of write and read requests across logical partitions.
Choosing low-cardinality keys like postalCode would group millions of devices into a small number of partitions, causing ingestion bottlenecks (hot partitions).
2
Select the storage redundancy tier that meets the regional resilience requirement.
Recommend Geo-redundant storage (GRS) or Read-access geo-redundant storage (RA-GRS).
Locally redundant storage (LRS) only replicates data within a single physical location and does not provide protection against regional outages.
3
Select the secure data access method for third-party auditing.
Recommend a Service SAS tied to a Stored Access Policy with a 2-hour validity window.
Tying the SAS to a Stored Access Policy allows revocation at any time by deleting or altering the policy. Using an ad-hoc SAS token with a long lifetime cannot be revoked without rotating storage account keys.

Anahtar Kavram

Azure Cosmos DB partition key selection, storage redundancy options for disaster recovery, and secure storage access management using SAS and Stored Access Policies.
Soru 651Soru

A digital banking platform is designing a storage solution for historical transaction records. The data will be stored in an Azure General Purpose v2 (GPv2) storage account. The platform's disaster recovery and high availability policies dictate the following constraints:

* The data must remain accessible even if a single datacenter in the primary region experiences a complete power outage.
* In the event of a major regional disaster affecting the primary region, the data must be recoverable in a secondary paired region.

Which two redundancy options satisfy these requirements? (Select two.)

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

Cevabı ve açıklamayı göster

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

Cevap

The correct options are geo-zone-redundant storage (GZRS) and read-access geo-zone-redundant storage (RA-GZRS).
The correct redundancy tiers are geo-zone-redundant storage (GZRS) and read-access geo-zone-redundant storage (RA-GZRS). Both options replicate data synchronously across three availability zones in the primary region, protecting against localized datacenter outages, and copy data asynchronously to a secondary region, protecting against regional disasters.

Adım Adım Çözüm

1
Determine the primary region resiliency requirement.
The storage solution must survive a localized datacenter outage in the primary region. This requires zone-redundant replication (ZRS, GZRS, or RA-GZRS) in the primary region.
Zone-redundancy replicates data across three physically separate availability zones within the primary region.
2
Determine the secondary region disaster recovery requirement.
The storage solution must support recovery in a secondary paired region in the event of a regional disaster. This requires geo-replication (GRS, GZRS, RA-GRS, or RA-GZRS).
Geo-replication copies data asynchronously to a secondary region to protect against regional outages.
3
Combine the requirements to identify the overlapping compliant redundancy tiers.
Only geo-zone-redundant storage (GZRS) and read-access geo-zone-redundant storage (RA-GZRS) satisfy both requirements.
Tiers like geo-redundant storage (GRS) fail the zone-redundant requirement in the primary region, while zone-redundant storage (ZRS) fails the geo-replication requirement.

Anahtar Kavram

Selecting Azure Storage redundancy tiers to meet combined local high availability (zonal) and disaster recovery (regional) objectives.
Soru 652Soru

A company has virtual machines (VMs) deployed in a subnet of an Azure virtual network. The VMs must securely access Azure Storage accounts. The design must block all general outbound internet traffic, prevent the need to manually update rules when Azure Storage IP addresses change, and minimize administrative overhead. Which two configurations should you include in the network security design?

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

Cevabı ve açıklamayı göster

Cevap: Configure an outbound Network Security Group (NSG) rule with the destination set to the Storage service tag.; Enable a virtual network service endpoint for Storage on the subnet.

Cevap

Configure an outbound Network Security Group (NSG) rule using the Storage service tag and enable a virtual network service endpoint for Storage on the subnet.
Configuring an outbound Network Security Group (NSG) rule with the Storage service tag allows traffic to reach Azure Storage without manual IP updates, and enabling a service endpoint on the subnet ensures that this traffic is routed privately over the Microsoft backbone network.

Adım Adım Çözüm

1
Determine the outbound traffic requirements for the virtual machines.
VMs must connect to Azure Storage, but general outbound internet traffic must be restricted.
This establishes the security boundaries for the subnet's egress traffic.
2
Select a method to manage IP address ranges dynamically for the destination rules.
Use the Storage service tag as the destination for the NSG outbound rule.
Service tags group IP address prefixes for Azure services, managed automatically by Microsoft to avoid manual rule maintenance.
3
Select a routing path that ensures private and secure access to Azure Storage.
Enable a virtual network service endpoint for Storage on the VM subnet.
Service endpoints route traffic directly over the Microsoft backbone network, providing private access without sending traffic to the public internet.

Anahtar Kavram

Network Security and Private Access using Service Tags and Service Endpoints
Soru 653Soru

An enterprise is designing a subscription governance model to manage resources across multiple departments. You need to implement a management group hierarchy and delegate resource access using a custom Azure RBAC role. The solution must ensure that administrative access is inherited across all department subscriptions and adheres to the principle of least privilege.

Which sequence of steps should you perform?

Öğeleri doğru sıraya koymak için sürükleyin

Cevabı ve açıklamayı göster

Cevap

The correct sequence is to first create the management group hierarchy, associate the departmental subscriptions with their designated management groups, define and create the custom Azure RBAC role specifying the management group paths in the AssignableScopes, create Microsoft Entra ID security groups for the administrative roles, and finally create the role assignments mapping the security groups to the custom role at the management group scope.
Establishing governance begins with defining the resource hierarchy (management groups) and placing subscriptions within that hierarchy. Once the hierarchy is established, the custom role definition is created with AssignableScopes set to the management groups. Then, Microsoft Entra ID security groups are created to hold users, and finally, the custom role is assigned to the security groups at the management group scope to enable inheritance.

Adım Adım Çözüm

1
Create the management group hierarchy.
Management groups are available in the tenant.
Establishing the management group structure is required before configuring assignable scopes or assigning permissions at these scopes.
2
Associate subscriptions with the management groups.
Subscriptions are organized under their respective management groups.
This enables inheritance of access controls and policies from the parent management groups down to the subscriptions.
3
Define and create the custom Azure RBAC role.
The custom RBAC role is registered and available for assignment.
The custom role's AssignableScopes must reference the existing management group resource IDs, so the hierarchy must exist first.
4
Create Microsoft Entra ID security groups.
Security groups representing operational roles are populated with users.
Assigning roles to security groups rather than individual users aligns with the principle of least privilege and simplifies management.
5
Assign the custom RBAC role to the security groups.
Role assignments are created at the management group scope.
This completes the delegation of access, ensuring users in the groups inherit the necessary permissions across all subscriptions in the management group.

Anahtar Kavram

Azure Management Groups allow logical grouping of subscriptions to apply access control, policies, and compliance settings. Custom RBAC roles require an AssignableScopes property that limits where the role can be assigned, and permissions are inherited from parent scopes (Management Groups) to child scopes (Subscriptions, Resource Groups, and Resources).
Soru 654Soru

A healthcare provider is designing a container-based claims processing application on Azure. The application has the following design requirements:

* A REST API microservice must receive claims and scale out rapidly during peak business hours, and scale down to zero instances during periods of inactivity.
* A background reporting workload must execute containerized jobs that process large datasets on a scheduled basis, with each job taking up to 45 minutes to complete.
* The overall solution must minimize administrative and infrastructure management overhead.

Which two Azure container hosting solutions should you recommend to meet these requirements? (Choose two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps to host the REST API microservice; Azure Container Apps jobs to host the background reporting workload

Cevap

Azure Container Apps to host the REST API microservice, and Azure Container Apps jobs to host the background reporting workload.
Azure Container Apps is the optimal solution for both requirements. For the REST API microservice, Azure Container Apps provides serverless HTTP-based scaling, including scaling to zero when there is no traffic, while minimizing management overhead. For the background reporting workload, Azure Container Apps jobs are designed specifically for executing run-to-completion tasks that can run for up to 24 hours, meeting the 45-minute requirement without infrastructure management overhead.

Adım Adım Çözüm

1
Evaluate the administrative overhead requirement.
Identify that Azure Kubernetes Service (AKS) introduces significant infrastructure management and platform overhead, making serverless options like Azure Container Apps more appropriate when Kubernetes API access is not explicitly required.
The scenario requires minimizing administrative and infrastructure management overhead.
2
Analyze the scaling and traffic patterns of the REST API microservice.
Determine that the REST API requires dynamic scaling based on HTTP requests, including scaling to zero. Azure Container Apps supports this natively out of the box.
Azure Container Instances does not offer built-in HTTP autoscaling to zero without external components.
3
Analyze the runtime requirements of the background reporting workload.
Identify that the background task is a containerized run-to-completion job that runs for up to 45 minutes. Azure Container Apps jobs support tasks running for up to 24 hours.
Azure Container Apps jobs are optimized for run-to-completion tasks, whereas standard Azure Container Apps are meant for continuously running services.

Anahtar Kavram

Selecting Azure container hosting solutions based on operational overhead, execution duration, and scaling requirements.
Soru 655Soru

An enterprise is designing a serverless and containerized architecture for a financial reconciliation platform. The system requires hosting two workloads with distinct execution behaviors and networking constraints:

* Workload 1: An API gateway helper that intercepts and validates inbound transactions. It experiences unpredictable, highly spiked traffic (from 0 to thousands of concurrent requests) with long periods of complete inactivity. To access protected on-premises ledger databases, this workload requires integration with an Azure Virtual Network (VNet). Minimizing idle infrastructure costs is critical.
* Workload 2: A batch reconciliation job that runs once daily. The job retrieves transaction logs, executes complex audit rules, and typically runs for 40 minutes. It must also run within a private subnet to securely communicate with back-end databases, and the team wants to minimize operational overhead.

Which two of the following Azure compute solutions should you recommend to support these workloads? (Select TWO.)

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

Cevabı ve açıklamayı göster

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

Cevap

Azure Functions on a Flex Consumption plan to host the API gateway helper (Workload 1), and Azure Container Apps Jobs to host the daily batch reconciliation job (Workload 2).
The correct solution involves selecting Azure Functions on a Flex Consumption plan for the API endpoint and Azure Container Apps Jobs for the batch reconciliation job. The Flex Consumption plan supports virtual network integration while allowing the application to scale to zero instances during idle periods, satisfying the cost and network security requirements. Azure Container Apps Jobs are designed for run-to-completion workloads, support virtual network integration, can run for up to several hours, and avoid the management overhead associated with Kubernetes clusters.

Adım Adım Çözüm

1
Analyze the requirements for Workload 1.
Workload 1 requires virtual network integration, rapid scaling under unpredictable traffic spikes, and scale-to-zero capability to minimize costs during idle periods.
Identifying these key constraints narrows down the options to plans that support virtual network integration without requiring an always-on instance.
2
Evaluate compute candidates for Workload 1.
The Flex Consumption plan satisfies virtual network integration, rapid scale-out, and scales to zero. The Premium plan and Dedicated App Service plans fail the scale-to-zero cost requirement because they charge for a minimum of one running instance.
Matching constraints to Azure compute plans ensures the most cost-effective and compliant serverless host is chosen.
3
Analyze the requirements for Workload 2.
Workload 2 requires running a batch job for 40 minutes inside a private subnet while minimizing operational overhead.
This workload has a long-running execution requirement that exceeds standard serverless timeout limits, and a preference for low operational complexity.
4
Evaluate compute candidates for Workload 2.
Azure Container Apps Jobs support runs of up to several hours, run in a private subnet, scale to zero, and have low overhead. Standard Consumption Functions fail due to a 10-minute timeout. Azure Kubernetes Service (AKS) succeeds technically but introduces high operational overhead.
This step eliminates options that either fail due to execution limits or introduce excessive operational and financial overhead.

Anahtar Kavram

Azure serverless compute selection based on execution limits, virtual network integration, scaling behavior, and operational overhead.
Tahmini Süre:3m 0s
Soru 656Soru

A global maritime logistics enterprise is designing a disaster recovery (DR) solution to replicate workloads from Azure North Europe to West Europe. The tracking architecture consists of two main virtual machines:

- `vm-track1`: Hosts the cargo tracking API and contains a Standard SSD OS disk with a write churn of 1 MB/s1\text{ MB/s} and a Premium SSD data disk with a write churn of 8 MB/s8\text{ MB/s} (total VM churn of 9 MB/s9\text{ MB/s}).
- `vm-db1`: Hosts a high-transaction PostgreSQL database and contains a Premium SSD OS disk with a write churn of 2 MB/s2\text{ MB/s} and two Premium SSD data disks: Data Disk 1 with a write churn of 15 MB/s15\text{ MB/s} and Data Disk 2 with a write churn of 22 MB/s22\text{ MB/s} (total VM churn of 39 MB/s39\text{ MB/s}).

The DR solution must guarantee a Recovery Point Objective (RPO) of 10 minutes10\text{ minutes} and a Recovery Time Objective (RTO) of 1 hour1\text{ hour} for both workloads.

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

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

Cevabı ve açıklamayı göster

Cevap: Replicate vm-track1 to the target region using Azure Site Recovery.; Implement native PostgreSQL streaming replication from vm-db1 to a standby instance in the target region.

Cevap

Replicate vm-track1 to the target region using Azure Site Recovery, and implement native PostgreSQL streaming replication from vm-db1 to a standby instance in the target region.
The correct design uses Azure Site Recovery to replicate vm-track1 because its write churn (8 MB/s8\text{ MB/s} on the data disk) is below the 10 MB/s10\text{ MB/s} standard disk replication limit. For vm-db1, because Data Disk 2 experiences a write churn of 22 MB/s22\text{ MB/s} (which exceeds the maximum ASR high-churn support limit of 20 MB/s20\text{ MB/s} per disk), Azure Site Recovery cannot be used. Instead, native PostgreSQL streaming replication must be implemented to replicate the database to the target region while meeting the 10 minutes10\text{ minutes} RPO requirement.

Adım Adım Çözüm

1
Analyze the write churn metrics for vm-track1.
The Standard SSD OS disk has a write churn of 1 MB/s1\text{ MB/s}, and the Premium SSD data disk has a write churn of 8 MB/s8\text{ MB/s}, with a total VM churn of 9 MB/s9\text{ MB/s}.
To determine if Azure Site Recovery (ASR) can support replication, as the standard limits are 10 MB/s10\text{ MB/s} per disk and 40 MB/s40\text{ MB/s} per VM, which vm-track1 satisfies.
2
Analyze the write churn metrics for vm-db1.
The Premium SSD OS disk has a write churn of 2 MB/s2\text{ MB/s}, Data Disk 1 has 15 MB/s15\text{ MB/s}, and Data Disk 2 has 22 MB/s22\text{ MB/s}, with a total VM churn of 39 MB/s39\text{ MB/s}.
To verify if ASR can support replication. While the total VM churn (39 MB/s39\text{ MB/s}) is within the high-churn VM support limits, Data Disk 2's churn (22 MB/s22\text{ MB/s}) exceeds the maximum ASR high-churn limit of 20 MB/s20\text{ MB/s} per disk.
3
Select the replication mechanism for both virtual machines based on churn and RPO/RTO requirements.
Replicate vm-track1 via ASR. For vm-db1, since ASR cannot support the disk churn, native database-level replication (such as PostgreSQL streaming replication) must be used to meet the 10 minutes10\text{ minutes} RPO.
Azure Backup cross-region restore is unsuitable as its replication and restore times cannot guarantee a 10 minutes10\text{ minutes} RPO and 1 hour1\text{ hour} RTO.

Anahtar Kavram

Azure Site Recovery limits and native database replication for high write churn workloads.
Soru 657Soru

An enterprise is designing a hub-and-spoke virtual network topology in Azure. The hub virtual network, `vnet-hub-core` (10.10.0.0/1610.10.0.0/16), hosts an Azure Firewall at 10.10.4.410.10.4.4 and an ExpressRoute Virtual Network Gateway. The ExpressRoute gateway connects to the on-premises network (192.168.0.0/16192.168.0.0/16) and receives a default route (0.0.0.0/00.0.0.0/0) via BGP to force-tunnel all internet traffic to the on-premises security appliance. A spoke virtual network, `vnet-prod-spoke` (10.20.0.0/1610.20.0.0/16), hosts a web application in `snet-web` (10.20.1.0/2410.20.1.0/24) and a database in `snet-db` (10.20.2.0/2410.20.2.0/24). You need to design a routing solution for `snet-web` to meet the following requirements:
- All traffic to other spoke virtual networks (which use the 10.0.0.0/810.0.0.0/8 address space) and the on-premises network must be routed through the Azure Firewall.
- Web servers in `snet-web` must communicate directly with the database in `snet-db` without passing through the Azure Firewall to minimize latency.
- All internet-bound traffic must be forced to the on-premises network via the ExpressRoute gateway.

Which route table configuration should you associate with `snet-web`?

Cevabı ve açıklamayı göster

Cevap: Associate a route table with gateway route propagation enabled. Add user-defined routes (UDRs) for 10.0.0.0/810.0.0.0/8 and 192.168.0.0/16192.168.0.0/16 with a next hop of Virtual Appliance pointing to the Azure Firewall (10.10.4.410.10.4.4).

Cevap

Associate a route table with gateway route propagation enabled. Add user-defined routes (UDRs) for 10.0.0.0/810.0.0.0/8 and 192.168.0.0/16192.168.0.0/16 with a next hop of Virtual Appliance pointing to the Azure Firewall (10.10.4.410.10.4.4).
The correct configuration uses gateway route propagation to allow the subnet to dynamically learn the default route (0.0.0.0/00.0.0.0/0) advertised by the ExpressRoute gateway from on-premises, satisfying the forced tunneling requirement. By adding UDRs for 10.0.0.0/810.0.0.0/8 and 192.168.0.0/16192.168.0.0/16 pointing to the Azure Firewall, spoke-to-spoke and on-premises traffic is properly redirected for security inspection. Lastly, because Azure prioritizes routes using Longest Prefix Match (LPM), traffic destined for the database subnet (10.20.2.0/2410.20.2.0/24) will match the local VNet system route (10.20.0.0/1610.20.0.0/16) rather than the broader UDR (10.0.0.0/810.0.0.0/8), ensuring direct local communication without traversing the firewall.

Adım Adım Çözüm

1
Evaluate the propagation of the default route.
Gateway route propagation must be enabled on the route table so that the subnet learns the BGP route 0.0.0.0/00.0.0.0/0 from the ExpressRoute Virtual Network Gateway.
This allows internet-bound traffic to be automatically routed to the ExpressRoute gateway for on-premises forced tunneling without needing a manual UDR.
2
Determine how to route spoke-to-spoke and on-premises traffic to the firewall.
Add user-defined routes (UDRs) for 10.0.0.0/810.0.0.0/8 and 192.168.0.0/16192.168.0.0/16 with the next hop set to the Azure Firewall IP (10.10.4.410.10.4.4).
This satisfies the security requirement to inspect all cross-virtual network and on-premises traffic using the hub firewall.
3
Analyze local virtual network routing under Longest Prefix Match (LPM) rules.
For traffic destined to 10.20.2.0/2410.20.2.0/24 (`snet-db`), Azure compares the system route 10.20.0.0/1610.20.0.0/16 (Virtual Network) and the UDR 10.0.0.0/810.0.0.0/8 (Virtual Appliance). Since 10.20.0.0/1610.20.0.0/16 is the longer prefix match, traffic is routed locally.
This ensures that traffic within the local VNet (`vnet-prod-spoke`) bypasses the firewall and maintains direct communication to minimize latency.

Anahtar Kavram

Azure Virtual Network routing priorities, specifically the interaction between User-Defined Routes (UDRs), BGP-propagated routes, and local VNet system routes using Longest Prefix Match (LPM).
Soru 658Soru

A company is designing a data storage solution for a medical telemetry application. The application writes telemetry logs directly to an Azure Blob Storage General Purpose v2 (GPv2) account.

The logs must be managed according to the following requirements:
- For the first 3030 days after creation, logs must be immediately readable with sub-second latency to support real-time dashboards.
- Between day 3131 and day 9090, logs are rarely accessed but must remain online and readable within 1010 minutes for ad-hoc audit queries.
- After 9090 days, logs must be retained for compliance for a total of 33 years (1,0951,095 days) from creation. A retrieval latency of up to 1515 hours is acceptable for compliance queries.
- The lifecycle management strategy must minimize total storage costs.

You need to design a lifecycle management policy that meets these requirements while avoiding early deletion charges. Which lifecycle action sequence should you recommend?

Cevabı ve açıklamayı göster

Cevap: Transition blobs to the Cool tier after 3030 days, transition blobs to the Archive tier after 9090 days, and delete blobs after 1,0951,095 days.

Cevap

Transition blobs to the Cool tier after 3030 days, transition blobs to the Archive tier after 9090 days, and delete blobs after 1,0951,095 days.
The correct recommendation is to transition blobs to the Cool tier after 3030 days, then to the Archive tier after 9090 days, and delete them after 1,0951,095 days. The Cool tier satisfies the 1010-minute query latency constraint because it is an online tier. Since the blobs stay in the Cool tier for 6060 days (from day 3030 to day 9090), they exceed the Cool tier's 3030-day minimum retention period, preventing early deletion charges. Transitioning to the Archive tier at day 9090 minimizes cost for the long-term retention period, and because the blobs reside in Archive for 1,0051,005 days, they exceed the Archive tier's 180180-day minimum retention period, meaning no early deletion charges are applied when deleted at day 1,0951,095.

Adım Adım Çözüm

1
Analyze access latency constraints for each time window.
Day 00 to 3030 requires sub-second latency (Hot tier). Day 3131 to 9090 requires queries within 1010 minutes, requiring an online tier (Cool or Cold). Day 9191 to 10951095 allows up to 1515 hours latency, allowing the Archive tier.
Filter out tiers that cannot meet the performance SLAs of each phase.
2
Calculate the duration of the intermediate phase and evaluate early deletion penalties.
The intermediate phase lasts 6060 days (9030=6090 - 30 = 60). The Cool tier has a 3030-day minimum retention, so 6060 days meets this threshold. The Cold tier has a 9090-day minimum retention, so transitioning after 6060 days would trigger a 3030-day early deletion penalty.
Choose the most cost-effective tier for the intermediate phase while avoiding extra fees.
3
Determine the long-term compliance storage tier and calculate its duration.
Moving to the Archive tier at day 9090 minimizes storage cost. The blobs spend 1,0051,005 days (109590=10051095 - 90 = 1005) in Archive. This exceeds the Archive 180180-day minimum retention threshold, ensuring no early deletion fee applies at the deletion point.
Verify that final deletion does not trigger compliance or retention penalties.

Anahtar Kavram

Azure Blob Storage Lifecycle Management Tiers and Minimum Retention Constraints
Soru 659Soru

You are designing a network security solution for an Azure virtual network. A subnet named Subnet1 contains 30 Azure virtual machines that need to retrieve cryptographic keys from Azure Key Vault. You must allow these virtual machines to make outbound connections to Azure Key Vault while blocking all other outbound access to the public internet. The solution must minimize the administrative effort required to maintain network security rules. Which of the following should you recommend including in the design?

Cevabı ve açıklamayı göster

Cevap: A Network Security Group (NSG) associated with Subnet1 that contains an outbound security rule allowing traffic where the destination is the AzureKeyVault service tag, followed by an outbound rule blocking all traffic to the Internet service tag.

Cevap

A Network Security Group (NSG) associated with Subnet1 that contains an outbound security rule allowing traffic where the destination is the AzureKeyVault service tag, followed by an outbound rule blocking all traffic to the Internet service tag.
The correct option recommends using a Network Security Group (NSG) with the built-in AzureKeyVault service tag to allow traffic to Azure Key Vault, followed by a rule blocking traffic to the Internet service tag. Service tags simplify NSG rule creation and maintenance by representing a group of IP address prefixes from a given Azure service. Azure manages the address prefixes encompassed by the service tag and automatically updates the service tag as addresses change, satisfying the constraint to minimize administrative effort.

Adım Adım Çözüm

1
Identify the destination service that the virtual machines need to communicate with, which is Azure Key Vault.
Determine that Azure Key Vault has a built-in Service Tag named AzureKeyVault.
Using service tags avoids the need to maintain static IP address lists, reducing administrative overhead.
2
Determine the rule hierarchy needed to permit the desired traffic while blocking all other outbound internet traffic.
Create an allow rule for the AzureKeyVault service tag and a deny rule for the Internet service tag with a lower priority.
NSG rules are processed in priority order, so the allow rule must be evaluated before the broader block rule.
3
Associate the configured NSG with Subnet1.
The network security rules are applied to all virtual machines within Subnet1.
Associating the NSG at the subnet level ensures uniform security policy application.

Anahtar Kavram

Azure Network Security Group Service Tags
Soru 660Soru

Match each traffic routing and failover requirement with the most appropriate Azure load balancing or traffic routing service configuration. Each service configuration may be used once, more than once, or not at all.

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

Öğeler

A global web application requires SSL offloading at the network edge, URL-path-based routing, and instant failover between active-active regions using Anycast IPv4/IPv6 addresses.
A business-critical database service requires global routing of SQL Server TCP traffic on port 1433, using Anycast IP addresses to onboard client traffic onto the Microsoft backbone at the nearest point of presence.
A legacy enterprise system running a proprietary TCP service on port 8080 requires global failover between an on-premises environment and an Azure region, utilizing DNS-based routing.
A web application hosted in a single Azure region requires internal load balancing across multiple Virtual Machine Scale Sets based on path rules, along with cookie-based session affinity.

Eşleşmeler

Cevabı ve açıklamayı göster

Cevap

Matching pairs: 1) Global web app with SSL offload/Anycast matches Azure Front Door; 2) SQL Server TCP 1433 over Anycast matches Azure Cross-Region Load Balancer; 3) Legacy TCP 8080 with DNS-based hybrid failover matches Azure Traffic Manager; 4) Single-region path-routing with cookie affinity matches Azure Application Gateway.
Each workload's requirement maps to the specific capabilities of Azure's load balancing services: Azure Front Door for global HTTP/HTTPS with Anycast and WAF; Azure Cross-Region Load Balancer for global TCP/UDP with Anycast; Azure Traffic Manager for DNS-based hybrid/custom TCP routing; and Azure Application Gateway for regional L7 routing with session affinity.

Adım Adım Çözüm

1
Analyze the network protocols and regional scopes of each scenario.
Identify that two scenarios require global Layer 7 routing (HTTP/HTTPS), one requires global Layer 4 routing (TCP 1433), one requires custom TCP on port 8080 across hybrid environments, and one requires regional Layer 7 routing.
This categorizes the candidate Azure routing services into L4 vs L7, and regional vs global.
2
Differentiate between global Layer 7 options based on performance and protocol constraints.
Map the global HTTPS scenario with WAF and SSL offloading to Azure Front Door, and the regional HTTPS scenario with session affinity to Azure Application Gateway.
Azure Front Door provides global Anycast-based routing, while Azure Application Gateway provides regional-only load balancing features.
3
Differentiate between global Layer 4 options and hybrid/custom port options.
Map the SQL Server TCP port 1433 Anycast requirement to Azure Cross-Region Load Balancer, and the legacy hybrid TCP port 8080 DNS-based requirement to Azure Traffic Manager.
Cross-Region Load Balancer provides Layer 4 Anycast routing, whereas Traffic Manager operates via DNS and supports external/on-premises endpoints for any custom port.

Anahtar Kavram

Design Traffic Routing and Failover Strategies
ÖncekiSayfa 33 / 60Sonraki
Tüm alıştırma soruları — Microsoft Azure Solutions Architect (AZ-305) | Examkin