Tüm alıştırma soruları

1198 soru

Soru 421Soru

An organization runs a critical transaction system on an Azure Virtual Machine. The virtual machine is configured with Premium SSD v2 managed disks. You need to establish a backup policy using Azure Backup that satisfies the following operational constraints:

* Retain daily recovery points for a total duration of 60 days.
* Guarantee near-instant recovery times for any file restoration from backups that are up to 6 days old.
* Recoveries from points older than 6 days may be performed using standard vault retrieval times.

Which backup policy configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: An Enhanced backup policy with the snapshot retention (instant restore) set to 6 days and the vault retention set to 60 days.

Cevap

An Enhanced backup policy with the snapshot retention (instant restore) set to 6 days and the vault retention set to 60 days.
The Enhanced backup policy is required to support Premium SSD v2 disks. Furthermore, the Enhanced policy allows the snapshot retention (instant restore) to be configured up to 30 days, which satisfies the requirement for a 6-day rapid restoration window. The vault retention can then keep the recovery points for the remaining 60 days.

Adım Adım Çözüm

1
Analyze disk compatibility requirements for the Azure Virtual Machine.
The virtual machine uses Premium SSD v2 managed disks, which are only supported by the Enhanced backup policy tier in Azure Backup.
Azure Backup Standard policies only support Standard HDD, Standard SSD, and Premium SSD (v1) disks. Premium SSD v2 and Ultra Disks require the Enhanced policy tier.
2
Evaluate the instant restore (snapshot retention) requirements.
The requirement is to provide near-instant restores from backups up to 6 days old. This requires setting the snapshot retention to at least 6 days.
Standard backup policies limit instant restore snapshot retention to a maximum of 5 days. The Enhanced backup policy allows snapshot retention to be configured up to 30 days.
3
Combine the disk support and snapshot retention requirements to select the correct policy configuration.
Select an Enhanced backup policy with snapshot retention set to 6 days and vault retention set to 60 days.
This satisfies the disk type constraint, enables the 6-day instant recovery window, and maintains the total backup history for the required 60 days.

Anahtar Kavram

Azure Backup policy tiers (Standard vs. Enhanced) and their respective disk capabilities and snapshot (instant restore) retention limits.
Tahmini Süre:1m 30s
Soru 422Soru

You are designing the data storage and diagnostics architecture for a global smart-home automation platform. The platform manages telemetry and configuration data for 10,000,00010,000,000 IoT devices across North America, Europe, and Asia. The solution must meet the following requirements:
- Support real-time telemetry ingestion with a write-to-read ratio of 9:19:1.
- Maintain sub-10 ms10\text{ ms} write latency globally by utilizing an active-active multi-region write configuration.
- Achieve a recovery time objective (RTO) of zero for regional disaster recovery.
- Prevent hot partitions during mass device reconnect events.
- Provide external diagnostic partners with read-only access to device logs for a maximum of 3030 days, with the ability to immediately revoke access if a security compromise occurs.

Which architecture configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Configure Azure Cosmos DB for NoSQL with multi-region writes enabled, partitioning the telemetry container by deviceId. Export diagnostics to an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS) and grant external access using Shared Access Signature (SAS) tokens associated with a stored access policy.

Cevap

Configure Azure Cosmos DB for NoSQL with multi-region writes enabled, partitioning the telemetry container by deviceId. Export diagnostics to an Azure Storage account configured with Read-Access Geo-Redundant Storage (RA-GRS) and grant external access using Shared Access Signature (SAS) tokens associated with a stored access policy.
Partitioning the database container by deviceId guarantees high cardinality, which spreads write throughput uniformly across partitions. Exporting diagnostic data to a Read-Access Geo-Redundant Storage (RA-GRS) account ensures that even if a primary region is offline, diagnostic logs remain accessible from the secondary region. Associating the SAS token with a stored access policy meets the security standard by permitting immediate revocation of external permissions through modification or deletion of the policy.

Adım Adım Çözüm

1
Analyze partition key cardinality requirements
Identify that partitioning by deviceId provides high cardinality, which distributes write requests evenly across physical partitions, preventing hot partitions during mass reconnects.
Choosing deviceType (low cardinality) would concentrate data from millions of devices onto a small set of logical partitions, causing partition key exhaustion and performance bottlenecks.
2
Evaluate storage redundancy requirements for regional resilience
Select Read-Access Geo-Redundant Storage (RA-GRS) to provide read availability from a secondary region during a primary region outage.
Locally Redundant Storage (LRS) only replicates data within a single datacenter facility, violating regional disaster recovery guidelines.
3
Select the correct SAS token delegation mechanism
Determine that SAS tokens must be associated with a stored access policy to support immediate revocation.
Ad-hoc SAS tokens defined directly in the URI cannot be revoked prior to expiration unless the master storage keys are rotated, which impacts all active integrations.

Anahtar Kavram

Designing partition keys for scalable NoSQL systems, choosing geographic data redundancy tiers, and securing Azure storage endpoints with revocable shared access mechanisms.
Soru 423Soru

An organization is designing a high-performance, three-tier web application in Azure. The compute tier will host virtual machines (VMs) running business logic. The architecture must meet the following requirements:
- Achieve a minimum VM uptime service level agreement (SLA) of 99.99%.
- Maintain network latency of less than 1 millisecond between the web servers, application servers, and database servers.
- Ensure that compute resources are distributed across distinct physical hardware racks to prevent localized host outages from taking down the entire application.

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

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

Cevabı ve açıklamayı göster

Cevap: Create one Proximity Placement Group for each availability zone, and associate the virtual machines in each zone with their respective Proximity Placement Group.; Deploy the virtual machines across multiple availability zones using a Virtual Machine Scale Set in Flexible orchestration mode.

Cevap

To meet the requirements, you must deploy the virtual machines across multiple availability zones using a Virtual Machine Scale Set in Flexible orchestration mode, and create one Proximity Placement Group for each availability zone.
The correct configurations are to deploy the virtual machines across multiple availability zones using a Virtual Machine Scale Set in Flexible orchestration mode, and to create one Proximity Placement Group for each availability zone. Distributing virtual machines across multiple availability zones provides the 99.99% uptime SLA required by Azure. Flexible orchestration mode allows full control over individual VMs and fault domains. Creating a Proximity Placement Group for each availability zone ensures that VMs within each zone are colocated to meet the sub-millisecond latency requirement without violating zone isolation.

Adım Adım Çözüm

1
Evaluate the uptime SLA requirement.
To guarantee a 99.99% VM uptime SLA, the virtual machines must be distributed across two or more Azure Availability Zones within a region.
Azure only guarantees a 99.99% SLA for VMs when two or more instances are deployed across two or more Availability Zones.
2
Analyze the latency requirement.
To achieve sub-millisecond latency, VMs must be physically close. While Proximity Placement Groups (PPGs) achieve this, they cannot span multiple zones without causing deployment failures or violating zone separation. Thus, a separate PPG must be created for each availability zone.
PPGs are physically bound to a single datacenter. Spanning them across zones defeats the high-availability zone boundaries.
3
Select the orchestration and deployment configuration.
Deploy the virtual machines using a Virtual Machine Scale Set in Flexible orchestration mode spanning the availability zones.
Flexible orchestration mode allows full control over individual VMs, VM sizes, and fault domains across zones.

Anahtar Kavram

Designing zone-redundant, low-latency compute solutions in Azure using Proximity Placement Groups and VMSS Flexible orchestration.
Soru 424Soru

A multinational financial services organization is designing a disaster recovery and high availability solution for its core ledger application. The application will be deployed across two Azure regions: East US (primary) and West US (secondary).

The database layer consists of an Azure SQL Managed Instance deployment in each region. The design must meet the following requirements:
- Support automatic failover to the secondary region if the primary region experiences an outage.
- Provide a connection configuration that automatically routes read-write operations to the active primary instance and read-only reporting queries to the secondary instance.
- Ensure that replication and database traffic between the primary and secondary instances does not traverse the public internet and uses private IP addresses.

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

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

Cevabı ve açıklamayı göster

Cevap: Create a failover group between the primary and secondary SQL Managed Instances, and configure the application connection strings to use the failover group's read-write and read-only listener endpoints.; Configure global virtual network peering between the virtual networks hosting the primary and secondary SQL Managed Instances to facilitate private database replication.

Cevap

Create a failover group between the SQL Managed Instances to handle automatic failover and listener routing, and configure global virtual network peering between their virtual networks to allow private database replication traffic.
To design a disaster recovery and high availability solution for Azure SQL Managed Instance that supports automatic failover and read-scale routing, you must use a failover group. The failover group provides two distinct listener endpoints (one for read-write and one for read-only traffic) that automatically adjust during failover. Furthermore, SQL Managed Instance replication requires direct network routing between instances over a private connection, which is achieved by setting up global virtual network peering between the primary and secondary virtual networks.

Adım Adım Çözüm

1
Analyze database type and cross-region requirements.
The workload uses Azure SQL Managed Instance. Cross-region disaster recovery for SQL Managed Instance requires failover groups; active geo-replication is not supported on SQL Managed Instance.
Choosing the correct Azure-native replication technology ensures compatibility with the chosen database offering.
2
Address private routing requirements.
Global virtual network peering is designed between the virtual networks containing the SQL Managed Instances in East US and West US.
Failover groups for SQL Managed Instance require private network connectivity (IP routing) between the instances, which global virtual network peering provides securely over the Microsoft backbone.
3
Address routing of read-write and read-only traffic.
Configure connection strings using the failover group's read-write and read-only listener endpoints.
This provides distinct connection endpoints for each workload type, decoupling the client from the physical server names and automatically handling failover routing.

Anahtar Kavram

Azure SQL Managed Instance Failover Groups and Network Requirements
Soru 425Soru

A company plans to deploy a new microservices application that consists of three containerized services. The application must support automatic scaling based on HTTP request volume, including scaling down to zero instances. The operations team has no Kubernetes experience and wants to minimize administrative overhead. Which Azure service should you recommend to host the application?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps

Cevap

Azure Container Apps
Azure Container Apps is the correct choice because it is a serverless container platform designed for microservices that scales dynamically based on HTTP traffic, supports scaling to zero, and abstracts away the underlying Kubernetes cluster management, minimizing administrative overhead.

Adım Adım Çözüm

1
Identify the key workload requirements: a multi-container microservices application, HTTP-based autoscaling to zero, and the need to minimize administrative overhead without Kubernetes expertise.
The solution must be a serverless, low-overhead hosting platform that manages container orchestration automatically.
This rules out complex container orchestration platforms that require manual cluster management.
2
Compare the available Azure container hosting options against these requirements.
Azure Container Apps provides serverless container execution, automatic scaling to zero based on HTTP traffic, and does not require Kubernetes cluster administration.
This perfectly matches all customer constraints.

Anahtar Kavram

Azure Container Apps provides a fully managed, serverless platform for hosting containerized microservices with scaling capabilities and minimal management overhead, making it the preferred choice over Azure Kubernetes Service for teams wanting to avoid cluster management.
Soru 426Soru

An organization is designing a privileged access solution for a team of external database administrators who need temporary access to the DocumentDB Database Account Contributor role on a production Cosmos DB account. The solution must minimize administrative overhead, enforce multi-factor authentication (MFA) and justification prior to access activation, and ensure that emergency access accounts are protected from lockout during MFA service outages. Which configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Create a Microsoft Entra ID security group for the administrators, make the group eligible for the role in Privileged Identity Management (PIM) requiring justification and MFA for activation, and exclude emergency access accounts from the Conditional Access policy requiring MFA.

Cevap

Create a Microsoft Entra ID security group for the administrators, make the group eligible for the role in Privileged Identity Management (PIM) requiring justification and MFA for activation, and exclude emergency access accounts from the Conditional Access policy requiring MFA.
The correct option addresses all governance requirements by using group-based assignment to minimize management overhead, configuring eligible status in PIM to require JIT activation with justification and MFA, and excluding emergency access accounts from MFA requirements to prevent administrative lockout.

Adım Adım Çözüm

1
Select group-based assignment over individual assignment.
Reduced administrative overhead by using a single Microsoft Entra ID security group instead of multiple direct PIM assignments.
Assigning role eligibility to a security group aligns with Azure identity governance best practices.
2
Configure the security group's PIM assignment type as eligible.
Just-in-time (JIT) access is enforced, requiring administrators to explicitly request and justify activation.
Making the assignment eligible rather than permanently active ensures compliance with least privilege.
3
Define Conditional Access and PIM activation settings.
MFA and justification are required for activation, while emergency access accounts are excluded from the MFA requirement.
Excluding break-glass accounts prevents total tenant lockout if the MFA service is unavailable.

Anahtar Kavram

Entra ID Privileged Access and Governance
Tahmini Süre:1m 30s
Soru 427Soru

An enterprise is designing a data storage and lifecycle strategy for telemetry logs stored in Azure Data Lake Storage Gen2 (ADLS Gen2). The logs are stored as block blobs and must adhere to the following operational and compliance requirements:

* Operational Monitoring (Days 1–10): The logs are heavily queried with sub-second latency requirements.
* Batch Reconciliation (Days 11–90): The logs are read weekly for database reconciliation. Active, online access with low retrieval cost is required.
* Compliance Retention (Days 91–180): The logs are rarely accessed but must be retained. In the event of a regulatory audit, the logs must be readable within 3 hours. To minimize administrative overhead and avoid relying on High-Priority rehydration, the retrieval must use standard online access.
* Deletion (Day 180): Due to privacy regulations, the logs must be permanently deleted exactly 180 days after creation.

Which of the following JSON lifecycle policy configurations should you recommend to minimize storage and retrieval costs while avoiding early deletion charges?

Cevabı ve açıklamayı göster

Cevap: {
"actions": {
"baseBlob": {
"tierToCool": {
"daysAfterModificationGreaterThan": 10
},
"tierToCold": {
"daysAfterModificationGreaterThan": 90
},
"delete": {
"daysAfterModificationGreaterThan": 180
}
}
}
}

Cevap

The configuration that transitions the blobs to Cool on day 10, to Cold on day 90, and deletes them on day 180.
The configuration that transitions the blobs to Cool on day 10, to Cold on day 90, and deletes them on day 180 is correct because it aligns perfectly with the access requirements and minimum retention periods of each tier. Specifically: (1) The Cool tier transition occurs on day 10, meaning blobs spend 80 days in Cool (which exceeds the 30-day minimum retention period for the Cool tier). (2) The Cold tier transition occurs on day 90, meaning blobs spend 90 days in Cold (which exactly meets the 90-day minimum retention period for the Cold tier before they are deleted on day 180). (3) The Cold tier provides online access with millisecond retrieval times, satisfying the 3-hour retrieval SLA without relying on High-Priority Archive rehydration. (4) Keeping the data in Cool from day 10 to day 90 supports the active batch reconciliation with lower transaction and retrieval costs compared to the Cold tier.

Adım Adım Çözüm

1
Analyze the query and retrieval latency requirements for each operational phase.
Operational monitoring (days 1-10) requires Hot tier. Batch reconciliation (days 11-90) requires low transaction retrieval costs with active online access, making Cool tier optimal. The audit phase (days 91-180) requires retrieval within 3 hours. Since Archive tier standard rehydration takes up to 15 hours and High-Priority is to be avoided, the data must remain in an online tier (Hot, Cool, or Cold).
Determines which tiers are technically viable for each phase of the lifecycle based on performance and SLA constraints.
2
Calculate the duration spent in each tier to verify minimum retention period compliance.
Cool tier minimum retention is 30 days; transitioning to Cool on day 10 and then to another tier on day 90 means the data spends 80 days in Cool, which is compliant. Cold tier minimum retention is 90 days; transitioning to Cold on day 90 and deleting on day 180 means the data spends exactly 90 days in Cold, which is compliant. Archive tier minimum retention is 180 days; transitioning to Archive on day 90 and deleting on day 180 means the data spends 90 days in Archive, which would violate the policy and incur early deletion charges.
Avoids early deletion fees, which are calculated based on the duration data stays in a specific billing tier.
3
Compare storage rates for the compliance phase (days 91-180).
Cold tier offers lower storage rates than Cool tier and meets the 3-hour retrieval SLA since it provides millisecond-level online access. Transitioning to Cold on day 90 is the most cost-effective approach.
Optimizes the total cost of ownership (TCO) while satisfying all system constraints.
4
Map the transitions to the correct JSON schema definitions under lifecycle management.
Configure 'tierToCool' for 10 days, 'tierToCold' for 90 days, and 'delete' for 180 days.
Translates the logical lifecycle plan into a valid Azure Resource Manager lifecycle policy action block.

Anahtar Kavram

Azure Storage Lifecycle Management tier transitions and minimum retention constraints
Soru 428Soru

You are designing a backup solution for an Azure Virtual Machine that hosts a critical transaction database. The virtual machine is configured as follows:

* Operating system disk: Standard SSD
* Data disks: Premium SSD v2

The backup solution must meet the following requirements:
* Provide a Recovery Point Objective (RPO) of 4 hours for the data disks.
* Support instant recovery from snapshots for up to 7 days.
* Retain weekly backups for 12 months in the vault.
* Ensure that the backup data remains available even if a primary datacenter in the region experiences an outage.
* Minimize storage costs by excluding the operating system disk from the frequent backups.

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

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

Cevabı ve açıklamayı göster

Cevap: A Recovery Services vault configured with Zone-Redundant Storage (ZRS); An Enhanced backup policy with a schedule configured for every 4 hours; Selective disk backup configuration to exclude the operating system disk

Cevap

The correct configurations are: a Recovery Services vault configured with Zone-Redundant Storage (ZRS), an Enhanced backup policy with a schedule configured for every 4 hours, and selective disk backup configuration to exclude the operating system disk.
To meet the requirements, the backup design must use an Enhanced backup policy because the VM uses Premium SSD v2 data disks, which are not supported by the Standard policy. The Enhanced policy also supports sub-daily schedules (achieving the 4-hour RPO) and selective disk backup, allowing the OS disk to be excluded. Finally, configuring the Recovery Services vault with Zone-Redundant Storage (ZRS) ensures the backups survive a datacenter outage in the region.

Adım Adım Çözüm

1
Determine the required backup policy tier.
Select the Enhanced backup policy tier.
Premium SSD v2 data disks require the Enhanced backup policy tier, which also supports sub-daily (every 4 hours) backups and selective disk exclusions.
2
Determine the storage redundancy tier for the Recovery Services vault.
Select Zone-Redundant Storage (ZRS).
ZRS replicates the backup data across three availability zones in the region, ensuring availability if a primary datacenter fails.
3
Configure selective disk backup in the Enhanced policy.
Exclude the operating system disk.
This minimizes vault storage costs by backing up only the database data disks.

Anahtar Kavram

Selecting and configuring the correct Azure Backup vault tier, policy type, and redundancy to meet performance, RPO, and resilience requirements.
Soru 429Soru

A company is designing a disaster recovery and traffic routing solution for a global web application. The solution must meet the following requirements:

* Route HTTPS traffic globally with SSL termination at the routing layer.
* Provide a single connection-string listener endpoint that automatically routes to the active database during a database failover.
* Store static files in a geo-redundant storage account that allows read-only access to the secondary region.

Which set of Azure services and configurations should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Front Door for global routing, Azure SQL Database auto-failover groups, and Read-Access Geo-Redundant Storage (RA-GRS)

Cevap

Azure Front Door for global routing, Azure SQL Database auto-failover groups, and Read-Access Geo-Redundant Storage (RA-GRS)
The correct answer combines Azure Front Door, Azure SQL Database auto-failover groups, and Read-Access Geo-Redundant Storage (RA-GRS). Azure Front Door functions at Layer 7 and is capable of terminating SSL sessions. Auto-failover groups manage database replication and host a single read-write listener that redirects to the active primary database instance automatically. RA-GRS ensures data is replicated to a secondary region while permitting read-only access to that secondary endpoint.

Adım Adım Çözüm

1
Evaluate the global routing requirements for Layer 7 capabilities.
Identify that global SSL termination requires an Anycast-based Layer 7 load balancer like Azure Front Door rather than a DNS-based Layer 4 service like Traffic Manager.
Traffic Manager only handles DNS routing and cannot intercept HTTPS traffic to perform SSL decryption.
2
Determine the database failover solution.
Choose Azure SQL Database auto-failover groups to provide a single listener endpoint that automatically redirects traffic.
Manual geo-replication lacks a unified connection endpoint and requires application configuration changes during a failover.
3
Select the correct storage redundancy tier.
Select Read-Access Geo-Redundant Storage (RA-GRS).
RA-GRS keeps the primary region writeable while providing read-only endpoints in the secondary region for disaster recovery.

Anahtar Kavram

Selecting and combining Azure load balancing, database replication, and storage redundancy options based on application layer requirements and failover strategies.
Tahmini Süre:50s
Soru 430Soru

A startup is designing a containerized microservices application that will process customer orders and store logs. The application consists of three simple, stateless containers. The design must meet the following requirements:

* Minimize the administrative effort required to manage the underlying container infrastructure.
* Automatically scale the containers based on the volume of incoming HTTP requests, including scaling down to zero during idle periods.
* Segregate the telemetry and application logs from different environments (development and production) into separate workspaces to comply with data access policies.

Which combination of Azure compute hosting and log monitoring configurations should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps to host the containers, and separate Log Analytics workspaces for the development and production environments

Cevap

Azure Container Apps to host the containers, and separate Log Analytics workspaces for the development and production environments
The correct option is correct because Azure Container Apps is a fully managed serverless container service that allows scaling to zero and eliminates the operational complexity of managing Kubernetes clusters. Additionally, deploying separate Log Analytics workspaces for development and production ensures strict data isolation and compliance with environment segregation policies.

Adım Adım Çözüm

1
Evaluate the container hosting requirements to determine the appropriate compute service.
Identify that the application uses simple, stateless containers, requires minimal administrative effort, and must scale to zero.
Azure Container Apps is a serverless hosting platform that abstracts Kubernetes management while supporting container scaling to zero, whereas Azure Kubernetes Service (AKS) requires managing nodes, clusters, and control planes, creating unnecessary management overhead.
2
Evaluate the logging and compliance requirements for environment segregation.
Determine that development and production logs must be isolated in separate workspaces to meet data access policies.
Separate Log Analytics workspaces are required to guarantee logical segregation and data sovereignty between environment levels, ensuring production data access is restricted.
3
Combine the chosen compute hosting and monitoring configurations.
Recommend Azure Container Apps paired with separate Log Analytics workspaces.
This combination successfully meets all operational simplicity, scaling, and compliance requirements.

Anahtar Kavram

Selecting container hosting services based on management overhead and scaling properties, combined with environment logging isolation.
Tahmini Süre:1m 30s
Soru 431Soru

An enterprise is designing a backup storage solution for a critical financial application. The backup files will be stored in Azure Blob Storage. The storage solution must satisfy the following requirements:

* The data must be protected against a regional disaster where the primary region becomes completely unavailable.
* External auditors must be granted temporary access to the backups via Shared Access Signatures (SAS).
* The security team must be able to immediately revoke access to the SAS tokens at any time without changing the storage account keys.

Which storage redundancy configuration and access control mechanism should you recommend?

Cevabı ve açıklamayı göster

Cevap: Geo-redundant storage (GRS) and SAS tokens associated with a stored access policy

Cevap

Geo-redundant storage (GRS) and SAS tokens associated with a stored access policy
Geo-redundant storage (GRS) replicates data to a secondary Azure region, ensuring that backups are protected against a regional disaster. Associating SAS tokens with a stored access policy provides a mechanism to change the permissions, start time, or expiry time, or to revoke the SAS immediately by deleting the policy, all without rotating the primary storage account keys.

Adım Adım Çözüm

1
Evaluate the redundancy requirements for regional disaster recovery.
Determine that Geo-redundant storage (GRS) is required to replicate data to a secondary region, whereas Locally redundant storage (LRS) only replicates data within a single datacenter and cannot survive a regional outage.
To protect data against a regional disaster where the primary region is unavailable, geo-replication is necessary.
2
Evaluate the security and revocation requirements for Shared Access Signatures (SAS).
Determine that the SAS tokens must be associated with a stored access policy to support immediate revocation without rotating the primary storage account keys.
Ad-hoc SAS tokens cannot be revoked before their expiration unless the storage account keys are rotated. A stored access policy allows instant revocation by modifying or deleting the policy directly.

Anahtar Kavram

Azure Blob Storage redundancy options and Shared Access Signature (SAS) delegation using stored access policies.
Soru 432Soru

A logistics company is designing an analytical data solution on Azure to monitor fleet telemetry and optimize delivery routes. The solution must satisfy the following technical requirements:

* Ingestion: Telemetry streams from 30,00030,000 active delivery vehicles, peaking at 4,0004,000 events per second.
* Storage: Telemetry data is saved in Parquet format on Azure Data Lake Storage Gen2 (ADLS Gen2). Total storage volume is expected to reach 90 TB90\text{ TB}.
* Resilience: The stored telemetry data must remain available for read access in a secondary region if a primary datacenter outage occurs.
* Analytics: Data analysts will run ad-hoc SQL queries on the historical Parquet files to identify route inefficiencies. Queries are run infrequently and unpredictably during business hours, averaging 1010 to 1212 queries per day.
* Security: External logistics partners must be granted read-only access to specific folders in ADLS Gen2 for 9090 days. This access must be immediately revocable if the partnership ends early.
* Cost: The solution must minimize idle compute charges and administrative overhead.

Which combination of storage replication, analytical query service, and access security should you recommend?

Cevabı ve açıklamayı göster

Cevap: Azure Data Lake Storage Gen2 with Read-Access Geo-Redundant Storage (RA-GRS), Azure Synapse Analytics serverless SQL pool, and a Shared Access Signature (SAS) associated with a Stored Access Policy.

Cevap

Azure Data Lake Storage Gen2 with Read-Access Geo-Redundant Storage (RA-GRS), Azure Synapse Analytics serverless SQL pool, and a Shared Access Signature (SAS) associated with a Stored Access Policy.
The correct architecture combines Read-Access Geo-Redundant Storage (RA-GRS) to satisfy the regional resilience requirement, Azure Synapse Analytics serverless SQL pool to query the Parquet files directly with zero idle compute costs, and a Shared Access Signature (SAS) backed by a Stored Access Policy to allow immediate revocation of external partner access.

Adım Adım Çözüm

1
Analyze the storage and resilience requirements.
The requirement states that telemetry data must remain available in a secondary region during a primary datacenter outage, ruling out Locally Redundant Storage (LRS). Read-Access Geo-Redundant Storage (RA-GRS) or Geo-Zone-Redundant Storage (GZRS) is required.
LRS keeps three copies of data within a single physical location, offering no protection against a regional datacenter disaster.
2
Evaluate the analytical query model.
Since queries are ad-hoc, run only 1010 to 1212 times daily, and query Parquet files directly, Azure Synapse Analytics serverless SQL pools should be used instead of dedicated SQL pools.
A serverless SQL pool uses a pay-per-query model (billing based on data processed) and has zero idle compute costs, whereas dedicated SQL pools charge for continuous provisioned compute resource and require importing data.
3
Determine the access security strategy.
A Shared Access Signature (SAS) tied to a Stored Access Policy is selected to grant external partners read-only access for 9090 days.
An ad-hoc SAS token cannot be revoked individually before expiration without rotating the master storage account keys. Associating the SAS with a Stored Access Policy enables immediate revocation by modifying or deleting the policy.

Anahtar Kavram

Integrating cost-effective analytical querying of raw files in a data lake with geo-redundant resilience and revocable access security.
Soru 433Soru

A company is planning the backup strategy for a group of Azure Virtual Machines that run a payroll processing application. The virtual machines use Premium SSD v2 managed disks. The backup design must meet the following requirements:
- Achieve a Recovery Point Objective (RPO) of 8 hours.
- Retain backup snapshots in the local storage tier for 5 days to allow immediate recovery.
- Ensure backup data remains available if an entire availability zone in the primary region fails, without replicating data to a secondary region.

Which two configuration settings should you include in the backup design?

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

Cevabı ve açıklamayı göster

Cevap: A Recovery Services vault configured with zone-redundant storage (ZRS); An Enhanced backup policy with a schedule of every 8 hours and snapshot retention of 5 days

Cevap

To meet the requirements, you must use a Recovery Services vault configured with zone-redundant storage (ZRS) and an Enhanced backup policy configured with an 8-hour schedule and 5 days of snapshot retention.
The correct solution includes configuring a Recovery Services vault with zone-redundant storage (ZRS) to protect against availability zone failures without replicating to a secondary region, and implementing an Enhanced backup policy to support Premium SSD v2, enable an 8-hour backup frequency, and specify 5 days of snapshot retention for instant recovery.

Adım Adım Çözüm

1
Select the correct vault type and redundancy
Identify that Azure VMs require a Recovery Services vault. To survive a zone outage within the same region, ZRS is required instead of LRS.
LRS does not survive a zone outage, while ZRS replicates data across three availability zones in the primary region.
2
Determine the backup policy type
Identify that Premium SSD v2 managed disks and sub-daily backups (every 8 hours) require an Enhanced backup policy.
Standard backup policies are limited to one backup per day and do not support Premium SSD v2 or Ultra disks.
3
Configure the snapshot retention for instant restore
Set the snapshot retention in the Enhanced policy to 5 days.
Instant recovery relies on local snapshots rather than vault-tier storage, so snapshot retention must match the instant recovery requirements.

Anahtar Kavram

Designing Azure VM Backup policies with Enhanced features and appropriate vault redundancy.
Soru 434Soru

VeloMed Solutions is designing a storage architecture for patient medical images and session recordings. The primary storage region is West US 3, and the secondary region is East US. The solution must meet the following requirements:
- The primary storage must tolerate the failure of a single Availability Zone in West US 3 with zero data loss (RPO=0RPO = 0) and immediate availability (RTO=0RTO = 0).
- If a catastrophic regional disaster occurs in West US 3, read access to existing images must be available in the secondary region with an RTO of less than 15 minutes.
- The maximum acceptable data loss (RPO) for files replicated to the secondary region is 15 minutes.
- Write operations must be restored in the secondary region with an RTO of less than 1 hour during a regional disaster.
- Storage costs must be minimized while meeting all recovery objectives.

Which of the following configurations and disaster recovery procedures should the cloud architect recommend to satisfy these requirements? (Select TWO.)

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

Cevabı ve açıklamayı göster

Cevap: Deploy the storage account using Read-Access Geo-Zone-Redundant Storage (RA-GZRS).; Initiate a customer-managed failover of the storage account to the secondary region if write capabilities must be restored during a regional outage.

Cevap

The storage account must be configured with Read-Access Geo-Zone-Redundant Storage (RA-GZRS), and a customer-managed failover must be initiated to the secondary region to restore write capabilities during a regional disaster.
The solution requires high availability across availability zones in the primary region (ruling out RA-GRS) and immediate read availability in the secondary region in under 15 minutes (ruling out standard GZRS). Deploying the storage account with Read-Access Geo-Zone-Redundant Storage (RA-GZRS) satisfies these parameters. Furthermore, because write operations cannot be routed to a secondary geo-redundant endpoint under normal or outage states without changing the account configuration, initiating a customer-managed failover is the only valid way to restore write capabilities within the 1-hour RTO constraint.

Adım Adım Çözüm

1
Analyze the primary region high availability requirements.
The requirement for zero data loss and immediate availability during a zone outage in West US 3 necessitates zone redundancy in the primary region (ZRS or GZRS/RA-GZRS). Locally redundant options (LRS/GRS/RA-GRS) are ruled out.
LRS does not replicate data across availability zones.
2
Analyze the disaster recovery read requirements.
The 15-minute RTO for reads during a regional outage requires immediate read availability in the secondary region. Standard GZRS does not expose a readable secondary endpoint unless a failover is completed, which would exceed the time limit. Therefore, Read-Access Geo-Zone-Redundant Storage (RA-GZRS) is required.
RA-GZRS provides a secondary read-only endpoint that is immediately available.
3
Analyze the write restoration requirements.
Writing directly to a secondary geo-redundant endpoint is impossible. To restore writes in the secondary region within 1 hour, a customer-managed failover must be triggered, which changes the DNS to point writes to the secondary region (converting the storage account to LRS in the process).
Only a failover can grant write access to the replicated data in the secondary region.

Anahtar Kavram

Azure Storage Replication and Customer-Managed Failover Mechanics
Soru 435Soru

A startup needs to host a simple, containerized web API. The solution must support automated scaling, require zero server or cluster management overhead, and provide a secure, private registry to store the container images. Which two services should you recommend?

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

Cevabı ve açıklamayı göster

Cevap: Azure Container Apps; Azure Container Registry

Cevap

Azure Container Apps and Azure Container Registry
Azure Container Apps offers serverless container execution that scales automatically, fulfilling the requirement for zero cluster management overhead. Azure Container Registry provides a secure, private repository to manage and store container images.

Adım Adım Çözüm

1
Analyze the hosting requirements.
The web API is a simple containerized workload that requires automatic scaling and zero cluster management overhead.
This rules out services requiring manual server management or Kubernetes infrastructure administration.
2
Select the appropriate container hosting service.
Azure Container Apps is selected because it provides serverless hosting for containers without requiring cluster configuration or management.
Azure Container Apps is optimized for simple microservices and APIs needing serverless scaling.
3
Select the secure image storage service.
Azure Container Registry is selected to securely store the container images in a private registry.
Azure Container Registry is the standard managed private registry service in Azure.

Anahtar Kavram

Selecting managed container hosting and private image storage solutions to minimize administrative overhead.
Soru 436Soru

An organization is deploying a critical production web application on Azure Virtual Machines. The application requires a compute service level agreement (SLA) of 99.99% for virtual machine uptime.

Which deployment strategy should you recommend to meet the SLA requirement?

Cevabı ve açıklamayı göster

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

Cevap

Deploy at least two virtual machines across two or more Availability Zones in the same Azure region.
Deploying at least two virtual machines across two or more Availability Zones in the same Azure region provides a 99.99% VM uptime SLA. Azure guarantees this level of availability when VMs are distributed across multiple zones because it protects the application from the failure of a single datacenter.

Adım Adım Çözüm

1
Identify the target SLA requirement.
The business requires a compute SLA of 99.99%.
This establishes the minimum availability target that the design must satisfy.
2
Evaluate Azure VM deployment options and their associated SLAs.
Availability Zones offer a 99.99% SLA, Availability Sets offer a 99.95% SLA, and single VMs offer a 99.9% SLA.
Comparing the SLA guarantees of different Azure high availability features helps select the appropriate strategy.
3
Select the option that meets the 99.99% SLA requirement.
Deploying at least two VMs across two or more Availability Zones is the only option that guarantees a 99.99% SLA.
This configuration provides protection against zone-level failures and meets the high availability target.

Anahtar Kavram

Azure Virtual Machine High Availability SLAs
Soru 437Soru

An enterprise is designing a telemetry and analytical storage solution on Azure. The solution must support ad-hoc exploratory queries on 5 TB5 \text{ TB} of daily log files in CSV and Parquet formats stored in Azure Data Lake Storage Gen2 (ADLS Gen2). The queries will be run sporadically throughout the day.

The design must meet the following requirements:
- Minimize provisioning and compute cost when no queries are running.
- Ensure that the primary storage account survives a regional datacenter outage.
- Secure access to ADLS Gen2 using Shared Access Signatures (SAS) that can be easily revoked if compromised.

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

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

Cevabı ve açıklamayı göster

Cevap: Configure the ADLS Gen2 storage account to use Geo-redundant storage (GRS).; Use Azure Synapse Analytics serverless SQL pools to query the data.

Cevap

Configure the Azure Data Lake Storage Gen2 storage account to use Geo-redundant storage (GRS), and use Azure Synapse Analytics serverless SQL pools to query the data.
Using serverless SQL pools in Azure Synapse Analytics is the most cost-effective choice for sporadic, ad-hoc queries because it uses a pay-per-query model and has no idle resources to pay for. Configuring Geo-redundant storage (GRS) ensures that the data is replicated to a secondary region, providing protection against regional outages.

Adım Adım Çözüm

1
Evaluate query requirement and cost profile.
Identify that the query patterns are ad-hoc and sporadic, meaning a serverless, pay-per-query model (serverless SQL pools) is much more cost-effective than a continuously running cluster (dedicated SQL pools).
This minimizes compute costs when no queries are running, addressing the first requirement.
2
Evaluate storage redundancy options for disaster recovery.
Determine that Locally redundant storage (LRS) is insufficient as it is bound to a single datacenter, whereas Geo-redundant storage (GRS) provides secondary-region replication.
This guarantees storage availability during a regional datacenter outage, addressing the second requirement.
3
Analyze secure token creation best practices.
Identify that generating a long-lived SAS directly linked to account keys lacks an easy revocation mechanism. Best practice demands stored access policies for easy revocation.
This ensures access can be easily revoked, addressing the security requirement.

Anahtar Kavram

Selecting cost-effective serverless analytics services and regional storage replication strategies on Azure.
Soru 438Soru

A retail company is designing the storage infrastructure for a new cloud-native order processing system. The system will store transaction logs in Azure Blob Storage. The storage solution must meet the following requirements:

- The data must be resilient to a datacenter outage within the primary region with zero data loss.
- The data must be replicated to a secondary region located at least 300 miles away.
- Analysts in the secondary region must be able to run read-only reporting queries against the replicated data at any time without impacting performance on the primary region and without initiating a storage account failover.

Which two configurations or actions should you recommend to meet the storage requirements? (Choose 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-Zone-Redundant Storage (RA-GZRS).; Direct the reporting applications to read data from the secondary endpoint of the storage account.

Cevap

To meet the requirements, you must configure the storage account to use Read-Access Geo-Zone-Redundant Storage (RA-GZRS) and direct the reporting applications to read data from the secondary endpoint of the storage account.
The correct options are configuring the storage account to use Read-Access Geo-Zone-Redundant Storage (RA-GZRS) and directing the reporting applications to read data from the secondary endpoint. RA-GZRS ensures zone redundancy in the primary region (protecting against a single datacenter outage) and replicates the data to a secondary region. The secondary endpoint allows read-only query access without initiating a failover.

Adım Adım Çözüm

1
Analyze primary region redundancy requirements.
Since the data must survive a datacenter outage in the primary region with zero data loss, the primary replication must use Zone-Redundant Storage (ZRS), which replicates data across availability zones.
Locally Redundant Storage (LRS) replicates data within a single datacenter, making it vulnerable to a datacenter outage.
2
Analyze secondary region replication requirements.
The replication must copy data to a secondary region, which requires Geo-Redundant replication. Combining zonal redundancy in the primary region with geo-redundancy yields Geo-Zone-Redundant Storage (GZRS).
GZRS provides both zone-level resilience in the primary region and region-level resilience in the secondary region.
3
Analyze access requirements for the secondary region.
The reporting queries need read-only access to the secondary region without initiating failover. This requires Read-Access Geo-Zone-Redundant Storage (RA-GZRS) and routing queries to the secondary endpoint.
Standard GZRS only provides access to the secondary region after a customer-managed or Microsoft-managed failover is initiated.

Anahtar Kavram

Selecting the appropriate Azure Storage redundancy tier (LRS vs ZRS vs GRS vs GZRS vs RA-GRS vs RA-GZRS) based on regional, zonal, write/read access, and data loss constraints.
Soru 439Soru

A logistics enterprise plans to deploy a high-performance document processing system on Azure. The system requires SMB file shares hosted on the Premium tier of Azure Files to meet sub-millisecond metadata latency requirements. The storage configuration must remain resilient and available if a single physical datacenter in the primary region experiences a power outage. Which storage redundancy configuration should you recommend?

Cevabı ve açıklamayı göster

Cevap: Zone-redundant storage (ZRS)

Cevap

Zone-redundant storage (ZRS)
Zone-redundant storage (ZRS) synchronously replicates data across three separate physical datacenters (Availability Zones) in the primary region. This allows the system to survive a datacenter outage. Because Premium Azure Files supports only LRS and ZRS, Zone-redundant storage (ZRS) is the only valid configuration that satisfies both the resiliency requirement and the latency constraint.

Adım Adım Çözüm

1
Analyze performance and protocol requirements.
Premium Azure Files is required to meet SMB protocol and sub-millisecond latency requirements.
Standard Azure Files does not guarantee sub-millisecond latencies, so the Premium tier must be selected.
2
Evaluate availability requirements against primary region datacenter failures.
Locally-redundant storage (LRS) is ruled out because it cannot survive a single datacenter outage.
LRS stores all replicas within one physical datacenter. Zone-redundancy is needed to survive zone/datacenter failures.
3
Check supported redundancy tiers for Premium Azure Files.
Premium Azure Files only supports Locally-redundant storage (LRS) and Zone-redundant storage (ZRS).
Geo-redundant configurations like GRS and GZRS are not supported for Premium tier file shares.

Anahtar Kavram

Azure Storage redundancy options and tier limitations
Tahmini Süre:1m 30s
Soru 440Soru

A company is planning to migrate a legacy on-premises SQL Server database to Azure. The database has the following requirements:
* Requires the execution of Common Language Runtime (CLR) integration assemblies and SQL Server Agent.
* Requires operating system-level access to the database host to install and run a custom security agent.
* The database transaction log files must be stored on a disk configuration that guarantees at least 15,00015,000 IOPS and sub-millisecond write latency.

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

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

Cevabı ve açıklamayı göster

Cevap: Deploy SQL Server on Azure Virtual Machines for the database tier; Configure Premium SSD or Ultra Disk storage for the database transaction logs

Cevap

Deploy SQL Server on Azure Virtual Machines for the database tier and configure Premium SSD or Ultra Disk storage for the database transaction logs.
The correct design uses SQL Server on Azure Virtual Machines because the database requires operating system-level access to install custom security agents. Additionally, the storage subsystem for the database transaction logs must utilize Premium SSD or Ultra Disk to support the 15,00015,000 IOPS and sub-millisecond write latency requirements.

Adım Adım Çözüm

1
Evaluate the database host access requirement.
The requirement for operating system-level access to run a custom security agent rules out fully managed Azure SQL offerings (such as Azure SQL Database and Azure SQL Database Managed Instance).
Managed database services abstract the underlying OS, preventing users from installing custom third-party agents on the host operating system.
2
Determine the database deployment model.
SQL Server on Azure Virtual Machines must be selected.
SQL Server on Azure VMs provides full administrative control over the operating system, allowing custom agents to be installed while still supporting legacy SQL Server features like SQL Server Agent and CLR.
3
Analyze the storage performance requirement for the transaction logs.
Standard storage tiers are eliminated, and high-performance tiers (Premium SSD or Ultra Disk) are selected.
A performance level of 15,00015,000 IOPS and sub-millisecond write latency requires Premium SSD or Ultra Disk storage. Standard HDD and Standard SSD storage options are limited by IOPS and throughput caps that make them unsuitable for high-performance transaction logs.

Anahtar Kavram

Selecting relational database deployment models based on administrative control and storage performance requirements.
ÖncekiSayfa 22 / 60Sonraki
Tüm alıştırma soruları — Microsoft Azure Solutions Architect (AZ-305) | Examkin