Tüm alıştırma soruları

1198 soru

Soru 941Soru

An enterprise is designing a data storage solution on Azure Blob Storage for an application that processes transactional logs. The storage requirements are as follows:

* Newly generated logs are accessed frequently for the first 30 days, and queries require sub-second retrieval times.
* Logs between 31 and 90 days old are accessed occasionally for monthly reports, and must also be available with sub-second retrieval times.
* Logs older than 90 days are rarely accessed but must be retained for 5 years to comply with regulatory audits. For these audits, a retrieval latency of up to 15 hours is acceptable.
* Storage costs must be minimized, and early deletion charges must be avoided.

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

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

Cevabı ve açıklamayı göster

Cevap: Transition blobs to the cool tier 30 days after creation.; Transition blobs to the archive tier 90 days after creation.

Cevap

Transition blobs to the cool tier 30 days after creation, and transition blobs to the archive tier 90 days after creation.
The correct strategy transitions the blobs to the cool tier after 30 days and to the archive tier after 90 days. This satisfies the sub-second retrieval requirement for the first 90 days (via hot and cool tiers) and complies with the 5-year retention requirement via the archive tier. Since the blobs spend 60 days in the cool tier (from day 30 to day 90), they exceed the cool tier's 30-day minimum retention threshold, preventing early deletion fees.

Adım Adım Çözüm

1
Analyze access frequency and latency requirements for each phase of the lifecycle.
Days 0-30 require Hot (frequent, sub-second). Days 31-90 require Cool or Cold (occasional, sub-second). Days 91+ require Archive (rare, high latency up to 15 hours).
This establishes the candidate storage tiers for each phase.
2
Evaluate minimum retention periods to prevent early deletion charges during transitions.
Transitioning from Hot to Cold at day 30, and then to Archive at day 90, keeps data in the Cold tier for only 60 days. This violates the 90-day minimum retention limit for the Cold tier, triggering charges. Transitioning to Cool at day 30 and then to Archive at day 90 keeps data in the Cool tier for 60 days, which safely exceeds the 30-day minimum retention for Cool.
This determines whether the Cool or Cold tier is appropriate for the middle phase.
3
Verify Archive tier compliance and duration.
Transitioning to the Archive tier at day 90 meets the 15-hour retrieval latency constraint via standard rehydration. The data remains in the Archive tier for approximately 5 years, which easily satisfies the 180-day minimum retention requirement for the Archive tier.
This ensures the final archiving step is cost-effective and compliant.

Anahtar Kavram

Azure Blob Storage lifecycle management tiers and minimum retention limits.
Soru 942Soru

You are designing the compute infrastructure for a critical real-time logistics routing application in Azure.

The solution must meet the following requirements:
- The compute tier must achieve an uptime Service Level Agreement (SLA) of 99.99%99.99\%.
- The tier must support a mix of standard CPU-optimized Virtual Machines (VMs) for routing calculations and GPU-enabled VMs for machine learning models within the same logical group.
- The compute instances must support auto-scaling and rolling upgrades.
- VMs that collaborate on a specific regional route calculation must have network latency of less than 1 ms1\text{ ms} between each other.

Which compute configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: A Virtual Machine Scale Set in Flexible orchestration mode distributed across multiple Availability Zones, with a Proximity Placement Group created and assigned for each individual Availability Zone.

Cevap

A Virtual Machine Scale Set in Flexible orchestration mode distributed across multiple Availability Zones, with a Proximity Placement Group created and assigned for each individual Availability Zone.
To achieve a 99.99%99.99\% uptime SLA, virtual machines must be deployed across multiple Availability Zones. To support heterogeneous VM sizes (mixing CPU-optimized and GPU-enabled instances) along with auto-scaling and rolling upgrades, a Virtual Machine Scale Set in Flexible orchestration mode is required. Finally, to ensure low-latency communication (less than 1 ms1\text{ ms}) within each zone without causing deployment failures or routing latency across zones, you must create and assign a Proximity Placement Group (PPG) for each individual Availability Zone.

Adım Adım Çözüm

1
Evaluate the uptime SLA requirement.
To meet the 99.99%99.99\% SLA requirement, the Virtual Machines must be deployed across at least two Availability Zones in an Azure region.
Azure offers a 99.99%99.99\% SLA for VM uptime only when two or more instances are deployed across two or more Availability Zones.
2
Evaluate the VM grouping and scale requirements.
A Virtual Machine Scale Set in Flexible orchestration mode must be chosen.
Flexible orchestration mode allows mixing multiple VM families (heterogeneous sizes like CPU-optimized and GPU-enabled) in the same scale set while supporting auto-scaling and rolling upgrades.
3
Address the low-latency placement requirement across multiple zones.
Create a separate Proximity Placement Group (PPG) for each Availability Zone and associate them with the VMs in those zones.
A single PPG cannot span multiple Availability Zones without either causing deployment allocation failures or failing the low-latency requirement because zones are physically separated. A PPG per zone ensures intra-zone low latency while preserving cross-zone high availability.

Anahtar Kavram

Designing compute high availability using Virtual Machine Scale Sets in Flexible orchestration mode across Availability Zones combined with Proximity Placement Groups.
Tahmini Süre:2m 30s
Soru 943Soru

An organization named AeroQuest Logistics uses an Azure Storage account configured with Read-access geo-redundant storage (RA-GRS) to store critical transit logs. The primary region hosting the storage account experiences a prolonged regional outage. The logistics application needs to resume write operations as quickly as possible. Which action should you recommend?

Cevabı ve açıklamayı göster

Cevap: Initiate a customer-managed failover of the storage account to promote the secondary endpoint to the new primary endpoint.

Cevap

Initiate a customer-managed failover of the storage account to promote the secondary endpoint to the new primary endpoint.
Initiating a customer-managed failover updates the DNS records of the storage account, promoting the secondary endpoint to the new primary endpoint. This action restores both read and write capabilities, switching the replication to Locally redundant storage (LRS).

Adım Adım Çözüm

1
Evaluate the current storage configuration and availability.
The storage account is configured as RA-GRS, meaning read access is available in the secondary region, but write access is restricted to the primary region.
Identify the limitations of the current replication state during a primary region outage.
2
Determine the mechanism to restore write availability.
Promoting the secondary region to become the new primary region through a customer-managed failover is required to enable write access.
Failover updates the DNS endpoints, converting the secondary endpoint to the primary, which allows both read and write operations.
3
Select the correct action that supports the failover.
Initiating a customer-managed failover is the only native way to restore writes on the storage account in the secondary region.
This updates the storage account's DNS records so that the secondary endpoint is promoted to the primary endpoint.

Anahtar Kavram

Customer-managed failover for Azure Storage accounts (GRS/RA-GRS) promotes the secondary endpoint to the primary endpoint to restore write access during a primary region outage.
Soru 944Soru

A financial services company is designing a new cloud-native application on Azure. The application will consist of several containerized microservices that process transactions.

The design requirements are as follows:
* The microservices must scale dynamically based on the number of messages in an Azure Service Bus queue using Kubernetes Event-driven Autoscaling (KEDA).
* Administrative effort for infrastructure management, such as cluster upgrades and node patching, must be minimized.
* The application does not require direct access to the Kubernetes API or custom resource definitions (CRDs).
* The application must be deployed across two different Azure regions to comply with strict regional data sovereignty laws. Log data originating from each region must be kept isolated and accessible only within that region.

You need to recommend a solution that meets the requirements.

Which solution should you recommend?

Cevabı ve açıklamayı göster

Cevap: Deploy the microservices to Azure Container Apps (ACA) in each region. Configure a separate Log Analytics workspace in each region.

Cevap

Deploy the microservices to Azure Container Apps (ACA) in each region and configure a separate Log Analytics workspace in each region.
The correct solution uses Azure Container Apps (ACA) combined with separate regional Log Analytics workspaces. Azure Container Apps is a serverless container hosting platform that supports event-driven autoscaling using KEDA natively. Because the workload does not require custom Kubernetes API access, choosing ACA minimizes the administrative overhead of managing underlying nodes and cluster configurations. Configuring separate Log Analytics workspaces in each region ensures logs originating from those regions are isolated, adhering to the data sovereignty rules.

Adım Adım Çözüm

1
Analyze compute requirements to select between Azure Kubernetes Service (AKS) and Azure Container Apps (ACA).
Azure Container Apps is chosen because the application requires KEDA scaling, requires no custom Kubernetes API access, and has a strict requirement to minimize infrastructure administration effort.
AKS requires administrative effort for node configuration, cluster upgrades, and patching, which is unnecessary for this microservices application.
2
Analyze compliance requirements for logging and data residency.
Separate Log Analytics workspaces must be deployed in each region.
Data sovereignty laws require that logs from each region remain isolated and accessible only within their respective regions, preventing the use of a single centralized workspace.
3
Combine compute and logging selections to identify the correct architecture.
The final recommendation is Azure Container Apps paired with separate regional Log Analytics workspaces.
This configuration meets all constraints regarding scaling, administrative overhead minimization, and regional log isolation.

Anahtar Kavram

Selecting container hosting options based on administrative effort constraints, KEDA integration, and logging isolation compliance.
Soru 945Soru

An automotive manufacturing company runs a critical assembly line coordination system on Azure virtual machines in the UK South region. The system consists of two tiers:
1. An application tier with three stateless web servers (`VM-App1`, `VM-App2`, and `VM-App3`).
2. A database tier running SQL Server on a virtual machine (`VM-DB1`).

The data and log disks on `VM-DB1` have a combined write churn of 75 MB/s75\text{ MB/s}, with the transaction log disk alone reaching a continuous write churn of 60 MB/s60\text{ MB/s}. The business requires a Recovery Point Objective (RPO) of 1515 minutes and a Recovery Time Objective (RTO) of 22 hours for the entire system.

Which disaster recovery strategy should you recommend to meet the requirements?

Cevabı ve açıklamayı göster

Cevap: Replicate the application tier virtual machines using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the database to the target region.

Cevap

Replicate the application tier virtual machines using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the database to the target region.
The correct strategy uses Azure Site Recovery for the application tier virtual machines, which fall well within supported limits, and SQL Server Always On Availability Groups for the database tier. Azure Site Recovery enforces a maximum write churn limit of 54 MB/s54\text{ MB/s} per disk for Premium SSDs under the high-churn replication policy. Because the database transaction log disk has a continuous write churn of 60 MB/s60\text{ MB/s}, block-level replication via Azure Site Recovery will fail. Using SQL Server Always On Availability Groups provides database-level replication that bypasses these storage-tier limits while meeting the 1515-minute RPO and 22-hour RTO.

Adım Adım Çözüm

1
Evaluate the write churn requirements of the database tier virtual machine against Azure Site Recovery limits.
The database transaction log disk has a continuous write churn of 60 MB/s60\text{ MB/s}, which exceeds the maximum supported limit of 54 MB/s54\text{ MB/s} per disk for Azure Site Recovery (even with the high-churn replication policy enabled).
This establishes that the database virtual machine cannot be replicated as-is using Azure Site Recovery block-level replication.
2
Determine the optimal disaster recovery mechanism for the SQL Server database tier.
SQL Server Always On Availability Groups replicates database transactions directly at the SQL application layer, bypassing Azure Site Recovery block-level disk limits, and satisfies the near-zero data loss (RPO) and fast failover (RTO) requirements.
To select a replication technology that natively supports high-churn database workloads and meets the strict RTO and RPO requirements.
3
Determine the optimal disaster recovery mechanism for the stateless web application tier.
The application tier VMs (`VM-App1`, `VM-App2`, and `VM-App3`) are stateless and have low write churn, making them ideal candidates for standard Azure Site Recovery replication.
To minimize replication cost and administrative overhead for non-database workloads while securing VM orchestration and failover capabilities.

Anahtar Kavram

Disaster recovery design involving mixed workloads with high write churn that exceed Azure Site Recovery limits.
Tahmini Süre:2m 0s
Soru 946Soru

A financial software company is migrating an on-premises document management system to Azure. The system requires a shared file storage solution accessible over SMB that can support an active-active configuration across multiple compute instances. The solution must guarantee single-digit millisecond latency for file operations and must survive the failure of an entire datacenter in the primary region without any data loss or application downtime. Which storage tier and redundancy option should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Premium Azure Files configured with Zone-Redundant Storage (ZRS)

Cevap

Premium Azure Files configured with Zone-Redundant Storage (ZRS)
The correct answer is Premium Azure Files configured with Zone-Redundant Storage (ZRS). Premium Azure Files is backed by SSDs to guarantee the required single-digit millisecond latency. Configuring it with ZRS ensures data is replicated synchronously across three availability zones, allowing it to survive a datacenter failure in the primary region without downtime or data loss.

Adım Adım Çözüm

1
Identify the protocol and latency requirements
The application requires an SMB-compatible shared file system with single-digit millisecond latency, which dictates the use of the Premium tier of Azure Files (backed by SSDs).
Standard Azure Files uses HDD storage and does not guarantee the low latency required for metadata and file operations.
2
Identify the high availability and disaster resilience requirements
The storage must survive the failure of an entire datacenter in the primary region, pointing to Zone-Redundant Storage (ZRS).
ZRS replicates data synchronously across three physical facilities (Availability Zones) in the region.
3
Verify storage account and tier limitations
Confirm that Premium Azure Files supports ZRS but does not support GRS.
Premium file shares are deployed in FileStorage accounts, which only support LRS and ZRS redundancy options.

Anahtar Kavram

Premium Azure Files supports only LRS and ZRS configurations, and ZRS must be chosen to satisfy both low-latency performance and zone-outage resilience.
Soru 947Soru

An organization is designing a high-availability compute infrastructure for a mission-critical financial transactions processing application in Azure. The compute tier will run on Azure Virtual Machines.

The solution must meet the following requirements:
- Provide a virtual machine uptime SLA of at least 99.99%99.99\%.
- Support automatic scaling of the compute tier using Virtual Machine Scale Sets (VMSS) with Flexible orchestration mode.
- Ensure the lowest possible network latency between the application VMs and a database cluster.

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

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

Cevabı ve açıklamayı göster

Cevap: Deploy the Virtual Machine Scale Set across multiple Availability Zones.; Create a Proximity Placement Group in each Availability Zone to co-locate the application VMs and database VMs within each zone.

Cevap

To meet the requirements, you should deploy the Virtual Machine Scale Set across multiple Availability Zones and create a Proximity Placement Group in each Availability Zone to co-locate the application VMs and database VMs within each zone.
To achieve the 99.99%99.99\% SLA, Azure virtual machines must be distributed across multiple Availability Zones. To ensure the lowest possible latency between the application and database VMs within those zones, a Proximity Placement Group should be created for each zone. This combination satisfies both the high-availability SLA and the low-latency networking requirements.

Adım Adım Çözüm

1
Identify the SLA requirement.
A 99.99%99.99\% virtual machine uptime SLA is required.
This SLA level can only be achieved in Azure by deploying VMs across two or more Availability Zones.
2
Determine the physical placement of resources to meet the latency requirement.
A Proximity Placement Group (PPG) must be used inside each Availability Zone.
A single PPG cannot span zones without risking latency issues or deployment failures. Therefore, separate PPGs are created for each Availability Zone to keep resources close within their respective zones.
3
Evaluate workload stability and VM pricing model.
Avoid Spot VMs and stick to standard VMs.
Spot VMs do not have an SLA and can be evicted randomly, which violates the high-availability requirement of a mission-critical platform.

Anahtar Kavram

Designing compute high availability using Availability Zones and Proximity Placement Groups to meet specific uptime SLAs and performance latency requirements.
Soru 948Soru

Skyline Freight Systems is designing a disaster recovery strategy for its shipment tracking application. The application writes critical transit logs to Azure Blob Storage. The design must meet the following requirements:
- Data must be replicated to a secondary Azure region.
- In the event of a primary region outage, the application must be able to read data from the secondary region.
- The recovery point objective (RPO) must be less than 15 minutes.
- If a failover is initiated to the secondary region, the application must be able to resume write operations.

Which two of the following configuration options and operational behaviors should you include in the design? (Select TWO)

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

Cevabı ve açıklamayı göster

Cevap: Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS) or Read-Access Geo-Zone-Redundant Storage (RA-GZRS).; Initiate a customer-managed failover of the storage account, which updates the primary endpoint to point to the secondary region and allows writes to resume.

Cevap

Configure the storage account to use Read-Access Geo-Redundant Storage (RA-GRS) or Read-Access Geo-Zone-Redundant Storage (RA-GZRS), and initiate a customer-managed failover of the storage account, which updates the primary endpoint to point to the secondary region and allows writes to resume.
To satisfy the requirements, the storage account must be configured with Read-Access Geo-Redundant Storage (RA-GRS) or Read-Access Geo-Zone-Redundant Storage (RA-GZRS). This ensures that the application can read from the secondary region while the primary is healthy or degraded. To restore write capabilities during a prolonged outage, a customer-managed storage account failover must be initiated. This updates the storage account's DNS records so that the secondary region becomes the new primary region, allowing the application to write to the storage account again.

Adım Adım Çözüm

1
Determine the required replication tier to support geo-redundancy and read access in the secondary region.
Identify that RA-GRS or RA-GZRS must be selected to allow reading from the secondary region without initiating a failover.
Standard GRS or GZRS does not allow read access to the secondary region unless a failover is triggered.
2
Analyze how write operations are restored in the event of a permanent primary region failure.
Identify that a customer-managed failover must be initiated, which changes the primary DNS endpoint of the storage account to point to the secondary region.
Before failover, the secondary endpoint is read-only. Performing a failover is required to make the secondary endpoint writeable as the new primary.

Anahtar Kavram

Azure Storage replication types (RA-GRS/RA-GZRS) provide read access to the secondary region, but write access to the secondary region is only enabled after initiating a storage account failover.
Tahmini Süre:1m 30s
Soru 949Soru

A company is designing a data storage solution on Azure Blob Storage to store monthly application transaction logs. The logs are stored in a General-purpose v2 storage account. The lifecycle requirements for the logs are as follows:
- For the first 4545 days after creation, logs are actively queried by an analytical application requiring sub-second retrieval latency.
- From day 4646 to day 180180, logs are rarely accessed, but when they are, they must be retrieved within 55 minutes.
- From day 181181 to day 365365, logs are only stored for compliance preparation. Retrieval latency of up to 1515 hours is acceptable.
- After 365365 days, the logs must be deleted permanently.

To minimize storage and retrieval costs, which of the following lifecycle management rule configurations should you recommend?

Cevabı ve açıklamayı göster

Cevap: Transition blobs to the Cold tier after 4545 days, transition to the Archive tier after 180180 days, and delete the blobs after 365365 days.

Cevap

Transition blobs to the Cold tier after 4545 days, transition to the Archive tier after 180180 days, and delete the blobs after 365365 days.
Transitioning blobs to the Cold tier after 4545 days satisfies the 55-minute retrieval requirement since the Cold tier offers sub-second retrieval latency, and it is more cost-effective than the Cool tier. The blobs remain in the Cold tier for 135135 days (from day 4646 to 180180), which is greater than the Cold tier's 9090-day minimum retention period, avoiding any early deletion penalties. Transitioning to the Archive tier after 180180 days is acceptable because the 1515-hour retrieval latency matches the Archive tier's standard rehydration speed. The blobs reside in the Archive tier for 185185 days (from day 181181 to 365365), which exceeds the Archive tier's 180180-day minimum retention period, avoiding early deletion penalties upon final deletion on day 366366.

Adım Adım Çözüm

1
Analyze retrieval latency requirements for each period to map compatible Azure Blob Storage tiers.
Days 11 to 4545 require sub-second latency (Hot tier). Days 4646 to 180180 require under 55 minutes (Hot, Cool, or Cold tiers are valid; Archive is invalid due to hours-long rehydration latency). Days 181181 to 365365 allow up to 1515 hours (Archive tier is valid).
Mapping latency limits guarantees that performance requirements are satisfied in every phase.
2
Determine the most cost-effective tier for the second phase (days 4646 to 180180) and check minimum retention limits.
Cold tier is selected because it has lower storage costs than Cool tier and meets the sub-second retrieval latency requirement. The logs remain in the Cold tier for 135135 days (from day 4646 to 180180). This exceeds the Cold tier minimum retention period of 9090 days, ensuring no early deletion or transition penalties are incurred.
Optimizing cost in intermediate tiers requires comparing storage rates and matching duration with minimum retention policies.
3
Evaluate the timing for the Archive tier transition and subsequent deletion.
Logs are transitioned to Archive on day 180180 and deleted after day 365365. The duration in the Archive tier is 185185 days (from day 181181 to 365365). This exceeds the Archive tier minimum retention period of 180180 days, avoiding any early deletion penalties.
Ensuring the data spends at least 180180 days in the Archive tier before deletion prevents early deletion charges.

Anahtar Kavram

Data Lifecycle Management and Retention
Soru 950Soru

An online education platform is designing a storage solution for video course materials using Azure Blob Storage. The solution must meet the following requirements:
- Replicate data across three availability zones in the primary region to protect against a zone outage.
- Replicate data to a secondary region to protect against a regional disaster.
Which two redundancy configuration options should you recommend? (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

Geo-zone-redundant storage (GZRS) and Read-access geo-zone-redundant storage (RA-GZRS)
The correct options are Geo-zone-redundant storage (GZRS) and Read-access geo-zone-redundant storage (RA-GZRS). These tiers replicate data across three Azure availability zones in the primary region, which protects against zone outages, and asynchronously replicate it to a secondary region, which protects against regional disasters.

Adım Adım Çözüm

1
Analyze primary region resiliency requirement
The requirement to protect against a zone outage in the primary region requires zone-redundant options (ZRS, GZRS, or RA-GZRS). Locally redundant (LRS) and geo-redundant (GRS) options are eliminated because they replicate locally within a single zone in the primary region.
Ensuring the data is spread across multiple availability zones in the primary region.
2
Analyze regional disaster recovery requirement
The requirement to protect against a regional disaster requires geo-replication to a secondary region. This eliminates Zone-redundant storage (ZRS).
Ensuring data is copied to a separate geographic region.
3
Select matching redundancy configurations
Both Geo-zone-redundant storage (GZRS) and Read-access geo-zone-redundant storage (RA-GZRS) replicate across three zones in the primary region and copy data to a secondary region, fulfilling all criteria.
Finding the storage tiers that satisfy both zonal and regional replication requirements.

Anahtar Kavram

Choosing Azure Storage replication options that combine zone-redundancy and geo-redundancy.
Soru 951Soru

A digital media broadcasting company is designing an Azure compute infrastructure for two new workloads:
- Workload 1: A video rendering system that processes non-urgent, interruptible background encoding tasks. The primary goal is to minimize compute costs, even if virtual machines are evicted during processing.
- Workload 2: A core licensing service that processes cryptographic keys, handles highly sensitive user data, requires physical isolation at the hardware level due to regulatory compliance, and must run continuously with a 99.99% availability SLA.

Which two compute virtualization solutions should you recommend to meet the requirements for these workloads? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure Spot Virtual Machines for Workload 1; Azure Dedicated Hosts for Workload 2

Cevap

Azure Spot Virtual Machines for Workload 1 and Azure Dedicated Hosts for Workload 2
Azure Spot Virtual Machines are correct for the video rendering workload because they allow the customer to take advantage of unused Azure capacity at significant cost savings, which is ideal for workloads that are non-urgent and can be interrupted. Azure Dedicated Hosts are correct for the licensing service because they provide physical servers dedicated to a single Azure subscription, satisfying the physical isolation requirement, and support zone-redundant deployments to meet the 99.99% SLA.

Adım Adım Çözüm

1
Analyze the requirements for Workload 1.
Identify that the workload consists of background, non-urgent, interruptible tasks where minimizing cost is the primary goal.
This establishes that the workload is suitable for transient compute models.
2
Evaluate compute solutions for Workload 1.
Determine that Azure Spot Virtual Machines offer the lowest cost for workloads that can tolerate eviction.
This matches the low-cost and interruptible nature of the video rendering jobs.
3
Analyze the requirements for Workload 2.
Identify that the workload requires physical hardware isolation for regulatory compliance and a 99.99% availability SLA.
This dictates the need for non-shared physical infrastructure and high-availability design.
4
Evaluate compute solutions for Workload 2.
Determine that Azure Dedicated Hosts provide physical isolation at the host level and can be placed across multiple availability zones to meet the 99.99% SLA.
This fully addresses the compliance and availability constraints.

Anahtar Kavram

Selecting Azure compute virtualization services based on cost, workload flexibility, hardware isolation, and availability SLA requirements.
Soru 952Soru

AquaShield Water Solutions is designing a disaster recovery solution for an application that processes real-time telemetry from water treatment facilities. The telemetry logs are written continuously to an Azure Blob Storage account in the East US region. The solution must meet the following requirements:
- During normal operations, the application must read and write data in the primary region.
- If a disaster disables the primary region, the application must be able to read existing telemetry logs immediately from a secondary region.
- The Recovery Point Objective (RPO) for data loss must be less than 15 minutes.
- If the primary region remains unavailable for an extended period, the application must be able to write new logs to the secondary region.
- Storage costs must be minimized.

Which storage configuration and disaster recovery strategy should you recommend?

Cevabı ve açıklamayı göster

Cevap: Use Read-Access Geo-Redundant Storage (RA-GRS). Configure the application to read from the secondary endpoint during a primary outage, and initiate a customer-managed failover to enable write operations in the secondary region if the outage is prolonged.

Cevap

Use Read-Access Geo-Redundant Storage (RA-GRS). Configure the application to read from the secondary endpoint during a primary outage, and initiate a customer-managed failover to enable write operations in the secondary region if the outage is prolonged.
Read-Access Geo-Redundant Storage (RA-GRS) with a customer-managed failover strategy meets all requirements. RA-GRS provides a read-only secondary endpoint that is immediately readable during a primary regional outage, achieving a read RTO of 0. GRS/RA-GRS replication is asynchronous and typically has a replication lag of under 15 minutes, meeting the 15-minute RPO. Initiating a customer-managed failover promotes the secondary endpoint to primary, which enables write operations during a prolonged outage, all while maintaining lower storage costs than multi-region active-write configurations.

Adım Adım Çözüm

1
Identify the read and write requirements during a regional outage.
The solution requires immediate read access to existing data (RTO of 0 for reads) and the ability to write to the secondary region during a prolonged outage.
This filters out replication options that do not support read access to the secondary region prior to failover, and options that cannot accept write traffic post-failover.
2
Evaluate storage replication options against the RPO and read access requirements.
LRS is eliminated as it lacks regional redundancy. GRS alone does not allow read access prior to failover. RA-GRS provides a read-only endpoint in the secondary region with an asynchronous replication lag of under 15 minutes, satisfying the 15-minute RPO and the immediate read requirement.
Only RA-GRS supports immediate read access to the secondary region during a primary outage.
3
Determine the mechanism for enabling write operations in the secondary region during a prolonged outage.
Initiating a customer-managed failover on the RA-GRS account promotes the secondary region to the primary endpoint, enabling write operations.
Writing directly to the RA-GRS secondary endpoint is not permitted as it is read-only; a failover must be triggered to allow write access.

Anahtar Kavram

Azure Storage replication redundancy options (RA-GRS) and the customer-managed failover mechanism to achieve HA/DR for non-relational storage.
Soru 953Soru

An organization is designing a container-based application on Azure that consists of public-facing web microservices and background processing jobs.

The application has the following requirements:
- The background processing jobs must scale dynamically to zero based on the number of messages in an Azure Service Bus queue.
- The web microservices must scale based on concurrent HTTP requests.
- You must minimize the administrative effort required to manage the container hosting infrastructure.
- You must store application logs in a way that strictly isolates development environment data from production environment data.

Which two components should you recommend as part of the architecture? (Select two.)

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

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps to host the microservices and background jobs; Two separate Azure Log Analytics workspaces to store logs for the development and production environments

Cevap

To meet the requirements, the architecture should include Azure Container Apps to host the workloads, minimizing administrative effort while providing native scaling features, and two separate Azure Log Analytics workspaces to ensure strict isolation of log data between environments.
Hosting workloads on Azure Container Apps meets the requirements for scaling to zero based on queue depth (using built-in KEDA integration) and HTTP-based scaling, while avoiding the operational burden of managing Kubernetes nodes. Additionally, configuring two separate Log Analytics workspaces ensures that development and production log data are completely isolated, fulfilling compliance boundaries.

Adım Adım Çözüm

1
Evaluate the compute hosting requirements for scaling and management overhead.
Azure Container Apps is selected over Azure Kubernetes Service because it supports scaling to zero via KEDA, scales on HTTP requests, and is a fully managed serverless service that minimizes cluster management overhead.
Reduces operational complexity while meeting dynamic scaling needs.
2
Evaluate the monitoring and compliance requirements for log data segregation.
Two separate Log Analytics workspaces are selected instead of a single centralized workspace.
Ensures strict isolation and boundary segregation between development and production log data to comply with security requirements.

Anahtar Kavram

Designing Azure container solutions with appropriate scaling and management overhead, along with compliant logging configurations.
Soru 954Soru

An enterprise is designing the compute architecture for a high-performance distributed database on Azure. The solution must meet the following requirements:

- Achieve a virtual machine uptime SLA of at least 99.99%99.99\%.
- Provide resiliency against a complete datacenter zone failure.
- Minimize network latency between the active database nodes within each region.

Which compute configuration should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy Virtual Machine Scale Sets in Flexible orchestration mode across 33 Availability Zones, utilizing a dedicated Proximity Placement Group (PPG) for each zone.

Cevap

Deploy Virtual Machine Scale Sets in Flexible orchestration mode across 33 Availability Zones, utilizing a dedicated Proximity Placement Group (PPG) for each zone.
Deploying Virtual Machine Scale Sets in Flexible orchestration mode across 33 Availability Zones satisfies the 99.99%99.99\% uptime SLA and zone-level resiliency requirements. Using a dedicated Proximity Placement Group (PPG) for each zone ensures that the virtual machines within each zone are colocated as closely as possible to minimize intra-zone network latency without causing deployment allocation failures.

Adım Adım Çözüm

1
Analyze the SLA and high availability requirements.
To achieve a 99.99%99.99\% uptime SLA and survive a zone failure, the VMs must be deployed across at least 22 (and ideally 33) Availability Zones.
Azure guarantees 99.99%99.99\% SLA only when VMs are deployed across multiple Availability Zones in the same region.
2
Evaluate the latency requirement in a multi-zone deployment.
Using a single Proximity Placement Group (PPG) across multiple zones does not reduce latency between zones and can cause deployment failures.
PPGs are designed for low-latency colocation within a single physical datacenter (zone). A single PPG cannot colocate VMs across physically separate zones.
3
Select the optimal configuration that combines zone redundancy and low latency.
Deploy VMSS in Flexible orchestration mode across 33 zones with a dedicated PPG per zone.
This setup allows zone redundancy for the cluster while ensuring ultra-low latency for the subset of nodes operating within each individual zone.

Anahtar Kavram

Designing compute high availability using Availability Zones and Proximity Placement Groups.
Soru 955Soru

You are designing the hosting infrastructure for a new event-driven image processing solution in Azure. The solution has the following workloads:

* API Ingestion: A lightweight endpoint that receives image upload metadata. It requires rapid auto-scaling to handle unpredictable spikes in traffic, and it must scale to zero instances during idle periods to minimize costs. It does not require virtual network (VNet) integration.
* Image Analyzer: A background processor that pulls image analysis tasks from a queue, processes the images, and writes the output to an Azure SQL Database. The processor requires VNet integration to connect securely to the database via a private endpoint, can take up to 1515 minutes to process a single complex image, and must scale to zero instances when the queue is empty to minimize costs.

Which compute configuration should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Host the API Ingestion on Azure Functions on a Consumption plan, and host the Image Analyzer on Azure Container Apps.

Cevap

Host the API Ingestion on Azure Functions on a Consumption plan, and host the Image Analyzer on Azure Container Apps.
Hosting the API Ingestion on the Azure Functions Consumption plan provides cost-effective, rapid scaling that goes down to zero instances when idle. Hosting the Image Analyzer on Azure Container Apps allows the background task to run for the required 1515 minutes, provides outbound virtual network integration to securely access the database via a private endpoint, and supports scaling down to zero instances using event-driven autoscaling to eliminate idle costs.

Adım Adım Çözüm

1
Analyze the API Ingestion hosting requirements.
The API endpoint requires rapid auto-scaling to handle traffic spikes and must scale to zero during idle periods to avoid costs. Virtual network integration is not required. Azure Functions on a Consumption plan is the most cost-effective service that satisfies these conditions.
The Consumption plan scales dynamically from zero and charges only when executions occur, with no base cost.
2
Evaluate Azure Functions options for the Image Analyzer workload.
The Image Analyzer requires outbound virtual network integration, runs for up to 1515 minutes, and must scale to zero instances. The standard Consumption plan is ruled out due to its 1010-minute execution timeout limit and lack of VNet integration. The Premium plan supports VNet integration and longer durations but requires at least one pre-warmed instance, failing the scale-to-zero requirement.
Identifying that standard Azure Functions plans violate either execution timeout limits or scale-to-zero cost constraints.
3
Select the optimal container-based compute option for the Image Analyzer.
Azure Container Apps supports custom virtual network deployments, has no strict 1010-minute execution limit, and scales to zero instances based on queue metrics (via KEDA). Azure Kubernetes Service also meets these technical requirements but introduces excessive operational overhead.
Choosing Azure Container Apps over Azure Kubernetes Service minimizes management overhead while fulfilling all functional and cost constraints.

Anahtar Kavram

Selecting the optimal Azure serverless or web hosting compute option by evaluating scaling requirements, execution timeout limits, network isolation, and operational overhead.
Soru 956Soru

A multinational bank is designing the compute virtualization infrastructure for a critical, steady-state financial compliance auditing application. The application has the following requirements:

- Must run continuously 2424 hours a day, 77 days a week (24/724/7) without unexpected evictions or interruptions.
- Must be deployed on physical servers dedicated to a single customer to satisfy hardware isolation compliance rules.
- Must support memory-optimized virtual machines with high memory-to-vCPU ratios.
- Must achieve a minimum compute availability SLA of 99.99%99.99\%.

Which of the following compute virtualization solutions should you recommend to meet these requirements?

Cevabı ve açıklamayı göster

Cevap: Deploy Azure Dedicated Hosts for Ev5-series virtual machines across at least two Availability Zones, and provision standard virtual machines on these hosts.

Cevap

Deploy Azure Dedicated Hosts for Ev5-series virtual machines across at least two Availability Zones, and provision standard virtual machines on these hosts.
Deploying Azure Dedicated Hosts provides physical servers dedicated to a single Azure subscription, satisfying the hardware isolation requirement. To achieve a 99.99%99.99\% availability SLA, Dedicated Hosts must be deployed across at least two Availability Zones in a region. Standard virtual machines (such as the memory-optimized Ev5-series) running on these hosts ensure steady-state, continuous execution without the eviction risk associated with Spot instances.

Adım Adım Çözüm

1
Identify the hardware isolation requirement.
Requires the use of Azure Dedicated Hosts to ensure the physical servers are dedicated to a single Azure subscription.
Standard multi-tenant virtual machines do not satisfy the hardware isolation compliance rule.
2
Determine the availability SLA requirement.
Requires deploying the Dedicated Hosts across at least two Availability Zones in the selected Azure region.
An availability SLA of 99.99%99.99\% for virtual machines requires multi-zone deployment. A single zone deployment only provides a lower SLA.
3
Evaluate the workload continuity and eviction constraints.
Requires provisioning standard (non-Spot) virtual machines.
Azure Spot VMs are subject to eviction at any time when capacity is needed, which violates the requirement to run continuously without unexpected evictions or interruptions.
4
Match the compute memory requirement.
Configure Ev5-series virtual machines on the Dedicated Hosts.
Ev5-series virtual machines are memory-optimized and satisfy the high memory-to-vCPU ratio constraint.

Anahtar Kavram

Azure Dedicated Hosts high availability and workload design
Tahmini Süre:2m 30s
Soru 957Soru

An insurance company is designing a disaster recovery (DR) solution to replicate its on-premises VMware workloads to Azure. The workload consists of two virtual machines:

- VM-App: An application server with an average write churn of 3 MB/s3\text{ MB/s} and a peak write churn of 8 MB/s8\text{ MB/s}.
- VM-Data: A database server with a single data disk that experiences an average write churn of 28 MB/s28\text{ MB/s} and a peak write churn of 45 MB/s45\text{ MB/s}.

The DR solution must support a Recovery Point Objective (RPO) of under 2 hours and a Recovery Time Objective (RTO) of under 1 hour.

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 VM-App to Azure by using Azure Site Recovery.; Configure SQL Server Always On Availability Groups to replicate the database from the on-premises environment to SQL Server on Azure Virtual Machines.

Cevap

Replicate VM-App to Azure by using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the database from the on-premises environment to SQL Server on Azure Virtual Machines.
The correct solution involves replicating the low-churn application VM (VM-App) using Azure Site Recovery, and using SQL Server Always On Availability Groups for the database VM (VM-Data). Since VM-Data's write churn (28 MB/s28\text{ MB/s} average, 45 MB/s45\text{ MB/s} peak) exceeds the standard ASR limit of 20 MB/s20\text{ MB/s} per Premium SSD disk, standard ASR replication is not suitable. Always On Availability Groups handle high-churn databases efficiently and can meet the strict RPO/RTO requirements.

Adım Adım Çözüm

1
Analyze the write churn for VM-App and VM-Data.
VM-App has an average write churn of 3 MB/s3\text{ MB/s} and a peak of 8 MB/s8\text{ MB/s}. VM-Data has an average write churn of 28 MB/s28\text{ MB/s} and a peak of 45 MB/s45\text{ MB/s}.
This establishes whether the workloads fall within the standard write churn limits of Azure Site Recovery.
2
Compare write churn against Azure Site Recovery limits.
VM-App is well below the standard 20 MB/s20\text{ MB/s} per Premium SSD disk limit. VM-Data exceeds the 20 MB/s20\text{ MB/s} per Premium SSD disk limit.
This determines which virtual machines can be safely replicated using Azure Site Recovery.
3
Determine the appropriate replication method for the high-churn database workload.
Since VM-Data cannot use Azure Site Recovery due to churn limits, SQL Server Always On Availability Groups must be used to replicate the SQL Server database to Azure VMs.
This ensures the database replication remains healthy and meets the RPO and RTO requirements.

Anahtar Kavram

Azure Site Recovery limits require checking disk write churn against limits (typically 20 MB/s20\text{ MB/s} per Premium SSD disk); workloads exceeding these limits must use native replication solutions like SQL Server Always On Availability Groups.
Soru 958Soru

A pharmaceutical company named Apex BioPharm is designing a business continuity solution for a clinical trials database application. The application writes critical patient monitoring logs to an Azure Storage account.

The solution must meet the following requirements:
- If the primary Azure region experiences an outage, data must remain readable from the secondary region.
- In the event of a disaster, write capabilities must be restored in the secondary region with a Recovery Time Objective (RTO) of 22 hours.
- The Recovery Point Objective (RPO) must be less than 1515 minutes.
- Costs must be minimized.

Which two actions should you recommend to meet the requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Configure the storage account to use Read-access geo-redundant storage (RA-GRS).; Initiate a customer-managed failover of the storage account to the secondary region if a primary region outage occurs.

Cevap

The correct actions are to configure the storage account to use Read-access geo-redundant storage (RA-GRS) and to initiate a customer-managed failover of the storage account to the secondary region during a primary region outage.
To support read availability in the secondary region during a primary region outage, the storage account must be configured with Read-access geo-redundant storage (RA-GRS). RA-GRS provides a secondary read-only endpoint. Because the secondary endpoint is read-only, write operations cannot be routed to it directly. To restore write capabilities in the secondary region within the 22-hour RTO, you must initiate a customer-managed failover, which changes the secondary region to the primary region and makes it writable.

Adım Adım Çözüm

1
Evaluate redundancy options to meet RPO and read availability requirements.
Selecting Read-access geo-redundant storage (RA-GRS) ensures asynchronous replication to a secondary region with an RPO of under 1515 minutes and allows read access to the secondary region during a primary outage.
Locally Redundant Storage (LRS) does not provide geo-redundancy, and standard GRS without read access would not allow reading from the secondary region prior to failover.
2
Determine how to restore write availability within the RTO.
Initiating a customer-managed failover converts the secondary region into the new primary, enabling full read and write access.
Writes cannot be performed directly to the secondary endpoint of an RA-GRS account, so a failover is required to restore write capabilities.

Anahtar Kavram

Designing storage redundancy and geo-failover strategies in Azure to meet specific recovery objectives (RTO and RPO).
Soru 959Soru

A financial services firm is designing a data retention strategy for transaction audit logs stored in an Azure Data Lake Storage Gen2 (ADLS Gen2) account. The logs must be managed according to the following requirements:

* The logs are actively analyzed and must remain in the Hot tier for the first 1515 days.
* From day 1616 to day 9090, the logs are accessed occasionally for reporting. The reporting application requires immediate, sub-second retrieval latency.
* After 9090 days, the logs must be retained for 77 years (2,5552,555 days) to comply with regulatory audits. During this time, they are rarely accessed, and a retrieval latency of several hours is acceptable.
* Storage costs must be minimized.

Which lifecycle management policy should you recommend?

Cevabı ve açıklamayı göster

Cevap: Transition the logs to the Cool tier after 1515 days, transition the logs to the Archive tier after 9090 days, and delete the logs after 2,5552,555 days.

Cevap

Transition the logs to the Cool tier after 1515 days, transition the logs to the Archive tier after 9090 days, and delete the logs after 2,5552,555 days.
The correct lifecycle policy transitions the logs to the Cool tier after 1515 days to maintain sub-second retrieval latency for reporting, moves them to the Archive tier after 9090 days to minimize storage costs for the remainder of the 77 years, and deletes them after 2,5552,555 days to comply with the retention policy.

Adım Adım Çözüm

1
Determine the storage tier strategy for the active analysis phase.
Keep the logs in the Hot tier for the first 1515 days.
This meets the active analysis access requirement while minimizing transaction costs.
2
Determine the storage tier strategy for the reporting phase from day 1616 to day 9090.
Transition the logs to the Cool tier after 1515 days.
The Cool tier reduces storage costs compared to the Hot tier while satisfying the sub-second retrieval latency requirement.
3
Determine the archiving and deletion schedule for the compliance phase after day 9090.
Transition the logs to the Archive tier after 9090 days and delete them after 2,5552,555 days.
The Archive tier offers the lowest storage cost for rare access and supports the required multi-hour retrieval. Deleting after 2,5552,555 days (77 years) satisfies the regulatory retention constraint.

Anahtar Kavram

Azure Storage lifecycle management allows automated tiering between Hot, Cool, and Archive tiers, along with automated deletion, based on age to balance retrieval latency requirements and storage costs.
Soru 960Soru

A retail company is designing the hosting architecture for a new serverless order management system. The solution must host two distinct services:

1. An order intake service that processes incoming HTTP webhooks. This service must scale dynamically to zero when idle and executes for less than three minutes per invocation.
2. A data ingestion background service that processes large files from a storage queue. Each message processing job runs continuously and can take up to 25 minutes to complete.

Which two Azure hosting options should you recommend to meet these requirements while minimizing administrative overhead? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Azure Functions on a Consumption plan to host the order intake service; Azure Container Apps Jobs to host the data ingestion background service

Cevap

Azure Functions on a Consumption plan should be used to host the order intake service, and Azure Container Apps Jobs should be used to host the data ingestion background service.
The correct recommendation is to host the order intake service on Azure Functions on a Consumption plan and host the data ingestion background service on Azure Container Apps Jobs. Azure Functions on a Consumption plan scale to zero and easily accommodate the 3-minute execution limit of the HTTP webhooks. Azure Container Apps Jobs are optimized for containerized tasks that run to completion and can execute for up to several hours, which accommodates the 25-minute execution duration without the management overhead of an AKS cluster.

Adım Adım Çözüm

1
Evaluate the execution time and workload characteristics of the order intake service.
The order intake service receives short-lived HTTP requests that execute in under 3 minutes. It requires automatic scaling and scaling to zero to optimize costs.
Azure Functions on a Consumption plan matches these serverless requirements and provides built-in scaling to zero with a maximum execution time limit of 10 minutes.
2
Evaluate the execution time and workload characteristics of the data ingestion background service.
The background service processes queue-based workloads that can take up to 25 minutes per execution, which exceeds standard serverless timeout limits.
An Azure Functions Consumption plan would time out after 10 minutes. Azure Container Apps Jobs support long-running, run-to-completion tasks that can execute for hours, while scaling to zero when the queue is empty.
3
Assess the administrative overhead constraints of the available solutions.
Azure Kubernetes Service (AKS) introduces unnecessary administrative complexity for hosting simple webhooks compared to serverless offerings.
Choosing Azure Functions and Azure Container Apps Jobs minimizes operational overhead, satisfying the host management constraints.

Anahtar Kavram

Selecting serverless hosting options based on execution timeouts and administrative overhead
Tahmini Süre:1m 30s
ÖncekiSayfa 48 / 60Sonraki