All practice questions

1198 questions

Question 381Question

A logistics enterprise is designing the storage architecture for a high-performance inventory tracking system. The system requires Azure Premium Block Blob storage to handle high-frequency write operations with sub-millisecond latency. The architecture must meet the following requirements:

- The storage must survive the loss of an entire datacenter (Availability Zone) within the primary region with zero data loss (RPO=0RPO = 0).
- A replica of the data must be maintained in a secondary region to support disaster recovery.
- A reporting application in the secondary region must have continuous read access to the replicated data.
- The system must support writing test data directly to the secondary region's storage endpoint during simulated disaster recovery drills without initiating a failover of the primary storage account.

Which storage design should you recommend?

Show answer & explanation

Answer: Create a Premium Block Blob storage account configured with Zone-Redundant Storage (ZRS) in the primary region, and use Azure Blob Storage Object Replication to replicate data to a separate Premium Block Blob storage account in the secondary region.

Answer

Create a Premium Block Blob storage account configured with Zone-Redundant Storage (ZRS) in the primary region, and use Azure Blob Storage Object Replication to replicate data to a separate Premium Block Blob storage account in the secondary region.
The correct design uses a Premium Block Blob storage account with Zone-Redundant Storage (ZRS) to meet the sub-millisecond latency and zone-redundancy requirements. Since Premium Block Blobs do not natively support geo-redundancy (GRS/GZRS), Azure Blob Storage Object Replication is configured to copy the data asynchronously to a separate Premium storage account in the secondary region. Because the destination is a distinct, independent storage account, it supports continuous read operations for reporting and allows direct write access for test data without requiring a storage account failover.

Step-by-Step Solution

1
Determine the performance and primary redundancy requirements.
Premium Block Blob storage configured with Zone-Redundant Storage (ZRS) is selected.
Sub-millisecond latency requires the Premium Block Blob performance tier. Surviving a zone failure with zero data loss (RPO=0RPO = 0) in the primary region requires ZRS, which replicates data synchronously across three availability zones.
2
Evaluate native geo-redundancy options for Premium Block Blobs.
Native GRS, GZRS, and their read-access variants are ruled out.
Azure Premium Block Blob accounts (blockBlobStorage) do not support native geo-redundancy options; they are restricted to LRS and ZRS.
3
Identify a replication mechanism that allows writes to the secondary target without failover.
Use Azure Blob Storage Object Replication between the primary ZRS account and a destination Premium account in the secondary region.
Object Replication replicates data block blobs asynchronously between two distinct storage accounts. Because the destination is a standalone storage account, the reporting application can continuously read from it, and test data can be written directly to it during drills without impacting the primary account or requiring a failover.

Key Concept

Azure Storage replication and service limits for Premium Block Blobs.
Question 382Question

A company is designing a storage solution for storing critical transaction records in Azure Blob Storage. The solution must meet the following requirements:
- Data must be replicated synchronously across three availability zones in the primary region.
- In the event of a regional outage in the primary region, the application must have immediate read-only access to the replicated data in the secondary region without waiting for a failover to be initiated.
- In the event of a prolonged primary region outage, the application must be able to resume write operations to the same primary endpoint URI after a failover is executed.

Which two options should you include in the storage design to meet the requirements?

Select all that apply

Show answer & explanation

Answer: Configure the storage account to use read-access geo-zone-redundant storage (RA-GZRS).; Ensure that after a customer-managed failover is executed, the storage account's redundancy type is converted to locally redundant storage (LRS) and the secondary read-only endpoint is removed.

Answer

Configure the storage account to use read-access geo-zone-redundant storage (RA-GZRS) and ensure that after a customer-managed failover is executed, the storage account's redundancy type is converted to locally redundant storage (LRS) and the secondary read-only endpoint is removed.
To meet the requirements, the storage account must be configured for read-access geo-zone-redundant storage (RA-GZRS). This option replicates data synchronously across three availability zones in the primary region (meeting the zone-redundancy requirement) and asynchronously replicates to a secondary region, where the read-access feature allows the application to query the secondary endpoint immediately. When a customer-managed failover is executed to resume write operations on the primary endpoint URI, the secondary region is promoted to the new primary region, the storage redundancy type is automatically converted to locally redundant storage (LRS), and the secondary endpoint is removed.

Step-by-Step Solution

1
Analyze the primary region redundancy requirement.
Synchronous replication across three availability zones requires zone-redundant storage (ZRS) or geo-zone-redundant storage (GZRS). Locally redundant storage (LRS) and geo-redundant storage (GRS) do not satisfy this as they replicate within a single facility.
This filters out options like RA-GRS which only provide local redundancy in the primary region.
2
Analyze the secondary region read access requirement.
Immediate read-only access to the secondary region without initiating a failover requires read-access enabled on the geo-redundancy option (RA-GZRS).
This ensures the application can query the secondary endpoint directly during normal operations or primary outages.
3
Evaluate write capabilities during a primary region outage.
The secondary endpoint is read-only. Writes are not allowed directly to the secondary endpoint. Resuming write operations requires executing a customer-managed failover to promote the secondary region to the new primary region.
This identifies that writing directly to the secondary endpoint without failover is impossible.
4
Determine the state of the storage account post-failover.
After failover is completed, the storage account's redundancy type in the new primary region automatically becomes LRS, and the secondary endpoint is removed.
This defines the correct post-failover lifecycle and the need to manually reconfigure geo-redundancy if required.

Key Concept

Azure Storage Account Redundancy and Customer-Managed Failover Mechanics
Estimated Time:3m 0s
Question 383Question

A software-as-a-service (SaaS) provider is designing a privileged access solution for 10 operations engineers who need temporary, approved Contributor access to a production Azure subscription. The design must enforce the principle of least privilege, require multi-factor authentication (MFA) for role activation, and ensure that access eligibility automatically expires after 180 days. Which of the following identity governance designs should you recommend?

Show answer & explanation

Answer: Configure a Microsoft Entra ID security group containing the operations engineers, and assign the group as eligible for the Contributor role in Privileged Identity Management (PIM) with approval and MFA requirements enabled in the PIM role settings.

Answer

Configure a Microsoft Entra ID security group containing the operations engineers, and assign the group as eligible for the Contributor role in Privileged Identity Management (PIM) with approval and MFA requirements enabled in the PIM role settings.
The correct design uses a Microsoft Entra ID security group to aggregate the operations engineers, satisfying the best practice of avoiding direct user assignments. By assigning this group as eligible (not active) for the Contributor role in Privileged Identity Management (PIM), access is kept just-in-time. The requirements for MFA and approval are enforced natively in the PIM role activation settings, and the 180-day limitation is configured via the assignment duration.

Step-by-Step Solution

1
Group creation and member addition
Create a security group in Microsoft Entra ID and add the 10 operations engineers to the group, enabling scalable and consolidated management.
Assigning permissions to a group instead of individual users aligns with Azure identity governance best practices.
2
Configure Privileged Identity Management (PIM) settings
Within PIM for Azure resources, configure the Contributor role settings to require manager approval for activation, require MFA during activation, and enforce a maximum duration.
This establishes just-in-time access constraints that satisfy the business requirements for MFA and approval.
3
Assign the security group to the role in PIM
Assign the security group as eligible for the Contributor role at the subscription scope with a maximum membership duration of 180 days.
This ensures the privileged access is temporary, can be activated only when needed, and automatically expires after the specified period.

Key Concept

Privileged Identity Management (PIM) Eligible Assignments and Group-Based Governance
Estimated Time:1m 30s
Question 384Question

An organization needs to design a disaster recovery solution to the Azure East US region for an on-premises VMware virtual machine named `SQL-VM1`. The VM has an OS disk and a single Premium SSD data disk. The write churn on the data disk is 8 MB/s8 \text{ MB/s}, and the total write churn for the entire VM is 10 MB/s10 \text{ MB/s}. The solution must achieve a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 1 hour. Which replication solution should you design to meet these requirements?

Show answer & explanation

Answer: Azure Site Recovery replication

Answer

Azure Site Recovery replication
The correct option is Azure Site Recovery replication because the VM's disk write churn (8 MB/s8 \text{ MB/s}) and total VM write churn (10 MB/s10 \text{ MB/s}) are well below the Azure Site Recovery limit of 20 MB/s20 \text{ MB/s} per disk and 54 MB/s54 \text{ MB/s} per VM. ASR supports near-continuous replication, making it the ideal choice to meet the 15-minute RPO and 1-hour RTO.

Step-by-Step Solution

1
Identify the source environment and requirements.
The workload is an on-premises VMware VM requiring replication to Azure East US with an RPO of 15 minutes and RTO of 1 hour.
To select the appropriate disaster recovery service based on source type and performance metrics.
2
Evaluate the disk metrics against Azure Site Recovery limits.
The VM's single data disk churn is 8 MB/s8 \text{ MB/s} and total VM churn is 10 MB/s10 \text{ MB/s}.
Azure Site Recovery standard replication supports up to 20 MB/s20 \text{ MB/s} per disk and 54 MB/s54 \text{ MB/s} total VM churn, confirming ASR is compatible with this workload.
3
Compare candidate services against RPO/RTO targets.
Azure Site Recovery provides continuous replication capable of meeting sub-hour RTO and low RPO targets, unlike backup-centric options.
To ensure the chosen solution satisfies both service limits and business recovery objectives.

Key Concept

Selecting Azure Site Recovery for workloads meeting supported disk churn limits and disaster recovery targets
Estimated Time:1m 0s
Question 385Question

A manufacturing enterprise operates globally and needs to design a data platform on Azure to process and analyze telemetry data from industrial IoT sensors. The platform must meet the following technical specifications:
- Ingestion rate: A continuous stream of 1500015{}000 events per second.
- Volume: A total storage capacity of 200 TB200\text{ TB} of historical sensor data stored in Parquet format.
- Query patterns: Data analysts execute ad-hoc, exploratory SQL queries on the historical Parquet files approximately 88 to 1212 times per week. The query latency must be under 45 seconds45\text{ seconds}.
- Resilience: The storage solution must remain available and readable in a secondary region in the event of a primary region outage.
- Cost and Operations: You must minimize operational overhead and ensure you do not pay for idle compute resources.

Which combination of Azure compute and storage configurations should you recommend?

Show answer & explanation

Answer: Azure Synapse Analytics serverless SQL pools querying an Azure Data Lake Storage Gen2 account configured with Read-Access Geo-Redundant Storage (RA-GRS)

Answer

Azure Synapse Analytics serverless SQL pools querying an Azure Data Lake Storage Gen2 account configured with Read-Access Geo-Redundant Storage (RA-GRS)
The configuration utilizing Azure Synapse Analytics serverless SQL pools and Azure Data Lake Storage Gen2 with Read-Access Geo-Redundant Storage (RA-GRS) satisfies all requirements. Serverless SQL pools charge on an on-demand basis per TB of data processed, aligning perfectly with low-frequency, ad-hoc queries (88 to 1212 times per week) and eliminating compute idle costs. RA-GRS provides the necessary regional disaster resilience by making data readable in the secondary region in the event of a primary region outage.

Step-by-Step Solution

1
Analyze the query frequency and compute model requirements.
An on-demand serverless SQL pool is selected instead of a dedicated SQL pool.
Queries are run infrequently (88 to 1212 times per week). Dedicated SQL pools would incur continuous costs for idle compute, whereas serverless SQL pools only charge per query, minimizing cost and operational overhead.
2
Analyze the storage redundancy and resilience requirements.
Read-Access Geo-Redundant Storage (RA-GRS) is selected instead of Locally Redundant Storage (LRS).
LRS is not resilient to regional outages. RA-GRS copies the data to a secondary region and ensures it remains readable even if the primary region fails.
3
Evaluate security and credentials constraints.
Direct long-lived ad-hoc SAS tokens are rejected.
Using a 3-year3\text{-year} ad-hoc SAS token introduces security risks and fails to utilize secure integration practices such as managed identities.

Key Concept

Selecting the optimal serverless query compute and geo-redundant storage integration to support cost-effective ad-hoc analytics with regional resilience.
Estimated Time:2m 30s
Question 386Question

A healthcare provider is designing the disaster recovery architecture for its patient management application. The database layer has the following requirements:
- Must support SQL Server Agent jobs to schedule nightly data synchronization.
- Must support cross-database queries between the patient records database and the billing database.
- Must support automatic failover to a secondary Azure region, utilizing a single connection endpoint that automatically redirects traffic without requiring application reconfiguration.
- Must ensure that all databases are isolated from the public internet, using private network paths for all communication.

Which database deployment and high availability/disaster recovery (HA/DR) configuration should you recommend?

Show answer & explanation

Answer: Configure Azure SQL Managed Instances in a failover group across two regions, establish global virtual network peering between the virtual networks hosting the instances, and configure the application to connect using the failover group's read-write listener.

Answer

Configure Azure SQL Managed Instances in a failover group across two regions, establish global virtual network peering between the virtual networks hosting the instances, and configure the application to connect using the failover group's read-write listener.
The correct solution uses Azure SQL Managed Instance to support SQL Server Agent and cross-database queries. Failover groups provide automatic failover and a single read-write listener endpoint, and global virtual network peering ensures private network communication between the regions without exposing endpoints to the public internet.

Step-by-Step Solution

1
Analyze database compatibility requirements.
SQL Server Agent and cross-database queries require Azure SQL Managed Instance or SQL Server on Azure VMs, ruling out Azure SQL Database single databases and Elastic Pools.
Azure SQL Database single databases and Elastic Pools do not natively support SQL Server Agent or cross-database queries.
2
Evaluate high availability and disaster recovery requirements.
Failover groups are required to support automatic failover with a single connection listener endpoint.
Active geo-replication only supports manual failover and does not provide a single connection listener endpoint.
3
Check network security and storage performance requirements.
Virtual network peering must be used for private network paths, and high-performance disks (Premium SSD or Ultra Disk) are required for database transaction logs to prevent write bottlenecks.
Standard HDD is unsuitable for transaction logs due to IOPS and throughput limitations, and the solution must avoid public internet exposure.

Key Concept

Selecting the appropriate Azure SQL relational database deployment option and configuring failover groups with network isolation to satisfy enterprise compatibility, performance, and recovery constraints.
Question 387Question

Aventis Pharmaceuticals is designing a secure access and identity solution for its Microsoft Entra ID tenant. The tenant will synchronize identities from an on-premises Active Directory Domain Services (AD DS) environment.

The solution must meet the following requirements:
- Enforce multi-factor authentication (MFA) for all administrative users using Conditional Access policies.
- Ensure that administrators can access the tenant even if a misconfiguration or outage affects the MFA service.
- Prevent administrators from having standing access to highly privileged roles.
- Implement the simplest possible hybrid identity authentication model that requires no on-premises server infrastructure for credential validation.

Which two of the following components should you include in the identity and authentication design? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: A dedicated, cloud-only emergency access account that is explicitly excluded from the Conditional Access policy; Password Hash Synchronization (PHS) to provide hybrid identity authentication

Answer

Include a dedicated, cloud-only emergency access account excluded from the Conditional Access policy, and use Password Hash Synchronization (PHS) to provide hybrid identity authentication.
To satisfy the requirements, the design must exclude a dedicated emergency access account from the Conditional Access policy enforcing MFA to prevent lockouts. It must also utilize Password Hash Synchronization (PHS) because it is the simplest hybrid authentication method and requires no on-premises infrastructure for validation, processing authentications entirely in the cloud.

Step-by-Step Solution

1
Analyze the resiliency requirement for administrative access during MFA outages.
Identify that an emergency access (break-glass) account must be created as a cloud-only account and excluded from Conditional Access policies that enforce MFA.
This prevents administrative lockout in the event of an MFA service outage or misconfiguration.
2
Evaluate the hybrid identity authentication requirements.
Select Password Hash Synchronization (PHS) as the authentication mechanism.
PHS is the simplest hybrid authentication option, validating credentials in the cloud and requiring no on-premises server infrastructure for authentication.
3
Verify options against the requirement to prevent standing access.
Ensure that administrative roles are configured using eligible assignments rather than permanent active assignments.
Eligible assignments require users to request activation for a limited duration, enforcing just-in-time access.

Key Concept

Microsoft Entra ID hybrid authentication and Conditional Access design resiliency
Estimated Time:1m 30s
Question 388Question

You are designing a backup solution for a cluster of Azure Virtual Machines that host a critical manufacturing execution system (MES). The virtual machines are configured as Trusted Launch VMs.

The solution must meet the following requirements:
- Backups must be performed every 4 hours to minimize data loss.
- In the event of a file deletion, you must be able to perform instant recoveries from snapshots for files deleted within the last 7 days.
- Backups must be resilient to zone-level outages.
- Backups older than 90 days must be automatically moved to a cost-effective archive storage tier.

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

Select all that apply

Show answer & explanation

Answer: Configure a Recovery Services vault with Zone-Redundant Storage (ZRS) redundancy.; Create an Enhanced backup policy with a schedule of every 4 hours and instant restore retention set to 7 days.

Answer

Configure a Recovery Services vault with Zone-Redundant Storage (ZRS) redundancy and create an Enhanced backup policy with a schedule of every 4 hours and instant restore retention set to 7 days.
To design a zone-resilient backup for Trusted Launch VMs with a 4-hour frequency, 7-day instant restore capability, and archive support, you must use a Recovery Services vault configured with Zone-Redundant Storage (ZRS) and apply an Enhanced backup policy.

Step-by-Step Solution

1
Analyze VM and policy capabilities requirements.
Trusted Launch VMs, 4-hour RPO, 7-day instant restore retention, and Archive tiering are required.
These parameters determine if a Standard or Enhanced backup policy is needed.
2
Evaluate backup policy tiers.
Enhanced backup policy is selected.
Standard backup policies do not support multiple backups per day, instant restore retention beyond 5 days, or Trusted Launch VMs.
3
Determine vault type and storage redundancy.
Recovery Services vault with ZRS is selected.
Azure VMs must be backed up to Recovery Services vaults. Zone-Redundant Storage (ZRS) is required to meet the resilience requirement against zone outages.

Key Concept

Azure Backup vault types, policy tiers (Standard vs Enhanced), and storage redundancy options for Virtual Machines.
Question 389Question

Your company is designing a governance solution for a multi-subscription Azure environment. A security team requires a custom RBAC role named 'Network Security Operator' to manage network security groups (NSGs) across all subscriptions in a specific department. These subscriptions are organized under a single department-level management group. You need to implement the custom role following the principle of least privilege. What is the correct sequence of steps to configure and assign this custom role?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

Retrieve the management group resource ID, define the custom role JSON with AssignableScopes set to the management group ID, register the custom role in the tenant, and then assign the role to the Entra ID group at the management group scope.
The correct sequence requires obtaining the management group resource ID first to populate the AssignableScopes property in the JSON file. Next, the JSON file is defined with the necessary network security group actions and the specific assignable scope. After defining the JSON, the custom role is registered in the Azure tenant. Once registered, it is assigned to the security team's Microsoft Entra ID group at the department-level management group scope, enabling least-privilege administrative inheritance across all descendant subscriptions.

Step-by-Step Solution

1
Retrieve the resource ID of the department-level management group.
You obtain the fully qualified Azure Resource Manager ID of the management group.
Custom roles require explicit resource IDs in their AssignableScopes list. The ID is necessary to construct the JSON file.
2
Create a custom role JSON definition with required NSG permissions and set AssignableScopes to the management group's resource ID.
A local JSON file containing the role's permissions and scope restrictions is prepared.
Defining the role's capabilities and assignable boundaries is a prerequisite to registering the role.
3
Register the custom role in the Azure tenant by importing the JSON definition.
The custom role is created and becomes globally visible in the Entra ID tenant.
The role definition must exist in the Azure Resource Manager control plane before any assignments can be made.
4
Assign the registered custom role to the security team's Microsoft Entra ID group at the department-level management group scope.
The group's members inherit the Network Security Operator permissions across all subscriptions in the management group.
Following the principle of least privilege and best practices, permissions are assigned to a group at the highest appropriate hierarchy level (management group) for inheritance.

Key Concept

Azure Custom RBAC Role Lifecycle and Scope Inheritance
Question 390Question

An enterprise is planning their Azure load balancing and high availability architecture. You must select the appropriate routing solutions for their workloads. Match each Azure service to its primary traffic routing mechanism and scope.

Click a left item, then click its matching right item

Items

Azure Traffic Manager
Azure Front Door
Azure Application Gateway

Matches

Show answer & explanation

Answer

Azure Traffic Manager matches DNS-based routing; Azure Front Door matches global Anycast-based HTTP/HTTPS routing; Azure Application Gateway matches regional virtual network-based routing.
The correct matches align each service with its unique operational layer and scope. Azure Traffic Manager relies on DNS to resolve endpoints globally, Azure Front Door leverages Anycast TCP at the edge for global web application delivery, and Azure Application Gateway manages regional, virtual network-integrated Layer 7 traffic routing.

Step-by-Step Solution

1
Identify the routing mechanism of Azure Traffic Manager.
Azure Traffic Manager operates at the DNS level, returning the IP address of the preferred endpoint directly to the client.
This matches the definition of a DNS-based global traffic router.
2
Identify the routing mechanism of Azure Front Door.
Azure Front Door terminates client HTTP/HTTPS requests at edge sites using Anycast TCP, optimizing global paths.
This matches the definition of an Anycast TCP global HTTP/HTTPS router.
3
Identify the routing mechanism of Azure Application Gateway.
Azure Application Gateway acts as a regional reverse proxy within a specific virtual network, routing by URL paths.
This matches the definition of a regional Layer 7 load balancer.

Key Concept

Distinction between DNS-based global routing, Anycast-based global routing, and regional Layer 7 load balancing in Azure.
Estimated Time:1m 0s
Question 391Question

An energy grid utility company deploys its core telemetry monitoring application to an Azure SQL Managed Instance in the East US region. To design a disaster recovery solution in the West US region, you must satisfy the following requirements:
- The Recovery Time Objective (RTO) must be less than 30 minutes.
- The Recovery Point Objective (RPO) must be less than 15 minutes.
- Client applications must automatically reconnect after a failover without requiring connection string modifications.
- Read-heavy reporting workloads must be offloaded to the secondary region to avoid impacting primary write operations.

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

Select all that apply

Show answer & explanation

Answer: Create an auto-failover group containing the primary and secondary SQL Managed Instances.; Configure the reporting applications to connect using the read-only listener endpoint of the auto-failover group.

Answer

To meet the requirements, you should create an auto-failover group containing the primary and secondary SQL Managed Instances, and configure reporting applications to connect using the read-only listener endpoint of the auto-failover group.
Creating an auto-failover group provides the replication and traffic routing mechanism required for Azure SQL Managed Instance. It generates a read-write listener for primary write operations and a read-only listener to offload query workloads to the secondary instance in the West US region. This setup satisfies both RTO and RPO requirements and avoids application configuration changes upon failover.

Step-by-Step Solution

1
Determine replication capability of Azure SQL Managed Instance.
Identify that Azure SQL Managed Instance does not support database-level active geo-replication and instead requires instance-level auto-failover groups for disaster recovery replication.
This ensures the correct deployment model is chosen for the database tier.
2
Address automatic client redirection requirements.
Establish listener endpoints by configuring an auto-failover group.
The listener endpoints automatically point to the new primary instance after a failover, eliminating the need to update application connection strings.
3
Offload read-only reporting queries.
Use the read-only listener endpoint to route reporting queries to the geo-secondary replica.
This prevents read workloads from consuming resources on the primary write database.

Key Concept

Azure SQL Managed Instance supports high availability and disaster recovery across regions using auto-failover groups, which provide separate read-write and read-only listener endpoints for seamless client redirection.
Question 392Question

Your enterprise has a management group hierarchy. You need to design a governance solution that delegates the ability to manage Azure resource locks across all subscriptions under a specific management group to an operations team. The solution must meet the following requirements:

* Ensure operations team members can only manage locks during authorized maintenance windows.
* Minimize administrative overhead as members of the operations team change.
* Follow the principle of least privilege.

Which two configurations should you include in the design?

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra ID security group that contains the operations team members.; Configure an eligible role assignment for the security group at the management group scope using Microsoft Entra Privileged Identity Management (PIM) for Azure resources.

Answer

To meet the requirements, you should create a Microsoft Entra ID security group containing the operations team members, and configure an eligible role assignment for this security group at the management group scope using Microsoft Entra Privileged Identity Management (PIM) for Azure resources.
Creating a Microsoft Entra ID security group minimizes administrative overhead because you can manage team membership without updating role assignments. Configuring an eligible role assignment via Microsoft Entra Privileged Identity Management (PIM) for Azure resources ensures that the group members only obtain the required permissions during maintenance windows (just-in-time access) rather than having permanent privileges, adhering to the principle of least privilege.

Step-by-Step Solution

1
Identify the requirement to minimize administrative overhead for team membership changes.
Determine that permissions must be assigned to a Microsoft Entra ID group rather than individual user accounts.
Using groups allows team membership to be managed dynamically without modifying the underlying role assignments.
2
Identify the requirement for time-bound access during authorized maintenance windows.
Determine that Privileged Identity Management (PIM) must be used to provide just-in-time (JIT) access, specifying eligible assignments rather than permanently active assignments.
Eligible assignments require users to explicitly activate their role, limiting exposure and enforcing the principle of least privilege.
3
Select the correct combination of options representing these two design decisions.
Select the option to create a security group and the option to configure an eligible assignment using PIM for Azure resources.
Combining group-based assignments with PIM eligible roles satisfies all design constraints.

Key Concept

Delegating administrative privileges using Microsoft Entra ID groups and just-in-time access via Privileged Identity Management (PIM) at the management group scope.
Question 393Question

You are designing a compute solution for a new microservices application in Azure. The application must support event-driven auto-scaling and dynamic web traffic routing. You need to minimize the operational and administrative effort required to manage the container orchestration infrastructure. Which Azure service should you recommend?

