All practice questions

1198 questions

Question 841Question

A retail company plans to migrate two on-premises SQL Server workloads to Azure. The migration requirements are as follows:

* Workload A: Runs an inventory application that requires cross-database queries across three databases and uses SQL Server Agent for automated maintenance tasks. The solution must minimize database administration effort.
* Workload B: Runs a customer feedback application that experiences highly unpredictable traffic patterns, with long periods of inactivity. Compute costs must be minimized during inactive periods, and the data must remain resilient against a local datacenter outage.

Which two Azure SQL options should you recommend?

Select all that apply

Show answer & explanation

Answer: Azure SQL Managed Instance for Workload A; Azure SQL Database Serverless for Workload B

Answer

Azure SQL Managed Instance for Workload A and Azure SQL Database Serverless for Workload B
Azure SQL Managed Instance is chosen for Workload A because it natively supports SQL Server Agent and cross-database queries, which are missing from Azure SQL Database single database, and reduces VM patching and management tasks. Azure SQL Database Serverless is chosen for Workload B because it provides an auto-pause feature that saves compute costs during inactive periods, and it can be deployed with zone redundancy to survive a local datacenter outage.

Step-by-Step Solution

1
Evaluate Workload A requirements: SQL Agent, cross-database queries, and minimized administrative effort.
Azure SQL Managed Instance is selected because it natively supports SQL Agent and cross-database queries, unlike Azure SQL Database single database, and has less administrative overhead than SQL Server on Azure VMs.
Managed Instance provides full PaaS benefits with near 100% compatibility with on-premises SQL Server features.
2
Evaluate Workload B requirements: unpredictable traffic, compute cost minimization during inactive periods, and resilience against local datacenter outages.
Azure SQL Database Serverless with Zone-Redundant Storage (ZRS) or Geo-Redundant Storage (GRS) is selected. Locally Redundant Storage (LRS) is ruled out.
Serverless tier supports auto-pausing to save on compute costs during idle periods, while LRS does not survive a datacenter-level failure.

Key Concept

Selecting appropriate Azure SQL deployment models based on operational features (SQL Agent, cross-database queries), scaling patterns (Serverless auto-pausing), and high availability requirements.
Estimated Time:2m 0s
Question 842Question

A company is setting up a development environment on an Azure virtual machine that runs a database. The database transaction logs require high-speed performance, and the database backups must be stored in a storage account that remains available if a single datacenter in the region fails.

Which disk type and storage replication option should be selected?

Show answer & explanation

Answer: Premium SSD for the transaction logs, and Zone-Redundant Storage for the backups

Answer

Premium SSD for the transaction logs, and Zone-Redundant Storage for the backups
The correct selection is Premium SSD for transaction logs combined with Zone-Redundant Storage for backups. Premium SSD satisfies the high-speed and low-latency performance demands of transactional logging, while Zone-Redundant Storage replicates backup data across multiple availability zones within the region, ensuring survival during a single datacenter failure.

Step-by-Step Solution

1
Evaluate the disk performance requirements for database transaction logs.
Database transaction logs are write-intensive and require low-latency performance. Premium SSD or Ultra Disk is appropriate, whereas Standard HDD is insufficient.
Standard HDD lacks the IOPS and throughput capabilities required to prevent performance bottlenecks on transaction logs.
2
Evaluate the resilience requirements for database backups.
To survive a physical failure of a single datacenter within a region, the data must be replicated across separate zones (Zone-Redundant Storage). Locally Redundant Storage (LRS) is insufficient.
LRS restricts replication to a single physical datacenter facility.
3
Identify the storage configuration that satisfies both requirements.
The correct combination is Premium SSD for the database transaction logs and Zone-Redundant Storage for the backups.
This configuration meets both performance and availability targets.

Key Concept

Selecting appropriate Azure storage tiers and redundancy options to balance performance workloads and disaster resilience requirements.
Question 843Question

Kestrel BioPharma has an on-premises Active Directory Domain Services (AD DS) forest containing 8,500 users. The company is designing a hybrid identity solution to integrate their AD DS forest with a new Microsoft Entra ID tenant. The solution must meet the following requirements:
- Users must sign in to cloud services using their on-premises credentials.
- The company must use Microsoft Entra ID Protection to identify compromised credentials that are leaked on the public internet.
- User authentication must succeed even if the on-premises network connection is temporarily unavailable.
- On-premises infrastructure requirements for authentication must be minimized.

Which identity synchronization and authentication method should you recommend?

Show answer & explanation

Answer: Password Hash Synchronization (PHS) with seamless Single Sign-On (SSO)

Answer

Password Hash Synchronization (PHS) with seamless Single Sign-On (SSO)
Password Hash Synchronization (PHS) satisfies all requirements. It replicates a hash of the user's password hash to Microsoft Entra ID, which allows authentication to take place in the cloud. Consequently, users can sign in even if the on-premises network is offline. PHS is also the only synchronization method that natively allows Microsoft Entra ID Protection to evaluate password hashes against leaked credentials. Furthermore, it requires no on-premises infrastructure for the authentication pathway, unlike federation or pass-through agents.

Step-by-Step Solution

1
Analyze the security and sign-in requirements for compromised credential detection and network outage resiliency.
Determined that Microsoft Entra ID Protection's leaked credential detection requires password hashes to be present in Microsoft Entra ID, and that authentication must function when the on-premises network is offline.
These requirements exclude authentication options that validate passwords strictly on-premises in real-time.
2
Evaluate the remaining options against the footprint constraint to minimize on-premises infrastructure.
Password Hash Synchronization (PHS) satisfies the requirements by shifting authentication entirely to the cloud with minimal local setup.
Unlike federated identity or pass-through architectures, PHS does not require dedicated on-premises authentication servers or high-availability agents in the authentication path.

Key Concept

Selecting hybrid identity authentication methods based on resiliency, security features, and infrastructure constraints
Question 844Question

You are designing an Azure Cosmos DB solution for a global retail application that manages product inventory. The application requires global replication across three Azure regions to support low-latency reads and writes, and it must scale to handle a 10:9010:90 read-to-write ratio. The database must achieve a 99.999%99.999\% write availability SLA and prevent hot partitions.

Which configuration should you recommend?

Show answer & explanation

Answer: Configure multi-region writes and set the partition key to a high-cardinality field such as ItemId.

Answer

Configure multi-region writes and set the partition key to a high-cardinality field such as ItemId.
Configuring multi-region writes allows writes to be processed locally in multiple regions, which meets the 99.999%99.999\% availability SLA and ensures low latency. Using a high-cardinality key like ItemId ensures write workloads are evenly distributed across physical storage partitions.

Step-by-Step Solution

1
Analyze the availability and replication requirements.
The solution must support low-latency reads and writes across three regions with a 99.999%99.999\% write availability SLA, which requires configuring multi-region writes.
Single-region writes cannot meet the 99.999%99.999\% SLA or provide low-latency writes globally.
2
Evaluate the partition key strategy to prevent hot partitions under a 10:9010:90 read-to-write (write-heavy) workload.
The partition key must have high cardinality to distribute writes evenly across physical partitions.
Low-cardinality keys like ProductStatus will bundle writes into a few logical partitions, causing throttling.
3
Select the option that correctly combines these design decisions.
Configuring multi-region writes with a high-cardinality partition key like ItemId satisfies all constraints.
This configuration provides the necessary scale, availability, and throughput distribution.

Key Concept

Azure Cosmos DB partition key selection and multi-region replication configuration
Estimated Time:1m 0s
Question 845Question

You are designing an identity security strategy for a manufacturing enterprise named Fabrikam, Inc. The enterprise has a Microsoft Entra ID tenant and wants to protect its Azure management interfaces. You must design a solution that meets the following requirements:
- All users assigned to highly privileged roles must use multi-factor authentication (MFA) to access the Azure portal.
- Privileged access must follow the principle of least privilege, ensuring roles are activated only when needed for a maximum of 4 hours.
- In the event of an unexpected Microsoft Entra MFA service outage, administrators must be able to log in to resolve the issue.
- The design must minimize administrative overhead and local infrastructure dependencies.

Which identity and access design should you recommend?

Show answer & explanation

Answer: Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments. Create a Conditional Access policy targeting administrative roles that requires MFA, and exclude a dedicated, cloud-only emergency access account from this policy.

Answer

Configure Microsoft Entra Privileged Identity Management (PIM) with eligible role assignments, enforce MFA for administrative roles using a Conditional Access policy, and exclude a dedicated cloud-only emergency access account from that policy.
The correct design uses Microsoft Entra Privileged Identity Management (PIM) with eligible assignments to ensure administrative roles are only active when needed, limiting standing access. Multi-factor authentication is enforced natively using a Conditional Access policy targeting administrative directory roles. By excluding a cloud-only emergency access account from this Conditional Access policy, the design ensures that administrators can regain control of the tenant if a primary authentication factor or MFA service outage occurs, minimizing local dependencies and administrative overhead.

Step-by-Step Solution

1
Analyze role activation requirements.
Determine that Microsoft Entra Privileged Identity Management (PIM) with eligible assignments is required to achieve just-in-time (JIT) role activation and adhere to the least privilege principle.
Eligible assignments require users to perform an activation step (with timed duration), whereas active assignments grant persistent privileges.
2
Select the appropriate MFA enforcement mechanism.
Select Microsoft Entra Conditional Access targeting administrative roles to enforce MFA during portal access.
Conditional Access provides granular control to require MFA for administrative roles without needing on-premises federation servers.
3
Design lockout resilience.
Define an exclusion in the Conditional Access MFA policy for a dedicated, cloud-only emergency access account (break-glass account).
If Microsoft Entra MFA is disrupted, the excluded emergency account can still sign in to modify policies or manage the tenant.
4
Evaluate local infrastructure requirements.
Avoid configuring Active Directory Federation Services (AD FS) as it introduces on-premises infrastructure dependencies, violating the requirement to minimize overhead.
Cloud-native capabilities in Microsoft Entra ID meet all constraints without requiring local servers.

Key Concept

Microsoft Entra ID Conditional Access, PIM, and emergency access account best practices.
Estimated Time:2m 0s
Question 846Question

A retail company plans to reorganize its Azure subscription governance. You are designing a strategy to delegate subscription-level billing and resource group management permissions using a custom Azure RBAC role. The custom role must be applied across multiple new subscriptions that will be grouped under a new management group hierarchy. You need to recommend the correct sequence of steps to implement this strategy while ensuring that administrators have immediate, inherited access to the subscriptions as soon as they are governed by the new hierarchy, and that no invalid scope references are created. Which sequence of actions should you recommend?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

Create the new management group hierarchy under the Tenant Root Group, define the custom Azure RBAC role specifying the new management group ID in the AssignableScopes property, assign the custom role to the Microsoft Entra ID security group at the management group scope, and then move the targeted Azure subscriptions into the new management group hierarchy.
Establishing the management group hierarchy first is required to obtain a valid resource ID for the custom role's assignable scopes. The custom role must then be defined before it can be assigned. Assigning the custom role at the management group level before moving subscriptions ensures that permissions are immediately inherited, eliminating any window where resources are unmanaged.

Step-by-Step Solution

1
Create the management group hierarchy.
The target Management Group hierarchy is established, producing a valid resource ID scope.
To provide a valid scope for the custom role's AssignableScopes and role assignment.
2
Define the custom role with AssignableScopes set to the management group.
The custom role is registered in Azure RBAC, ready for assignment.
A custom role must exist and target the correct assignable scope before it can be assigned.
3
Create the role assignment at the management group level for the Entra ID security group.
The security group is authorized to perform the role's actions across the entire management group hierarchy.
To ensure permission inheritance is established at the destination scope before resources are introduced.
4
Move the subscriptions into the management group hierarchy.
Subscriptions immediately inherit the custom role permissions.
To govern the subscriptions under the new model without causing administrative gaps.

Key Concept

Subscription governance deployment sequence and RBAC inheritance rules.
Question 847Question

An organization is designing a shared storage architecture for a hybrid application. The application components are deployed in an Azure Kubernetes Service (AKS) cluster and on-premises virtual machines. The solution must meet the following requirements:
- Provide a shared file system that can be mounted concurrently by multiple AKS pods (ReadWriteMany) and the on-premises virtual machines using the SMB protocol.
- Ensure that the storage can survive a physical zone outage in the primary Azure region without data loss or service disruption.
- Provide access to on-premises users using their existing on-premises Active Directory Domain Services (AD DS) credentials.
- Secure the storage access; if Shared Access Signatures (SAS) are used for any ad-hoc diagnostic transfers, they must support easy revocation.

Which two actions should you include in the storage design?

Select all that apply

Show answer & explanation

Answer: Create an Azure Files Premium file share configured with Zone-Redundant Storage (ZRS).; Enable on-premises Active Directory Domain Services (AD DS) authentication for the Azure storage account.

Answer

To meet the requirements, the design must include creating an Azure Files Premium file share configured with Zone-Redundant Storage (ZRS) and enabling on-premises Active Directory Domain Services (AD DS) authentication for the Azure storage account.
The correct architecture consists of creating an Azure Files Premium file share configured with Zone-Redundant Storage (ZRS) and enabling on-premises Active Directory Domain Services (AD DS) authentication. ZRS ensures high availability across zones. Premium files deliver the required sub-second failover and high performance for containerized workloads. On-premises AD DS integration allows seamless mounting of SMB shares using existing corporate credentials.

Step-by-Step Solution

1
Select the appropriate storage service and protocol.
Azure Files Premium SMB share is chosen to support ReadWriteMany mounts from AKS and SMB access from on-premises virtual machines.
Azure Files provides managed SMB shares that can be mounted concurrently by AKS pods and on-premises virtual machines.
2
Choose the replication strategy to handle zonal outages.
Zone-Redundant Storage (ZRS) is selected.
ZRS replicates data synchronously across three availability zones in the primary region, surviving a zone outage without service disruption.
3
Configure the authentication mechanism for hybrid access.
On-premises Active Directory Domain Services (AD DS) authentication is enabled on the storage account.
This allows clients to authenticate to the Azure file shares using their existing on-premises domain credentials over VPN or ExpressRoute.
4
Ensure secure and revocable SAS generation.
Stored access policies should be used instead of long-lived, direct-URI SAS tokens.
Ad-hoc SAS tokens with long lifetimes created without a stored access policy cannot be easily revoked without rotating the storage keys, which causes service disruption.

Key Concept

Designing secure, zone-resilient hybrid file storage using Azure Files Premium with ZRS and on-premises AD DS integration.
Question 848Question

An enterprise organization is designing a privileged access solution for Microsoft Entra ID. The solution must secure administrative access to the User Administrator role. The design must ensure that administrators only have access when needed, direct assignment of roles to individual user accounts is avoided, and activation requires approval. In the event of an identity service disruption, emergency break-glass accounts must remain functional and not be locked out. Which two of the following configuration steps should you include in the design?

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra role-assignable group, assign the User Administrator role to the group, and configure Privileged Identity Management (PIM) for Groups to make administrators eligible for group membership.; Configure Privileged Identity Management (PIM) activation settings for the User Administrator role to require Multi-Factor Authentication (MFA) and designate a specific approver group.

Answer

To meet the requirements, the design must use a Microsoft Entra role-assignable group combined with Privileged Identity Management (PIM) for Groups to manage eligibility dynamically, and configure PIM settings for the User Administrator role to require MFA and administrative approval.
The correct architecture uses Microsoft Entra role-assignable groups managed via PIM for Groups to avoid assigning privileges directly to individual user accounts. Simultaneously, configuring PIM activation policies for the role ensures that any eligible member who tries to activate the role must complete multi-factor authentication and receive approval from the designated group before access is provisioned.

Step-by-Step Solution

1
Evaluate the requirement for avoiding direct individual role assignments.
Identify that assigning roles to a role-assignable group managed via PIM for Groups is the recommended approach for scalable administration.
Direct role assignments to individual user accounts increase administrative overhead and are harder to audit.
2
Evaluate the requirement for just-in-time access verification and approval.
Identify that configuring PIM settings for the role is the standard way to enforce MFA and approval flows on activation.
PIM role settings manage the lifecycle and verification requirements of role activation.
3
Analyze the impact on emergency access accounts.
Identify that emergency accounts must be excluded from policies that enforce MFA blockages to prevent lockout.
Exclusions are critical to ensure that break-glass accounts remain functional during identity failures.

Key Concept

Privileged access governance and just-in-time role activation using Microsoft Entra PIM and role-assignable groups.
Estimated Time:2m 0s
Question 849Question

You are designing an Azure storage solution for a company that is deploying a new logging application and a critical backup system. You have the following requirements:

1. The logging application requires high-performance managed disk storage to support continuous, low-latency write operations.
2. The critical backup files must remain highly available even if an entire Azure data center in the primary region suffers a complete power outage.

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

Select all that apply

Show answer & explanation

Answer: Premium SSD Managed Disks for the logging application; Zone-redundant storage (ZRS) for the critical backups

Answer

The correct configurations are to use Premium SSD Managed Disks for the logging application and Zone-redundant storage (ZRS) for the critical backups.
Premium SSD Managed Disks provide the performance and low latency necessary for continuous write operations in a logging application, while Zone-redundant storage (ZRS) protects critical backups against datacenter-wide failures by replicating data across multiple physical zones.

Step-by-Step Solution

1
Determine the optimal disk type for the logging workload.
Premium SSD Managed Disks are selected because they support low latency and high IOPS required for active logging.
Standard HDD disks do not meet performance expectations for continuous, low-latency write operations.
2
Determine the required redundancy tier for the backup files to survive a datacenter outage.
Zone-redundant storage (ZRS) is selected because it replicates data across three separate zones.
Locally redundant storage (LRS) only protects against local hardware failures within a single datacenter and cannot survive a complete datacenter outage.

Key Concept

Selecting appropriate Azure storage tiers and redundancy options based on application performance requirements and disaster recovery constraints.
Estimated Time:1m 0s
Question 850Question

An organization is designing the storage infrastructure for a mission-critical financial application hosted on Azure Virtual Machines. The application has the following storage requirements:

1. Database transaction logs: Must support up to 60,00060,000 IOPS and less than 1 ms1\text{ ms} latency. The storage must remain available even if an entire Azure Availability Zone suffers an outage.
2. Long-term database backups: Must be stored in blob storage, retain high durability, be resilient against a regional disaster, and allow immediate read access to the secondary region at all times.
3. Temporary ETL files: Will be accessed via Shared Access Signatures (SAS) by external partners. The SAS tokens must be valid for 66 months, but the security team must have the ability to immediately revoke access if a token is compromised.

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

Select all that apply

Show answer & explanation

Answer: Provision Azure Premium SSD v2 disks configured with Zone-Redundant Storage (ZRS) for the database transaction logs.; Configure the backup blob storage account to use Read-Access Geo-Redundant Storage (RA-GRS).; Generate Shared Access Signatures (SAS) by binding them to a Stored Access Policy on the blob container.

Answer

To meet the storage requirements, you must provision Azure Premium SSD v2 disks with Zone-Redundant Storage (ZRS) for the transaction logs, configure the backup storage account to use Read-Access Geo-Redundant Storage (RA-GRS), and generate the Shared Access Signatures (SAS) by binding them to a Stored Access Policy.
The correct configurations are: using Azure Premium SSD v2 disks with Zone-Redundant Storage (ZRS) for the transaction logs, because Premium SSD v2 can deliver the required 60,00060,000 IOPS and sub-millisecond latency, while ZRS protects against zone-level failures; using Read-Access Geo-Redundant Storage (RA-GRS) for the backups, which replicates data to a secondary region for disaster recovery and permits read access to the secondary region at all times; using a Stored Access Policy to bind the SAS tokens, which enables immediate revocation of the SAS by simply deleting or changing the policy, without impacting other tokens or rotating storage keys.

Step-by-Step Solution

1
Analyze the virtual machine disk performance and availability requirements.
The workload needs up to 60,00060,000 IOPS, sub-millisecond latency, and zone-level resilience. While Ultra Disk meets the performance limits, it only supports Locally Redundant Storage (LRS). Therefore, Azure Premium SSD v2 with Zone-Redundant Storage (ZRS) must be selected.
Premium SSD v2 supports up to 80,00080,000 IOPS and less than 1 ms1\text{ ms} latency, and supports ZRS configuration in supported regions.
2
Evaluate backup replication requirements.
Backups require durability, regional disaster resilience, and continuous read access in the secondary region. Read-Access Geo-Redundant Storage (RA-GRS) satisfies all these conditions.
RA-GRS provides geo-replication with read access to the secondary endpoint before failover occurs.
3
Establish a secure mechanism for temporary external access with revocation capability.
Shared Access Signatures (SAS) must be bound to a Stored Access Policy.
An ad-hoc SAS cannot be revoked without rotating account keys. A Stored Access Policy allows direct revocation by deleting or updating the policy.

Key Concept

Selecting Azure disk types, blob storage replication models, and SAS security patterns to meet performance, availability, and compliance requirements.
Question 851Question

A global retail firm is designing a privileged access and identity governance strategy for their Azure environment. The firm has the following requirements:
- External developers must be granted temporary, just-in-time (JIT) Contributor access to specific resource groups. This access must be assigned and managed collectively to simplify auditing and onboarding/offboarding.
- The IT department must enforce a tenant-wide Conditional Access policy requiring Multi-Factor Authentication (MFA) for all administrative roles, while ensuring that the organization does not get locked out of the tenant in the event of an MFA service outage.

Which of the following designs meets these requirements while adhering to the principle of least privilege?

Show answer & explanation

Answer: Create a Microsoft Entra security group for the external developers. Configure Microsoft Entra Privileged Identity Management (PIM) for Azure resources to assign the group as eligible for the Contributor role on the target resource groups. Create a Conditional Access policy requiring MFA for administrative roles, and exclude emergency access accounts from this policy.

Answer

Create a Microsoft Entra security group for the external developers. Configure Microsoft Entra Privileged Identity Management (PIM) for Azure resources to assign the group as eligible for the Contributor role on the target resource groups. Create a Conditional Access policy requiring MFA for administrative roles, and exclude emergency access accounts from this policy.
The correct option addresses all compliance requirements. Assigning the Contributor role as eligible to a Microsoft Entra security group ensures just-in-time (JIT) access via PIM, while keeping administration manageable and auditable via group membership. Excluding emergency access (break-glass) accounts from the Conditional Access MFA policy prevents lockout in case of an MFA outage.

Step-by-Step Solution

1
Analyze the governance requirement for group-based resource access.
Identify that permissions must be assigned to Microsoft Entra security groups rather than directly to individual user accounts to adhere to administrative delegation and audit scalability best practices.
Assigning roles directly to individuals is harder to manage and audit over time.
2
Analyze the just-in-time (JIT) access requirement.
Determine that the Contributor role assignment should be configured as eligible in Privileged Identity Management (PIM) rather than active.
Eligible assignments require users to explicitly activate the role when needed, supporting JIT principles, whereas active assignments grant privileges permanently.
3
Analyze the security and availability requirements for administrative MFA.
Exclude emergency access (break-glass) accounts from the Conditional Access policy requiring MFA.
Ensures the organization can access the tenant if an MFA service outage or identity provider disruption occurs, preventing tenant lockout.

Key Concept

Group-based role delegation with Privileged Identity Management (PIM) and Conditional Access emergency exclusions.
Estimated Time:2m 0s
Question 852Question

An enterprise is designing the storage architecture for a transaction database hosted on Azure Virtual Machines and its associated backups. The architecture must meet the following requirements:

* Database Data Volume: Requires 65,000 IOPS and 900 MB/s throughput. The storage must survive a zone outage within the primary region without data loss.
* Database Log Volume: Requires guaranteed sub-millisecond write latency and 10,000 IOPS. Application-level replication provides cross-zone disaster recovery.
* Backups: Must be stored in Azure Blob Storage. An external auditor requires read access to these backups for 48 hours. This access must be immediately revocable at any time without rotating the primary storage account keys.

Which configuration should you recommend?

Show answer & explanation

Answer: Configure Premium SSD v2 with Zone-Redundant Storage (ZRS) for the data volume, Ultra Disk with Locally Redundant Storage (LRS) for the log volume, and generate a Shared Access Signature (SAS) token associated with a stored access policy for the backup blobs.

Answer

Configure Premium SSD v2 with Zone-Redundant Storage (ZRS) for the data volume, Ultra Disk with Locally Redundant Storage (LRS) for the log volume, and generate a Shared Access Signature (SAS) token associated with a stored access policy for the backup blobs.
The correct configuration uses Premium SSD v2 with Zone-Redundant Storage (ZRS) for the data volume to satisfy both the high performance requirements (65,000 IOPS and 900 MB/s) and the zone-failure resiliency requirement. It uses Ultra Disk with Locally Redundant Storage (LRS) for the database log volume to guarantee the sub-millisecond write latency required. Finally, it uses a Shared Access Signature (SAS) token linked to a stored access policy to grant the auditor temporary access to the backups, allowing immediate revocation if necessary without rotating the primary storage account keys.

Step-by-Step Solution

1
Select storage for the database data volume.
Premium SSD v2 with Zone-Redundant Storage (ZRS) is selected.
The data volume requires 65,000 IOPS and 900 MB/s, which exceeds the single-disk limits of Premium SSD v1. Premium SSD v2 supports up to 80,000 IOPS and 1,200 MB/s on a single disk and supports ZRS for zone resiliency. Ultra Disk does not support ZRS.
2
Select storage for the database log volume.
Ultra Disk with Locally Redundant Storage (LRS) is selected.
The database log volume requires guaranteed sub-millisecond write latency, which is a key capability of Ultra Disk. Since replication is handled at the application layer, LRS at the storage layer is acceptable.
3
Select access mechanism for backups.
Shared Access Signature (SAS) associated with a stored access policy.
A stored access policy allows the SAS token to be revoked at any time by modifying or deleting the policy. An ad-hoc SAS token can only be revoked by rotating the storage account keys, which would disrupt other operations.

Key Concept

Azure Managed Disks performance levels (Premium SSD v2 vs. Ultra Disk), disk redundancy (ZRS vs. LRS), and secure Blob access using Shared Access Signatures with stored access policies.
Question 853Question

Tailwind Traders is designing an identity and access management solution for their Microsoft Entra ID tenant. The tenant is synchronized with 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 roles.
- Ensure that administrators can access privileged roles only when required, using a Just-In-Time (JIT) access model that enforces justification and MFA.
- Mitigate the risk of tenant lockout in the event of a Microsoft Entra ID MFA service outage.
- Minimize infrastructure complexity and administrative overhead.

Which identity and access design should you recommend?

Show answer & explanation

Answer: Deploy Password Hash Synchronization (PHS). Configure Microsoft Entra Privileged Identity Management (PIM) with eligible assignments for administrative roles. Create a Conditional Access policy requiring MFA for administrators, and exclude two cloud-only emergency access accounts that are assigned the Global Administrator role permanently and use non-phone-based authentication.

Answer

Deploy Password Hash Synchronization (PHS), configure eligible administrative role assignments in Privileged Identity Management (PIM), and create a Conditional Access policy enforcing MFA while excluding two cloud-only emergency access accounts.
The correct design uses Password Hash Synchronization (PHS) to keep hybrid identity infrastructure simple. It leverages Privileged Identity Management (PIM) with eligible assignments to ensure that administrators do not hold standing privileges and must request activation (enforcing Just-In-Time access with MFA and justification). Finally, it secures the tenant against outages by excluding dedicated, cloud-only emergency access accounts from the Conditional Access MFA policy, in alignment with Microsoft architectural guidelines.

Step-by-Step Solution

1
Select the hybrid authentication method that minimizes infrastructure complexity.
Password Hash Synchronization (PHS) is selected instead of Active Directory Federation Services (AD FS) because it requires no complex on-premises federation infrastructure.
The scenario requires minimizing infrastructure complexity and administrative overhead.
2
Configure role governance for Just-In-Time (JIT) access.
Microsoft Entra Privileged Identity Management (PIM) is configured with eligible assignments for administrative roles, requiring justification and MFA upon activation.
Eligible assignments prevent permanent privilege accumulation and enforce JIT governance.
3
Configure Conditional Access policies to prevent lockout during MFA service outages.
Excluding dedicated, cloud-only emergency access (glass-breaker) accounts from the Conditional Access policy ensures access is maintained if the MFA service fails.
Microsoft best practices dictate that at least one or two emergency access accounts must be excluded from MFA policies to mitigate the risk of tenant lockout.

Key Concept

Designing resilient identity, hybrid authentication, and conditional access policies in Microsoft Entra ID.
Estimated Time:2m 0s
Question 854Question

An enterprise is designing a subscription governance and identity delegation strategy for a hybrid environment organized under a single management group hierarchy. The design must accommodate two distinct administrative requirements:

- A third-party audit team requires read-only access to view all resources and security configurations across all subscriptions under the Root Management Group, but only during scheduled quarterly audit windows.
- The cloud operations team must be able to deploy, start, stop, and delete virtual machines within the Prod-Compute-RG resource group under the Production subscription, without being able to modify access control settings or delegate roles.

The design must minimize administrative overhead and enforce the principle of least privilege.

Which two actions should you include in the identity and governance design?

Select all that apply

Show answer & explanation

Answer: Configure an eligible role assignment in Microsoft Entra Privileged Identity Management (PIM) at the Root Management Group scope for a security group containing the audit team members.; Assign the Virtual Machine Contributor role to a security group containing the operations team members at the Prod-Compute-RG resource group scope.

Answer

Configure an eligible role assignment in Microsoft Entra Privileged Identity Management (PIM) at the Root Management Group scope for a security group containing the audit team members, and assign the Virtual Machine Contributor role to a security group containing the operations team members at the resource group scope.
The correct solution involves configuring an eligible role assignment in Microsoft Entra PIM at the Root Management Group level for the security auditors, and assigning the Virtual Machine Contributor role to a security group at the resource group scope for the operations team. Using PIM eligible assignments ensures that auditors only have access when they activate their role during scheduled audits. Using the Virtual Machine Contributor role at the resource group scope allows the operations team to manage virtual machines without having permission to manage access control. Group-based assignments ensure scalable governance.

Step-by-Step Solution

1
Analyze the audit team's access requirements.
The audit team requires periodic, temporary access across all subscriptions. Permission inheritance from the Root Management Group is required, and access must be restricted to scheduled windows.
This determines that Microsoft Entra Privileged Identity Management (PIM) should be used at the Root Management Group scope with eligible (just-in-time) assignments rather than permanent active assignments.
2
Analyze the operations team's permissions and scope requirements.
The operations team needs to manage virtual machines within a single resource group, without modifying access control (RBAC).
This maps to the Virtual Machine Contributor built-in role scoped to the specific resource group (Prod-Compute-RG), which excludes User Access Administrator privileges.
3
Apply scale and administrative overhead design constraints.
Assign permissions to Entra ID security groups rather than individual user accounts.
Group-based assignment aligns with Microsoft identity governance best practices to reduce administrative overhead and scale access management.

Key Concept

Azure RBAC and subscription governance require using group-based assignments for scale, built-in roles like Virtual Machine Contributor for least-privilege resource management, and Microsoft Entra PIM with eligible assignments to govern temporary or periodic privileged scopes.
Question 855Question

An international company hosts application workloads in Azure across two regions: East US and North Europe. The company's compliance policy dictates that all log data must remain within the region where it was generated. You need to design a monitoring and log routing solution that automatically configures diagnostic logging for newly deployed resources, complies with regional data residency, and minimizes administrative overhead for user access management. Which of the following configurations should you include in the design? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Deploy a separate Log Analytics workspace in East US and another in North Europe to store logs generated within each respective region.; Create Azure Policy assignments with the DeployIfNotExists effect to automatically configure diagnostic settings for new resources to route to the regional workspaces.

Answer

Deploy a separate Log Analytics workspace in East US and another in North Europe, and create Azure Policy assignments with the DeployIfNotExists effect.
Deploying regional Log Analytics workspaces ensures compliance with regional data residency constraints. Using Azure Policy with the DeployIfNotExists effect ensures that new resources automatically have diagnostic logging configured without manual intervention or deployment failures.

Step-by-Step Solution

1
Analyze the regional data residency requirement.
Determine that a single centralized workspace in East US is not compliant because logs generated in Europe would cross boundaries, necessitating regional workspaces.
Data residency mandates keeping logs local to the generating region.
2
Address the requirement to automatically configure diagnostic settings on newly deployed resources.
Select Azure Policy with a DeployIfNotExists effect to automatically configure diagnostic logging rather than a Deny policy which blocks creation.
DeployIfNotExists automates remediation during deployment, satisfying the requirement to automatically configure logging.
3
Evaluate access management overhead.
Avoid assigning roles directly to individual users to minimize management overhead, pointing out that RBAC roles should be assigned to groups.
Group-based role assignment scales administrative access management.

Key Concept

Designing regional log storage compliance and automated log routing configuration using Azure Policy.
Question 856Question

An organization is migrating several legacy workloads to Azure and plans to use Azure Cosmos DB. You need to recommend the appropriate Azure Cosmos DB API for each workload based on their technical requirements.

Match each workload pattern to its corresponding Azure Cosmos DB API.

Click a left item, then click its matching right item

Items

A social networking application that needs to query complex entity relationships and traverse graphs using Apache TinkerPop.
A retail inventory system migrating from an existing open-source MongoDB deployment with minimal changes to the application code.
An IoT logging system that writes time-series telemetry structured as wide-column tables compatible with Apache Cassandra.
A customer portal needing to store and query semi-structured JSON documents using standard SQL queries.

Matches

Show answer & explanation

Answer

Match 'Apache TinkerPop' to 'API for Gremlin', 'MongoDB deployment' to 'API for MongoDB', 'Apache Cassandra wide-column tables' to 'API for Cassandra', and 'JSON documents using standard SQL' to 'API for NoSQL'.
Each workload is mapped to the API that supports its specific query paradigm and database driver compatibility: Apache TinkerPop maps to API for Gremlin, MongoDB migration maps to API for MongoDB, Cassandra wide-column queries map to API for Cassandra, and SQL-like JSON document queries map to the native API for NoSQL.

Step-by-Step Solution

1
Analyze the graph database requirement.
Since it uses Apache TinkerPop, it matches the API for Gremlin.
The API for Gremlin is designed specifically for graph workloads using the TinkerPop standard.
2
Analyze the MongoDB migration requirement.
Since it requires migrating an existing MongoDB deployment with minimal changes, it matches the API for MongoDB.
The API for MongoDB allows existing MongoDB drivers and tools to interact with Azure Cosmos DB directly.
3
Analyze the wide-column and Cassandra compatibility requirement.
Since it requires Cassandra compatibility, it matches the API for Cassandra.
The API for Cassandra is compatible with Cassandra Query Language (CQL) and drivers.
4
Analyze the SQL query on JSON documents requirement.
Since it requires querying JSON using SQL, it matches the API for NoSQL.
The API for NoSQL is the native document model that uses SQL-like queries.

Key Concept

Selecting the correct Azure Cosmos DB API based on database model, compatibility requirements, and query language needs.
Question 857Question

An organization named Litware, Inc. is designing an identity and access management solution for their Microsoft Entra ID tenant. The organization has an on-premises Active Directory Domain Services (AD DS) environment.

The solution must meet the following requirements:
- Ensure that users can authenticate to cloud services even if the on-premises network or AD DS domain controllers are offline, with minimal configuration overhead and without requiring on-premises server infrastructure.
- Require multi-factor authentication (MFA) for all administrative roles.
- Prevent administrative lockout in the event of an MFA service outage or misconfiguration.
- Implement Privileged Identity Management (PIM) for the Global Administrator role to enforce just-in-time (JIT) access.

Which two actions should you recommend to meet the requirements?

Select all that apply

Show answer & explanation

Answer: Configure Password Hash Synchronization (PHS) as the hybrid identity authentication method.; Configure a Conditional Access policy that requires MFA for all administrative roles, and exclude emergency access accounts from the policy.

Answer

Configure Password Hash Synchronization (PHS) as the hybrid identity authentication method, and configure a Conditional Access policy requiring MFA for administrative roles while excluding emergency access accounts.
The correct solution involves configuring Password Hash Synchronization (PHS) to ensure authentication resilience without requiring on-premises server infrastructure, and configuring a Conditional Access policy requiring MFA for administrators that excludes emergency access accounts to prevent tenant lockout during a service disruption.

Step-by-Step Solution

1
Select the appropriate hybrid authentication method.
Password Hash Synchronization (PHS) is selected.
PHS allows authentication to occur entirely in Microsoft Entra ID, ensuring sign-in resilience if on-premises domain controllers are offline, with minimal management overhead compared to AD FS or Pass-through Authentication (PTA).
2
Design the Conditional Access policy for administrator MFA.
A Conditional Access policy is designed to require MFA for all administrative roles, with an explicit exclusion for emergency access accounts.
This configuration satisfies the MFA requirement for admins while safeguarding against tenant lockout if the MFA service or the policy itself is misconfigured.
3
Ensure just-in-time access configurations for privileged roles.
Users are configured with eligible PIM assignments rather than active assignments.
Eligible assignments require users to request and activate the role when needed, implementing just-in-time access and avoiding permanently active assignments.

Key Concept

Microsoft Entra ID hybrid authentication resilience and secure Conditional Access configuration for administrative accounts.
Question 858Question

A company is planning a new database deployment on Azure for two internal applications. The design must accommodate the following requirements:

- Application 1: Requires a database that supports SQL Server Agent for automated job scheduling and SQL Server Common Language Runtime (CLR) integration. You must minimize operational overhead.
- Application 2: Requires a database that experiences highly unpredictable query volume, with long periods of inactivity and sudden brief spikes in demand. You must minimize compute costs during idle periods.

Which two database solutions should you recommend?

Select all that apply

Show answer & explanation

Answer: Azure SQL Managed Instance for Application 1; Azure SQL Database serverless for Application 2

Answer

Azure SQL Managed Instance for Application 1 and Azure SQL Database serverless for Application 2
The correct options are Azure SQL Managed Instance for Application 1 and Azure SQL Database serverless for Application 2. Azure SQL Managed Instance supports features like SQL Server Agent and CLR integration while maintaining a fully managed service model, which minimizes operational overhead. Azure SQL Database serverless is designed for workloads with unpredictable query volume and idle periods, as it offers automatic compute scaling and database pausing to minimize costs.

Step-by-Step Solution

1
Analyze the database requirements for Application 1.
Identified the need for SQL Server Agent and CLR integration, combined with the goal to minimize operational overhead.
These feature requirements rule out Azure SQL Database single database, while the operational overhead goal makes Azure SQL Managed Instance a better choice than SQL Server on Azure VMs.
2
Analyze the database requirements for Application 2.
Identified the need to handle unpredictable spikes in traffic and minimize costs during long periods of inactivity.
Azure SQL Database serverless automatically scales compute and pauses the database during idle periods, satisfying the cost and demand requirements.
3
Select the two options that match the required services.
Azure SQL Managed Instance for Application 1 and Azure SQL Database serverless for Application 2 are identified as the correct targets.
These two deployment models perfectly align with the compatibility and cost-saving constraints.

Key Concept

Matching application workload requirements to appropriate Azure SQL relational database services based on feature compatibility, operational overhead, and cost optimization tiers.
Question 859Question

A company is designing the storage architecture for a health informatics application hosted on Azure Linux virtual machines. The design must meet the following requirements:

- The application requires a shared filesystem that is POSIX-compliant, supports concurrent read/write access from multiple VMs with sub-millisecond metadata latency, and can survive a datacenter zone outage.
- Database transaction logs must be stored on VM disk storage that guarantees sub-millisecond write latency and supports scaling IOPS and throughput dynamically without virtual machine deallocation.
- System audit logs must be stored in a WORM (Write Once, Read Many) state for seven years. External auditors must be granted access to these logs for exactly 30 days using a token that can be revoked immediately if a security compromise is suspected.

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

Select all that apply

Show answer & explanation

Answer: Configure Azure Files Premium tier using the Network File System (NFS) protocol and Zone-Redundant Storage (ZRS).; Deploy Premium SSD v2 disks for the database transaction logs and adjust performance settings dynamically as workload demands change.; Configure Azure Blob Storage with a time-based retention policy, and generate a Service SAS linked to a Stored Access Policy for audit log access.

Answer

Configure Azure Files Premium tier using NFS and ZRS; deploy Premium SSD v2 disks for database logs with dynamic performance tuning; and configure Azure Blob Storage with a time-based retention policy using a Service SAS linked to a Stored Access Policy.
To design the storage solutions optimally: First, Azure Files Premium using the NFS v4.1 protocol and ZRS satisfies the requirement for a zone-redundant, sub-millisecond POSIX-compliant shared filesystem on Linux. Second, Premium SSD v2 disks provide sub-millisecond write latency and support modifying IOPS and throughput online without deallocating the VM. Third, storing audit logs in Azure Blob Storage with a time-based retention policy satisfies WORM compliance, and generating a Service SAS linked to a Stored Access Policy permits revoking the 30-day token immediately by modifying or deleting the policy.

Step-by-Step Solution

1
Analyze the shared filesystem requirement.
Identify that POSIX compliance on Linux VMs with sub-millisecond metadata latency requires Azure Files Premium tier mounted via NFS v4.1, and zone survivability requires ZRS redundancy.
Standard tier or SMB protocol fails to meet native POSIX/latency or redundancy requirements.
2
Evaluate the database transaction log disk requirement.
Select Premium SSD v2 (or Ultra Disk) since it supports sub-millisecond latencies and dynamic tuning of IOPS/throughput without deallocating the VM.
Standard SSD or Premium SSD v1 do not meet the performance tiering and online dynamic scaling needs.
3
Evaluate audit log immutability and delegation requirements.
Select Azure Blob Storage immutable storage with a time-based retention policy for WORM, and use a Service SAS associated with a Stored Access Policy.
Using a Stored Access Policy allows instantaneous revocation of the 30-day token, whereas ad-hoc SAS tokens require key rotation to revoke.

Key Concept

Selecting Azure storage services, disk tiers, redundancy levels, and access delegation mechanisms based on POSIX compliance, latency, write-intensity, dynamic performance scaling, WORM compliance, and token revocation requirements.
Question 860Question

An enterprise is designing a privileged access governance model for its Microsoft Entra ID tenant to align with corporate security guidelines. The design must satisfy the following requirements:
- Administrative privileges must be granted on a temporary, just-in-time (JIT) basis.
- Privileged access management must scale efficiently without causing high administrative overhead as the team grows.
- All administrative access to cloud resources must be protected by Multi-Factor Authentication (MFA).
- The enterprise must ensure that administrators can still access the tenant in the event of a widespread MFA service disruption or identity provider outage.

Which identity and access management design should you recommend?

Show answer & explanation

Answer: Create Microsoft Entra security groups for administrative roles, configure these groups as eligible for the roles in Privileged Identity Management (PIM), enforce Multi-Factor Authentication (MFA) for administrative access via Conditional Access, and exclude a designated emergency access account from the MFA policy.

Answer

Create Microsoft Entra security groups for administrative roles, configure these groups as eligible for the roles in Privileged Identity Management (PIM), enforce Multi-Factor Authentication (MFA) for administrative access via Conditional Access, and exclude a designated emergency access account from the MFA policy.
The correct strategy uses group-based access management for scalability, Privileged Identity Management (PIM) eligibility for just-in-time access, Conditional Access policies for MFA security, and excludes a break-glass account to ensure resiliency against service outages.

Step-by-Step Solution

1
Select a scalable structure for role assignments
Use Microsoft Entra ID security groups (role-assignable groups) instead of assigning permissions to individual users.
Group-based assignment reduces management overhead and makes permissions scaling easier.
2
Configure just-in-time (JIT) administrative access
Use Privileged Identity Management (PIM) to configure role assignments as eligible rather than permanently active.
Eligible assignments ensure users must request access when needed, minimizing standing privileges.
3
Secure administrative sessions with MFA and prevent lockout
Implement a Conditional Access policy enforcing MFA for the administrative groups, and exclude a designated emergency access (break-glass) account.
This guarantees security for daily operational accounts while ensuring access is preserved during an identity provider or MFA service outage.

Key Concept

Designing secure and resilient privileged access using Microsoft Entra Privileged Identity Management, group-based RBAC, and emergency lockout protection policies.
PreviousPage 43 / 60Next
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin