All practice questions

1198 questions

Question 221Question

An animation studio is migrating its core rendering pipeline to Azure. The pipeline consists of 150150 Linux-based virtual machines running rendering software.

The design requirements for the shared storage solution are as follows:
- Protocol & Compatibility: The rendering nodes require shared storage that supports NFS, POSIX-compliant file permissions, and hard links.
- Performance: The storage must support high-throughput parallel reads and writes, achieving sub-1010 millisecond metadata operation latency.
- Availability: The storage solution must remain available even if a single physical datacenter (availability zone) in the primary Azure region experiences an outage.
- Administration: The storage solution must minimize the administrative overhead of managing OS-level clustering, virtual machines, or file system updates.

Which storage solution should you recommend in the design?

Show answer & explanation

Answer: An Azure Files NFS v 4.14.1 share in a Premium FileStorage account configured with Zone-Redundant Storage (ZRS).

Answer

An Azure Files NFS v 4.14.1 share in a Premium FileStorage account configured with Zone-Redundant Storage (ZRS).
The correct solution is the option recommending an Azure Files NFS v 4.14.1 share in a Premium FileStorage account configured with Zone-Redundant Storage (ZRS). This fully managed service natively supports POSIX permissions and hard links required by Linux workloads, delivers sub-1010 millisecond metadata latency via the Premium tier, and survives availability zone outages through ZRS.

Step-by-Step Solution

1
Analyze compatibility and protocol requirements.
The rendering nodes are Linux-based and require NFS with support for POSIX-compliant permissions and hard links. This excludes SMB-based storage configurations.
Linux rendering pipelines typically rely on hard links and POSIX permissions, which are fully supported under NFS but not natively preserved over SMB without complex AD mappings.
2
Evaluate performance and account tier constraints.
The solution must support sub-1010 millisecond latency and high-throughput operations, requiring a Premium storage tier. NFS v 33 on Blob Storage requires a Premium BlockBlobStorage account, and NFS v 4.14.1 on Azure Files requires a Premium FileStorage account.
Standard tiers do not support NFS protocols and cannot guarantee the sub-1010 millisecond metadata latencies required for rendering workloads.
3
Evaluate availability and redundancy requirements.
To survive a physical datacenter (availability zone) outage, the storage account must be configured with Zone-Redundant Storage (ZRS). Locally Redundant Storage (LRS) is eliminated.
ZRS replicates data synchronously across three availability zones within the primary region, providing resiliency against zone failures that LRS cannot offer.
4
Select the fully managed solution that satisfies all conditions.
An Azure Files NFS v 4.14.1 share in a Premium FileStorage account with ZRS meets all compatibility, performance, and availability constraints while minimizing management overhead.
It offers a fully managed (PaaS) file share, eliminating the administrative effort of managing custom VM clusters.

Key Concept

Selecting the correct Azure Files tier, protocol (NFS vs SMB), and redundancy options for high-performance Linux workloads requiring POSIX compliance and zone-level resilience.
Question 222Question

A maritime shipping enterprise is designing a secure ingestion pipeline for container telemetry logs stored in an Azure Blob Storage account named telemetrydata. External IoT gateway devices managed by a third-party vendor must upload telemetry files to a container named uploads. The security design must meet the following requirements:
- The gateway devices must only be allowed to write data to the container and must be blocked from reading, listing, or modifying existing data.
- The access credentials must expire after 90 days, and security administrators must have the ability to immediately revoke all outstanding access tokens in the event of a gateway breach without modifying storage account keys.
- All traffic to the storage account must be restricted to the vendor's dedicated public outbound IP range.

Which two actions should you include in the design?

Select all that apply

Show answer & explanation

Answer: Create a Stored Access Policy on the uploads container specifying Write-only permissions and generate a service Shared Access Signature (SAS) token referencing the policy.; Configure the storage account firewall to restrict access, permitting traffic only from the vendor's dedicated public outbound IP range.

Answer

Create a Stored Access Policy on the uploads container specifying Write-only permissions and generate a service Shared Access Signature (SAS) token referencing the policy, and configure the storage account firewall to restrict access, permitting traffic only from the vendor's dedicated public outbound IP range.
To support immediate revocation of the access tokens without modifying the storage account keys, a Stored Access Policy must be created. Modifying or deleting the Stored Access Policy immediately invalidates any service SAS tokens associated with it. Restricting the storage account firewall to specific outbound IP ranges secures the network perimeter by ensuring only traffic from the vendor's IoT gateway devices is allowed.

Step-by-Step Solution

1
Analyze the token revocation requirement.
Identify that ad-hoc SAS tokens require storage account key rotation to revoke early, whereas service SAS tokens linked to a Stored Access Policy can be revoked instantly by modifying or deleting the policy.
To satisfy the constraint of immediate token revocation without modifying storage account keys.
2
Evaluate the network access control requirements.
Determine that the Azure Storage firewall must be configured to permit traffic exclusively from the third-party vendor's public IP addresses.
To satisfy the requirement of restricting traffic to the vendor's dedicated public outbound IP range.
3
Evaluate identity-based access controls against requirements.
Identify that direct assignment of the Storage Blob Data Contributor role violates the least-privilege policy (since it allows read and delete operations) and violates governance best practices.
To rule out the direct RBAC assignment distractor.

Key Concept

Securing Azure Storage access through a combination of network firewalls and revocable service SAS tokens using Stored Access Policies.
Estimated Time:2m 30s
Question 223Question

A logistics company is designing the Azure storage infrastructure for a legacy fleet management application. The application will run on Azure Virtual Machines and has the following storage requirements:
- The virtual machine operating system and application binaries require persistent disk storage that supports sub-millisecond write latency.
- A shared file system is required to store application configuration files. The share must support the SMB 3.0 protocol, be accessible simultaneously by multiple virtual machines, and must survive a local datacenter zone outage.
- External partners need read-only access to specific PDF reports stored in Azure Blob Storage. This access must be granted via a Shared Access Signature (SAS) that can be easily revoked if compromised, without regenerating storage account keys.

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

Select all that apply

Show answer & explanation

Answer: Premium SSD v2 managed disks for the operating system and application binaries; A Shared Access Signature (SAS) token for the Blob storage container that is associated with a stored access policy

Answer

Premium SSD v2 managed disks for the operating system and application binaries, and a Shared Access Signature (SAS) token for the Blob storage container that is associated with a stored access policy.
Premium SSD v2 managed disks satisfy the requirement for sub-millisecond write latency. Additionally, associating a Shared Access Signature (SAS) token with a stored access policy enables revocation without rotating the primary storage account keys.

Step-by-Step Solution

1
Analyze the VM disk latency requirement.
Identify that sub-millisecond latency demands high-performance SSD tiers (such as Premium SSD v2 or Ultra Disk) rather than magnetic-based standard options.
This rules out Standard HDD options which are designed for backup/archival and do not guarantee low latency.
2
Evaluate the file share zone outage requirement.
Determine that the storage account containing the Azure Files share must be configured with Zone-Redundant Storage (ZRS) or Geo-Zone-Redundant Storage (GZRS).
Locally Redundant Storage (LRS) stores three copies of data inside a single datacenter zone, making it a single point of failure during a zone outage.
3
Assess the secure data sharing and revocation requirement.
Determine that the SAS token must be associated with a stored access policy.
If an ad-hoc SAS is compromised, revoking it requires rotating the storage account keys, which breaks other services. A stored access policy can be deleted or updated to immediately invalidate the associated SAS token.

Key Concept

Azure Managed Disk selection, Azure Files availability zones, and secure Blob storage sharing with revocable SAS tokens using stored access policies.
Question 224Question

Emberwood Manufacturing is designing a secure identity governance and access control solution for its Microsoft Entra ID tenant.

The company must satisfy the following administrative access requirements:
- Ensure that administrators can activate their privileged roles only when needed, for a maximum duration of 4 hours, and require multi-factor authentication (MFA) during activation.
- Prevent administrative lockout from the tenant in the event of a primary MFA service outage or misconfiguration.

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

Select all that apply

Show answer & explanation

Answer: Exclude dedicated emergency access accounts from all Conditional Access policies that enforce multi-factor authentication.; Configure administrative roles in Microsoft Entra Privileged Identity Management (PIM) as eligible assignments with an activation duration limit.

Answer

Exclude dedicated emergency access accounts from all Conditional Access policies that enforce multi-factor authentication, and configure administrative roles in Microsoft Entra Privileged Identity Management (PIM) as eligible assignments with an activation duration limit.
Excluding emergency access accounts from MFA requirements ensures that administrators can still log in to recover the tenant in the event of an MFA service failure. Configuring administrative roles as eligible assignments in Privileged Identity Management (PIM) enforces just-in-time access controls with a strict duration limit and MFA activation requirement.

Step-by-Step Solution

1
Evaluate the requirement to prevent administrative lockout during MFA outages.
Determine that emergency access accounts must be created and explicitly excluded from all MFA-enforcing Conditional Access policies.
If all accounts are subject to MFA, a service outage will prevent any administrator from logging in to fix tenant configurations.
2
Evaluate the requirement to limit administrative role activation to 4 hours with MFA validation.
Select Microsoft Entra Privileged Identity Management (PIM) and configure roles as eligible assignments.
PIM eligible assignments enforce just-in-time access where the administrator must activate the role, perform MFA, and be bound by the maximum activation duration setting.

Key Concept

Designing secure administrative access using Microsoft Entra Privileged Identity Management (PIM) and emergency access account exclusions in Conditional Access policies.
Question 225Question

You are designing a subscription governance and delegated administration solution for a new Azure landing zone. The solution must meet the following requirements:
- Establish a new management boundary for a dedicated business unit.
- Implement a custom Azure RBAC role named 'Resource Lock Manager' that allows managing resource locks but prevents deletion of any resources. This role must only be assignable within this new management boundary.
- Ensure that the operations team members can only active this role on-demand to align with the principle of least privilege.
- Use a Microsoft Entra ID group to minimize direct role assignments to individual users.

Which sequence of configuration steps should you perform to implement the solution?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence of steps is: First, create a new Management Group to serve as the management boundary. Second, define the 'Resource Lock Manager' custom Azure RBAC role, setting the 'AssignableScopes' property to the path of the new Management Group. Third, create a Microsoft Entra ID security group with the 'isAssignableToRole' property set to true. Fourth, assign the 'Resource Lock Manager' custom role to the Microsoft Entra ID security group at the new Management Group scope. Fifth, configure Privileged Identity Management (PIM) for Groups on the security group, and assign the operations team members as eligible.
The correct sequence respects the resource and configuration dependencies. The Management Group must be created first to obtain its resource path. The custom role definition references this path in its 'AssignableScopes' property. Next, the target security group must be created. The custom role can then be assigned to the group at the Management Group scope. Finally, PIM for Groups can be configured for the group to delegate eligible membership to the operations team.

Step-by-Step Solution

1
Create the new Management Group.
A new management boundary is established with a unique resource path.
The unique resource ID of the Management Group is a hard dependency for the custom RBAC role's scope definitions.
2
Define the 'Resource Lock Manager' custom Azure RBAC role with the 'AssignableScopes' set to the Management Group.
The custom role is registered and available for assignment within the Management Group hierarchy.
The role definition must exist and target the correct boundary scope before it can be assigned to any security principal.
3
Create a Microsoft Entra ID group with the 'isAssignableToRole' parameter enabled.
A role-assignable Entra ID security group is created.
Using a role-assignable group is a prerequisite for assigning custom Azure RBAC roles and configuring PIM for Groups.
4
Assign the custom RBAC role to the Entra ID group at the Management Group scope.
The group is granted the 'Resource Lock Manager' permissions over all resources in the Management Group scope.
The role assignment must exist at the group level so that users who activate their membership automatically inherit the custom role's permissions.
5
Enable PIM for Groups on the group and configure the operations team members as eligible.
Users can activate group membership on-demand, which dynamically grants them the custom RBAC role.
This prevents permanent assignment of administrative privileges, fulfilling the least-privilege requirement.

Key Concept

Azure RBAC delegation using custom roles, management group scopes, and Entra ID PIM for Groups.
Estimated Time:3m 0s
Question 226Question

AeroSpire Aerospace is designing a hybrid identity and access management solution for a new Microsoft Entra ID tenant that integrates with an on-premises Active Directory Domain Services (AD DS) forest. The solution must meet the following requirements:

- Users on corporate-joined devices must be automatically signed in without entering credentials.
- On-premises server infrastructure dependencies and operational overhead for identity federation must be minimized.
- All directory administrators must be prompted for multi-factor authentication (MFA) when accessing the Azure portal, using a Just-In-Time (JIT) administrative access workflow.
- In the event of a tenant-wide MFA service disruption, at least one administrative account must retain emergency access to the Azure portal.

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

Show answer & explanation

Answer: Configure Password Hash Synchronization (PHS) with Seamless Single Sign-On (SSO). Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments. Implement a Conditional Access policy requiring MFA for Microsoft Azure Management, and exclude a dedicated cloud-only emergency access account from the policy.

Answer

Configure Password Hash Synchronization (PHS) with Seamless Single Sign-On (SSO). Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments. Implement a Conditional Access policy requiring MFA for Microsoft Azure Management, and exclude a dedicated cloud-only emergency access account from the policy.
The correct solution uses Password Hash Synchronization (PHS) with Seamless SSO to satisfy the Single Sign-On and minimal infrastructure requirements. Microsoft Entra PIM with eligible role assignments implements the JIT administrative workflow. Finally, excluding a dedicated cloud-only emergency access account from the Conditional Access policy ensures administrative access is maintained if the MFA service is disrupted.

Step-by-Step Solution

1
Select the appropriate hybrid authentication method.
Password Hash Synchronization (PHS) with Seamless SSO.
PHS with Seamless SSO fulfills the automatic sign-in requirement for corporate network-connected devices while keeping on-premises infrastructure minimal compared to AD FS.
2
Determine the administrative governance model.
Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments.
Setting assignments to eligible rather than active ensures that administrators must activate their roles when needed, implementing a JIT access model.
3
Design the Conditional Access policy and lockout protection mechanism.
Enforce MFA for the Microsoft Azure Management app while excluding a cloud-only emergency access account.
Excluding a dedicated, highly secured emergency access (break-glass) account ensures that administrators do not get locked out of the tenant in case of an MFA platform outage.

Key Concept

Designing secure, resilient identity architecture using Microsoft Entra authentication, Privileged Identity Management, and Conditional Access exclusions.
Estimated Time:2m 30s
Question 227Question

A healthcare provider is designing the cloud architecture for a new clinical trials application. The application's database layer has the following technical and operational requirements:

* It must host two databases that require cross-database queries and transactions.
* It must use custom SQL Server Common Language Runtime (SQL CLR) assemblies to handle legacy data encryption methods.
* It must be deployed within a private subnet of an Azure Virtual Network to prevent any public internet exposure.
* It must minimize administrative overhead by eliminating operating system patching and manual backup tasks.
* It must remain operational and survive the failure of an entire Azure Availability Zone within the hosting region.

Which Azure SQL deployment option should you recommend?

Show answer & explanation

Answer: Azure SQL Managed Instance in the Business Critical tier configured with zone redundancy

Answer

Azure SQL Managed Instance in the Business Critical tier configured with zone redundancy
The correct option is Azure SQL Managed Instance in the Business Critical tier configured with zone redundancy. Azure SQL Managed Instance is a fully managed service that eliminates OS patching and backup management, yet provides high compatibility with the SQL Server database engine, including support for SQL CLR assemblies and cross-database queries. It is deployed via VNet injection into a private subnet. Configuring it in the Business Critical tier with zone redundancy replicates data across multiple availability zones, ensuring resilience against zone outages.

Step-by-Step Solution

1
Evaluate the database engine feature requirements.
The application requires SQL CLR assemblies and cross-database queries.
This rules out Azure SQL Database single databases or elastic pools, which do not support these features natively.
2
Evaluate the administrative and networking constraints.
The solution must minimize OS patching and backup management, and it must run within a private subnet of an Azure Virtual Network.
This rules out SQL Server on Azure VMs, which requires user-managed OS-level patching and backup policies, despite supporting CLR and private network deployment.
3
Evaluate the high availability and resilience constraints.
The database must survive the outage of an entire Azure Availability Zone.
This rules out any tier configured with locally redundant storage (LRS). Azure SQL Managed Instance in the Business Critical tier with zone redundancy enabled replicates data across availability zones to meet this requirement.

Key Concept

Selecting the appropriate Azure SQL deployment option based on legacy feature compatibility, management overhead, and high availability requirements.
Estimated Time:2m 30s
Question 228Question

An organization is designing a subscription governance model to allow network security administrators to manage network security rules across multiple subscriptions. To follow the principle of least privilege, the administrators must only be able to elevate their access on-demand using Just-In-Time (JIT) access. You need to configure this administrative model. In which order should you perform the configuration steps?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

To implement this design, first create a parent Management Group and associate the subscriptions. Next, create a custom Azure RBAC role with the required permissions and set its assignable scope to the Management Group. Then, create a Microsoft Entra ID security group and assign the custom role to it at the Management Group scope. Finally, configure PIM for Groups to make users eligible for the security group, enabling JIT access.
Establishing the Management Group first provides the container needed for scope inheritance and is required before configuring custom roles targeting that scope. The custom role must specify the Management Group in its assignable scopes. The security group must be created next so that the custom role can be assigned to it. Assigning the custom role to the group at the Management Group scope ensures the permissions are inherited by all child subscriptions. Finally, configuring PIM for Groups enables Just-In-Time membership, fulfilling the requirement for JIT administrative access.

Step-by-Step Solution

1
Establish the management scope.
A new parent Management Group containing the target subscriptions is created.
This establishes the scope hierarchy and allows governance controls to inherit downward.
2
Define the custom Azure RBAC role.
A custom role definition is registered with the parent Management Group in its AssignableScopes.
Custom roles must define where they can be assigned. The Management Group must exist before it can be referenced in the role definition's assignable scopes.
3
Deploy a Microsoft Entra security group.
A security group exists to hold the network administrators.
Group-based role assignment is a best practice that simplifies PIM integration and minimizes individual role assignments.
4
Bind the custom role to the security group.
The security group is assigned the custom role at the parent Management Group scope.
This configuration ensures that any active member of the security group inherits the custom role permissions across all subscriptions in the Management Group.
5
Enable Privileged Identity Management for the security group.
Administrator accounts are made eligible for the security group in PIM.
This enables Just-In-Time (JIT) membership elevation, satisfying the least privilege and on-demand requirements.

Key Concept

Group-based Azure RBAC scope inheritance combined with Microsoft Entra PIM for Groups to achieve Just-In-Time least privilege management.
Question 229Question

An organization is designing an identity governance and privileged access solution for external database administrators who require temporary access to manage an Azure SQL Managed Instance. The solution must meet the following requirements:
- Administrators must request access on-demand (just-in-time) for a duration of no more than 6 hours.
- Multi-factor authentication (MFA) must be enforced during the role activation process.
- The design must minimize administrative overhead and avoid assigning roles directly to individual user accounts.
- To prevent tenant lockout during a regional identity provider disruption, emergency break-glass accounts must be protected from being locked out by MFA policies.

Which configuration should you recommend to meet these requirements?

Show answer & explanation

Answer: Create a Microsoft Entra ID security group, assign the required Azure RBAC roles to this group, configure eligible memberships for the administrators using Microsoft Entra Privileged Identity Management (PIM) for Groups with activation MFA enabled, and exclude emergency access accounts from Conditional Access MFA policies.

Answer

Create a Microsoft Entra ID security group, assign the required Azure RBAC roles to this group, configure eligible memberships for the administrators using Microsoft Entra Privileged Identity Management (PIM) for Groups with activation MFA enabled, and exclude emergency access accounts from Conditional Access MFA policies.
The correct solution leverages Microsoft Entra Privileged Identity Management (PIM) for Groups to assign the Azure RBAC roles to a group rather than to individual users, reducing overhead. By making the users eligible members and requiring MFA on activation, it achieves JIT access for up to 6 hours. Finally, excluding emergency break-glass accounts from tenant-wide Conditional Access MFA policies ensures that administrators can still log in to recover the tenant during a major MFA outage.

Step-by-Step Solution

1
Determine the resource authorization structure that minimizes administrative overhead.
Identify that assigning Azure RBAC roles to a Microsoft Entra ID security group instead of individual accounts reduces overhead and supports scalable governance.
Direct RBAC assignments to individuals violate the group-based access control principle and increase administrative complexity.
2
Select the just-in-time (JIT) access mechanism.
Configure Privileged Identity Management (PIM) for Groups, setting the external database administrators as eligible members rather than active permanent members.
PIM for Groups ensures that memberships are only active when requested and automatically expire after the 6-hour limit, satisfying JIT requirements.
3
Apply multi-factor authentication (MFA) to the activation process.
Enable the MFA requirement in the PIM group activation settings.
This guarantees that users must verify their identity using MFA when they elevate their access, without needing a persistent Conditional Access policy that could interfere with other scenarios.
4
Address the resiliency and lockout requirements for emergency access.
Ensure emergency break-glass accounts are explicitly excluded from all tenant-wide Conditional Access MFA policies.
Excluding emergency accounts prevents administrative lockout in the event of an identity provider or MFA system outage.

Key Concept

Designing secure, JIT, and highly resilient administrative access using PIM for Groups and Conditional Access exclusions.
Question 230Question

A retail business requires a daily ingestion pipeline to transfer 50 GB50\text{ GB} of operational log files from on-premises servers to Azure. The pipeline runs once every 24 hours. The storage solution must persist the logs in a hierarchical structure and guarantee data durability even during a regional datacenter disaster. Additionally, the data science team needs to perform infrequent, exploratory analysis directly on these files. Which two architectural choices should you make to meet these requirements? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure Data Factory to manage and run the daily transfer pipeline; Azure Data Lake Storage Gen2 using Geo-Redundant Storage (GRS)

Answer

Azure Data Factory and Azure Data Lake Storage Gen2 using Geo-Redundant Storage (GRS)
To orchestrate the daily transfer pipeline, Azure Data Factory is the correct choice. To survive a regional outage, the storage must be configured with Geo-Redundant Storage (GRS) since it replicates the data to a secondary region.

Step-by-Step Solution

1
Identify the orchestration service required for daily batch data movement from an on-premises database to Azure.
Azure Data Factory is selected because it is designed to orchestrate and execute batch data ingestion pipelines.
This meets the daily pipeline orchestration requirement.
2
Determine the required replication strategy for Azure Data Lake Storage Gen2 to survive a regional outage.
Geo-Redundant Storage (GRS) is selected.
GRS replicates data to a secondary region, ensuring durability during a regional disaster, whereas LRS only replicates within a single datacenter.

Key Concept

Designing batch data integration pipelines and choosing disaster-resilient analytical storage replication.
Question 231Question

Solaris Green Energy is designing an identity security strategy for its Microsoft Entra ID tenant. The design must enforce multi-factor authentication (MFA) for all administrative roles to protect resources from unauthorized access. To mitigate the risk of tenant lockout during an identity service outage or misconfiguration, the security team requires an emergency access plan.

Which of the following recommendations should you include in the identity design?

Show answer & explanation

Answer: Designate two cloud-only accounts, assign them the Global Administrator role, and exclude them from all Conditional Access policies that require multi-factor authentication.

Answer

Designate two cloud-only accounts, assign them the Global Administrator role, and exclude them from all Conditional Access policies that require multi-factor authentication.
Designating two cloud-only accounts, assigning them the Global Administrator role, and excluding them from all Conditional Access policies that require multi-factor authentication is the recommended Microsoft best practice. These 'break-glass' accounts ensure that at least one administrator can access the tenant to remediate configurations or service outages, even if the primary authentication mechanisms or multi-factor authentication systems are unavailable.

Step-by-Step Solution

1
Analyze the requirements for administrative MFA enforcement and tenant lockout prevention.
Identified that while MFA must be enforced for administrators, a recovery mechanism (emergency/break-glass accounts) must be established to bypass MFA during policy misconfigurations or service outages.
This establishes the need for accounts that are decoupled from standard authentication paths and policies.
2
Evaluate the architectural constraints of the emergency accounts.
Determined that these accounts must be cloud-only (to avoid on-premises federation dependencies) and excluded from Conditional Access policies enforcing MFA.
Cloud-only accounts operate independently of on-premises sync issues, and excluding them from CA policies prevents lockout if a policy is configured incorrectly.
3
Compare design recommendations against administrative security governance.
Selecting the option that uses cloud-only accounts excluded from MFA policies satisfies the requirement, while other options either create lockout risks, misconfigure PIM, or introduce unnecessary on-premises dependencies.
Provides a robust, compliant emergency access design aligned with Microsoft architectural best practices.

Key Concept

Emergency access accounts (break-glass accounts) design in Microsoft Entra ID
Question 232Question

A smart grid utility provider is planning to migrate its relational data workloads to Azure. The migration includes the following two target databases:

* TelemetryDB stores real-time smart meter telemetry data and requires full access to the operating system's registry and local file system to run legacy hardware-interface drivers.
* BillingDB stores customer billing history and requires support for cross-database queries and SQL Server Agent jobs to automate end-of-month processing, but the operations team wants to eliminate operating system-level patching and management.

Which two Azure SQL deployment options should you recommend to host these databases? (Select two.)

Select all that apply

Show answer & explanation

Answer: SQL Server on Azure Virtual Machines for TelemetryDB; Azure SQL Managed Instance for BillingDB

Answer

SQL Server on Azure Virtual Machines for TelemetryDB and Azure SQL Managed Instance for BillingDB
Hosting TelemetryDB on SQL Server on Azure Virtual Machines is correct because the database requires full access to the operating system registry and file system to run legacy drivers, which is only supported in an IaaS model. Hosting BillingDB on Azure SQL Managed Instance is correct because it provides a fully managed PaaS environment that eliminates operating system patching while supporting cross-database queries and SQL Server Agent.

Step-by-Step Solution

1
Analyze the requirements for TelemetryDB to determine the necessary level of control.
TelemetryDB requires OS-level registry and file system access to support legacy hardware-interface drivers.
Identifying these requirements rules out fully managed PaaS solutions (Azure SQL Database and Azure SQL Managed Instance), which do not expose the underlying operating system.
2
Analyze the requirements for BillingDB to determine the necessary level of service management.
BillingDB requires cross-database queries and SQL Server Agent, but also requires a fully managed environment without OS patching.
Identifying these requirements rules out Azure SQL Database single database (which lacks native SQL Server Agent and cross-database queries) and SQL Server on Azure VMs (which requires manual OS patching).
3
Match each database to the appropriate Azure SQL deployment option.
TelemetryDB must be hosted on SQL Server on Azure Virtual Machines, and BillingDB must be hosted on Azure SQL Managed Instance.
This combination satisfies all configuration, compatibility, and management constraints.

Key Concept

Understanding the feature support and management boundaries of different Azure SQL deployment options (Azure SQL Database, Azure SQL Managed Instance, and SQL Server on Azure VMs) is critical to matching legacy requirements with the appropriate service tier.
Question 233Question

An enterprise e-commerce platform is migrating its containerized workloads to Azure Kubernetes Service (AKS) running on Linux nodes. You are designing the storage architecture to meet the following requirements:

* A shared file share is required to store product catalog assets. It must be mounted directly by multiple concurrent Linux pods, support the NFS v4.1 protocol, provide zone redundancy, and deliver sub-millisecond latency for metadata operations.
* A stateful database container requires a persistent volume that supports at least 25,00025,000 IOPS and sub-millisecond write latency, and must remain available even if a single Azure availability zone suffers an outage.

Which two storage configurations should you include in your design? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Premium Azure Files share using the NFS v4.1 protocol configured with Zone-Redundant Storage (ZRS); Premium SSD v2 managed disks configured with Zone-Redundant Storage (ZRS)

Answer

Premium Azure Files share using the NFS v4.1 protocol configured with Zone-Redundant Storage (ZRS) and Premium SSD v2 managed disks configured with Zone-Redundant Storage (ZRS)
The required architecture must include a high-performance shared file system and a high-performance database persistent volume, both configured with Zone-Redundant Storage (ZRS). A Premium Azure Files share configured with NFS v4.1 and ZRS satisfies the file share requirement by supporting concurrent Linux pod mounting, low latency, and zone-redundant availability. Premium SSD v2 managed disks configured with ZRS satisfy the database requirement by supporting up to 80,000 IOPS and sub-millisecond latency while providing zone redundancy.

Step-by-Step Solution

1
Evaluate the requirements for the shared file system: concurrent Linux pod mounting, NFS v4.1 protocol, zone redundancy, and sub-millisecond metadata latency.
Identify that Premium Azure Files configured with ZRS and NFS v4.1 fulfills all performance and accessibility requirements, as standard tiers do not support these performance levels or protocol configurations.
Premium Azure Files is designed for high-performance and low-latency workloads, offering NFS v4.1 support and ZRS.
2
Evaluate the database persistent volume requirements: 25,00025,000 IOPS, sub-millisecond write latency, and protection against a single zone outage.
Identify that Premium SSD v2 managed disks support ZRS and can scale up to 80,00080,000 IOPS and sub-millisecond latency, whereas Ultra Disk only supports LRS and cannot satisfy the zone failure protection requirement.
ZRS is required to survive a single availability zone failure at the storage layer, which rules out Ultra Disk.

Key Concept

Selecting Azure storage solutions (Azure Files and managed disks) based on performance, protocol, and availability requirements.
Question 234Question

A financial technology enterprise is designing a secure integration interface for a partner firm, Alpha Analytics, to retrieve historical transaction records stored in an Azure Blob Storage container named `tx-archive-2026`. The design must satisfy the following requirements:
- Alpha Analytics must have read-only access to the blobs.
- Access must be limited to a maximum duration of 4848 hours.
- Access must be restricted to Alpha Analytics' public outbound IP range (203.0.113.0/24203.0.113.0/24).
- The enterprise must have the capability to immediately revoke access before the 4848-hour window expires, without rotating the storage account keys or affecting other services.

Which storage security and access control solution should you recommend?

Show answer & explanation

Answer: Create a stored access policy on the container that specifies Read permissions. Generate a service Shared Access Signature (SAS) associated with the stored access policy, and configure the SAS to restrict access to the IP range 203.0.113.0/24203.0.113.0/24.

Answer

Create a stored access policy on the container that specifies Read permissions. Generate a service Shared Access Signature (SAS) associated with the stored access policy, and configure the SAS to restrict access to the IP range 203.0.113.0/24203.0.113.0/24.
The correct solution uses a service Shared Access Signature (SAS) linked to a stored access policy. By specifying the Read permissions and expiration on the stored access policy, the enterprise can revoke access instantly by modifying or deleting the policy, without needing to rotate the master storage account keys. The IP restriction is placed directly on the generated SAS token to meet the network requirements.

Step-by-Step Solution

1
Analyze the requirement for individual revocation of the access token.
Identify that to revoke a Shared Access Signature (SAS) without changing the storage account master keys, the SAS must be associated with a stored access policy.
Stored access policies reside on the storage container and can be modified or deleted to instantly invalidate any associated SAS tokens.
2
Apply constraints for permissions, time duration, and network limits.
Define Read permissions and a maximum of 4848 hours of validity on the stored access policy. Apply the IP restriction of 203.0.113.0/24203.0.113.0/24 on the SAS token parameters.
This satisfies the read-only, time-bounded, and network-isolated access requirements.
3
Evaluate identity and role assignment options.
Select the service SAS over direct RBAC assignments or permanent PIM groups.
Direct user RBAC assignments violate scalable management principles, and active/permanent PIM assignments violate JIT principles while requiring excessive administrative overhead.

Key Concept

Stored Access Policies vs. Ad-hoc SAS for Revocation Control
Question 235Question

An enterprise is designing a data analytics and integration platform on Azure to process and analyze financial transaction records. The platform must meet the following requirements:

- Historical Data: Store 150 TB150\text{ TB} of structured historical data in Parquet format. The storage solution must remain resilient against a regional datacenter outage.
- Daily Ingestion: Process 2 TB2\text{ TB} of new transaction records appended nightly. The batch integration pipeline runs for 33 hours and requires support for complex transactional upsert operations.
- Ad-hoc Analytics: Allow data analysts to run occasional, unpredictable ad-hoc queries throughout the day. Each query typically scans up to 10 TB10\text{ TB} of data.
- Interactive Reporting: Serve a critical executive dashboard accessed concurrently by up to 100100 users between 09:00 and 11:00 daily. Dashboard queries require a guaranteed response latency of under 55 seconds against a pre-aggregated 50 GB50\text{ GB} dataset.
- Cost Optimization: Minimize operational and compute costs, avoiding charges for idle resources when no queries are active.

Which architectural solution should you recommend?

Show answer & explanation

Answer: Configure Azure Data Lake Storage Gen2 (ADLS Gen2) with Geo-Redundant Storage (GRS). Use Azure Synapse Spark pools to execute the nightly ETL pipeline and write upserts in Delta format. For ad-hoc analytics, use an Azure Synapse Serverless SQL pool. Load the pre-aggregated dashboard dataset into an Azure SQL Database Serverless tier.

Answer

Configure Azure Data Lake Storage Gen2 (ADLS Gen2) with Geo-Redundant Storage (GRS). Use Azure Synapse Spark pools to execute the nightly ETL pipeline and write upserts in Delta format. For ad-hoc analytics, use an Azure Synapse Serverless SQL pool. Load the pre-aggregated dashboard dataset into an Azure SQL Database Serverless tier.
The correct solution uses Azure Data Lake Storage Gen2 with GRS to satisfy the regional resilience requirement. Azure Synapse Spark pools run only when active during the nightly 33-hour ETL window to perform transactional updates (upserts) in Delta format. For ad-hoc queries, a Serverless SQL pool charges only per TB scanned, which is ideal for occasional use. For the high-concurrency dashboard, Azure SQL Database Serverless provides sub-second query latency and automatically pauses during off-peak hours, ensuring cost optimization.

Step-by-Step Solution

1
Select the storage redundancy model based on resilience requirements.
Azure Data Lake Storage Gen2 (ADLS Gen2) configured with Geo-Redundant Storage (GRS).
GRS replicates data asynchronously to a secondary region, protecting against regional datacenter outages, whereas LRS only replicates within a single datacenter.
2
Select the query engine for occasional, large ad-hoc queries.
Azure Synapse Serverless SQL pool.
Since ad-hoc queries run occasionally and scan up to 10 TB10\text{ TB} each, a Serverless SQL pool is highly cost-effective because it charges only per data scanned ($5 per TB) and incurs zero costs when idle.
3
Select the database engine to serve high-concurrency dashboard queries.
Azure SQL Database Serverless.
Azure SQL Database handles high-concurrency workloads for small datasets (50 GB50\text{ GB}) efficiently. The Serverless tier scales compute dynamically during peak hours (09:00 to 11:00) and autopauses during inactive hours to minimize costs.
4
Select the processing engine for nightly transactional batch ETL.
Azure Synapse Spark pools using Delta format.
Spark pools handle large scale ETL (2 TB2\text{ TB} daily) efficiently, support Delta Lake for ACID transaction support and upserts, and automatically pause when the 33-hour pipeline completes.

Key Concept

Designing a modern data warehouse architecture that separates storage, batch processing, interactive serving, and ad-hoc query capabilities using serverless and auto-scaling components to optimize cost and performance.
Question 236Question

A global retail company is planning its peak shopping season operations in Azure. The security architecture team needs to delegate temporary administrative access to the Site Reliability Engineering (SRE) team to manage Azure Kubernetes Service (AKS) clusters during maintenance windows. The design must ensure zero-standing administrative privileges, adhere to the principle of least administrative overhead for user management, and protect the tenant against lockouts.

Which of the following actions should you include in the identity governance and privileged access design? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra ID security group for the SRE team, and make this group eligible for the required Azure RBAC roles in Privileged Identity Management (PIM).; Exclude emergency-access (break-glass) accounts from any Conditional Access policies that enforce multi-factor authentication (MFA) for administrative roles.

Answer

Create a Microsoft Entra ID security group for the SRE team and make it eligible for Azure RBAC roles in PIM, and exclude emergency-access accounts from Conditional Access policies enforcing MFA.
Minimizing administrative overhead and enforcing zero-standing access is achieved by assigning SREs to a security group and making that group eligible for the target roles in PIM. To prevent complete tenant lockout, emergency-access accounts must be excluded from strict Conditional Access policies requiring MFA.

Step-by-Step Solution

1
Analyze requirements for zero-standing privileges and minimal user-management overhead.
Identify that Privileged Identity Management (PIM) with eligible assignments should be used, and the roles should be assigned to a security group rather than individual users.
Eligible role assignments require activation on-demand to achieve zero-standing privileges, while assigning roles to groups simplifies administration.
2
Address the requirement to prevent tenant lockout during administrative access configurations.
Determine that emergency-access (break-glass) accounts must be excluded from multi-factor authentication (MFA) requirements in Conditional Access.
Failing to exclude break-glass accounts from MFA policies risks a total tenant lockout if the MFA service encounters an outage.

Key Concept

Designing secure identity delegation using Microsoft Entra Privileged Identity Management (PIM) eligible groups and ensuring emergency lockout protection.
Estimated Time:2m 0s
Question 237Question

A company is planning to migrate an on-premises SQL Server database to Azure. The database requires the use of SQL Server Agent to run scheduled maintenance tasks and relies on cross-database queries. The migration solution must also support automatic database backups with a retention period of up to 10 years.

Which two Azure SQL deployment options support these requirements? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure SQL Managed Instance; SQL Server on Azure Virtual Machines

Answer

Azure SQL Managed Instance and SQL Server on Azure Virtual Machines
Azure SQL Managed Instance and SQL Server on Azure Virtual Machines are the deployment options that support instance-level features like SQL Server Agent and cross-database queries. Both options also support backing up databases with long-term retention up to 10 years.

Step-by-Step Solution

1
Identify the legacy feature requirements in the scenario.
The database requires SQL Server Agent and cross-database queries.
These requirements narrow the choice to deployment options that provide instance-level capabilities.
2
Evaluate the Azure SQL deployment options against the identified legacy requirements.
Azure SQL Managed Instance and SQL Server on Azure Virtual Machines support both SQL Server Agent and cross-database queries natively. Azure SQL Database (single database and elastic pools) does not natively support these features.
Azure SQL Database is a database-level service, whereas SQL Server Agent and cross-database queries require instance-level features.
3
Verify backup retention requirements for the compatible deployment options.
Both Azure SQL Managed Instance (via Long-Term Retention) and SQL Server on Azure Virtual Machines (via Azure Backup for SQL Server) support automated backups with up to 10 years of retention.
This step confirms both options fully satisfy all functional and recovery constraints.

Key Concept

Azure SQL Deployment Options Feature Compatibility
Question 238Question

A logistics company is designing a disaster recovery solution for an application database. The database is currently hosted on Azure SQL Managed Instance. The solution must meet the following requirements:
- Support automatic failover to a secondary region.
- Provide a single connection endpoint for read-write traffic and a separate endpoint that automatically routes read-only reporting queries to the secondary region.
- Keep the Recovery Point Objective (RPO) under 5 seconds.
- Ensure all replication traffic between the primary and secondary instances remains within a private network boundary.

Which solution should you recommend?

Show answer & explanation

Answer: An Azure SQL Managed Instance Failover Group deployed across peered virtual networks, utilizing the read-only listener endpoint for reporting.

Answer

An Azure SQL Managed Instance Failover Group deployed across peered virtual networks, utilizing the read-only listener endpoint for reporting.
The correct solution uses an Azure SQL Managed Instance Failover Group configured across peered virtual networks. Failover Groups support automatic failover, meet the low RPO, and provide two distinct listener endpoints (read-write and read-only). The read-only endpoint automatically routes reporting traffic to the secondary instance, while virtual network peering ensures that all replication traffic remains secure and private.

Step-by-Step Solution

1
Identify the source database service model and HA/DR capabilities.
The workload runs on Azure SQL Managed Instance. This service supports Failover Groups for cross-region disaster recovery and automatic failover, but does not support Active Geo-Replication.
Choosing the correct replication feature is critical since features vary between Azure SQL Database and Azure SQL Managed Instance.
2
Verify read-scale requirements and routing.
Failover Groups provide a read-write listener and a read-only listener. The read-only listener automatically routes traffic to the secondary replica without needing connection string changes in the main application.
This satisfies the requirement to route reporting queries to the secondary region using a dedicated endpoint.
3
Determine the network security configuration.
Configuring virtual network peering between the virtual networks hosting the primary and secondary Managed Instances allows private traffic routing over the Azure backbone.
This satisfies the security requirement to keep replication traffic within a private network boundary.

Key Concept

Azure SQL Managed Instance Failover Groups
Question 239Question

An enterprise is designing the security and access control architecture for an Azure Storage account named finstatements that will host sensitive monthly financial statements. The design must meet the following requirements:

* Internal auditors must be granted temporary Read access to the statements only when actively performing a quarterly audit. The activation of this access must require multi-factor authentication (MFA) and administrative approval.
* Auditor access must be managed at a group level to ensure scalable administration and avoid individual user-level assignments.
* An automated reporting service must have Read access to the statements using a Shared Access Signature (SAS) that expires in 180 days, but the SAS must be capable of being revoked immediately if compromised without affecting other storage operations.

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

Select all that apply

Show answer & explanation

Answer: Configure Microsoft Entra Privileged Identity Management (PIM) to make a Microsoft Entra ID group containing the auditors eligible for the Storage Blob Data Reader role.; Generate the SAS token for the automated reporting service by associating it with a Stored Access Policy on the destination blob container.

Answer

Configure Microsoft Entra Privileged Identity Management (PIM) to make a Microsoft Entra ID group containing the auditors eligible for the Storage Blob Data Reader role, and generate the SAS token for the automated reporting service by associating it with a Stored Access Policy on the destination blob container.
The correct configurations involve using Microsoft Entra Privileged Identity Management (PIM) to make a Microsoft Entra ID group containing the auditors eligible for the Storage Blob Data Reader role, and generating the SAS token for the automated reporting service by associating it with a Stored Access Policy. Using PIM with an eligible group assignment ensures JIT access, approval workflows, and scalable group management. Associating the SAS token with a Stored Access Policy enables immediate revocation by removing or modifying the policy without rotating storage account keys.

Step-by-Step Solution

1
Analyze the access requirements for the internal auditors.
Auditors require temporary access that is group-managed and requires MFA/approval on activation.
Privileged Identity Management (PIM) provides just-in-time (JIT) access control. Assigning eligibility to a group ensures group-level scalability and prevents direct user-level role assignments.
2
Analyze the access requirements for the automated reporting service.
The service requires a SAS token valid for 180 days that can be revoked immediately.
An ad-hoc SAS token cannot be individually revoked before its expiration date. Associating the SAS token with a Stored Access Policy enables individual revocation by deleting or updating the policy on the storage container.

Key Concept

Securing data storage access using just-in-time role eligibility via PIM and revocable SAS tokens via Stored Access Policies.
Question 240Question

An organization is designing a secure access and identity infrastructure using Microsoft Entra ID. The solution must enforce different access controls and verification methods depending on the context of the authentication attempt. Match each business or technical security requirement to the most appropriate Microsoft Entra ID or Conditional Access feature.

Click a left item, then click its matching right item

Items

Require multi-factor authentication (MFA) only when a sign-in attempt is classified as a medium or high risk based on real-time telemetry.
Block access to cloud applications when user connections originate from geographic regions outside the organization's approved operating zones.
Restrict administrative access to Microsoft Azure portal to require phishing-resistant authentication methods such as FIDO2 security keys.
Prevent non-compliant corporate devices from accessing business-critical cloud applications.

Matches

Show answer & explanation

Answer

Sign-in risk policy matches with requiring MFA for medium/high risk; Named locations match with blocking access from unapproved geographic regions; Authentication strengths match with restricting administrative access to phishing-resistant methods; Device compliance requirement matches with blocking non-compliant devices.
The correct mapping pairs each operational requirement to its specialized Conditional Access or Entra ID authentication capability: risk-based policies monitor real-time threat levels, named locations restrict geographic access, authentication strengths dictate the credential type (such as phishing-resistant), and device state checks verify management compliance.

Step-by-Step Solution

1
Identify the requirement to evaluate real-time sign-in safety and apply MFA selectively.
This requires evaluating risk levels on a per-session basis, which aligns with Microsoft Entra ID Protection's sign-in risk policies.
Sign-in risk checks verify if the credentials might be compromised during the authentication flow.
2
Identify the requirement to block access based on geographic location parameters.
This maps to defining named locations (either IP ranges or countries) and targeting them within a Conditional Access policy set to block access.
Named locations are the primary mechanism for location-based Conditional Access rules.
3
Identify the requirement to enforce phishing-resistant authentication methods for administrators.
This requires using Entra ID authentication strengths within a Conditional Access policy.
Authentication strengths allow granular specification of permitted credentials (such as FIDO2 security keys) rather than a general MFA challenge.
4
Identify the requirement to verify device health status before permitting app access.
This requires using the device compliance status grant control within a Conditional Access policy.
Conditional Access can read the device compliance status from mobile device management solutions like Microsoft Intune to grant or deny access.

Key Concept

Designing granular access control policies using Microsoft Entra ID Conditional Access and authentication configurations.
PreviousPage 12 / 60Next
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin