All practice questions

1198 questions

Question 181Question

Novis Health has an Azure subscription hierarchy organized under a root management group named Novis-Root. Below Novis-Root, there are three management groups: Novis-Prod, Novis-Dev, and Novis-Shared. The company is designing a governance strategy for Azure Storage accounts. The strategy must meet the following compliance requirements:

* All storage accounts must restrict public network access.
* For resources in Novis-Prod, any attempt to deploy a storage account that allows public network access must be blocked.
* For resources in all other management groups under Novis-Root, storage accounts that allow public network access must be allowed to deploy but must be flagged as non-compliant in reports.

Which policy assignment strategy meets the requirements while minimizing administrative overhead?

Show answer & explanation

Answer: Assign the policy to Novis-Root with the effect set to Audit. Assign the same policy to Novis-Prod with the effect set to Deny.

Answer

Assign the policy to Novis-Root with the effect set to Audit, and assign the same policy to Novis-Prod with the effect set to Deny.
The correct strategy leverages policy inheritance and Azure Policy evaluation behavior. Assigning the policy with the Audit effect at Novis-Root automatically applies it to all descendant scopes (Novis-Prod, Novis-Dev, and Novis-Shared), ensuring non-compliant storage accounts in Dev and Shared are flagged in compliance reports. Assigning the policy with the Deny effect specifically at Novis-Prod blocks non-compliant resource creation in the production scope. Since Deny is evaluated before Audit, any non-compliant deployment in Novis-Prod is blocked immediately, while other scopes remain audited. This approach achieves the requirements with only two assignments.

Step-by-Step Solution

1
Determine the required policy effects for each scope.
Novis-Prod requires blocking non-compliant resources (Deny effect). Other scopes require monitoring and reporting without blocking (Audit effect).
To match the compliance enforcement goals for production and non-production environments.
2
Analyze inheritance and assignment scopes to minimize overhead.
By assigning Audit at the root (Novis-Root), it inherits down to all child scopes. A separate Deny assignment at Novis-Prod overrides the behavior for production.
Inheritance reduces the number of assignments since any new management groups under the root will automatically be audited without additional assignments.
3
Evaluate exclusions and exemptions against reporting requirements.
Exclusions (notScopes) and policy exemptions completely bypass evaluation or mark resources as exempt. Neither option flags resources as non-compliant.
To ensure compliance reporting works as specified for non-production scopes.

Key Concept

Azure Policy assignment scopes, inheritance, and effect evaluation order.
Question 182Question

You are designing an Azure Cosmos DB NoSQL API solution for a global telemetry tracking application. The workload consists of a 90:10 read/write ratio, with data ingested from devices globally. You need to ensure the system survives a regional outage to meet disaster recovery SLAs and scales efficiently without creating hot partitions.

Which two configurations should you recommend to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Replicate the database across multiple Azure regions and enable automatic failover.; Partition the container using a high-cardinality key such as deviceId.

Answer

Replicating the database across multiple regions with automatic failover and partitioning the container using a high-cardinality key (such as deviceId) are the correct configurations.
Replicating across multiple regions with automatic failover ensures that the Cosmos DB database remains available during a regional disaster. Using a high-cardinality partition key, such as deviceId, distributes requests and storage evenly across logical partitions to prevent hot partitions.

Step-by-Step Solution

1
Analyze the resiliency requirements to ensure survival of regional outages.
Identify that multi-region replication with automatic failover is required to maintain availability during regional disasters.
Single-region deployments cannot survive regional datacenter outages.
2
Analyze the scaling requirements to prevent hot partitions.
Select a partition key with high cardinality (such as deviceId).
Low-cardinality keys like deviceStatus group too many documents into the same partition, leading to hot partitions under scale.

Key Concept

Azure Cosmos DB multi-region replication and partition key selection
Question 183Question

An international logistics enterprise is designing the cloud architecture to host its core tracking and shipping application on Azure. The application's backend consists of three highly interdependent databases that perform cross-database transactions and rely on SQL Server Agent for scheduled ETL jobs. Additionally, the application requires SQL Server FILESTREAM to read and write unstructured shipping documents directly to the local file system. The proposed architecture must ensure these databases are deployed in a private network environment and support automatic failover with a recovery time objective (RTO) of under 10 seconds. Which Azure SQL deployment option should you recommend to meet these requirements?

Show answer & explanation

Answer: SQL Server on Azure Virtual Machines configured with an Always On Availability Group

Answer

SQL Server on Azure Virtual Machines configured with an Always On Availability Group
SQL Server on Azure Virtual Machines configured with an Always On Availability Group is the only deployment option that supports all the specified requirements. SQL Server on Azure VMs supports the full feature set of SQL Server, including FILESTREAM (which requires local OS file system access), SQL Server Agent, and cross-database transactions. Configuring it with an Always On Availability Group inside a virtual network meets both the network isolation and the sub-10 second RTO requirements.

Step-by-Step Solution

1
Identify the critical SQL Server feature requirements from the scenario.
The application requires cross-database transactions, SQL Server Agent, and SQL Server FILESTREAM.
These features narrow down the compatible Azure SQL deployment options.
2
Evaluate the compatibility of Azure SQL Database (single database or elastic pools) and Azure SQL Managed Instance against these features.
Neither Azure SQL Database nor Azure SQL Managed Instance supports SQL Server FILESTREAM. Azure SQL Database also lacks native SQL Server Agent and cross-database transaction support.
Managed service limitations exclude Azure SQL Database and Azure SQL Managed Instance, leaving SQL Server on Azure Virtual Machines as the only option that supports FILESTREAM.
3
Determine the high availability configuration for SQL Server on Azure Virtual Machines to meet the RTO target.
SQL Server Always On Availability Groups deployed on Azure VMs provide automatic failover and can meet the RTO requirement of under 10 seconds.
Always On Availability Groups provide the necessary high availability and low RTO within a private virtual network.

Key Concept

SQL Server feature compatibility across Azure SQL deployment options, specifically regarding FILESTREAM and administrative capabilities.
Estimated Time:3m 0s
Question 184Question

A legal services firm is deploying a new application on Azure that uses a relational database. The design must accommodate the following requirements:

- The database must support cross-database queries and SQL Server Agent.
- The database must be highly available and resilient to zone outages.
- Administrative effort for managing the underlying operating system must be eliminated.

Which relational database solution and configuration should you recommend?

Show answer & explanation

Answer: Azure SQL Database Managed Instance configured with zone-redundant storage

Answer

Azure SQL Database Managed Instance configured with zone-redundant storage
The correct option is Azure SQL Database Managed Instance configured with zone-redundant storage because it supports instance-level features such as SQL Server Agent and cross-database queries, requires no operating system management, and is resilient to availability zone failures through zone-redundant replication.

Step-by-Step Solution

1
Evaluate feature requirements.
SQL Server Agent and cross-database queries require instance-level features, ruling out Azure SQL Database single database.
Azure SQL Database single database does not natively support SQL Server Agent or cross-database queries.
2
Evaluate management requirements.
Operating system administrative effort must be eliminated, ruling out SQL Server on Azure Virtual Machines.
SQL Server on Azure VMs is a fully self-managed Infrastructure-as-a-Service (IaaS) option requiring OS patching.
3
Evaluate resiliency requirements.
Resilience to zone outages requires a zone-redundant storage option.
Locally redundant storage is limited to a single facility and cannot survive a zone failure, whereas zone-redundant storage replicates data across multiple zones.

Key Concept

Azure SQL relational deployment selection based on legacy compatibility features, high availability, and operational overhead boundaries.
Estimated Time:2m 0s
Question 185Question

A global aviation logistics company is designing an identity governance and privileged access strategy for its Azure environment. The environment contains several subscriptions hosting flight scheduling applications.

The company has the following security requirements:
- External consultants must be granted the Contributor role on a subscription named Sub1 only when they are actively performing maintenance tasks.
- The access granted to external consultants must be automatically audited every 30 days, and any access not explicitly re-approved must be revoked.
- Emergency break-glass administrator accounts must remain functional even if there is an outage of the company's identity provider or primary multi-factor authentication (MFA) service.
- All administrator access assignments must follow the principle of least privilege and use group-based assignment where possible.

Which two configuration steps should you recommend to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra ID security group for the external consultants, configure it as eligible for the Contributor role in Sub1 using Privileged Identity Management (PIM) for Azure resources, and set up a monthly recurring access review.; Configure Conditional Access policies to enforce multi-factor authentication (MFA) for administrative access, ensuring that emergency break-glass accounts are excluded from these policies.

Answer

Create a Microsoft Entra ID security group for the external consultants, configure it as eligible for the Contributor role in Sub1 using PIM for Azure resources with a monthly recurring access review, and configure Conditional Access policies to enforce MFA for administrative access while excluding emergency break-glass accounts.
To support just-in-time access for external consultants, configuring an eligible role assignment via Privileged Identity Management (PIM) for Azure resources is the correct approach. Group-based assignment ensures scalability. A monthly access review automatically audits and revokes inactive access. For emergency break-glass accounts, excluding them from Conditional Access MFA policies ensures they remain accessible even during an outage of the MFA provider.

Step-by-Step Solution

1
Evaluate the external consultant access requirements.
Identified the need for group-based delegation, just-in-time (JIT) activation, and a 30-day automated review process.
Creating a security group and assigning it as eligible for the Contributor role via Privileged Identity Management (PIM) for Azure resources provides JIT capability. Configuring monthly access reviews satisfies the automatic 30-day revocation requirement.
2
Evaluate the emergency access requirements.
Identified the need to prevent tenant lockout during primary identity provider or MFA service outages.
Excluding emergency break-glass accounts from Conditional Access policies that enforce MFA ensures that administrators can access the environment using alternative verification methods if the primary MFA service goes offline.

Key Concept

Designing privileged access management using Microsoft Entra ID PIM and securing emergency accounts against lockout.
Question 186Question

A company named AeroSpace Dynamics is designing a governance strategy for its Azure environment. The environment consists of multiple subscriptions under a single management group.

You must enforce the following compliance requirements:
1. All resource groups must have an Owner tag. If a resource group is created without this tag, the tag must be automatically added and set to a default value during resource group creation.
2. All Azure SQL databases must have vulnerability assessment configured. If a database is deployed without it, the vulnerability assessment settings must be deployed automatically.

You need to recommend the Azure Policy effects that will satisfy these requirements without blocking resource creation.

Which two policy effects should you recommend? (Select two.)

Select all that apply

Show answer & explanation

Answer: Modify; DeployIfNotExists

Answer

The correct policy effects are Modify and DeployIfNotExists.
The Modify effect should be recommended to automatically add or update resource tags during creation or update. The DeployIfNotExists effect should be recommended to automatically deploy the vulnerability assessment resource template when a SQL database is created without it. Both effects satisfy the requirements without blocking resource creation.

Step-by-Step Solution

1
Analyze the first requirement: automatically adding an Owner tag to a resource group if it is missing during creation without blocking the deployment.
The Modify policy effect is ideal for adding, updating, or removing properties or tags during resource creation or update.
Unlike Deny, Modify corrects the resource at creation time without failing the deployment.
2
Analyze the second requirement: automatically deploying vulnerability assessment settings for Azure SQL databases if they are missing.
The DeployIfNotExists (DINE) policy effect is designed to deploy a template containing a child or related resource when the target resource is created or updated and does not have the specified configuration.
Using DINE ensures automatic remediation of the database configuration without blocking the initial deployment.

Key Concept

Selecting the correct Azure Policy effect (Modify vs. DeployIfNotExists vs. Deny/Audit) based on remediation and deployment blocking requirements.
Estimated Time:2m 0s
Question 187Question

A company has 100 GB100\text{ GB} of transactional logs in CSV format stored in an Azure Data Lake Storage Gen2 (ADLS Gen2) account. You need to design an analytical query solution that meets the following requirements:
- Allows data analysts to run ad-hoc, exploratory T-SQL queries on the CSV files.
- Minimizes costs and administrative overhead by avoiding persistent compute resources.
- Ensures that the data remains available even if the primary Azure region suffers a complete outage.

Which two configurations should you recommend in your design?

Select all that apply

Show answer & explanation

Answer: Query the files directly using a serverless SQL pool in Azure Synapse Analytics.; Configure the storage account to use Geo-Redundant Storage (GRS).

Answer

Query the files directly using a serverless SQL pool in Azure Synapse Analytics and configure the storage account to use Geo-Redundant Storage (GRS).
Using a serverless SQL pool in Azure Synapse Analytics allows you to run ad-hoc T-SQL queries directly on the CSV files in Azure Data Lake Storage Gen2 without the cost or overhead of provisioned compute. To ensure regional resilience, configuring the storage account with Geo-Redundant Storage (GRS) replicates data to a secondary region, protecting against regional outages.

Step-by-Step Solution

1
Determine the optimal query compute option.
Serverless SQL pool is selected.
Since the queries are ad-hoc and run infrequently on CSV files, a serverless SQL pool avoids the administrative overhead and cost of running a persistent dedicated SQL pool.
2
Determine the optimal storage redundancy model.
Geo-Redundant Storage (GRS) is selected.
To ensure availability during a complete regional outage, GRS replicates data to a secondary region, unlike LRS which is confined to a single datacenter.

Key Concept

Designing cost-effective analytical storage queries and high-availability storage configurations.
Question 188Question

You are designing a secure data storage solution in Azure. A partner organization requires read-only access to a specific Azure Blob Storage container for a period of 30 days. The security policy mandates that you must be able to revoke this access immediately if a security breach occurs, without rotating the storage account access keys.

Which of the following access control strategies should you recommend?

Show answer & explanation

Answer: Generate a Shared Access Signature (SAS) token that is associated with a stored access policy.

Answer

Generate a Shared Access Signature (SAS) token that is associated with a stored access policy.
Associating a Shared Access Signature (SAS) with a stored access policy allows you to manage the lifetime and permissions of the SAS dynamically. If you need to revoke access, you can delete or modify the stored access policy on the container. This immediately invalidates any SAS tokens generated from that policy without needing to rotate the storage account's primary or secondary access keys, minimizing disruption to other services.

Step-by-Step Solution

1
Analyze the requirement for temporary, revocable access to a blob container without key rotation.
Identified that rotating storage account keys is unacceptable for revocation.
Rotating keys would disrupt other clients and applications using the same storage account.
2
Evaluate how to revoke a Shared Access Signature (SAS) token.
Found that an ad-hoc SAS cannot be revoked without key rotation, whereas a SAS associated with a stored access policy can be revoked by modifying or deleting the policy.
Stored access policies bind the SAS validation to the policy's state in Azure Storage.
3
Select the security control that matches the scenario requirements.
Recommend generating a SAS token associated with a stored access policy.
This fulfills the 30-day access, read-only permissions, and instant revocation requirements without rotating storage account keys.

Key Concept

Using stored access policies to manage and revoke Shared Access Signatures (SAS) without rotating storage account keys.
Question 189Question

You are designing the storage architecture for a new high-performance financial ledger system hosted on Azure Linux Virtual Machines.

The system must satisfy the following requirements:
* Database transaction logs: Support up to 2000020{}000 IOPS and 500 MB/s500\text{ MB/s} throughput with sub-millisecond latency. The storage solution must sustain a single availability zone outage without data loss.
* Shared configuration files: Multiple Linux VMs must concurrently access a POSIX-compliant shared file system over the NFS v4.1 protocol. This storage must also remain available during an availability zone outage.
* Historical audit logs: Store logs cost-effectively for 77 years. They are rarely accessed, but when requested, they must be fully available for read operations within 1010 minutes.

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

Select all that apply

Show answer & explanation

Answer: Provision Premium SSD v2 Managed Disks configured with Zone-Redundant Storage (ZRS) for the database transaction logs.; Create an Azure Files Premium share using the NFS v4.1 protocol and configured with Zone-Redundant Storage (ZRS) for the shared configuration files.

Answer

Provision Premium SSD v2 Managed Disks configured with Zone-Redundant Storage (ZRS) for the database transaction logs, and create an Azure Files Premium share using the NFS v4.1 protocol and configured with Zone-Redundant Storage (ZRS) for the shared configuration files.
Premium SSD v2 Managed Disks support ZRS and allow independent provisioning of up to 8000080{}000 IOPS and 1200 MB/s1{}200\text{ MB/s} throughput with sub-millisecond latencies, making them ideal for the transaction logs. Azure Files Premium (FileStorage) supports NFS v4.1 and ZRS, meeting the multi-VM concurrent POSIX-compliant access and zone-resiliency requirements for the configuration files.

Step-by-Step Solution

1
Analyze the requirements for the database transaction logs.
The workload requires up to 2000020{}000 IOPS, 500 MB/s500\text{ MB/s} throughput, sub-millisecond latency, and zone redundancy. Premium SSD v2 satisfies these performance metrics and supports Zone-Redundant Storage (ZRS). Ultra Disks do not support ZRS and are limited to Locally-Redundant Storage (LRS).
To ensure both performance targets and high availability constraints are met for critical database transaction logs.
2
Analyze the requirements for the shared configuration files.
The workload requires a POSIX-compliant shared file system accessible by multiple Linux VMs concurrently via NFS v4.1, along with zone redundancy. Azure Files Premium (FileStorage) is required to support the NFS v4.1 protocol with the necessary low latency and supports ZRS. Azure Files Standard with SMB fails both the protocol and performance requirements.
To select a compatible file storage service and protocol that supports multi-writer access on Linux with zone-level resilience.
3
Analyze the requirements for the historical audit logs.
The logs must be accessible within 1010 minutes. While the Archive tier is cost-effective, it requires a rehydration process that takes hours, which is too slow. Therefore, Hot, Cool, or Cold Blob Storage tiers must be used instead of the Archive tier.
To ensure that retrieval times do not exceed the 1010-minute threshold defined by business requirements.

Key Concept

Selecting Azure disk tiers and file storage services based on performance, protocol (NFS vs SMB), availability (ZRS vs LRS), and retrieval latency requirements.
Question 190Question

An organization needs to grant a third-party audit application read-only access to an Azure Blob storage container for exactly 30 days. Security policies require that administrators must have the ability to immediately revoke this access at any time if a security compromise is suspected, without rotating the storage account keys or affecting other active integrations. Which access control strategy should you recommend?

Show answer & explanation

Answer: Create a Stored Access Policy on the container with read permissions and a 30-day expiration, then generate a SAS token associated with this policy.

Answer

Create a Stored Access Policy on the container with read permissions and a 30-day expiration, then generate a SAS token associated with this policy.
The correct option outlines using a Stored Access Policy on the blob container to control the SAS token's permissions and lifetime. By linking the SAS token to a Stored Access Policy, administrators can revoke the access instantly by deleting or changing the policy, without impacting any other integrations or rotating account access keys.

Step-by-Step Solution

1
Analyze the core requirements for the solution.
Identify that the solution must provide temporary access (30 days) and be immediately revocable without rotating storage account keys or affecting other integrations.
This establishes the constraints for evaluating the different storage access mechanisms.
2
Evaluate the capabilities of Shared Access Signatures (SAS) and Stored Access Policies.
Determine that while an ad-hoc SAS can set a 30-day duration, it cannot be revoked without rotating keys. A Stored Access Policy provides a management layer on the container that allows immediate revocation by modifying or deleting the policy.
This isolates the optimal security control that satisfies both the expiration and instant revocation requirements.
3
Contrast the storage security control with identity-based controls.
Confirm that direct RBAC role assignments or permanent group assignments fail either the delegation structure recommendations or the automatic 30-day expiration requirement.
This eliminates non-conforming configurations and validates the choice of using a Stored Access Policy.

Key Concept

Stored Access Policies provide a way to group Shared Access Signatures (SAS) and place additional constraints on them, enabling revocation of the SAS tokens by modifying or deleting the policy rather than rotating storage keys.
Question 191Question

A retail company is designing the network security architecture for a new containerized inventory application hosted on Azure Container Apps integrated with a virtual network named VNet1. The design must meet the following requirements:
- The application must securely retrieve secrets from an Azure Key Vault named KV1.
- KV1 must disable all public network access.
- The containerized application must resolve and connect to KV1 over a private IP address within VNet1.
- Administrative maintenance must be minimized.

Which two actions should you include in the design?

Select all that apply

Show answer & explanation

Answer: Create a private endpoint for KV1 in a subnet of VNet1.; Configure an Azure Private DNS zone named privatelink.vaultcore.azure.net and link it to VNet1.

Answer

To secure access to the Key Vault over private IP addresses and disable public exposure, you must create a private endpoint for the Key Vault inside the virtual network and configure an Azure Private DNS zone named privatelink.vaultcore.azure.net linked to the virtual network for proper name resolution.
To secure the Azure Key Vault by disabling public access while allowing the application to connect over a private IP, a private endpoint must be created in the virtual network. To ensure name resolution works seamlessly without changing connection strings, an Azure Private DNS zone named privatelink.vaultcore.azure.net must be deployed and linked to the virtual network.

Step-by-Step Solution

1
Identify the private connectivity requirements.
Since the Key Vault must have public access disabled and be accessed over a private IP, Azure Private Link (Private Endpoint) is required.
Private endpoints expose PaaS services on a private IP address within a virtual network subnet.
2
Determine the DNS resolution mechanism.
An Azure Private DNS zone named privatelink.vaultcore.azure.net must be linked to the application VNet.
Applications must still address the Key Vault using its public FQDN, which must resolve to the private endpoint IP address locally.
3
Evaluate and eliminate administrative overhead options.
Avoid manual NSG IP configuration and custom routing rules.
Manual IP rules in NSGs and redundant UDRs increase configuration overhead and fail to align with Azure network security best practices.

Key Concept

Designing private access to Azure PaaS resources using Private Endpoints and integrated Private DNS zones.
Question 192Question

An international logistics enterprise is architecting an Azure Cosmos DB for NoSQL solution to track real-time container dispatch updates. The workload profile consists of 60% writes and 40% reads. Updates are generated by thousands of IoT sensors across three main hubs: East US, West US, and North Europe.

The architecture must satisfy the following criteria:
- Guarantee a write availability SLA of 99.999%.
- Maintain write response times under 10 ms at the 99th percentile by allowing writes to execute in the closest regional hub.
- Prevent performance bottlenecks (hot partitions) at busy shipping hubs during peak operating hours.
- Keep the local client consistency model at Session level.

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

Select all that apply

Show answer & explanation

Answer: Enable multiple write regions for the Azure Cosmos DB account.; Use a synthetic key combining the hub identifier and the dispatch transaction identifier as the partition key.

Answer

To meet the requirements, you must enable multiple write regions for the Azure Cosmos DB account and use a synthetic key combining the hub identifier and the dispatch transaction identifier as the partition key.
The requirements call for a 99.999% write availability SLA and sub-10ms write latency. Enabling multiple write regions satisfies this by allowing writes to run locally and offering the 99.999% SLA. Additionally, to avoid hot partitions under heavy load at specific hubs, a high-cardinality partition key is required. A synthetic key combining the hub identifier and the dispatch transaction identifier distributes the write requests evenly across logical partitions.

Step-by-Step Solution

1
Analyze the SLA and latency requirements for write operations.
Determine that a 99.999% write availability SLA and local sub-10ms latency require configuring the Azure Cosmos DB account with multiple write regions.
Single-write region configurations only provide up to a 99.99% write availability SLA and force cross-region network hops for writes originating outside the primary region.
2
Analyze partition key options to avoid performance bottlenecks (hot partitions) during peak traffic.
Determine that the partition key must have high cardinality to distribute the load across multiple physical partitions.
Using a low-cardinality key like a hub identifier would cause all traffic for that hub to hit a single logical partition, leading to rate limiting (HTTP 429).
3
Select the appropriate high-cardinality partitioning strategy.
Combine the hub identifier and the dispatch transaction identifier to form a synthetic partition key.
The combination creates a unique, high-cardinality key that ensures even distribution of write operations while preserving session-level consistency.

Key Concept

Designing globally distributed Azure Cosmos DB configurations for high availability, low latency, and efficient partitioning under write-heavy workloads.
Question 193Question

An organization plans to migrate a high-throughput transaction processing database to Azure Virtual Machines. The database transaction log files require high IOPS and consistently low latency. The database architecture must be resilient to the outage of a single datacenter within the primary Azure region. Which disk storage configuration should you recommend for the database transaction logs?

Show answer & explanation

Answer: Premium SSD managed disks configured with Zone-Redundant Storage (ZRS)

Answer

Premium SSD managed disks configured with Zone-Redundant Storage (ZRS) should be recommended because they satisfy the high IOPS and low latency requirements for database transaction logs while providing zone redundancy to protect against a single datacenter failure in the primary region.
Premium SSD managed disks configured with Zone-Redundant Storage (ZRS) provide the necessary high IOPS and low-latency performance required for database transaction logs, while replicating the data across three separate availability zones within the primary region to survive a single datacenter failure.

Step-by-Step Solution

1
Analyze the performance requirements of the database transaction logs.
The workload requires high IOPS and low latency, which rules out Standard HDD and Standard SSD tiers.
Database transaction logs are highly sensitive to write latency. Standard storage tiers cannot guarantee the necessary performance.
2
Analyze the resiliency requirements.
The storage must survive a single datacenter outage within the primary region, indicating a requirement for zone-redundancy (ZRS).
Locally Redundant Storage (LRS) keeps data within a single datacenter and cannot survive a datacenter failure.
3
Combine performance and resiliency needs to select the correct disk type and redundancy option.
Premium SSD with Zone-Redundant Storage (ZRS) meets both performance and zone resiliency requirements.
Premium SSD provides the necessary performance tier, while ZRS provides the required availability zone replication.

Key Concept

Selecting the appropriate disk storage tier and redundancy option based on application performance needs and high availability requirements.
Question 194Question

An insurance company plans to migrate an on-premises claims processing database system to Azure. The system has the following requirements:
- Runs scheduled ETL processing and database maintenance using SQL Server Agent jobs.
- Requires cross-database queries across two databases using three-part names.
- Must restrict database network traffic to a specific Azure Virtual Network (VNet) without exposing public endpoints.
- Must minimize administrative overhead for operating system patching and VM management.

Which Azure SQL deployment option should you recommend?

Show answer & explanation

Answer: Azure SQL Managed Instance

Answer

Azure SQL Managed Instance
Azure SQL Managed Instance is the correct choice because it supports legacy SQL Server features such as SQL Server Agent jobs and cross-database queries using three-part names, while running as a fully managed Platform as a Service (PaaS) that handles operating system patching and backups automatically. It also deploys directly into an Azure Virtual Network for secure, private connectivity.

Step-by-Step Solution

1
Analyze the application's compatibility requirements.
The requirements specify SQL Server Agent jobs and cross-database queries using three-part names.
These features are typical of legacy SQL Server environments and are not natively supported in Azure SQL Database (Single Database or Elastic Pools) without workarounds.
2
Analyze the network isolation requirement.
The database traffic must be restricted to an Azure Virtual Network without exposing public endpoints.
Azure SQL Managed Instance deploys directly into an Azure Virtual Network subnet by default, providing native network isolation.
3
Analyze the management overhead requirement.
Operating system patching and VM management must be minimized.
SQL Server on Azure Virtual Machines requires full OS and SQL Server management (IaaS), whereas Azure SQL Managed Instance is a fully managed Platform as a Service (PaaS) that automates these tasks.
4
Select the service that meets all criteria.
Azure SQL Managed Instance satisfies SQL Server Agent, cross-database queries, VNet integration, and low administrative overhead.
It is the only option that fulfills both the compatibility and PaaS requirements.

Key Concept

Azure SQL deployment option selection based on SQL Server feature compatibility, network isolation, and management overhead.
Question 195Question

A retail company is designing a monitoring and log routing architecture for its Azure workloads. You need to match each monitoring requirement to its correct Azure Monitor destination or feature. Which destination or feature should you associate with each requirement?

Click a left item, then click its matching right item

Items

Archive subscription-level Azure Activity logs for 5 years to meet regulatory compliance audits at the lowest storage cost.
Stream diagnostic logs from an Azure Application Gateway in near real-time to a third-party SIEM system.
Perform complex query analysis and correlation across multiple resources using Kusto Query Language (KQL).
Configure alerts on virtual machine CPU utilization that trigger within a minute of a threshold breach.

Matches

Show answer & explanation

Answer

Archive subscription-level Azure Activity logs for 5 years to meet regulatory compliance audits at the lowest storage cost matches with Azure Storage account; Stream diagnostic logs from an Azure Application Gateway in near real-time to a third-party SIEM system matches with Azure Event Hubs; Perform complex query analysis and correlation across multiple resources using Kusto Query Language (KQL) matches with Azure Monitor Log Analytics workspace; Configure alerts on virtual machine CPU utilization that trigger within a minute of a threshold breach matches with Azure Monitor Metrics.
The matching pairs correctly align each specific monitoring and alerting requirement to the Azure service designed to address it. Under Azure Monitor diagnostic settings, logs can be routed to a Storage Account for low-cost compliance archiving, Event Hubs for real-time external pipeline integration, or a Log Analytics workspace for KQL query analytics. Time-series metrics are natively written to the Azure Monitor Metrics database to enable sub-minute metric alerts.

Step-by-Step Solution

1
Analyze the log archiving requirement.
Long-term (5-year) compliance retention with the primary constraint of 'lowest storage cost' maps to Azure Storage, as archiving logs to blob storage is significantly cheaper than retaining them in a Log Analytics workspace.
To satisfy retention requirements cost-effectively.
2
Analyze the real-time external streaming requirement.
Streaming diagnostic logs to a third-party, non-Azure SIEM in near real-time is best achieved by routing logs through Azure Event Hubs, which acts as a message broker for ingestion pipelines.
To support external SIEM ingestion.
3
Analyze the query and correlation requirement.
Querying logs via Kusto Query Language (KQL) requires the logs to be stored in an Azure Monitor Log Analytics workspace, which is the native environment for log search and correlation queries.
To enable interactive log querying with KQL.
4
Analyze the near real-time alerting requirement.
Metric alerts targeting fast evaluation times (e.g., under a minute) run against the Azure Monitor Metrics store (a time-series database) rather than Log Analytics logs, providing quicker alert response times.
To minimize latency for infrastructure alerts.

Key Concept

Log routing destinations in Azure Monitor support distinct operational requirements, where Storage Accounts are optimized for cost-effective long-term retention, Event Hubs for real-time external integration, Log Analytics workspaces for rich KQL queries, and Azure Monitor Metrics for low-latency alerting.
Question 196Question

An enterprise is designing a governance strategy for its Azure subscriptions. The security team requires that all newly created Azure Storage accounts must have their minimum TLS version configured to version 1.2. If a deployment request does not specify this version or sets it to a lower value, the configuration must be automatically updated to version 1.2 without blocking the deployment of the resource. Which Azure Policy configuration should you recommend to meet these requirements with the least administrative overhead?

Show answer & explanation

Answer: An Azure Policy using the Modify effect to set the minimum TLS version property to 1.2 during resource creation.

Answer

An Azure Policy using the Modify effect to set the minimum TLS version property to 1.2 during resource creation.
The correct solution is to use the Modify effect. The Modify effect is used to add, replace, or remove properties or tags on a resource during creation or update. It allows the resource deployment to succeed while automatically correcting the minimum TLS version to 1.2, meeting the requirements with the least administrative overhead.

Step-by-Step Solution

1
Analyze the governance requirement and target setting.
The requirement is to ensure the minimum TLS version on new storage accounts is set to 1.2, which is a resource property ('properties.minimumTlsVersion').
Understanding whether the target is a property of the resource itself or an auxiliary resource determines the correct policy effect.
2
Evaluate the remediation behavior.
The setting must be automatically updated during creation without blocking the deployment.
This rules out the Deny effect (which blocks deployment) and the Audit effect (which only reports but does not remediate).
3
Select the policy effect that updates properties with the least overhead.
The Modify effect is chosen over DeployIfNotExists.
Modify is designed for direct property changes on the resource itself during creation/update, whereas DeployIfNotExists is intended for deploying auxiliary, nested resources (like diagnostics or backup settings) and would introduce unnecessary template deployment overhead.

Key Concept

Selecting the correct Azure Policy effect to enforce compliance on resource properties without blocking deployments.
Question 197Question

An organization named Meridian Global Solutions plans to design a hybrid identity solution using Microsoft Entra ID. The organization has an on-premises Active Directory Domain Services (AD DS) forest. You need to recommend an identity architecture that meets the following requirements:
- Users must sign in to cloud resources using their on-premises credentials.
- Users' compromised credentials must be automatically detected and flagged on Microsoft Entra ID without depending on on-premises authentication infrastructure.
- All users assigned to highly privileged roles must be forced to use multi-factor authentication (MFA) to access the Azure portal.
- The risk of complete administrative lockout due to MFA service disruptions or misconfigured Conditional Access policies must be mitigated.
- The exposure of privileged roles must be minimized by requiring approval and just-in-time activation.

Which combination of hybrid authentication, Conditional Access configuration, and role assignment strategy should you recommend?

Show answer & explanation

Answer: Implement Password Hash Synchronization (PHS), configure a Conditional Access policy requiring MFA for all administrative roles with an exclusion for an emergency access account, and assign users as eligible for privileged roles in Privileged Identity Management (PIM).

Answer

Implement Password Hash Synchronization (PHS), configure a Conditional Access policy requiring MFA for all administrative roles with an exclusion for an emergency access account, and assign users as eligible for privileged roles in Privileged Identity Management (PIM).
The correct option outlines the optimal architecture. Password Hash Synchronization (PHS) natively enables Microsoft Entra ID Protection to perform leaked credential detection in the cloud, fulfilling the requirement without requiring on-premises server evaluation. Setting up a Conditional Access policy that enforces MFA for administrative roles but excludes a designated emergency access account prevents admin lockout in the event of a tenant-wide MFA disruption. Using eligible assignments in Microsoft Entra Privileged Identity Management (PIM) enforces just-in-time activation and requires approvals, keeping highly privileged roles inactive until needed.

Step-by-Step Solution

1
Select the appropriate hybrid authentication method based on requirements.
Password Hash Synchronization (PHS) is selected.
PHS allows Microsoft Entra ID to perform leaked credential detection directly in the cloud without relying on on-premises agents or redirecting authentication requests to local servers, minimizing infrastructure overhead.
2
Design the Conditional Access policy and lockout mitigation strategy.
A Conditional Access policy is designed to enforce MFA for all administrative roles, with a specific exclusion group containing a dedicated emergency access (glass-breaker) account.
Excluding an emergency access account from MFA enforcement ensures that administrators can still sign in and remediate issues in the event of an MFA service failure or policy misconfiguration.
3
Design the privileged access lifecycle and role assignment strategy.
Privileged Identity Management (PIM) is utilized, configuring administrative roles as eligible rather than permanently active.
Eligible assignments mandate that administrators perform just-in-time (JIT) activation with optional approval, minimizing the attack surface and mitigating risks associated with compromised privileged credentials.

Key Concept

Microsoft Entra ID hybrid identity design, Conditional Access policy exclusions, and Privileged Identity Management (PIM) role assignments.
Estimated Time:2m 30s
Question 198Question

A smart-grid utility provider is designing an identity governance and privileged access solution to comply with regional energy infrastructure regulations. The company must allow an external security team consisting of five auditors to review the configuration of all Azure resources across three production subscriptions for a limited period of 30 days. The auditors require read-only access.

The solution must meet the following requirements:
- Ensure the auditors must request approval and perform multi-factor authentication (MFA) each time they access the subscriptions.
- Minimize administrative overhead when managing access for the five external auditors.
- Prevent administrative tenant lockout in the event of an MFA service outage.

Which solution should you recommend?

Show answer & explanation

Answer: Create a Microsoft Entra security group containing the five auditors. In Privileged Identity Management (PIM), configure an eligible assignment for the group to the Reader role at the subscription level, with a 30-day assignment lifetime. Exclude emergency access accounts from the Conditional Access policy that enforces MFA.

Answer

Create a Microsoft Entra security group containing the five auditors. In Privileged Identity Management (PIM), configure an eligible assignment for the group to the Reader role at the subscription level, with a 30-day assignment lifetime. Exclude emergency access accounts from the Conditional Access policy that enforces MFA.
The correct solution involves creating a Microsoft Entra security group to hold the auditor accounts, which minimizes administrative overhead. By configuring the security group's assignment to the Reader role as eligible in Privileged Identity Management (PIM) rather than active, the auditors are required to perform multi-factor authentication (MFA) and request approval to activate the role only when needed (just-in-time access). Finally, excluding the emergency access accounts from the Conditional Access policy enforcing MFA prevents tenant lockout in case of an MFA service failure.

Step-by-Step Solution

1
Group external users to minimize overhead
Create a Microsoft Entra security group and add the five external auditor accounts as members, allowing role assignments to be managed collectively.
Directly assigning roles to multiple individual accounts increases administrative complexity and overhead.
2
Enforce just-in-time (JIT) access using Privileged Identity Management (PIM)
Configure the security group with an eligible assignment for the Reader role at the subscription level, set with a maximum lifetime of 30 days.
This guarantees that permissions are not permanently active, requiring the auditors to activate the role and authenticate via MFA on demand.
3
Configure emergency access account exclusion
Exclude emergency access (break-glass) accounts from the Conditional Access policy that enforces MFA.
This ensures that administrators can still access the tenant to resolve issues during an MFA service outage, preventing lockout.

Key Concept

Privileged Identity Management (PIM) eligibility combined with Microsoft Entra group management and break-glass account governance.
Question 199Question

Solis Renewable Technologies has an on-premises Active Directory Domain Services (AD DS) forest with 5,400 users. The company is designing a hybrid identity solution to integrate with a new Microsoft Entra ID tenant.

The solution must satisfy the following requirements:
- Users must be able to sign in using their existing on-premises credentials.
- Users must be able to reset their own passwords on-premises via the cloud portal.
- Authentication must continue to function even if the network connection between the on-premises datacenter and Azure is temporarily lost.
- The infrastructure complexity and administrative overhead of the identity sync solution must be minimized.

Which hybrid identity synchronization and authentication design should you recommend?

Show answer & explanation

Answer: Microsoft Entra Connect with Password Hash Synchronization (PHS) and Password Writeback enabled.

Answer

Microsoft Entra Connect with Password Hash Synchronization (PHS) and Password Writeback enabled.
Password Hash Synchronization (PHS) copies password hashes to Microsoft Entra ID, allowing authentication requests to be processed completely in the cloud. This ensures that authentication remains operational even if on-premises connectivity is lost. Enabling Password Writeback allows users to use Microsoft Entra ID Self-Service Password Reset (SSPR) to change or reset their passwords and have those changes updated in the on-premises Active Directory in real time. PHS also represents the lowest administrative overhead compared to federated or pass-through architectures.

Step-by-Step Solution

1
Evaluate the authentication availability constraint.
Real-time authentication solutions (Pass-through Authentication and Active Directory Federation Services) are ruled out because they fail when the on-premises network connection is lost.
Both PTA and AD FS rely on active on-premises connectivity to authenticate users, whereas PHS enables cloud-based authentication using synchronized password hashes.
2
Evaluate the self-service password reset constraint.
Password Writeback must be enabled in Microsoft Entra Connect.
Password Writeback is the specific feature that allows password changes made via Entra ID Self-Service Password Reset (SSPR) to sync back to the on-premises Active Directory.
3
Evaluate the administrative overhead and complexity constraint.
Confirm Password Hash Synchronization (PHS) as the primary option over AD FS and PTA.
PHS does not require any additional on-premises agents or federation server infrastructure, minimizing complexity and administrative cost.

Key Concept

Selecting and configuring hybrid identity sync and authentication methods to meet availability, self-service, and complexity requirements.
Question 200Question

A company is planning to migrate two relational database workloads to Azure. The workloads have the following requirements:

* Workload 1: A legacy database that relies on SQL Server Agent jobs, cross-database queries, and Common Language Runtime (CLR). The database administrators want to eliminate OS-level maintenance and automated backup infrastructure management.
* Workload 2: A new application database with highly variable, unpredictable read/write traffic that must automatically pause compute billing during inactive periods to minimize costs.

Which two Azure SQL options should you recommend? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure SQL Managed Instance for Workload 1; Azure SQL Database (Serverless tier) for Workload 2

Answer

Azure SQL Managed Instance for Workload 1 and Azure SQL Database (Serverless tier) for Workload 2
Azure SQL Managed Instance provides the instance-level capabilities (SQL Server Agent, cross-database queries, and CLR) required for Workload 1 without the administrative overhead of VM management. Azure SQL Database Serverless automatically scales and pauses compute during idle times, meeting the requirements of Workload 2.

Step-by-Step Solution

1
Evaluate legacy database compatibility and operational requirements for Workload 1.
The workload requires SQL Server Agent, cross-database queries, and CLR, along with zero OS patching and backup management overhead. Azure SQL Managed Instance supports these instance-level features while acting as a fully managed PaaS solution.
Choosing the correct PaaS database tier requires matching compatibility requirements to the features supported by each service level.
2
Evaluate scaling and cost optimization requirements for Workload 2.
The database has highly variable and unpredictable traffic and must pause compute billing when inactive. Azure SQL Database (Serverless tier) automatically scales compute resources and supports an auto-pause behavior that stops billing during idle periods.
Serverless computes optimize resource usage and cost for applications with intermittent, unpredictable usage patterns.
3
Select the correct combination of options.
Recommend Azure SQL Managed Instance for Workload 1 and Azure SQL Database (Serverless tier) for Workload 2.
This combination uniquely satisfies the technical capabilities, operational limits, and cost constraints for both database workloads.

Key Concept

Selecting Azure SQL deployment models and tiers based on application feature compatibility (SQL Agent, CLR, cross-database queries) and cost/scaling requirements.
PreviousPage 10 / 60Next
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin