All practice questions

1198 questions

Question 261Question

An organization hosts its production workloads on Azure Virtual Machines. You are designing an Azure Backup solution that must meet the following requirements:
- Technical recoveries of backups from the last 55 days must achieve the lowest possible Recovery Time Objective (RTO) by restoring directly from local disk snapshots.
- Monthly backups must be retained for 33 years (3636 months) to satisfy regulatory auditing compliance.
- The backup data must remain accessible even in the event of an entire Azure region outage.

You deploy a Recovery Services vault configured with Geo-Redundant Storage (GRS). Which configuration should you recommend in the backup policy?

Show answer & explanation

Answer: A backup policy with an instant restore snapshot retention of 55 days, and a long-term retention configuration that keeps monthly recovery points in the vault for 3636 months.

Answer

A backup policy with an instant restore snapshot retention of 55 days, and a long-term retention configuration that keeps monthly recovery points in the vault for 3636 months.
The correct configuration uses an instant restore retention of 55 days to meet the low RTO requirement by restoring directly from local disk snapshots, while keeping the monthly recovery points in the vault for 3636 months to satisfy regulatory compliance. It utilizes GRS to ensure regional resilience.

Step-by-Step Solution

1
Analyze RTO requirements for recent backups.
The requirement states recoveries of backups from the last 55 days must restore directly from local disk snapshots. This is achieved by setting the operational tier (instant restore) retention to 55 days.
Azure Backup's instant restore feature retains snapshots on the VM's disks for 11 to 55 days under a standard policy, allowing direct restorations without copying data from the vault.
2
Analyze long-term compliance retention requirements.
The monthly backups must be kept for 3636 months. This long-term retention should be stored in the vault tier, not as local disk snapshots, to control costs.
Keeping snapshots on managed disks for 3636 months is not supported by Azure Backup policy limits, and storing them on standard/premium SSDs would incur extreme storage costs.
3
Determine the vault resilience configuration.
Confirm that the Recovery Services vault is configured with Geo-Redundant Storage (GRS) as deployed.
GRS replicates backup data to a secondary paired region, ensuring that the backups remain accessible even if the primary region experiences a complete outage.

Key Concept

Azure Backup operational tier (instant restore) vs. vault tier configuration
Estimated Time:2m 0s
Question 262Question

A financial services firm is designing the cloud database architecture for a new customer portal. The design must satisfy the following requirements:

* Automatically fail over to a secondary Azure region with no client connection string modifications.
* Restrict database access to private IP addresses within a specific virtual network, preventing all public internet access.
* Minimize administrative overhead for database operations and patching.

Which two features or configurations should you include in the design?

Select all that apply

Show answer & explanation

Answer: Azure SQL Database failover groups; Private endpoints for Azure SQL Database

Answer

Azure SQL Database failover groups and Private endpoints for Azure SQL Database
The correct options are Azure SQL Database failover groups and Private endpoints for Azure SQL Database. Azure SQL Database failover groups manage database replication and failover to a secondary region, providing a single listener that automatically routes client traffic without connection string updates. Private endpoints secure the database within a virtual network using private IP addresses, allowing public endpoints to be disabled to satisfy network security requirements. Both features are native to Azure SQL Database, which minimizes administrative overhead as a fully managed service.

Step-by-Step Solution

1
Analyze the high availability and client redirection requirements.
Azure SQL Database failover groups provide automatic failover and a single listener, removing the need for connection string modifications, unlike active geo-replication which requires manual client redirection.
This identifies the correct feature for regional disaster recovery without client disruption.
2
Analyze the network security requirement.
Private endpoints assign private IP addresses from the virtual network, allowing public access to be completely disabled.
This satisfies the requirement to secure access using private IP addresses within a VNet.
3
Evaluate administrative overhead.
Azure SQL Database is a fully managed Platform as a Service (PaaS) that handles OS and database patching automatically, whereas SQL Server on Azure Virtual Machines (IaaS) requires manual maintenance.
This filters out Infrastructure as a Service (IaaS) solutions to minimize management effort.

Key Concept

Azure SQL Database High Availability and Networking Features
Estimated Time:1m 30s
Question 263Question

An enterprise is designing a subscription governance and access model for a new division. The division will use a dedicated Azure subscription under the corporate management group. You need to design an identity and access management solution that meets the following security and operational guidelines:

* Database administrators (DBAs) must be able to manage Azure SQL databases, but they should only have these privileges when active on-call or working on an assigned incident.
* Auditor accounts must be able to view all resource configurations across the subscription but must not be allowed to modify any settings.
* All administrative privileges must be audit-compliant, scalable, and follow the principle of least privilege.
* Virtual machine deployments must automatically have a monitoring agent installed without requiring manual intervention by developers.

Which of the following configuration options should you include in the design? (Select THREE.)

Select all that apply

Show answer & explanation

Answer: Configure a Microsoft Entra ID security group for the database administrators, and assign this group eligible access to the SQL Server Contributor role using Privileged Identity Management (PIM) at the subscription scope.; Create a Microsoft Entra ID security group for the auditors, and assign this group the Reader role at the subscription scope.; Assign an Azure Policy definition with the DeployIfNotExists effect at the subscription scope to automatically install the monitoring agent on newly deployed virtual machines.

Answer

Configure a Microsoft Entra ID security group for database administrators and assign it eligible access to the SQL Server Contributor role via PIM; assign the Reader role to a group for auditors at the subscription scope; and deploy an Azure Policy with the DeployIfNotExists effect to automatically install the monitoring agent.
The correct options ensure governance aligns with scalable management and security. Eligible PIM group assignments grant temporary database administrator access only when required. A Reader role group assignment delegated at the subscription level provides read-only auditor access. DeployIfNotExists Azure Policy automatically remediates compliance by deploying the monitoring agent.

Step-by-Step Solution

1
Evaluate the database administrator requirement for temporary access.
Identify that Privileged Identity Management (PIM) eligible role assignments for a group provide just-in-time administrative access, meeting audit and least-privilege requirements without standing permissions.
Security best practices demand that privileged roles are not permanently assigned, and administration must scale via groups.
2
Evaluate the auditor requirement for read-only access.
Identify that the built-in Reader role assigned to a Microsoft Entra ID security group at the subscription scope provides read-only visibility to all resources.
Reader is the standard role for viewing resource metadata without modification capabilities, and assigning it to a group satisfies governance requirements.
3
Evaluate the automatic monitoring agent installation requirement.
Determine that an Azure Policy with the DeployIfNotExists effect can deploy the agent extension during VM creation if it is missing.
DeployIfNotExists automatically remediates non-compliant resources, ensuring compliance without forcing manual deployment by developers.

Key Concept

Azure RBAC, Subscription Governance, PIM role assignment strategies, and Azure Policy remediation effects.
Question 264Question

Tailwind Traders is designing a storage solution for critical database backups. The backups must be protected against a regional disaster. The recovery time objective (RTO) requires these backup files to be accessible for immediate restore operations at any time without rehydration delays. Which storage configuration should be selected to meet these requirements?

Show answer & explanation

Answer: GRS (Geo-Redundant Storage) in the Hot tier

Answer

GRS (Geo-Redundant Storage) in the Hot tier
Selecting GRS (Geo-Redundant Storage) in the Hot tier provides the necessary regional redundancy to survive a complete outage of the primary region. Storing the database backups in the Hot tier ensures that the files remain online and can be retrieved immediately without the latency associated with rehydrating data from the Archive tier.

Step-by-Step Solution

1
Evaluate the regional resilience requirement.
LRS is eliminated because it only replicates data within a single datacenter, whereas GRS provides replication to a secondary region to survive regional disasters.
The scenario requires protection against a regional disaster.
2
Evaluate the accessibility requirement.
The Archive tier is eliminated because it requires rehydrating data to an online tier before access, which takes hours and violates the immediate access requirement.
The RTO requires immediate accessibility without rehydration delays.
3
Verify write capabilities of the secondary region.
RA-GRS cannot be configured to allow direct writes to both regions, as secondary regions in Azure geo-redundant storage are read-only prior to failover.
Azure storage replication architecture only supports read access on the secondary endpoint.

Key Concept

Azure Storage replication tiers and access tier capabilities
Question 265Question

An organization is architecting a globally distributed storage solution using Azure Cosmos DB. The system must support four distinct application components, each with unique data access patterns, migration origins, and scaling requirements. The components must be highly resilient across multiple Azure regions, support sub-10ms read/write latencies, and minimize code changes during migration from legacy environments.

Match each application requirement on the left to the correct Azure Cosmos DB API on the right to align with the workloads.

Click a left item, then click its matching right item

Items

A migration of an on-premises time-series telemetry store that utilizes Column Family data structures, requiring native Cassandra Query Language (CQL) queries.
A new social media analysis tool mapping complex user relationships, shared interests, and multi-layered hierarchies using graph traversal algorithms.
A global catalog application requiring transactional execution, JSON document indexing, and ad-hoc SQL-like SELECT queries.
An e-commerce shopping cart service migrated from an open-source document store, requiring BSON document compatibility and driver reuse.

Matches

Show answer & explanation

Answer

Match Cassandra Query Language queries to the API for Cassandra; match graph relationships to the API for Gremlin; match SQL-like JSON document queries to the API for NoSQL; and match BSON document workloads to the API for MongoDB.
Each application component is matched to its corresponding Cosmos DB API based on its storage model (wide-column, graph, document) and the compatibility needs of legacy queries.

Step-by-Step Solution

1
Analyze each workload's storage model and migration constraints.
Identified wide-column, graph traversal, native SQL document, and BSON requirements.
Matching requires parsing the underlying storage patterns and interface compatibility.
2
Map the API compatibility options provided by Azure Cosmos DB.
CQL maps to Cassandra API, Gremlin maps to Gremlin API, SQL document queries map to NoSQL API, and BSON maps to MongoDB API.
Cosmos DB offers specific APIs to match industry-standard protocols to ease migration paths.

Key Concept

Azure Cosmos DB Multi-Model APIs
Question 266Question

You are designing a business continuity and disaster recovery solution for a suite of critical Azure Virtual Machines hosting an enterprise resource planning (ERP) application.

The solution must satisfy the following technical and compliance requirements:
1. Operational recovery: Must support instant recovery of VMs directly from local snapshots for any recovery points created within the last 14 days.
2. Compliance retention: Backups must be retained in vault storage for 365 days.
3. Regional resiliency: Backups must be replicated to a secondary paired region. Administrators must be able to perform test restores in the secondary region at any time, including when the primary region is fully operational.

Which vault type, storage redundancy, and backup policy configuration should you recommend?

Show answer & explanation

Answer: A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross Region Restore (CRR) enabled, using an Enhanced backup policy with the instant restore retention set to 14 days.

Answer

A Recovery Services vault configured with Geo-Redundant Storage (GRS) and Cross Region Restore (CRR) enabled, using an Enhanced backup policy with the instant restore retention set to 14 days.
The correct configuration uses a Recovery Services vault (which is the correct vault type for Azure Virtual Machines) configured with Geo-Redundant Storage (GRS) and Cross Region Restore (CRR) enabled, allowing read/restore access to the secondary region at all times. Additionally, it specifies an Enhanced backup policy to accommodate the 14-day instant restore snapshot retention requirement, which exceeds the 5-day limit of Standard backup policies.

Step-by-Step Solution

1
Determine the correct vault type for Azure Virtual Machine backups.
Identify that Recovery Services vaults are required for Azure VM backups, eliminating options that use Backup vaults.
Azure Backup uses Recovery Services vaults for VMs, SQL Server/SAP HANA on VMs, and Azure Files, while Backup vaults are used for newer workloads like Azure Disks, Blobs, and PostgreSQL.
2
Determine the required vault storage redundancy and restore capabilities.
Identify that Geo-Redundant Storage (GRS) with Cross Region Restore (CRR) is required, eliminating Locally Redundant Storage (LRS).
To satisfy the requirement of performing test restores in the secondary region at any time (even when the primary region is healthy), Cross Region Restore must be enabled, which requires GRS.
3
Determine the backup policy sub-type and parameters required to meet the retention criteria.
Identify that an Enhanced backup policy is required to support a 14-day instant restore retention window.
Standard backup policies only support keeping instant restore snapshots for 1 to 5 days. To keep snapshots for 14 days (which are used for instant recovery), an Enhanced policy is needed as it supports up to 30 days of instant restore retention.

Key Concept

Azure Backup Vault Selection, Policy Tiers, and Redundancy Options
Estimated Time:3m 0s
Question 267Question

An organization is designing the storage architecture for a line-of-business application migrating to Azure. The application has the following design requirements:
- The database backend requires disk storage capable of delivering sub-millisecond read/write latency for transaction logs.
- A shared configuration file repository must be accessible concurrently by multiple application servers using the SMB protocol and must remain operational during a zone-level outage.
- Access to the configuration files must be secured and easily revokable if credentials are compromised.

Which two storage configurations should you recommend to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Configure Premium SSD v2 managed disks for the database transaction logs.; Configure Azure Files Premium tier with Zone-Redundant Storage (ZRS) for the shared configuration files.

Answer

Configure Premium SSD v2 managed disks for the database transaction logs, and configure Azure Files Premium tier with Zone-Redundant Storage (ZRS) for the shared configuration files.
Premium SSD v2 managed disks are the correct choice for transaction logs because they offer low sub-millisecond latencies and high performance. Azure Files Premium tier with Zone-Redundant Storage (ZRS) satisfies the SMB concurrent access and zone-outage resilience requirements by replicating data across three availability zones within the region.

Step-by-Step Solution

1
Analyze the database performance requirement.
The database transaction logs require sub-millisecond latency. This rules out Standard HDD and Standard SSD managed disks.
Only Premium SSD v2 or Ultra Disk managed disks can guarantee the sub-millisecond latencies needed for high-performance write operations like transactional logging.
2
Evaluate the file repository accessibility and redundancy requirements.
The configuration files must be accessible via SMB and survive a zone outage. This points to Azure Files Premium with Zone-Redundant Storage (ZRS).
Azure Files Premium provides SMB access with low latency, and ZRS ensures that the file share remains available even if one datacenter zone fails within the region. Locally Redundant Storage (LRS) is not zone-resilient.
3
Evaluate the security and revocation requirement.
Ad-hoc SAS tokens with long lifetimes should be avoided because they cannot be easily revoked without rotating storage account keys.
Using identity-based authentication or SAS tokens associated with stored access policies allows for immediate revocation and meets security best practices.

Key Concept

Selecting appropriate disk performance tiers and storage redundancy configurations to meet low-latency and high-availability requirements in Azure.
Question 268Question

You are designing a backup solution for a fleet of Azure Virtual Machines running a business-critical enterprise resource planning (ERP) application.

The design must satisfy the following requirements:
- Restore operations for backups younger than 7 days must achieve the lowest possible Recovery Time Objective (RTO) by recovering directly from local snapshots (Instant Restore).
- Recovery points must be retained in a Recovery Services vault for 365 days to meet regulatory compliance.
- The solution must allow restoration to a paired secondary region at any time, even if the primary region is fully functional and online.

Which backup configuration should you recommend?

Show answer & explanation

Answer: Configure a Recovery Services vault with Geo-redundant storage (GRS) and Cross Region Restore enabled. Define an Enhanced backup policy with an instant restore retention of 7 days and a vault retention of 365 days.

Answer

Configure a Recovery Services vault with Geo-redundant storage (GRS) and Cross Region Restore enabled, and define an Enhanced backup policy with an instant restore retention of 7 days and a vault retention of 365 days.
The correct configuration uses Geo-redundant storage (GRS) combined with Cross Region Restore (CRR) to satisfy the requirement of restoring to a paired secondary region at any time. Furthermore, because the low-RTO operational recovery requirement spans 7 days, an Enhanced backup policy must be used since the Standard backup policy type enforces a maximum limit of 5 days for local instant restore snapshots.

Step-by-Step Solution

1
Analyze the regional resilience and availability requirements.
Since backups must be restorable to a paired secondary region at any time even when the primary region is fully functional, Geo-redundant storage (GRS) with Cross Region Restore (CRR) must be enabled on the Recovery Services vault.
Standard GRS only allows restoration in the secondary region after Azure declares a disaster and initiates a failover. Enabling CRR allows the customer to perform restores in the secondary region at any time.
2
Determine the backup policy type needed to meet the Recovery Time Objective (RTO) requirement.
An Enhanced backup policy is required because the instant restore retention must be set to 7 days.
The Standard backup policy only supports instant restore (snapshot) retention between 1 and 5 days. The Enhanced backup policy supports snapshot retention up to 30 days, allowing the 7-day low RTO requirement to be met.
3
Evaluate long-term retention requirements.
Set the vault retention to 365 days in the Enhanced backup policy.
This satisfies the regulatory compliance requirement to retain recovery points for one year.

Key Concept

Azure VM Backup Policy Types and Vault Storage Redundancy Options
Question 269Question

A financial services firm is designing a secure storage solution for a multi-tenant payment processing platform. Transaction logs are stored in an Azure Blob Storage container named `ledgers`. The solution must satisfy the following security and governance requirements:

- External compliance auditors require read access to the `ledgers` container for a single 8-hour audit window. If a security incident is detected, administrative access must be capable of immediately terminating the auditors' access without affecting other storage operations or rotating the master storage account keys.
- The internal security engineering team requires administrative access to manage the storage account settings and access policies. Their access must follow the principle of least privilege, utilizing Just-in-Time (JIT) access elevation and avoiding direct user assignments to ensure scalable governance.

Which two security controls should you recommend to meet these requirements?

Select all that apply

Show answer & explanation

Answer: For the external auditors, configure a Stored Access Policy on the `ledgers` container and generate a Shared Access Signature (SAS) token associated with that policy.; For the internal security engineering team, create a Microsoft Entra ID security group, assign the required storage administrative RBAC roles to the group, and configure eligible assignments using Privileged Identity Management (PIM).

Answer

Configure a Stored Access Policy on the container and associate the SAS token with it for the external auditors, and create a Microsoft Entra ID security group with eligible assignments in Privileged Identity Management (PIM) for the security engineering team.
Associating the external auditors' Shared Access Signature (SAS) with a Stored Access Policy allows administrators to revoke access instantly by deleting or changing the policy, meeting the compliance window and safety parameters. Using a Microsoft Entra ID group with eligible Privileged Identity Management (PIM) assignments for the internal team ensures administrative access is governed via groups and elevated only when needed (JIT).

Step-by-Step Solution

1
Analyze the access revocation requirement for the external auditors.
Identified that immediate, non-disruptive revocation is required.
An ad-hoc SAS token cannot be revoked without key rotation. A Stored Access Policy (SAP) allows immediate revocation by modifying or deleting the policy directly on the container.
2
Analyze the identity and governance requirements for the internal security team.
Identified that JIT access and scalable governance are required.
Direct assignments to user accounts are unscalable. Security groups should be used. JIT requires PIM eligible assignments rather than active ones.
3
Select the configuration options that implement both secure controls.
Selected the Stored Access Policy strategy and the Entra ID group with PIM eligible assignment.
This combination satisfies the revocation constraint for external users and the JIT and group-based access requirements for internal administrators.

Key Concept

Azure Storage access control and privilege governance using Stored Access Policies and Entra ID Privileged Identity Management.
Question 270Question

A logistics enterprise is designing a secure storage solution for external supplier invoices stored in an Azure Blob Storage container named supplierinvoices within a storage account named logisticsdata. The solution must satisfy the following security and operational requirements:

- External auditors require read access to the container for a temporary 14-day audit window. The access must be immediately revocable at any time during the audit without affecting other applications or rotating the storage account access keys.
- Internal financial analysts require read and write access to the container. They must obtain access only on-demand and for a limited duration, utilizing administrative self-service activation. The administration of access must scale efficiently without managing individual user permissions.

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

Select all that apply

Show answer & explanation

Answer: Configure a stored access policy on the supplierinvoices container and generate a service shared access signature (SAS) token associated with this policy for the external auditors.; In Microsoft Entra Privileged Identity Management (PIM) for groups, assign the Storage Blob Data Contributor role as eligible to a Microsoft Entra ID security group containing the financial analysts.

Answer

Configure a stored access policy on the supplierinvoices container and generate a service shared access signature (SAS) token associated with this policy for the external auditors, and in Microsoft Entra Privileged Identity Management (PIM) for groups, assign the Storage Blob Data Contributor role as eligible to a Microsoft Entra ID security group containing the financial analysts.
The correct design uses a stored access policy to secure the external auditor's temporary access, enabling immediate revocation by deleting or modifying the policy without rotating storage account keys. For the financial analysts, configuring the Storage Blob Data Contributor role as eligible for a Microsoft Entra ID security group ensures that access is only granted on-demand (just-in-time) through PIM self-service activation and simplifies administration by managing access at the group level.

Step-by-Step Solution

1
Address the external auditor revocation requirement.
Using a service SAS token associated with a stored access policy allows immediate revocation by modifying or deleting the stored access policy, keeping other services unaffected.
Ad-hoc SAS tokens cannot be revoked without rotating the storage account access keys, which would affect other services.
2
Address the internal analyst on-demand activation requirement.
Using Microsoft Entra Privileged Identity Management (PIM) for groups to assign the Storage Blob Data Contributor role as eligible meets the on-demand activation requirement.
Active PIM assignments provide permanent access instead of just-in-time access.
3
Address the administration and scalability requirement.
Assigning the role to a Microsoft Entra ID group instead of individual accounts ensures administrative scalability.
Direct user role assignments do not scale and are harder to audit and maintain.

Key Concept

Designing secure access to Azure Storage using Stored Access Policies for SAS revocation and Microsoft Entra PIM for groups to achieve scalable, just-in-time RBAC administration.
Question 271Question

A financial services company is designing a storage solution for external consultants who need to upload weekly reports to an Azure Blob Storage container named consultant-uploads. The design must satisfy the following requirements:
- The consultants must be granted write-only access to the container for a duration of 90 days.
- The consultants must not be required to authenticate using Microsoft Entra ID.
- The security team must be able to immediately revoke the access if a compliance violation is detected.
Which of the following access control strategies should you recommend to meet these requirements?

Show answer & explanation

Answer: Create a stored access policy on the container, and then generate a service Shared Access Signature (SAS) token associated with that policy.

Answer

Create a stored access policy on the container, and then generate a service Shared Access Signature (SAS) token associated with that policy.
Associating a service Shared Access Signature (SAS) with a stored access policy allows the policy to be modified or deleted. Deleting or modifying the policy immediately revokes the SAS token, meeting the requirement of instant revocation. Since a SAS token does not require Microsoft Entra ID authentication, this approach meets all the requirements.

Step-by-Step Solution

1
Analyze the authentication requirement.
The requirement states that consultants must not use Microsoft Entra ID. This rules out solutions based on Entra ID RBAC or Privileged Identity Management (PIM) assignments.
Shared Access Signatures (SAS) allow clients to access storage resources without having an Entra ID identity.
2
Evaluate the revocation and duration requirement.
The SAS token must last for 90 days but must be instantly revocable. An ad-hoc SAS cannot be revoked without rotating keys, whereas a SAS associated with a stored access policy can be revoked by deleting or changing the policy.
Stored access policies provide server-side control over SAS lifetimes and permissions.
3
Combine security and configuration best practices.
Select the strategy that uses a stored access policy to manage a service SAS.
This is the only strategy that provides non-identity based access that is immediately revocable without rotating account keys.

Key Concept

Stored Access Policies vs. Ad-hoc SAS
Estimated Time:1m 30s
Question 272Question

A company is planning to migrate an on-premises inventory application to Azure. The application database tier consists of three databases that frequently execute cross-database queries using three-part names. The databases also rely on SQL Server Agent for scheduled data-cleansing jobs. You need to design a relational data storage solution that supports these database features while minimizing the operational effort required to manage operating system patching and backups.

Which Azure SQL deployment option should you recommend?

Show answer & explanation

Answer: Azure SQL Database Managed Instance

Answer

Azure SQL Database Managed Instance
The correct answer is Azure SQL Database Managed Instance. It supports near 100% compatibility with the on-premises SQL Server database engine, including native support for SQL Server Agent and cross-database queries. As a Platform as a Service (PaaS) offering, it automatically handles operating system updates, database engine patching, and backups, which satisfies the requirement to minimize administrative overhead.

Step-by-Step Solution

1
Analyze the technical requirements of the on-premises database tier.
Identify the need for SQL Server Agent for scheduled jobs and cross-database query support (three-part names).
Determining compatibility constraints is the first step in mapping workloads to the correct Azure SQL service.
2
Evaluate the management and administrative overhead constraints.
Note that the solution must minimize operational effort for OS patching and backups.
This requirement points toward a Platform as a Service (PaaS) solution rather than an Infrastructure as a Service (IaaS) solution.
3
Match requirements against the capabilities of Azure SQL tiers.
Select Azure SQL Database Managed Instance because it offers near-complete compatibility with SQL Server features like SQL Server Agent and cross-database queries, while operating as a fully managed PaaS database service.
Only the Managed Instance tier satisfies all technical features without requiring the operational overhead of managing virtual machines.

Key Concept

Selecting Azure SQL deployment options based on legacy SQL Server feature requirements and management boundaries.
Estimated Time:1m 30s
Question 273Question

An enterprise is designing the storage infrastructure for a new mission-critical transaction processing application deployed on Azure Virtual Machines. The architecture must satisfy the following requirements:

- The transaction log drive requires block storage that supports at least 50005{}000 IOPS and 200200 MB/s of throughput with sub-millisecond write latency.
- The transaction log storage must remain highly available and survive a physical datacenter (availability zone) outage within the primary Azure region without data loss.
- Application audit logs stored in Azure Blob Storage must be securely shared with external auditors via time-bound links that can be revoked immediately at any time without rotating the primary storage account keys or affecting other active signatures.

Which storage configuration should you recommend?

Show answer & explanation

Answer: Premium SSD v2 Managed Disks configured with Zone-Redundant Storage (ZRS) for the transaction logs, and Azure Blob Storage with Shared Access Signatures (SAS) tied to a Stored Access Policy for the audit logs.

Answer

The correct option recommends Premium SSD v2 Managed Disks with Zone-Redundant Storage (ZRS) for the transaction logs, and Azure Blob Storage with Shared Access Signatures (SAS) tied to a Stored Access Policy for the audit logs.
The correct configuration uses Premium SSD v2 with Zone-Redundant Storage (ZRS) for the VM disks to guarantee sub-millisecond latencies, support the throughput/IOPS specifications, and withstand an availability zone failure. By using a Shared Access Signature tied to a Stored Access Policy, the audit logs can be shared securely with external partners, and the access can be instantly revoked by modifying or deleting the policy in Azure without rotating the master storage account keys.

Step-by-Step Solution

1
Evaluate disk options for the transaction log performance requirements.
Standard HDD is eliminated as it cannot deliver sub-millisecond latencies or support 50005{}000 IOPS. Premium SSD v2 is selected because it meets both performance metrics and supports sub-millisecond write latency.
Database transaction logs are latency-sensitive and require high-performance block storage.
2
Determine the redundancy level required to survive a physical datacenter outage.
Locally Redundant Storage (LRS) is eliminated because it is confined to a single datacenter. Zone-Redundant Storage (ZRS) is selected because it replicates data across three availability zones in the region.
The system must survive a zone outage without data loss.
3
Identify the mechanism for sharing blob storage that allows instant revocation without rotating primary account keys.
Ad-hoc SAS is eliminated because it cannot be revoked without key rotation. A SAS associated with a Stored Access Policy is selected because modifying or deleting the policy immediately invalidates the SAS.
The security requirements demand granular, immediate revocation of external auditor access.

Key Concept

Selecting appropriate Azure disk storage and configuring secure data access mechanisms
Question 274Question

You are designing a high availability and disaster recovery (HA/DR) solution for an on-premises database that is migrating to Azure. The database relies on SQL Server Agent jobs and performs cross-database queries. The disaster recovery design must support automatic failover to a secondary region, a Recovery Time Objective (RTO) of 1 hour, and a single connection endpoint that redirects application traffic without requiring connection string modifications during a failover. Which solution should you recommend?

Show answer & explanation

Answer: Azure SQL Managed Instance configured with a failover group

Answer

Azure SQL Managed Instance configured with a failover group
The correct answer is Azure SQL Managed Instance configured with a failover group. Azure SQL Managed Instance supports features required for legacy SQL Server migrations, including SQL Server Agent and cross-database queries. Configuring it with a failover group enables automatic failover to a secondary region and provides a read-write listener endpoint, allowing the application to connect using a single connection string that automatically redirects traffic during failover.

Step-by-Step Solution

1
Analyze the database compatibility and feature requirements.
The database requires SQL Server Agent and cross-database queries, which rules out Azure SQL Database single database and points to Azure SQL Managed Instance or SQL Server on Azure VMs.
Azure SQL Database single database does not support SQL Server Agent or cross-database queries.
2
Evaluate the HA/DR requirements.
The solution must support automatic failover to a secondary region with a single listener endpoint.
This eliminates configurations that require manual failover and application connection string changes.
3
Verify storage and performance requirements.
SQL Server on Azure VMs with Standard HDD is eliminated due to inadequate performance for database transaction logs.
Standard HDD is unsuitable for database transaction logs, which require low latency and high IOPS provided by Premium SSD or Ultra Disk.

Key Concept

Designing relational database HA and DR using failover groups and choosing the correct Azure SQL service tier based on application compatibility.
Question 275Question

A medical records company is designing an Azure Storage solution for document uploads. The system requirements specify that all uploaded documents must be replicated synchronously across three distinct availability zones within the primary region to protect against a localized datacenter failure.

Which two redundancy options meet these requirements?

Select all that apply

Show answer & explanation

Answer: Zone-redundant storage (ZRS); Geo-zone-redundant storage (GZRS)

Answer

Zone-redundant storage (ZRS) and Geo-zone-redundant storage (GZRS) meet the requirements because they replicate data synchronously across three availability zones in the primary region.
Zone-redundant storage (ZRS) and Geo-zone-redundant storage (GZRS) both replicate data synchronously across three Azure availability zones in the primary region, meeting the requirement to survive a localized zone or datacenter outage.

Step-by-Step Solution

1
Analyze the requirement for synchronous replication in the primary region.
The solution must replicate data across three distinct availability zones synchronously in the primary region.
This establishes that the primary storage redundancy configuration must be zone-redundant.
2
Evaluate the replication behavior of each Azure Storage option.
Zone-redundant storage (ZRS) and Geo-zone-redundant storage (GZRS) use zone-redundant replication (synchronous replication across three zones) in the primary region. Locally-redundant storage (LRS) and Geo-redundant storage (GRS) use locally-redundant replication (synchronous replication within a single facility) in the primary region.
Identifying the primary replication mechanism for each tier determines which options meet the criteria.
3
Select the options that provide primary zone redundancy.
Zone-redundant storage (ZRS) and Geo-zone-redundant storage (GZRS) are selected.
Both options ensure that data is synchronously written to three availability zones in the primary region, surviving a zone-level outage.

Key Concept

Data replication strategies in Azure Storage, focusing on primary region zone redundancy (ZRS/GZRS) versus local redundancy (LRS/GRS).
Question 276Question

An enterprise is designing a secure identity governance and privileged access strategy for its Azure infrastructure. The solution must meet the following requirements:

* A team of 10 system administrators must be granted administrative privileges on Azure subscription resources only when performing specific maintenance windows, requiring justification and multi-factor authentication (MFA).
* Administrative permissions must be managed at scale, avoiding direct role assignments to individual users.
* A backup mechanism must be established to ensure administrative access to the tenant remains possible even if the primary authentication systems or Conditional Access policies fail, preventing tenant lockout.

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

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra ID security group containing the system administrators and configure the group as eligible for the target Azure RBAC roles in Privileged Identity Management (PIM).; Create two emergency access accounts with the Global Administrator role and exclude them from all Conditional Access policies.

Answer

To satisfy the governance requirements, you must create a Microsoft Entra ID security group containing the system administrators and configure the group as eligible for the target Azure RBAC roles in Privileged Identity Management (PIM), and create two emergency access accounts with the Global Administrator role while excluding them from all Conditional Access policies.
The correct options involve creating a Microsoft Entra ID security group for the administrators and making it eligible in PIM, which ensures that role elevations are requested only when needed (JIT) and are managed collectively rather than individually. Furthermore, configuring emergency access accounts with the Global Administrator role and excluding them from Conditional Access policies guarantees that the tenant remains accessible during disasters without risk of MFA-induced lockouts.

Step-by-Step Solution

1
Analyze the requirements for group management and JIT access.
Determine that administrators should not be assigned roles individually and must use PIM eligibility.
Aligns with Microsoft Entra best practices for scalable governance and JIT elevation.
2
Establish the group role assignment strategy.
Create a security group, add the 10 administrators to it, and assign the group as eligible for the desired Azure roles in PIM.
Allows administrators to activate their role only when needed, requiring MFA and justification, without individual user role maintenance.
3
Formulate a break-glass disaster recovery plan.
Create two emergency access accounts assigned the Global Administrator role, and exclude them from all Conditional Access policies.
Ensures that administrative access is possible in emergency scenarios, preventing lockout.

Key Concept

Microsoft Entra ID Privileged Identity Management (PIM) and emergency access account governance.
Question 277Question

You are designing a globally distributed data storage solution for an international supply chain tracking system. The system must ingest telemetry data from 2,000,0002,000,000 active tracking devices. The workload is write-heavy, consisting of 85%85\% writes and 15%15\% reads. The data must be accessible with sub-10 ms10\text{ ms} read and write latencies globally. The architecture must guarantee 99.999%99.999\% write availability and support regional disaster recovery. You decide to use Azure Cosmos DB for NoSQL with multi-region writes enabled. Which configuration should you recommend to meet the requirements while preventing performance degradation and ensuring disaster resilience?

Show answer & explanation

Answer: Configure Azure Cosmos DB with multi-region writes. Select DeviceId as the partition key. Configure Session consistency, enable zone-redundant backup storage (ZRS) for recovery, and use short-lived Shared Access Signatures (SAS) linked to a stored access policy for diagnostic data export.

Answer

Configure Azure Cosmos DB with multi-region writes, using DeviceId as the partition key, Session consistency, zone-redundant backup storage (ZRS), and short-lived Shared Access Signatures (SAS) linked to a stored access policy.
The correct configuration uses DeviceId as the partition key to ensure a high-cardinality distribution of data, preventing hot partitions. It uses Session consistency which is fully supported under multi-region write configurations in Azure Cosmos DB. Zone-redundant storage (ZRS) backups guarantee regional disaster resilience, and SAS tokens governed by a stored access policy ensure secure, revocable access to diagnostic exports.

Step-by-Step Solution

1
Analyze partition key cardinality requirements.
DeviceId is selected instead of DeviceStatus to guarantee high cardinality and even write distribution.
Low cardinality partition keys like DeviceStatus lead to hot partitions, which cause RU throttling.
2
Verify consistency level support for multi-region writes.
Session consistency is selected because it is supported with multi-region writes, whereas Strong and Bounded Staleness are not.
Azure Cosmos DB multi-region writes only support Session, Consistent Prefix, and Eventual consistency.
3
Select appropriate backup storage redundancy and security policy.
Zone-redundant storage (ZRS) is chosen for backups to handle datacenter outages, and SAS tokens are associated with stored access policies to allow revocation.
LRS lacks disaster resilience, and long-lived ad-hoc SAS tokens introduce security vulnerabilities.

Key Concept

Azure Cosmos DB partition key selection, consistency levels under multi-region writes, and storage backup redundancy.
Question 278Question

An organization is designing a storage solution for a medical imaging application that generates high-resolution files. The solution must meet the following requirements:
- Files must be immediately accessible via HTTP/HTTPS protocols.
- Files are frequently accessed during the first 30 days, after which they are rarely accessed but must remain available for retrieval within seconds.
- External medical partners must be granted temporary access to specific files. The organization must be able to immediately revoke all active external access links to a container if a security breach is suspected, without modifying the primary storage account keys.
- Data must be replicated to a secondary region to protect against regional disasters, but read access to the secondary region is not required under normal operations.

Which storage configuration should you recommend?

Show answer & explanation

Answer: Azure Blob storage configured with Geo-Redundant Storage (GRS), using Shared Access Signatures (SAS) governed by a Stored Access Policy, and a lifecycle policy that moves files to the Cool tier after 30 days.

Answer

Azure Blob storage configured with Geo-Redundant Storage (GRS), using Shared Access Signatures (SAS) governed by a Stored Access Policy, and a lifecycle policy that moves files to the Cool tier after 30 days.
The correct configuration uses Azure Blob storage with GRS for regional redundancy (without active read access to the secondary), a Stored Access Policy to govern SAS tokens so that access can be revoked immediately by modifying or deleting the policy, and a lifecycle management rule to transition data to the Cool tier after 30 days to meet the retrieval time constraint (seconds vs. hours for the Archive tier).

Step-by-Step Solution

1
Determine the appropriate redundancy option to satisfy the regional disaster recovery requirement without read-access overhead.
Select Geo-Redundant Storage (GRS) instead of Locally Redundant Storage (LRS) or Read-Access Geo-Redundant Storage (RA-GRS).
GRS replicates data to a secondary region, providing protection against regional outages, but keeps the secondary endpoint offline/unavailable for reads under normal conditions.
2
Identify the mechanism that allows temporary sharing of container contents with the ability to instantly revoke all active links.
Use Shared Access Signatures (SAS) associated with a Stored Access Policy (SAP).
An ad-hoc SAS can only be revoked by rotating storage account keys, whereas a SAS linked to a Stored Access Policy can be revoked immediately by deleting or modifying the policy.
3
Determine the best cost-optimized tier that still allows low-latency retrieval within seconds after 30 days.
Use a lifecycle management policy to transition blobs to the Cool tier.
The Cool tier is optimized for infrequently accessed data and supports sub-second retrieval times, whereas the Archive tier takes hours to rehydrate.

Key Concept

Selecting the optimal Azure Blob storage configuration by balancing replication requirements, access tier retrieval latency constraints, and instant security token revocation features.
Estimated Time:1m 30s
Question 279Question

An enterprise is implementing a subscription governance strategy. You need to create a custom Azure RBAC role named 'VM Operator' that allows users to manage virtual machines but prevents them from modifying associated virtual networks. The role must be assignable across all subscriptions in a specific Management Group named 'Production-MG'.

Which sequence of steps should you perform to define, create, and assign this custom RBAC role?

Drag items to arrange them in the correct order

Show answer & explanation

Answer

The correct sequence starts with retrieving the resource ID of the 'Production-MG' management group, followed by configuring the AssignableScopes property in the custom role definition JSON, registering the custom role in Azure, and finally creating the role assignment for the security group at the management group scope.
To successfully deploy and assign a custom role at the management group scope, you must follow a dependency-aware sequence: first, retrieve the scope's resource ID; second, reference it in the custom role definition's AssignableScopes; third, register the definition in Azure; and fourth, assign the registered role to the target identity group.

Step-by-Step Solution

1
Retrieve the resource ID of the 'Production-MG' management group.
You obtain the resource path, for example: `/providers/Microsoft.Management/managementGroups/Production-MG`.
Custom roles assigned or scoped to a management group require the exact Resource ID in their definition.
2
Edit the custom role JSON definition file.
The `AssignableScopes` array contains the management group resource ID.
Defining the scope prevents the role from being used outside the designated management group hierarchy.
3
Run the creation command, such as `az role definition create --role-definition <file.json>`.
The custom role is registered and becomes available for assignment in the Azure tenant.
A custom role must exist in the tenant's registry before assignments can be made.
4
Create the role assignment to the target group at the management group scope.
Users in the group receive the specified permissions across all subscriptions in the management group.
Applying the assignment at the management group level ensures policy and access inheritance across all child subscriptions.

Key Concept

Azure Custom Role Definition and Deployment Workflow
Question 280Question

You are designing a backup solution for production Azure Virtual Machines. The solution must meet the following requirements:
- Operational restores for failures occurring within the last few days must have a Recovery Time Objective (RTO) of under 10 minutes by utilizing the Instant Restore feature.
- The solution must minimize operational costs by using a standard backup policy rather than an enhanced backup policy.
- All backup data must remain within the primary region to comply with local data residency regulations.

What is the maximum retention period in days that can be configured for the instant recovery snapshots in the standard backup policy?

Show answer & explanation

Answer: 5

Answer

5
The correct answer is 5. For standard Azure VM backup policies, the Instant Restore feature keeps snapshots locally for a range of 1 to 5 days (defaulting to 2 days). This meets the low RTO requirement for recent backups while staying within the standard policy constraints to minimize cost.

Step-by-Step Solution

1
Identify the constraints and backup policy type specified in the design scenario.
The scenario requires using a standard backup policy to minimize costs, and calls for sub-10-minute RTO restores utilizing the Instant Restore feature.
This establishes that the retention limits for the standard backup policy's snapshot tier must be evaluated.
2
Determine the maximum configuration limit for instant restore snapshots in a standard policy.
The standard backup policy supports instant restore snapshot retention only between 1 and 5 days, whereas the enhanced policy supports up to 30 days.
Because the standard policy must be used, the maximum value that can be configured is 5 days.

Key Concept

Azure Backup Virtual Machine policy tiers and Instant Restore limits
PreviousPage 14 / 60Next
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin