All practice questions

1198 questions

Question 41Question

An enterprise is migrating a legacy, stateful transaction processing application to Azure. The application has the following requirements:
- It requires physical isolation at the hardware host level to meet compliance and licensing standards.
- The steady-state workload requires 32 vCPUs and 256 GiB of RAM, running continuously 24/7.
- The virtual machines must have a guaranteed 99.95% availability SLA.
- The database log drive requires 20,000 IOPS and sub-millisecond latency.
- The application cannot be containerized due to kernel-level licensing checks.

Which of the following compute and storage designs should you recommend to meet the requirements while minimizing costs?

Show answer & explanation

Answer: Deploy two Azure Dedicated Hosts of the Esv5-family (one in Availability Zone 1 and one in Availability Zone 2). Deploy one E32s v5 virtual machine on each host, and configure the database log volume using Premium SSD v2 disks.

Answer

Deploy two Azure Dedicated Hosts of the Esv5-family (one in Availability Zone 1 and one in Availability Zone 2), deploy one E32s v5 virtual machine on each host, and configure the database log volume using Premium SSD v2 disks.
Deploying two Azure Dedicated Hosts of the Esv5-family across two Availability Zones, running E32s v5 virtual machines with Premium SSD v2 disks, is correct. Esv5-series hosts and VMs provide the exact 1:8 CPU-to-memory ratio needed (32 vCPUs and 256 GiB RAM), avoiding the higher costs of overprovisioning. Azure Dedicated Hosts satisfy the physical isolation requirement at the host level. Placing the hosts and VMs in two different Availability Zones ensures the 99.95% VM availability SLA is met. Finally, Premium SSD v2 provides the required 20,000 IOPS and sub-millisecond latency for database logs cost-effectively.

Step-by-Step Solution

1
Analyze compliance and hardware isolation requirements.
Azure Dedicated Hosts are required because the workload requires physical isolation at the hardware host level.
Dedicated Hosts provide physical servers dedicated to a single Azure subscription, satisfying physical isolation compliance.
2
Determine the optimal VM series based on the CPU-to-memory ratio.
Select the Esv5-series (specifically E32s v5) which offers a 1:8 vCPU-to-GiB RAM ratio (32 vCPUs and 256 GiB RAM).
General-purpose Dsv5-series (1:4 ratio) would require overprovisioning to 64 vCPUs to get 256 GiB RAM, which increases licensing and compute costs.
3
Design the architecture to meet the 99.95% availability SLA.
Provision two Dedicated Hosts distributed across two Availability Zones (Zone 1 and Zone 2) and deploy one VM on each host.
To achieve the 99.95% (or 99.99%) VM availability SLA, VM instances must be distributed across different fault domains or Availability Zones.
4
Select the storage disk type for the database log drive.
Configure the log drive with Premium SSD v2.
Premium SSD v2 supports sub-millisecond latency and can be provisioned with up to 80,000 IOPS, meeting the 20,000 IOPS database log requirements cost-effectively.

Key Concept

Designing compute virtualization solutions with dedicated hosts, high availability across zones, memory-optimized VM sizing, and high-performance storage.
Estimated Time:3m 0s
Question 42Question

A multi-region retail enterprise is establishing a new environment in Azure for its inventory forecasting service. The service is hosted within a dedicated subscription. The operations team consists of 15 system administrators who require contributor permissions at the subscription scope to troubleshoot infrastructure issues. The company's security policy mandates that administrators must not hold permanent high-privilege access, and all access assignments must minimize administrative overhead while ensuring full auditability of elevated permissions.

Which approach should you recommend to meet these requirements?

Show answer & explanation

Answer: Configure Microsoft Entra Privileged Identity Management (PIM) to make a Microsoft Entra ID security group eligible for the Contributor role at the subscription scope, and add the 15 system administrators as members of the group.

Answer

Configure Microsoft Entra Privileged Identity Management (PIM) to make a Microsoft Entra ID security group eligible for the Contributor role at the subscription scope, and add the 15 system administrators as members of the group.
The correct design uses Microsoft Entra Privileged Identity Management (PIM) to assign a security group as eligible for the Contributor role. This meets the security requirement for just-in-time (JIT) access with full auditing, while assigning the role to a security group instead of individual users minimizes administrative overhead and aligns with governance best practices.

Step-by-Step Solution

1
Group administrators in Microsoft Entra ID
A security group is created containing all 15 system administrators.
This simplifies management and aligns with administrative delegation best practices by avoiding direct user role assignments.
2
Configure role eligibility in Privileged Identity Management
The Contributor role at the subscription scope is assigned to the security group as an 'eligible' assignment.
This ensures that administrators must explicitly activate their roles when troubleshooting, enforcing the principle of least privilege through just-in-time access.
3
Enforce auditing and activation requirements
Administrators can activate their eligible role when needed, generating an audit trail of the elevation event.
This satisfies the governance requirement that all elevation events must be monitored and audited.

Key Concept

Azure RBAC, subscription governance, and PIM group-based eligible assignments
Estimated Time:2m 0s
Question 43Question

You are an Azure Solutions Architect designing a data storage solution for a global media streaming platform. The platform must store real-time user playback progress and watch history. The workload has a read-to-write ratio of approximately 40:6040:60. The solution must be distributed across three regions (East US, West Europe, and East Asia) to achieve sub-10ms write latency at the 99th percentile and support an active-active setup. The platform requires a 99.999% availability SLA for both reads and writes. High availability and regional disaster resilience must be guaranteed for all data, including database backups.

Which two configuration options should you include in the architectural design to meet these requirements? (Select TWO)

Select all that apply

Show answer & explanation

Answer: Enable multi-region writes for the Azure Cosmos DB account to support the active-active global configuration and satisfy the low latency and high availability SLA.; Select a high-cardinality partition key, such as a combination of user ID and session ID, to distribute read and write operations evenly across logical partitions.

Answer

Enable multi-region writes for the Azure Cosmos DB account and select a high-cardinality partition key, such as a combination of user ID and session ID.
The correct solution involves enabling multi-region writes for the Azure Cosmos DB account and selecting a high-cardinality partition key (user ID + session ID). Multi-region writes ensure write operations are committed locally in all designated regions, satisfying both the sub-10ms write latency and the 99.999% write availability SLA. A high-cardinality partition key guarantees that the write-heavy workload is evenly distributed across logical and physical partitions, avoiding resource hot spots.

Step-by-Step Solution

1
Analyze global availability and latency requirements.
Identified that active-active multi-region writes are required to meet sub-10ms write latency and the 99.999% availability SLA.
Single-region write models incur cross-region network latency for writes originating in other regions, which exceeds the sub-10ms limit, and only offer 99.99% availability for writes.
2
Evaluate partitioning strategy for write-heavy workload.
Determined that a high-cardinality partition key like user ID and session ID is necessary to avoid physical partition throughput limits.
Cosmos DB distributes data based on partition keys. Low-cardinality keys like region create hot partitions that bottleneck writes and waste RU/s.
3
Evaluate backup redundancy and security configuration.
Ruled out Locally Redundant Storage (LRS) for backups and long-lived Shared Access Signatures without stored access policies.
LRS does not survive datacenter outages, and long-lived SAS tokens cannot be easily revoked if leaked, failing resiliency and security best practices.

Key Concept

Azure Cosmos DB Multi-Region Replication and Partitioning Design
Question 44Question

An enterprise is designing a hub-and-spoke virtual network topology in Azure to secure traffic between application tiers.

The hub virtual network, `vnet-useast-hub` (10.100.0.0/1610.100.0.0/16), hosts an Azure Firewall with the private IP address 10.100.2.410.100.2.4.

The app spoke virtual network, `vnet-useast-app` (10.101.0.0/1610.101.0.0/16), contains two subnets:
* `web-subnet` (10.101.1.0/2410.101.1.0/24)
* `api-subnet` (10.101.2.0/2410.101.2.0/24)

The database spoke virtual network, `vnet-useast-db` (10.102.0.0/1610.102.0.0/16), contains one subnet:
* `db-subnet` (10.102.1.0/2410.102.1.0/24)

Both spoke virtual networks are peered with `vnet-useast-hub`. No direct peering exists between the spokes.

You need to design a routing solution that meets the following requirements:
1. All outbound traffic from `web-subnet` to `db-subnet` must be routed through the Azure Firewall in the hub.
2. All return traffic from `db-subnet` to `web-subnet` must also traverse the Azure Firewall.
3. Traffic between `web-subnet` and `api-subnet` within the app spoke must remain local and route directly without traversing the firewall.

Which of the following configurations should you implement to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Associate a route table with `web-subnet` and add a route for destination 10.102.0.0/1610.102.0.0/16 with a next hop type of Virtual Appliance and IP address 10.100.2.410.100.2.4.; Associate a route table with `db-subnet` and add a route for destination 10.101.1.0/2410.101.1.0/24 with a next hop type of Virtual Appliance and IP address 10.100.2.410.100.2.4.

Answer

To meet the requirements, you must associate a route table with the web subnet containing a route for the database virtual network prefix (10.102.0.0/1610.102.0.0/16) pointing to the Azure Firewall (10.100.2.410.100.2.4), and associate another route table with the database subnet containing a route for the web subnet prefix (10.101.1.0/2410.101.1.0/24) pointing to the Azure Firewall (10.100.2.410.100.2.4).
To route traffic from the web subnet to the database spoke, a route table must be associated with the web subnet that forwards traffic destined for the database address space (10.102.0.0/1610.102.0.0/16) to the Azure Firewall (10.100.2.410.100.2.4). For return traffic, a corresponding route table must be associated with the database subnet to route traffic destined for the web subnet (10.101.1.0/2410.101.1.0/24) back to the Azure Firewall. This ensures bidirectional traffic flows through the firewall without affecting other spoke-to-spoke or internal routes.

Step-by-Step Solution

1
Determine how to route traffic from the web subnet to the database subnet through the Azure Firewall.
A User-Defined Route (UDR) is needed on `web-subnet` for destination `10.102.0.0/16` with the next hop set to the virtual appliance IP `10.100.2.4`.
Since the app spoke and database spoke are only peered with the hub and not directly with each other, they rely on system routes that do not automatically route through the firewall. A UDR specifically targeting the database subnet's address space redirects this traffic to the firewall.
2
Determine how to route return traffic from the database subnet back to the web subnet through the Azure Firewall.
A UDR is needed on `db-subnet` for the specific destination `10.101.1.0/24` pointing to the next hop `10.100.2.4`.
Because the firewall is stateful, the return traffic must also traverse the firewall. Routing to the specific subnet prefix `10.101.1.0/24` ensures that only return traffic to the web tier is routed via the firewall, while traffic to other subnets is unaffected.
3
Verify that local traffic within the app spoke remains direct and local.
Ensure no UDRs are created on `web-subnet` that override the local system route (`10.101.0.0/16` -> Local) or target `10.101.2.0/24` directly.
Azure system routes prioritize the most specific route. If a UDR with `10.101.0.0/16` or `10.101.2.0/24` is associated with `web-subnet` pointing to the firewall, it overrides the default 'Virtual Network' local system routing, causing local traffic to traverse the firewall and violating the constraints.

Key Concept

User-Defined Routes (UDRs) override Azure system routes. In a hub-and-spoke topology, spoke-to-spoke traffic must be explicitly routed through a central network virtual appliance or firewall using UDRs. However, care must be taken not to override the local virtual network system route, which would disrupt direct intra-VNet communication.
Estimated Time:2m 0s
Question 45Question

A financial technology enterprise is designing a global, multi-region traffic routing and failover solution for its payment processing platform deployed in the East US 2 and West Europe regions. The solution must accommodate the following incoming traffic streams:

* Stream 1: HTTPS-based web API traffic requiring SSL termination at the network edge, path-based routing (routing `/charge` and `/refund` requests to different backend pools), and integrated Web Application Firewall (WAF) protection.
* Stream 2: A proprietary, latency-sensitive TCP-based client application communicating over port 90909090. This stream does not support HTTP encapsulation and must be routed to the closest healthy regional endpoint.

Which traffic routing configuration should you recommend to meet these requirements?

Show answer & explanation

Answer: Deploy Azure Front Door to route Stream 1, and configure Azure Traffic Manager to route Stream 2 to regional Standard Load Balancers.

Answer

Deploy Azure Front Door to route Stream 1, and configure Azure Traffic Manager to route Stream 2 to regional Standard Load Balancers.
The correct configuration uses Azure Front Door for the HTTPS-based web API traffic (Stream 1) because Front Door provides global Anycast routing, SSL offloading at the edge, path-based routing, and integrated Web Application Firewall capabilities. For the proprietary TCP-based traffic on port 90909090 (Stream 2), Azure Traffic Manager is the appropriate choice because it works at the DNS layer and is protocol-independent. Traffic Manager resolves DNS queries to the IP address of the closest healthy regional Standard Load Balancer, allowing direct TCP connections over port 90909090 without trying to proxy the traffic through an HTTP-only service.

Step-by-Step Solution

1
Analyze the protocols and routing requirements of Stream 1.
Stream 1 requires HTTPS, SSL termination, WAF, and URL-path routing. This requires a global Layer 7 load balancer.
Only Layer 7 load balancers can inspect the URI path, handle SSL offloading, and apply WAF rules.
2
Select the appropriate service for Stream 1.
Azure Front Door is selected.
Azure Front Door is a global Anycast-based Layer 7 service matching all requirements for Stream 1.
3
Analyze the protocol and routing requirements of Stream 2.
Stream 2 requires custom TCP on port 90909090 with low-latency global routing to regional endpoints.
Since the protocol is non-HTTP TCP, a Layer 7 global routing solution like Azure Front Door cannot be used.
4
Select the appropriate service for Stream 2.
Azure Traffic Manager is selected to resolve DNS requests to regional Standard Load Balancers.
Azure Traffic Manager operates at the DNS level, making it protocol-independent, allowing it to route clients to regional public IPs hosting the TCP service on port 90909090.

Key Concept

Selecting and combining global Azure load balancing services based on layer-specific capabilities (Layer 4 vs. Layer 7) and protocol limitations.
Estimated Time:2m 30s
Question 46Question

An organization is designing a disaster recovery (DR) solution from the East US region to the West US region for an inventory management system. The system consists of two Web tier VMs (each with a 100 GB100\text{ GB} Premium SSD and a write churn of 0.5 MB/s0.5\text{ MB/s}), two App tier VMs (each with a 128 GB128\text{ GB} Premium SSD and a write churn of 1.5 MB/s1.5\text{ MB/s}), and one Database tier VM running SQL Server on an Azure VM. The Database VM has one OS disk with a write churn of 2 MB/s2\text{ MB/s}, one data disk with a write churn of 8 MB/s8\text{ MB/s}, and one transaction log disk with a write churn of 26 MB/s26\text{ MB/s}. All disks on the Database VM are Premium SSDs. The organization requires a target recovery point objective (RPO) of 15 minutes15\text{ minutes} and a recovery time objective (RTO) of 2 hours2\text{ hours}. Which disaster recovery design should you recommend?

Show answer & explanation

Answer: Replicate the Web and App tier VMs using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the database to a SQL Server instance running on an Azure VM in the West US region.

Answer

Replicate the Web and App tier VMs using Azure Site Recovery, and configure SQL Server Always On Availability Groups to replicate the database to a SQL Server instance running on an Azure VM in the West US region.
The correct design uses Azure Site Recovery to replicate the Web and App tier VMs, while using SQL Server Always On Availability Groups to replicate the database. This is because the Database VM's transaction log disk has a write churn of 26 MB/s26\text{ MB/s}, which exceeds the maximum support limit of 20 MB/s20\text{ MB/s} per Premium SSD disk for Azure Site Recovery (even with the high-churn profile enabled). Utilizing SQL Server Always On Availability Groups bypasses this ASR limitation and ensures the database is replicated with minimal latency, satisfying the 15 minutes15\text{ minutes} RPO and 2 hours2\text{ hours} RTO.

Step-by-Step Solution

1
Analyze the write churn metrics for all disks in the workload.
The Web VMs have a churn of 0.5 MB/s0.5\text{ MB/s} per disk. The App VMs have a churn of 1.5 MB/s1.5\text{ MB/s} per disk. The Database VM has disk churn rates of 2 MB/s2\text{ MB/s} (OS disk), 8 MB/s8\text{ MB/s} (data disk), and 26 MB/s26\text{ MB/s} (transaction log disk). The total Database VM churn is 36 MB/s36\text{ MB/s}.
This step evaluates whether each virtual machine and its individual disks fall within the support limits of Azure Site Recovery.
2
Compare disk write churn rates against Azure Site Recovery capacity limits.
The Web and App tier VMs are within both standard and high churn limits. For the Database VM, the transaction log disk's write churn of 26 MB/s26\text{ MB/s} exceeds the maximum limit of 20 MB/s20\text{ MB/s} per Premium SSD disk supported by Azure Site Recovery (even under the high-churn capability).
This determines that the Database VM cannot be replicated using Azure Site Recovery and requires a different disaster recovery method.
3
Select a disaster recovery replication strategy for the database tier that supports high write churn and meeting the RPO/RTO.
SQL Server Always On Availability Groups running on Azure VMs in the target region support replication of database transaction logs natively and can easily handle a write churn rate of 26 MB/s26\text{ MB/s} while meeting the 15 minutes15\text{ minutes} RPO.
This completes the hybrid design by pairing Azure Site Recovery for the supported tiers with a native database availability solution for the high-churn SQL Server tier.

Key Concept

Azure Site Recovery (ASR) has strict write churn limits per disk (10 MB/s10\text{ MB/s} standard, 20 MB/s20\text{ MB/s} high churn for Premium SSD v1) and per VM. For virtual machines running database engines with write-intensive transaction logs that exceed these limits, database-native replication mechanisms (such as SQL Server Always On Availability Groups) must be used instead of ASR.
Question 47Question

A conglomerate has an on-premises Active Directory Domain Services (AD DS) forest and three Microsoft Entra ID tenants. You are designing a hybrid and multi-tenant identity solution that must satisfy constraints regarding hybrid synchronization footprints, external collaboration types, self-service governance, and multi-tenant synchronization. Match each business and technical requirement to the most appropriate Microsoft Entra ID technology.

Click a left item, then click its matching right item

Items

Sync users from an isolated on-premises forest with no direct network connectivity to the primary sync server, while supporting password hash sync for authentication continuity.
Enable users from a sister company's Entra tenant to collaborate in Microsoft Teams shared channels without generating guest user accounts.
Provide external vendors access to internal line-of-business apps using guest accounts that support identity governance access reviews.
Provision and update internal user objects across all three Microsoft Entra tenants to build a unified global address list.

Matches

Show answer & explanation

Answer

Syncing from a disconnected forest matches Microsoft Entra Connect cloud sync; collaborating in Teams shared channels without guest accounts matches Microsoft Entra B2B direct connect; providing partner access to web applications with guest management matches Microsoft Entra B2B collaboration; and automating internal sync across multiple corporate tenants matches Cross-tenant synchronization.
The correct matches map each business scenario to the precise Entra capability: cloud sync is the lightweight option for isolated forests; B2B direct connect allows direct Teams channel sharing without guest objects; B2B collaboration provides guest-based application governance; and cross-tenant sync replicates internal users across cloud tenants.

Step-by-Step Solution

1
Analyze the isolated on-premises forest sync requirement with minimal infrastructure footprint.
Identify Microsoft Entra Connect cloud sync as the optimal lightweight sync method that routes through the cloud.
Cloud sync is suited for scenarios like mergers where networks are separated and minimal local footprint is desired.
2
Evaluate Teams shared channels collaboration requirements that must avoid guest account overhead.
Identify Microsoft Entra B2B direct connect.
Direct connect is designed for real-time collaboration where users authenticate in their home directory, bypassing guest account creation entirely.
3
Examine external web application access that requires full identity lifecycle governance.
Identify Microsoft Entra B2B collaboration.
B2B collaboration creates guest accounts that are fully compatible with access reviews and typical application assignments.
4
Determine the synchronization mechanism for internal users across multiple managed Microsoft Entra tenants.
Identify Cross-tenant synchronization.
Cross-tenant synchronization enables automatic user provisioning between different Entra tenants in a multi-tenant organization.

Key Concept

Selecting hybrid and multi-tenant identity technologies based on connection, security, and lifecycle requirements.
Estimated Time:3m 0s
Question 48Question

An organization needs to collect Azure diagnostic logs for resources deployed across two distinct regulatory jurisdictions (Europe and the US). The requirements are:

1. Europe diagnostic logs must remain resident in Europe.
2. US diagnostic logs must remain resident in the US.
3. Access to the logs must be granted to the security team using the most scalable and maintainable administrative model.

Which two configurations should you include in the monitoring and governance design?

Select all that apply

Show answer & explanation

Answer: Deploy separate Log Analytics workspaces in the Europe and US regions.; Assign the Monitoring Reader role to a Microsoft Entra group containing the security team members.

Answer

To satisfy the regional data residency requirements, you must deploy separate Log Analytics workspaces in Europe and the US. To manage security permissions scaleably, you should assign the Monitoring Reader role to a Microsoft Entra ID group rather than individual users.
Deploying separate Log Analytics workspaces in the Europe and US regions ensures that diagnostic logs do not leave their respective geographical boundaries, fulfilling the regional residency requirement. Assigning the Monitoring Reader role to a Microsoft Entra group simplifies administrative management by allowing permissions to be updated through group membership rather than individual role assignments.

Step-by-Step Solution

1
Analyze data residency requirements.
Europe logs must stay in Europe; US logs must stay in the US.
This prevents cross-region data transfer, requiring regional workspaces.
2
Evaluate the governance and access model.
Assign permissions to a security group rather than individuals.
Group-based assignment reduces administrative overhead and ensures scalability.
3
Evaluate automatic diagnostic deployment strategy.
DeployIfNotExists is the correct policy effect for remediation, not Deny.
A Deny policy would block deployment rather than automatically configuring diagnostics.

Key Concept

Designing regional log routing architecture and scalable access control for Azure Monitor Log Analytics.
Estimated Time:1m 30s
Question 49Question

You are designing a monitoring and log routing solution for an enterprise Azure environment. Match each log ingestion or routing requirement to its most appropriate Azure Monitor destination or configuration component.

Click a left item, then click its matching right item

Items

Diagnostic logs of an Azure Key Vault that must be ingested into a non-Azure SIEM system in near real-time.
Platform metrics and logs of virtual machines across multiple subscriptions that need to be analyzed using Kusto Query Language (KQL).
Azure subscription Activity Logs that must be retained for 5 years to meet regulatory compliance at the lowest possible cost.
Custom application logs from on-premises servers that need to be ingested into Azure Monitor without deploying local agents on the virtual machines.

Matches

Show answer & explanation

Answer

Key Vault logs to SIEM match with Azure Event Hubs; VM platform metrics and logs match with Centralized Log Analytics Workspace; Subscription Activity Logs for 5-year retention match with Azure Storage Account; Custom agentless on-premises logs match with Data Collection Endpoint and Logs Ingestion API.
The correct pairings align each workload's technical and financial constraints to the exact Azure Monitor feature designed for that purpose: Event Hubs for real-time SIEM integration, Log Analytics for active KQL query support, Storage Accounts for low-cost archive, and the Logs Ingestion API with a Data Collection Endpoint for custom agentless data submission.

Step-by-Step Solution

1
Evaluate the real-time third-party SIEM log delivery requirement.
Identify Azure Event Hubs as the message queueing mechanism that interfaces with external security tools.
SIEM systems require a low-latency push stream, which Event Hubs provides.
2
Determine the query requirements for VM logs across multiple subscriptions.
Select a centralized Log Analytics Workspace to store and analyze logs.
KQL queries and dashboards require logs to be stored in a queryable analytics engine.
3
Assess the long-term retention requirement under strict cost-minimization constraints.
Route Activity Logs to an Azure Storage Account.
Storage accounts offer the cheapest tier of storage for compliance logs that do not need to be queried regularly.
4
Analyze the custom, agentless ingestion requirement for on-premises systems.
Utilize a Data Collection Endpoint (DCE) and the Logs Ingestion API.
This setup allows secure log ingestion over HTTPS directly from code or custom integrations without a VM agent.

Key Concept

Selecting optimal Azure Monitor routing destinations and ingestion mechanisms based on cost, latency, query, and integration constraints.
Question 50Question

Your company wants to enforce tagging standards for Azure storage accounts. You need to design an Azure Policy strategy that meets the following compliance requirements:

* If a storage account is deployed without the 'Environment' tag, the deployment must be blocked.
* If a storage account is deployed without the 'CostCenter' tag, the policy should automatically add the tag with a default value of 'Unassigned' during creation.

Which two Azure Policy effects should you recommend to meet these compliance requirements?

Select all that apply

Show answer & explanation

Answer: The Deny effect to block storage accounts without the Environment tag; The Modify effect to add the CostCenter tag with a default value during deployment

Answer

To meet the compliance requirements, you should use the Deny effect to block resource creation when the 'Environment' tag is missing, and the Modify effect to automatically add the 'CostCenter' tag with a default value during resource creation or update.
The requirement to block deployment when the 'Environment' tag is missing is met by using the Deny effect, which prevents resource creation. The requirement to automatically add the 'CostCenter' tag with a default value of 'Unassigned' during deployment is met by using the Modify effect, which can alter resource properties such as tags during creation or update.

Step-by-Step Solution

1
Analyze the requirement to prevent the deployment of storage accounts that lack the 'Environment' tag.
Determine that blocking non-compliant resource creation requires an effect that prevents execution of the resource provider request.
The Deny effect evaluates the resource request during creation or update and rejects the request if it does not match the policy parameters.
2
Analyze the requirement to automatically add the 'CostCenter' tag with a default value of 'Unassigned' during deployment if it is missing.
Determine that altering the resource properties (adding a tag) during creation or update requires an effect that modifies the request payload.
The Modify effect is the recommended way to manage tags and other properties on Azure resources automatically without blocking the deployment.

Key Concept

Azure Policy effects determine the action taken when a policy rule matches a resource. Choosing between Deny, Modify, Audit, and DeployIfNotExists depends on whether the resource must be blocked, corrected during creation, logged for compliance tracking, or remediated after deployment.
Question 51Question

FinSecure Corp has multiple subscriptions organized under a single Azure tenant. The compliance team mandates that all Azure Key Vaults must have diagnostic settings configured to route audit logs to a central Log Analytics workspace. Developer teams frequently deploy new Key Vaults using infrastructure as code (IaC) templates that often omit the diagnostic settings. The proposed governance solution must ensure that diagnostic settings are configured automatically upon vault creation, must not block developer deployments, and must minimize administrative overhead. Which of the following governance strategies should you recommend?

Show answer & explanation

Answer: Assign an Azure Policy initiative containing a policy definition with the DeployIfNotExists effect at the management group level to automatically deploy diagnostic settings for Key Vaults.

Answer

Assign an Azure Policy initiative containing a policy definition with the DeployIfNotExists effect at the management group level to automatically deploy diagnostic settings for Key Vaults.
The correct strategy uses the DeployIfNotExists policy effect assigned at the management group level. This effect checks for the existence of a child resource (in this case, diagnostic settings) when a parent resource (Key Vault) is created. If the child resource does not exist, Azure Policy deploys it using a template. This remediates the resource automatically in real-time, does not block the initial deployment, and minimizes administrative overhead through inheritance.

Step-by-Step Solution

1
Analyze the requirement to configure a dependent resource (diagnostic settings) automatically upon parent resource (Key Vault) creation.
Identify that the DeployIfNotExists policy effect is designed to deploy templates and remediate non-compliance automatically when a resource is created or updated.
This meets the primary automated configuration objective.
2
Evaluate the requirement that the solution must not block developer deployments.
Rule out Deny policies, as they prevent the creation of resources and block deployments.
Ensuring uninterrupted developer workflows is a core constraint.
3
Select the scope and policy structure that minimizes administrative overhead across multiple subscriptions.
Determine that assigning a policy initiative at the management group level ensures inheritance across all subscriptions without direct per-subscription assignment.
This establishes centralized governance at scale.

Key Concept

Azure Policy Governance
Estimated Time:1m 30s
Question 52Question

An organization is designing a monitoring and log routing architecture for application workloads deployed across two Azure regions: East US and North Europe. The solution must meet the following requirements:
- Regulatory compliance mandates that operational logs generated in North Europe must reside within the North Europe region and must not be accessible from the East US region.
- Resource owners must only be able to query logs for the specific Azure resources they own, without having access to other operational logs in the same workspace.
- Diagnostic settings for all newly created virtual machines must be configured automatically to route logs to the appropriate regional workspace.

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

Select all that apply

Show answer & explanation

Answer: Separate Log Analytics workspaces in East US and North Europe with the workspace access mode configured to require resource-context access.; An Azure Policy definition configured with the DeployIfNotExists effect to deploy diagnostic settings to new virtual machines.

Answer

Include separate Log Analytics workspaces in East US and North Europe with resource-context access configured, along with an Azure Policy definition that uses the DeployIfNotExists effect to apply diagnostic settings to new virtual machines.
The solution requires regional data residency and resource-context access. Creating separate regional workspaces (one in East US and one in North Europe) with resource-context enabled ensures compliance with data residency and allows resource-based access. Azure Policy with a DeployIfNotExists effect automatically configures VM diagnostic settings to point to the correct regional workspace upon creation.

Step-by-Step Solution

1
Address data residency and compliance requirements.
Determine that separate Log Analytics workspaces are required in East US and North Europe to ensure European logs remain in North Europe.
Regulatory compliance requires that logs do not leave their respective regions.
2
Select the appropriate workspace access mode to enforce granular access controls.
Configure resource-context access mode on the workspaces.
This allows resource owners to view logs for only their resources, rather than giving them workspace-wide access.
3
Automate the deployment of diagnostic settings.
Implement an Azure Policy definition using the DeployIfNotExists effect targeting virtual machines.
The DeployIfNotExists effect automatically applies diagnostic settings to new resources upon deployment, whereas the Deny effect would block creation instead of performing auto-configuration.

Key Concept

Designing compliant, secure, and automated log routing architectures using regional Log Analytics workspaces, resource-context access control, and Azure Policy remediation.
Question 53Question

VoltGrid Power operates a multi-region grid telemetry network in Azure. The resource hierarchy consists of a root management group named VoltGrid-Root, which contains two child management groups: VoltGrid-Americas and VoltGrid-Eurasia. Under VoltGrid-Americas, you have two subscriptions: Telemetry-Prod-Sub and Grid-Dev-Sub.

You need to design a governance strategy to enforce the following compliance requirements:
1. All Azure Virtual Machines deployed to Telemetry-Prod-Sub must have the Azure Monitor Agent (AMA) installed automatically upon deployment.
2. All Azure SQL Databases deployed within the VoltGrid-Americas management group must be blocked from creation if transparent data encryption (TDE) is not configured to use a customer-managed key (CMK).
3. The SQL Database TDE restriction must not apply to resources in a development resource group named Sandbox-RG located inside Grid-Dev-Sub.

The solution must minimize administrative overhead and avoid manual remediation processes.

Which two configurations should you include in your Azure Policy design?

Select all that apply

Show answer & explanation

Answer: Assign a policy definition with the DeployIfNotExists effect to Telemetry-Prod-Sub to deploy the Azure Monitor Agent extension.; Assign a policy definition with the Deny effect to VoltGrid-Americas to restrict SQL Database TDE configuration, and configure the assignment's notScopes property to exclude Sandbox-RG.

Answer

Assign a policy definition with the DeployIfNotExists effect to Telemetry-Prod-Sub to deploy the Azure Monitor Agent, and assign a policy definition with the Deny effect to VoltGrid-Americas to restrict SQL Database TDE configuration while configuring the assignment's notScopes property to exclude Sandbox-RG.
To meet the compliance requirements with the least administrative effort, you should use the DeployIfNotExists effect to install the Azure Monitor Agent automatically on virtual machines. To block non-compliant databases across the entire Americas branch, the Deny policy must be applied at the VoltGrid-Americas management group scope. To exclude the specific development resources in Sandbox-RG from this block, you should use the notScopes (exclusion) property on the policy assignment. This keeps administrative overhead low and ensures that the policy rules are not evaluated within the sandbox scope.

Step-by-Step Solution

1
Analyze the automatic agent installation requirement.
Identify DeployIfNotExists as the correct effect for enforcing compliance by automatically deploying missing extensions.
DeployIfNotExists allows Azure Policy to deploy the Azure Monitor Agent extension dynamically if a Virtual Machine is created or updated without it, eliminating manual remediation.
2
Analyze the blocking requirement for SQL Databases without customer-managed keys.
Select the Deny effect at the VoltGrid-Americas management group scope.
The Deny effect prevents the creation of resources that do not match the specified compliance criteria, ensuring strict compliance across all child subscriptions.
3
Determine the optimal configuration for exempting the sandbox resource group.
Apply the notScopes property to the Deny policy assignment for Sandbox-RG.
The notScopes property prevents the policy from evaluating resources inside the specified resource group, allowing development resources to bypass the restrictions without modifying policy logic or affecting other subscriptions.

Key Concept

Azure Policy effects and assignment scope exclusions
Question 54Question

Zephyr Health designs its Azure environment using a management group hierarchy. Under the root management group, a production management group named Zephyr-Prod contains multiple subscriptions, including Prod-App1. A security requirement states that all Azure Virtual Machines deployed to subscriptions under Zephyr-Prod must be automatically configured to back up to a Recovery Services vault. If a virtual machine is deployed without backup, it must be automatically remediated by deploying the required backup extension. However, virtual machines deployed in a specific resource group named In-Memory-DB-RG within Prod-App1 must be exempted from this backup requirement due to performance and latency constraints. Which Azure Policy strategy should you recommend to meet these compliance requirements while minimizing administrative overhead?

Show answer & explanation

Answer: Assign an Azure Policy Initiative containing a DeployIfNotExists policy for Azure Backup at the Zephyr-Prod management group scope, and add the resource ID of the In-Memory-DB-RG resource group to the notScopes property of the policy assignment.

Answer

Assign an Azure Policy Initiative containing a DeployIfNotExists policy for Azure Backup at the Zephyr-Prod management group scope, and add the resource ID of the In-Memory-DB-RG resource group to the notScopes property of the policy assignment.
The correct strategy uses the DeployIfNotExists effect, which checks for the existence of a nested resource (the backup configuration/extension) and deploys it if missing, ensuring automatic remediation. Assigning this at the management group level applies it globally to child subscriptions, and using the notScopes property on the assignment successfully exempts the latency-sensitive database resource group with minimal administration.

Step-by-Step Solution

1
Determine the correct policy effect for deploying dependent resources.
DeployIfNotExists is selected.
Deploying a backup extension and association to configure a VM for backup requires deploying nested resources, which is the primary purpose of the DeployIfNotExists (DINE) effect.
2
Determine the optimal assignment scope to enforce compliance with minimal overhead.
Zephyr-Prod management group scope is selected.
Assigning the policy at the management group level ensures that all existing and future subscriptions underneath automatically inherit the policy, avoiding repetitive subscription-level assignments.
3
Determine the mechanism to exempt the specific resource group.
Use the notScopes (exclusion) property on the policy assignment.
The notScopes property prevents the policy from being evaluated or enforced on specific resource groups, subscriptions, or resources within the assigned scope, satisfying the exemption requirement with zero additional policy definitions.

Key Concept

Azure Policy effects and assignment scope exclusions
Estimated Time:2m 0s
Question 55Question

An enterprise manages its Azure resources using a Management Group hierarchy consisting of a Root Management Group, under which sit a Production Management Group (containing production subscriptions) and a Non-Production Management Group (containing Dev and Test subscriptions).

You need to design a governance strategy using Azure Policy to meet the following requirements:
1. All virtual networks deployed within the Production Management Group must have Azure Network Watcher flow logs enabled and configured to send data to a central Log Analytics workspace. Non-compliant virtual networks must be automatically remediated during deployment without blocking the resource creation.
2. Virtual machines of the G-series must be blocked from deployment within the Test subscription to control costs. However, developers must be allowed to deploy these virtual machines within a specific resource group named PerfTesting-RG inside the Test subscription.
3. Administrative overhead for managing policy assignments and compliance must be minimized.

Which policy design should you recommend?

Show answer & explanation

Answer: Assign a policy definition using the DeployIfNotExists effect to the Production Management Group to configure Network Watcher flow logs. Assign a policy definition using the Deny effect to the Test subscription to restrict G-series virtual machines, and add the PerfTesting-RG resource group to the exclusion scope (notScopes) of this assignment.

Answer

Assign a policy definition using the DeployIfNotExists effect to the Production Management Group to configure Network Watcher flow logs. Assign a policy definition using the Deny effect to the Test subscription to restrict G-series virtual machines, and add the PerfTesting-RG resource group to the exclusion scope (notScopes) of this assignment.
The correct design uses the DeployIfNotExists effect at the Production Management Group level to automatically and natively remediate non-compliant virtual networks by deploying Network Watcher flow logs without blocking deployment. To restrict G-series virtual machines, a Deny policy is assigned directly to the Test subscription. Adding the performance testing resource group to the notScopes property of the assignment excludes it from evaluation permanently, which is cleaner and carries less administrative overhead than managing separate policy assignments or using formal Policy Exemptions, which are typically designed for temporary exceptions.

Step-by-Step Solution

1
Select the policy effect for Network Watcher flow logs.
DeployIfNotExists effect is chosen.
The requirement states that non-compliant resources must be automatically remediated during deployment without blocking resource creation. DeployIfNotExists evaluates the resource and deploys a template to remediate it if it does not exist.
2
Select the policy effect for VM size restrictions.
Deny effect is chosen.
The requirement states that G-series virtual machines must be blocked from deployment. The Deny effect prevents resource creation if it matches the policy rule.
3
Determine the assignment scope and exclusion mechanism for the VM restriction.
Assign to the Test subscription and exclude the PerfTesting-RG resource group using the notScopes property.
Using the notScopes property during assignment prevents the policy from evaluating resources in the designated resource group, minimizing administrative overhead compared to setting up individual Policy Exemptions or separate assignments.
4
Determine the assignment scope for the flow logs policy.
Assign directly to the Production Management Group.
Targeting the assignment directly to the Production Management Group ensures the policy only applies where needed, eliminating the need to manage exemptions for the Non-Production Management Group.

Key Concept

Azure Policy effects (DeployIfNotExists, Deny) and assignment scopes including exclusions (notScopes) to enforce compliance with minimal administrative overhead.
Question 56Question

An enterprise operates a web application deployed in both the East US and North Europe regions. European Union (EU) data sovereignty regulations mandate that all monitoring logs containing EU user activity must remain physically within Europe and be accessible only by European administrators. US operations logs have no such restrictions. You need to design an Azure Monitor log routing solution that complies with these regulations while adhering to Microsoft security and administrative best practices. Which design should you recommend?

Show answer & explanation

Answer: Deploy a Log Analytics workspace in North Europe and a separate Log Analytics workspace in East US. Configure diagnostic settings on regional resources to route logs to their respective regional workspaces, and grant workspace access to EU administrators via Microsoft Entra groups.

Answer

Deploy a Log Analytics workspace in North Europe and a separate Log Analytics workspace in East US. Configure diagnostic settings on regional resources to route logs to their respective regional workspaces, and grant workspace access to EU administrators via Microsoft Entra groups.
The correct design utilizes regional Log Analytics workspaces to satisfy regional data residency requirements for EU data sovereignty. Access is granted through Microsoft Entra groups rather than individual user accounts to adhere to RBAC scalability and security best practices.

Step-by-Step Solution

1
Analyze compliance and data sovereignty requirements.
EU logs must reside in Europe, which requires deploying a separate Log Analytics workspace in the North Europe region.
Data sovereignty mandates local data residency; centralized workspaces across regional boundaries are not compliant in this scenario.
2
Evaluate identity and access management requirements.
EU administrators should access the EU workspace using Microsoft Entra security groups.
Directly assigning roles to user accounts increases administrative overhead and violates standard identity governance practices.
3
Determine the correct Azure Policy configuration for compliance enforcement.
Use DeployIfNotExists or Modify policies instead of Deny policies if automatic remediation of diagnostic settings is needed.
Deny policy effects block non-compliant deployments rather than automatically configuring log routing settings.

Key Concept

Designing regional and compliant log routing architectures using Azure Monitor, Log Analytics workspaces, and Microsoft Entra RBAC best practices.
Question 57Question

Contoso Pharmaceuticals has an on-premises Active Directory Domain Services (AD DS) environment and multiple Microsoft Entra ID tenants. The company needs to design a hybrid and multi-tenant identity solution to satisfy various connectivity, security, and partnership requirements. Match each operational requirement to the most appropriate Microsoft Entra ID synchronization or collaboration feature.

Click a left item, then click its matching right item

Items

Synchronize user accounts from on-premises AD DS to Azure and allow sign-in even during local network outages, without using federation.
Validate user passwords against on-premises AD DS in real-time using lightweight local agents, ensuring passwords are never stored in the cloud in any form.
Automate the provisioning and lifecycle management of user accounts across multiple distinct Microsoft Entra ID tenants owned by the same parent organization.
Enable external contractors to authenticate using their existing corporate or consumer identity provider to access shared corporate resources.

Matches

Show answer & explanation

Answer

Password Hash Synchronization (PHS) matches the requirement to allow sign-in during local network outages without federation. Pass-through Authentication (PTA) matches the requirement to validate passwords against on-premises AD DS in real-time. Cross-tenant synchronization matches the requirement to automate user account management across distinct Microsoft Entra ID tenants. Microsoft Entra B2B collaboration matches the requirement to enable external contractors to authenticate using their existing identity providers.
The correct association maps each business requirement to its specific technical implementation. Password Hash Synchronization supports cloud-based authentication during local link failures. Pass-through Authentication ensures zero-cloud credential footprint by executing validation on-premises in real-time. Cross-tenant synchronization facilitates identity management across different corporate tenants. B2B collaboration enables external users to access internal resources using their native credentials.

Step-by-Step Solution

1
Analyze the requirement for local network outage resilience without federation.
Identify Password Hash Synchronization (PHS) as the feature that keeps credentials in the cloud and allows local outages to not affect cloud logins.
Cloud-only verification is resistant to on-premises link failures.
2
Analyze the requirement for real-time validation without storing password hashes in the cloud.
Identify Pass-through Authentication (PTA) as the feature using local agents for real-time check without cloud storage.
PTA routes the request to local domain controllers.
3
Analyze the requirement for automated provisioning across multiple internal Entra tenants.
Identify Cross-tenant synchronization as the service that automates lifecycle management of internal multi-tenant users.
Cross-tenant synchronization provides automated CRUD operations across tenants.
4
Analyze the requirement for external contractor access using their own identity provider.
Identify Microsoft Entra B2B collaboration as the mechanism for external partner access.
B2B collaboration relies on external identity providers to validate user identity.

Key Concept

Selecting appropriate synchronization and collaboration technologies based on organizational requirements, security constraints, and network topology.
Question 58Question

Your organization is designing a security strategy for a Microsoft Entra ID tenant. You plan to deploy a Conditional Access policy that requires Multi-Factor Authentication (MFA) for all users assigned directory role administrator privileges. To prevent administrative lockout during a service outage or configuration error, which design decision should you implement?

Show answer & explanation

Answer: Exclude a dedicated emergency access account from the Conditional Access policy.

Answer

Exclude a dedicated emergency access account from the Conditional Access policy.
Excluding a dedicated emergency access (break-glass) account from the Conditional Access policy allows administrators to regain access to the Entra ID tenant to disable or adjust policies if a service outage or misconfiguration prevents standard authentication.

Step-by-Step Solution

1
Identify the primary risk of enforcing tenant-wide administrator MFA.
The main risk is administrative lockout if the MFA service is offline or if a policy is misconfigured.
Administrators would have no way to log in and disable the faulty policy.
2
Determine the Microsoft best practice for preventing administrative lockout.
Create a dedicated emergency access (break-glass) account that is excluded from MFA policies.
This account acts as a fallback to restore access and adjust policies in emergencies.
3
Select the option that aligns with the exclusion requirement.
Excluding a dedicated emergency access account from the Conditional Access policy.
It fulfills the requirement to prevent lockout while keeping standard administrator accounts secured under MFA.

Key Concept

Excluding emergency access (break-glass) accounts from Conditional Access policies is critical to prevent complete administrative lockout in Microsoft Entra ID.
Question 59Question

Aetherius Logistics has an on-premises Active Directory Domain Services (AD DS) domain. The company is designing a hybrid identity solution using a single Microsoft Entra ID tenant. The solution must meet the following requirements:
- Users must be able to sign in to cloud resources using their on-premises credentials.
- If the network connection between the on-premises datacenter and Azure is temporarily lost, users must still be able to authenticate to cloud resources.
- Users must be able to reset their passwords using Microsoft Entra Self-Service Password Reset (SSPR), and the changes must immediately update on-premises AD DS.
- On-premises infrastructure footprint and management overhead must be minimized.

Which hybrid identity synchronization and authentication solution should you recommend?

Show answer & explanation

Answer: Microsoft Entra Connect sync using Password Hash Synchronization (PHS) with Password Writeback enabled

Answer

Microsoft Entra Connect sync using Password Hash Synchronization (PHS) with Password Writeback enabled
The correct option is Password Hash Synchronization (PHS) with Password Writeback enabled because PHS copies the password hashes to Microsoft Entra ID, allowing authentication to occur entirely in the cloud, which ensures business continuity during on-premises network outages. Password Writeback ensures that SSPR updates are written back to on-premises Active Directory, and PHS has the lowest infrastructure overhead among hybrid identity options.

Step-by-Step Solution

1
Analyze the business continuity requirement.
Since users must authenticate even during an on-premises network outage, authentication must occur directly in the cloud. This rules out Pass-through Authentication (PTA) and Active Directory Federation Services (AD FS) without complex, highly available configurations.
PTA and AD FS rely on on-premises resources to validate credentials in real time.
2
Analyze the self-service capability requirement.
Users must reset passwords in Microsoft Entra ID and have them update on-premises AD DS. This requires enabling Password Writeback, which is a feature of Microsoft Entra Connect sync.
Password Writeback synchronizes password changes from cloud to on-premises in real-time.
3
Select the correct combination that minimizes on-premises infrastructure.
Password Hash Synchronization (PHS) with Password Writeback meets all constraints with minimal local footprint compared to AD FS.
PHS utilizes the Microsoft Entra Connect sync agent without requiring additional dedicated authentication servers.

Key Concept

Selecting the appropriate hybrid identity authentication method to ensure business continuity and minimize infrastructure overhead
Question 60Question

An enterprise has Azure resources deployed in the East US and West Europe regions. To meet regulatory requirements, resource diagnostic logs from West Europe must remain within the European Union (EU) borders, while logs from East US must reside within the United States. Regional administrators must be able to query logs for their respective regions only, while a global security audit team requires access to all logs across both regions. You need to design the Azure Monitor log architecture to support this configuration with minimum administrative overhead. Which two configurations should you include in the design?

Select all that apply

Show answer & explanation

Answer: Create one Log Analytics workspace in the East US region and a second Log Analytics workspace in the West Europe region.; Assign the regional administrators to region-specific Microsoft Entra groups, and assign those groups the Log Analytics Reader role on the respective regional workspace.

Answer

To meet the requirements, create regional Log Analytics workspaces in East US and West Europe, and manage permissions using regional Microsoft Entra groups assigned to the Log Analytics Reader role on their respective workspaces.
To comply with data residency regulations, diagnostic logs must be stored in the respective region of origin. Thus, separate workspaces in East US and West Europe are required. Additionally, to minimize administrative overhead and follow security best practices, access management should use Microsoft Entra groups rather than direct role assignments to individual user accounts.

Step-by-Step Solution

1
Determine the required number and locations of Log Analytics workspaces based on data residency.
Two workspaces are required: one in East US and one in West Europe to ensure EU logs do not leave the EU boundary.
Log Analytics workspace data residency is bound to the region where the workspace itself is deployed.
2
Determine the access model and delegation mechanism for the regional administrators.
Create Microsoft Entra groups for each region and assign the Log Analytics Reader role at the workspace scope.
Group-based RBAC assignments are recommended to minimize administrative overhead compared to individual user assignments.
3
Evaluate compliance automation alternatives for diagnostic settings deployment.
Avoid Deny policies for automatic deployment; instead, prepare DeployIfNotExists policies.
Deny blocks deployments but does not perform remediation or configuration actions.

Key Concept

Designing compliant, regional Azure Monitor Log Analytics workspace architectures and secure access controls using group-based RBAC.
PreviousPage 3 / 60Next
All practice questions — Microsoft Azure Solutions Architect (AZ-305) | Examkin