Show answer & explanation

Answer: Azure Container Apps

Answer

Azure Container Apps
Azure Container Apps is the correct service because it provides a serverless platform built on Kubernetes technologies like KEDA and Dapr, enabling auto-scaling and traffic routing with minimal operational overhead.

Step-by-Step Solution

1
Analyze the requirements to identify the core needs: event-driven auto-scaling, dynamic web traffic routing, and minimized operational and administrative effort.
Determined that the solution must be a fully managed, serverless platform to minimize administrative overhead.
This rules out solutions that require virtual machine or Kubernetes infrastructure management.
2
Compare Azure Container Apps against Azure Kubernetes Service (AKS).
Selected Azure Container Apps as it natively supports KEDA-based event scaling and ingress routing without cluster management.
Using Azure Kubernetes Service (AKS) introduces unnecessary administrative complexity for simple microservice hosting.

Key Concept

Serverless container hosting with Azure Container Apps
Estimated Time:1m 0s
Question 394Question

You are designing a backup solution for a set of Azure Virtual Machines running a critical enterprise application. The virtual machines are configured with Premium SSD v2 managed disks and require backups to be taken every 12 hours. The solution must meet the following requirements:
- Ensure backups are resilient to a zone outage in the primary region.
- Support restoring the virtual machines to a paired region in the event of a regional disaster.
- Allow instant recovery of the virtual machines from snapshots for up to 10 days.

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

Select all that apply

Show answer & explanation

Answer: A Recovery Services vault configured with geo-zone-redundant storage (GZRS) and Cross-Region Restore enabled; An Enhanced backup policy with the instant restore retention set to 10 days

Answer

A Recovery Services vault configured with geo-zone-redundant storage (GZRS) with Cross-Region Restore enabled, and an Enhanced backup policy with the instant restore retention set to 10 days.
The correct configurations are geo-zone-redundant storage (GZRS) with Cross-Region Restore enabled and an Enhanced backup policy with the instant restore retention set to 10 days. GZRS ensures that the backup vault remains available even if an entire availability zone in the primary region fails, while Cross-Region Restore enables recovery in the paired secondary region. An Enhanced backup policy is required because the VMs use Premium SSD v2 disks and need multiple backups per day (every 12 hours), both of which are unsupported by the Standard policy. Furthermore, the Enhanced policy supports the required 10-day instant recovery snapshot retention, whereas the Standard policy is limited to a maximum of 5 days.

Step-by-Step Solution

1
Analyze the storage redundancy and disaster recovery requirements.
The solution must survive a zone failure in the primary region (requiring zone-redundant storage) and support restore to a paired region (requiring geo-replication). Geo-zone-redundant storage (GZRS) combines these two capabilities by replicating data across three zones in the primary region and replicating to a secondary region. Cross-Region Restore must be enabled to allow restoring backups to the secondary region.
This determines the correct vault storage tier and recovery configuration.
2
Evaluate the workload characteristics and backup frequency requirements.
The virtual machines use Premium SSD v2 managed disks and require backups every 12 hours (multiple backups per day). This requires the Enhanced backup policy tier, as the Standard backup policy tier does not support Premium SSD v2 disks and is limited to one backup per day.
This determines the appropriate backup policy tier.
3
Verify the instant recovery retention requirements.
The requirement is to retain instant recovery snapshots for 10 days. The Standard backup policy limits instant restore snapshot retention to a maximum of 5 days. The Enhanced backup policy supports instant restore snapshot retention for up to 30 days.
This confirms that the Enhanced backup policy is required to support the 10-day instant recovery window.

Key Concept

Selecting vault storage redundancy and backup policy tiers based on disk types, backup frequency, zonal availability, and instant recovery duration requirements.
Estimated Time:2m 0s
Question 395Question

An organization is designing a high availability compute solution in Azure for a legacy line-of-business application. The application will run on two virtual machines. The organization has the following requirements:
- The virtual machines must be protected against a datacenter outage within the Azure region.
- The solution must achieve a virtual machine uptime SLA of 99.99%.

Which two configurations should you recommend to meet these requirements? (Select two.)

Select all that apply

Show answer & explanation

Answer: Deploy the virtual machines as individual instances across different Availability Zones, placing one in Zone 1 and the other in Zone 2.; Deploy the virtual machines using a Virtual Machine Scale Set (VMSS) in Flexible orchestration mode spread across multiple zones.

Answer

Deploy the virtual machines as individual instances across different Availability Zones, and deploy the virtual machines using a Virtual Machine Scale Set in Flexible orchestration mode spread across multiple zones.
To achieve a 99.99% Virtual Machine uptime SLA and protect against datacenter outages in Azure, virtual machines must be distributed across multiple Availability Zones. Individual VMs placed in different zones (such as Zone 1 and Zone 2) or a Virtual Machine Scale Set configured with Flexible orchestration and spread across zones satisfy this requirement.

Step-by-Step Solution

1
Analyze the high availability and SLA requirements.
The requirements specify protection against a datacenter outage and a 99.99% virtual machine uptime SLA.
This determines that the VMs must be placed across different physical datacenters, which translates to Azure Availability Zones.
2
Identify configurations that utilize multiple Availability Zones.
Individual VMs deployed in separate zones (Zone 1 and Zone 2) and a Virtual Machine Scale Set configured for Flexible orchestration spread across zones are identified as valid compute configurations.
Both methods physically isolate the VMs in different zones within the region, providing the required zone-redundancy and meeting the 99.99% SLA.
3
Eliminate configurations confined to a single zone or datacenter.
Deploying within a single Availability Zone or using an Availability Set are ruled out.
These configurations place VMs within the same failure boundary, failing to protect against datacenter outages and offering lower uptime SLAs (99.9% and 99.95% respectively).

Key Concept

Azure Availability Zones and VM SLAs
Question 396Question

A company is designing a container-based solution to process sensitive transaction workloads. The design must satisfy the following requirements:
- Host containerized applications that scale dynamically based on request load.
- Minimize container infrastructure management and administrative effort.
- Ensure that transaction audit logs are stored in compliance with strict data residency laws, requiring complete isolation of logs between different geographic regions.

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

Select all that apply

Show answer & explanation

Answer: Azure Container Apps for hosting the workloads; Dedicated regional Log Analytics workspaces for each geographical region

Answer

The design should include Azure Container Apps to host the workloads and dedicated regional Log Analytics workspaces for each geographical region.
The correct solution includes Azure Container Apps to host the containerized applications because it is a serverless container service that minimizes administration overhead by eliminating the need to manage Kubernetes nodes or APIs. Additionally, it includes dedicated regional Log Analytics workspaces to satisfy compliance constraints requiring geographic log isolation and data residency.

Step-by-Step Solution

1
Evaluate the container hosting requirements against the constraint of minimizing administrative overhead.
Identify that Azure Container Apps provides a managed serverless platform that simplifies container management compared to Azure Kubernetes Service.
Choosing a serverless hosting model removes the operational burdens of cluster administration, scaling configurations, and node updates.
2
Evaluate compliance and logging isolation constraints.
Determine that dedicated regional Log Analytics workspaces are necessary to isolate log data geographically.
A single shared workspace cannot guarantee regional segregation, which violates data sovereignty laws.

Key Concept

Choosing low-overhead serverless container options and designing geographically isolated monitoring solutions to satisfy regulatory compliance.
Question 397Question

A media streaming platform needs to host user-uploaded images and subtitles in a standard Azure General Purpose v2 storage account. The design requires the data to survive a major regional disaster. Additionally, during a primary region outage, the application must be able to immediately switch to reading the images and subtitles from the secondary region without triggering any failover process. Which two replication tiers should the architect select?

Select all that apply

Show answer & explanation

Answer: Read-access geo-redundant storage (RA-GRS); Read-access geo-zone-redundant storage (RA-GZRS)

Answer

Read-access geo-redundant storage (RA-GRS) and Read-access geo-zone-redundant storage (RA-GZRS) are the two replication tiers that meet all requirements.
Read-access geo-redundant storage (RA-GRS) and Read-access geo-zone-redundant storage (RA-GZRS) both replicate data to a secondary region for disaster resilience, and they provide a read-only secondary endpoint. This allows applications to immediately read data from the secondary region during a primary region outage without initiating a failover.

Step-by-Step Solution

1
Analyze the regional disaster resilience requirement.
Locally redundant storage (LRS) is ruled out because it only replicates data within a single datacenter in the primary region and cannot survive a regional disaster.
The system must survive a major regional disaster, requiring geo-redundant replication.
2
Analyze the secondary read access requirement.
Standard Geo-redundant storage (GRS) is ruled out because it does not allow read access to the secondary region unless a failover is initiated.
The application must be able to switch to reading from the secondary region immediately during an outage without waiting for or triggering a failover.
3
Select replication options that support both geo-redundancy and secondary read access.
Read-access geo-redundant storage (RA-GRS) and Read-access geo-zone-redundant storage (RA-GZRS) are selected.
Both RA-GRS and RA-GZRS replicate data to a secondary region and provide a secondary read-only endpoint that is immediately available.

Key Concept

Determining storage replication requirements for regional redundancy and immediate secondary read access in Azure Storage.
Estimated Time:1m 30s
Question 398Question

A company is designing a storage solution for a legal compliance application that stores historical case documents. The documents are accessed frequently during the first 30 days after creation. After 30 days, the documents are rarely accessed, but the company is legally required to retain them for 7 years. When a document is requested, it must be available for immediate download with sub-second retrieval times. The storage solution must survive a regional disaster. Which storage configuration should you recommend?

Show answer & explanation

Answer: A Geo-Redundant Storage (GRS) account with a lifecycle management policy that transitions documents to the Cool tier 30 days after creation

Answer

A Geo-Redundant Storage (GRS) account with a lifecycle management policy that transitions documents to the Cool tier 30 days after creation
A Geo-Redundant Storage (GRS) account with a lifecycle management policy transitioning blobs to the Cool tier after 30 days is the correct solution. GRS satisfies the requirement to survive a regional disaster by replicating data to a secondary region. The Cool tier minimizes storage costs for data that is rarely accessed after 30 days while keeping the data online for immediate, sub-second retrieval.

Step-by-Step Solution

1
Determine the required redundancy based on disaster recovery needs.
Since the solution must survive a regional disaster, Locally Redundant Storage (LRS) is insufficient. Geo-Redundant Storage (GRS) is required.
GRS replicates data synchronously three times within the primary region, and then asynchronously replicates it to a secondary paired region hundreds of miles away, securing availability even in the event of a regional outage.
2
Evaluate the retrieval latency requirement for historical documents.
The documents must be retrieved in less than a second (sub-second retrieval).
This rules out the Archive tier, which is an offline tier requiring a rehydration process that takes hours to complete.
3
Identify the most cost-effective online storage tier for data that is infrequently accessed after 30 days.
The Cool tier is the appropriate choice as it offers lower storage costs than the Hot tier while keeping the data online with sub-second retrieval latency.
Lifecycle management policies can automate the transition of blobs from Hot to Cool after 30 days to optimize costs.

Key Concept

Selecting the appropriate storage redundancy and access tiers using Azure Blob Storage lifecycle management to balance cost, performance, and regional resilience.
Question 399Question

A clinical research organization is designing a security solution for an Azure Blob Storage container named researchdata that stores sensitive genetic sequencing results. The solution must meet the following access requirements:
1. Internal researchers require ongoing read access to the sequencing data. Access must be managed at scale rather than via individual assignments.
2. A partner laboratory requires read access to the data for a specific 48-hour window to validate findings.
3. The partner laboratory's access must support immediate revocation in case of a security anomaly, without affecting the access of internal researchers.

Which security configuration should you recommend to meet these requirements?

Show answer & explanation

Answer: Assign the Storage Blob Data Reader role to a Microsoft Entra ID security group containing the internal researchers. For the partner laboratory, generate a Shared Access Signature (SAS) token associated with a Stored Access Policy on the container.

Answer

Assign the Storage Blob Data Reader role to a Microsoft Entra ID security group containing the internal researchers. For the partner laboratory, generate a Shared Access Signature (SAS) token associated with a Stored Access Policy on the container.
The correct strategy uses group-based role assignments for the internal researchers to ensure scalable administration and follows the principle of least privilege. For the external partner laboratory, it uses a container-level Shared Access Signature (SAS) backed by a Stored Access Policy. This configuration meets the 48-hour access limit and allows the organization to revoke the SAS token immediately if necessary by altering or deleting the Stored Access Policy, without affecting the storage account keys or other users.

Step-by-Step Solution

1
Address the internal researchers' requirement by using group-based access control.
Create a Microsoft Entra ID security group, add the researchers, and assign the Storage Blob Data Reader role to the group.
This scales access management and avoids assigning RBAC permissions directly to individual user accounts.
2
Address the partner laboratory's temporary access and revocation requirements.
Define a Stored Access Policy on the container with a 48-hour lifetime, and generate a SAS token derived from this policy.
Using a Stored Access Policy allows the token to be immediately revoked by modifying or deleting the policy, which is not possible with an ad-hoc SAS without rotating the storage keys.

Key Concept

Combining Microsoft Entra ID group-based RBAC with Stored Access Policies on storage containers to balance ongoing access management with secure, revocable temporary access.
Estimated Time:1m 30s
Question 400Question

A logistics company is designing a highly available and disaster-resilient relational database backend for its global fleet-tracking application. The database tier must support cross-database queries and SQL Server Agent jobs to orchestrate daily ETL tasks. The disaster recovery design must meet a Recovery Time Objective (RTO) of 15 minutes and a Recovery Point Objective (RPO) of 5 seconds. All failover operations must occur automatically without requiring client application connection string modifications, and all reporting queries must be dynamically offloaded to a readable secondary replica in the disaster recovery region. To maintain compliance, all database replication traffic must remain isolated from the public internet.

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

Select all that apply

Show answer & explanation

Answer: Deploy Azure SQL Managed Instance in the primary and secondary regions, configure a failover group, and configure client applications to connect using 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 Azure SQL Managed Instances to facilitate database replication.

Answer

Deploy Azure SQL Managed Instance in a failover group with read-write and read-only listener endpoints, and configure Global Virtual Network Peering between the virtual networks hosting the instances.
The correct architecture uses Azure SQL Managed Instance to support cross-database queries and SQL Server Agent jobs. Configuring a failover group satisfies the requirements for low RTO/RPO, automatic failover, and dynamic read-scale routing using listener endpoints. Establishing Global Virtual Network Peering between the hosting virtual networks ensures that replication traffic remains private and does not traverse the public internet.

Step-by-Step Solution

1
Analyze database feature requirements
Identify that SQL Server Agent and cross-database queries require Azure SQL Managed Instance rather than Azure SQL Database.
Choosing the correct deployment option ensures legacy compatibility constraints are satisfied.
2
Analyze high availability and disaster recovery requirements
Identify that automatic failover without connection string changes and dynamic read-scale routing require a failover group with listener endpoints.
Failover groups provide read-write and read-only listeners that automatically redirect traffic during failovers.
3
Analyze network isolation requirements
Identify that replication traffic between SQL Managed Instances must flow securely. Global Virtual Network Peering provides direct, private IP connectivity over the Microsoft backbone network.
Replication for SQL Managed Instance failover groups must be configured over a private network connection (VPN or Peering).

Key Concept

Designing disaster recovery and high availability for Azure SQL Managed Instance using failover groups and Global VNet Peering to meet performance, network isolation, and compatibility requirements.
Estimated Time:3m 0s
PreviousPage 20 / 60Next