All practice questions

1198 questions

Question 601Question

Meridian Global Logistics is designing an identity security strategy for its hybrid cloud environment. The organization synchronizes its on-premises Active Directory Domain Services (AD DS) directory to Microsoft Entra ID using Password Hash Synchronization (PHS). You need to design an access control solution that meets the following security requirements:
- Enforce Multi-Factor Authentication (MFA) for administrative access to the Azure management portal.
- Ensure that administrators only assume privileged roles when performing administrative tasks, rather than having persistent access.
- Guarantee that emergency access (break-glass) accounts remain functional to prevent tenant lockout during an MFA system outage.

Which of the following designs should you recommend?

Show answer & explanation

Answer: Configure Microsoft Entra Privileged Identity Management (PIM) with eligible assignments for administrative roles, enforce Multi-Factor Authentication (MFA) via a Conditional Access policy targeting administrative apps, and exclude emergency access accounts from the policy.

Answer

Configure Microsoft Entra Privileged Identity Management (PIM) with eligible assignments for administrative roles, enforce Multi-Factor Authentication (MFA) via a Conditional Access policy targeting administrative apps, and exclude emergency access accounts from the policy.
The correct design ensures that administrative roles are non-persistent by configuring them as eligible in Microsoft Entra Privileged Identity Management (PIM). It enforces MFA for administrative access using a Conditional Access policy, while excluding break-glass accounts from this policy to prevent administrative lockout during MFA system outages.

Step-by-Step Solution

1
Select Microsoft Entra Privileged Identity Management (PIM) to control administrative role elevation.
Using eligible role assignments ensures that administrative access is just-in-time (JIT) rather than permanent, meeting the requirement for non-persistent access.
This enforces the principle of least privilege and prevents administrators from constantly holding elevated rights.
2
Enforce Multi-Factor Authentication (MFA) via Conditional Access targeting the Microsoft Azure Management cloud app.
All administrative access to the Azure portal requires MFA.
This secures administrative interfaces against credential compromise.
3
Exclude emergency access (break-glass) accounts from the Conditional Access policy.
Emergency access accounts can authenticate without triggering MFA requirements.
This guarantees that administrators can still access the tenant in the event of an MFA service outage.

Key Concept

Microsoft Entra ID Authentication and Conditional Access
Question 602Question

A regional healthcare provider is designing an identity and access management solution for its IT operations team, which manages Azure resources. The solution must meet the following requirements:
- Manage permissions at scale without administrative overhead when members join or leave the team.
- Ensure that administrators do not have persistent access to high-privilege roles, requiring them to request access only when performing active maintenance.
- Maintain a break-glass emergency access account that is guaranteed access to the tenant even during a Microsoft Entra ID authentication outage.

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

Select all that apply

Show answer & explanation

Answer: Create a Microsoft Entra ID security group for the administrators and make this group eligible for Azure RBAC roles within Microsoft Entra Privileged Identity Management (PIM).; Exclude the emergency access (break-glass) accounts from Microsoft Entra Conditional Access policies that enforce Multi-Factor Authentication (MFA).

Answer

Create a Microsoft Entra ID security group for the administrators and make this group eligible for Azure RBAC roles within Microsoft Entra Privileged Identity Management (PIM), and exclude the emergency access (break-glass) accounts from Microsoft Entra Conditional Access policies that enforce Multi-Factor Authentication (MFA).
To design a secure, scalable governance structure, assigning Azure RBAC roles to Microsoft Entra security groups reduces administration because roles are automatically inherited as members join or leave the group. Configuring these groups as eligible in Microsoft Entra Privileged Identity Management (PIM) enforces just-in-time (JIT) access, which minimizes persistent privileged access. Additionally, excluding emergency access accounts from Conditional Access policies that enforce Multi-Factor Authentication (MFA) prevents administrative lockout during a system outage.

Step-by-Step Solution

1
Evaluate the requirement for managing permissions at scale without administrative overhead when members change.
Determine that group-based role assignment is required instead of individual user assignments.
Group-based role assignments allow administrative changes to occur by updating group membership rather than updating individual role assignments.
2
Evaluate the requirement to prevent persistent high-privilege access and enforce request-based access.
Determine that Microsoft Entra Privileged Identity Management (PIM) with eligible assignments is required.
PIM eligible assignments allow administrators to activate roles only when performing maintenance, ensuring just-in-time access.
3
Evaluate the requirement to protect emergency access accounts from identity service outages.
Determine that these accounts must be excluded from Conditional Access policies that require Multi-Factor Authentication.
Excluding break-glass accounts ensures access to the Azure portal even if MFA services are unavailable.

Key Concept

Microsoft Entra ID Privileged Identity Management (PIM) eligibility and Conditional Access exclusion policies for emergency access accounts.
Question 603Question

You are designing a backup solution for a pool of Azure Virtual Machines hosting a business application. The solution must meet the following requirements:
- Retain daily backups for 3030 days.
- Retain weekly backups for 33 years and store them in the most cost-effective storage tier available.
- Ensure backup data is resilient against a zone outage within the primary region.

Which two configurations should you include in the backup design?

Select all that apply

Show answer & explanation

Answer: A Recovery Services vault configured with zone-redundant storage (ZRS) redundancy; An Enhanced backup policy with a tiering rule to move weekly recovery points to the Vault-archive tier

Answer

Configure a Recovery Services vault with zone-redundant storage (ZRS) redundancy and implement an Enhanced backup policy with a tiering rule to move weekly recovery points to the Vault-archive tier.
To satisfy the resiliency requirement against zone-level failures, the Recovery Services vault must use zone-redundant storage (ZRS). To store the weekly backups cost-effectively for 3 years, the solution must use an Enhanced backup policy that supports tiering the recovery points to the Vault-archive tier, which offers the lowest storage cost for long-term archival data.

Step-by-Step Solution

1
Select the appropriate storage redundancy for the backup vault to survive a zone outage.
Configure the Recovery Services vault with zone-redundant storage (ZRS).
ZRS replicates the backup data synchronously across three availability zones, ensuring data access even if a zone outage occurs.
2
Select the backup policy type and long-term retention storage strategy.
Deploy an Enhanced backup policy with a tiering rule pointing to the Vault-archive tier.
Only Enhanced backup policies support tiering weekly recovery points to the Vault-archive tier, which drastically reduces storage costs for the required 3-year retention period.

Key Concept

Designing resilient and cost-optimized Azure Virtual Machine backup solutions using vault redundancy tiers and Enhanced backup policy archiving rules.
Question 604Question

VeloStyle Retail is designing a disaster recovery and business continuity solution for its product catalog images, which are stored in a general-purpose v2 Azure Storage account in the East US region.

The solution must meet the following requirements:
- During a primary region outage, the application must maintain read access to the images from the secondary region (West US) with a Recovery Time Objective (RTO) of zero.
- The application must support writing new images once a failover to the secondary region is initiated.
- Regional resilience must be maximized, while keeping replication costs minimized compared to multi-zone cross-region setups.

Which two actions should you include in the design to meet these requirements? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Configure the storage account replication to Read-access geo-redundant storage (RA-GRS).; Initiate a customer-managed failover of the storage account to the West US region to restore write capability during a primary region outage.

Answer

Configure the storage account replication to Read-access geo-redundant storage (RA-GRS) and initiate a customer-managed failover of the storage account to the West US region to restore write capability during a primary region outage.
The correct options are configuring the replication to Read-access geo-redundant storage (RA-GRS) and initiating a customer-managed failover to the secondary region during an outage. RA-GRS provides a secondary read-only endpoint that is always accessible, ensuring a read RTO of zero. To restore write functionality, a customer-managed failover is required to swap the primary and secondary regions, making the secondary region the new primary region with write support.

Step-by-Step Solution

1
Select a geo-redundant storage replication tier that supports read access to the secondary region without a failover.
Read-access geo-redundant storage (RA-GRS) is selected as it meets the RTO of zero for reads and is more cost-effective than zone-redundant storage tiers.
Standard GRS does not allow read access to the secondary endpoint until a failover is initiated, which would fail the RTO=0 read requirement.
2
Determine the mechanism for restoring write access during a primary region outage.
Initiate a customer-managed failover of the storage account.
Under RA-GRS, the secondary endpoint is read-only. A failover must be initiated to promote the secondary region to primary, which enables write access.

Key Concept

Azure Storage replication failover behavior and secondary endpoint access controls.
Question 605Question

An architect is designing a virtual network topology in Azure to support a hybrid cloud environment. The design includes a hub virtual network named `vnet-prod-hub` and a spoke virtual network named `vnet-prod-spoke`. The hub virtual network contains a virtual network gateway that connects to the company's on-premises office. A virtual network peering connection is established between `vnet-prod-hub` and `vnet-prod-spoke`. You need to ensure that virtual machines in `vnet-prod-spoke` can route their traffic to the on-premises office by using the virtual network gateway in `vnet-prod-hub`. What peering setting should you enable on the virtual network peering configuration in `vnet-prod-spoke`?

Show answer & explanation

Answer: Enable 'Use the remote virtual network's gateway' on the peering configuration from the spoke to the hub.

Answer

Enable 'Use the remote virtual network's gateway' on the peering configuration from the spoke to the hub.
To allow resources in a spoke virtual network to use a gateway in a peered hub virtual network, you must enable the 'Use the remote virtual network's gateway' setting on the spoke virtual network's peering configuration. This configures the system routes in the spoke to route traffic destined for on-premises networks through the hub gateway.

Step-by-Step Solution

1
Identify the location of the virtual network gateway.
The gateway is in the hub virtual network (vnet-prod-hub).
This determines which virtual network acts as the transit network for hybrid connectivity.
2
Configure gateway transit on the hub virtual network's peering.
The hub peering configuration must allow gateway transit (Use this virtual network's gateway).
This allows the hub virtual network to share its gateway with peered spoke networks.
3
Configure the spoke virtual network's peering settings.
Enable 'Use the remote virtual network's gateway' on the peering configuration from vnet-prod-spoke to vnet-prod-hub.
This allows the virtual machines in the spoke virtual network to route transit traffic through the gateway in the peered hub virtual network.

Key Concept

Virtual network peering gateway transit allows peered virtual networks to share a gateway for hybrid connectivity, removing the need to deploy gateways in every spoke.
Estimated Time:1m 0s
Question 606Question

Your company has virtual machines deployed in an Azure Virtual Network subnet. The virtual machines must be allowed to retrieve secrets from Azure Key Vault and access files stored in Azure storage accounts. You need to configure a Network Security Group (NSG) to permit this outbound traffic. The design must minimize administrative overhead and avoid the configuration of individual IP addresses. Which two service tags should you include in the outbound security rules of the NSG?

Select all that apply

Show answer & explanation

Answer: AzureKeyVault; Storage

Answer

The correct service tags are AzureKeyVault and Storage.
The service tags AzureKeyVault and Storage are the official, built-in tags provided by Microsoft to represent all IP address prefixes for Azure Key Vault and Azure Storage, respectively. Implementing these tags in the NSG rules allows outbound access to these services without requiring manual configuration or maintenance of individual IP ranges.

Step-by-Step Solution

1
Identify the target Azure services requiring outbound network access from the subnet.
The services are Azure Key Vault and Azure Storage.
Outbound security rules must allow access to these specific services.
2
Evaluate the requirement to minimize administrative overhead and avoid individual IP addresses.
Determine that built-in Azure service tags must be used instead of manually maintaining IP lists.
Service tags automatically manage the IP address prefixes for Azure services, reducing administrative work.
3
Identify the exact names of the service tags for Azure Key Vault and Azure Storage.
The service tag for Azure Key Vault is AzureKeyVault, and the service tag for Azure Storage is Storage.
Using the exact service tag names ensures the NSG rules are valid and function correctly.

Key Concept

Azure Virtual Network service tags simplify network security group (NSG) configuration by representing a group of IP address prefixes from a specific Azure service.
Question 607Question

An architect is evaluating Azure compute options for a web API. The solution must satisfy the following requirements:

- Process incoming HTTP requests that trigger complex calculations lasting up to 1515 minutes.
- Establish secure outbound communication to a backend database via a Private Endpoint inside an Azure Virtual Network (VNet).
- Automatically scale down to zero instances during idle periods to eliminate compute charges.
- Minimize administrative and infrastructure management overhead.

Which hosting option should the architect recommend?

Show answer & explanation

Answer: Azure Functions on a Flex Consumption plan

Answer

Azure Functions on a Flex Consumption plan
The hosting option specifying Azure Functions on a Flex Consumption plan is correct. This hosting plan natively supports outbound Virtual Network integration, allowing secure communication to the database private endpoint. It scales to zero instances during inactivity, resulting in zero compute charges, and supports HTTP execution timeouts of up to 330330 minutes, satisfying the 1515-minute requirement.

Step-by-Step Solution

1
Evaluate the execution duration requirement against the candidate hosting options.
The Consumption plan is eliminated due to its 1010-minute execution timeout. Azure Container Apps is eliminated because its HTTP ingress enforces a hard 120120-second timeout limit for direct HTTP requests.
Architectural constraints require support for 1515-minute request durations, which exceeds the limit of these plans.
2
Evaluate network security and cost requirements.
The Elastic Premium plan is eliminated because it requires at least one pre-warmed instance, violating the requirement of scaling down to zero compute charges during idle periods.
The solution must support outbound Virtual Network integration to connect to a private endpoint and scale to zero compute charges.
3
Verify Flex Consumption plan capabilities against all requirements.
Flex Consumption supports outbound Virtual Network integration via subnet delegation, scales to zero instances (incurring zero cost when idle), and has a maximum execution timeout of 330330 minutes (exceeding the 1515-minute requirement).
Flex Consumption combines the network integration of premium hosting plans with the scale-to-zero billing of consumption hosting plans.

Key Concept

Selecting the appropriate Azure compute and hosting plan based on execution limits, virtual network integration, and scale-to-zero cost requirements.
Question 608Question

A company is designing a storage solution using a General Purpose v2 storage account to store block blobs containing media files for a web application in the East US region. The storage solution must meet the following requirements:

* Provide resilience against the outage of a single datacenter zone within the primary region.
* Provide regional disaster recovery by replicating the data to a secondary region.
* Minimize costs by avoiding charges for read access to the secondary region, which is not required.

Which redundancy option should you select for the storage account?

Show answer & explanation

Answer: Geo-zone-redundant storage (GZRS)

Answer

Geo-zone-redundant storage (GZRS)
Geo-zone-redundant storage (GZRS) is correct because it combines the zone-level redundancy of ZRS in the primary region with the regional replication of GRS. It copies data across three availability zones in the primary region, safeguarding against zone failures, and replicates it asynchronously to a secondary region for disaster recovery, all without paying the extra premium for read-access to the secondary region.

Step-by-Step Solution

1
Analyze the primary region availability requirement.
The solution must survive a zone failure in the primary region, which requires a zone-redundant option (ZRS or GZRS) rather than a locally-redundant option (LRS or GRS).
LRS and GRS store data within a single availability zone in the primary region, making them vulnerable to zone outages.
2
Analyze the regional disaster recovery requirement.
The solution must replicate data to a secondary region, which requires a geo-redundant option (GZRS) rather than a zone-only option (ZRS).
ZRS does not replicate data outside the primary region.
3
Evaluate read-access requirements and cost constraints.
Since read access to the secondary region is not required, choosing GZRS instead of RA-GZRS minimizes cost.
RA-GZRS incurs additional charges for providing read access to the secondary replica.

Key Concept

Selecting the optimal Azure storage redundancy tier based on zonal availability, regional disaster recovery, and cost constraints.
Question 609Question

An organization hosts a critical financial web application in the Canada Central region. The application architecture consists of the following components:

- Two web server virtual machines (`Web-VM1` and `Web-VM2`), each containing a single 127 GB127\text{ GB} Standard SSD disk with a write churn of 1.5 MB/s1.5\text{ MB/s} per disk.
- One database virtual machine (`DB-VM1`) running Microsoft SQL Server with a total VM write churn of 50 MB/s50\text{ MB/s}. The virtual machine has three disks: an OS disk (Standard SSD, 2 MB/s2\text{ MB/s} write churn), a database data disk (Premium SSD v1, 14 MB/s14\text{ MB/s} write churn), and a transaction log disk (Premium SSD v1, 34 MB/s34\text{ MB/s} write churn).

The organization is designing a disaster recovery (DR) solution to the Canada East region. The design must meet the following objectives:

- A recovery time objective (RTO) of 2 hours2\text{ hours} for the entire application.
- A recovery point objective (RPO) of 4 hours4\text{ hours} for the web servers.
- A recovery point objective (RPO) of 10 seconds10\text{ seconds} for the database server.

Which disaster recovery strategy should you recommend?

Show answer & explanation

Answer: Configure Azure Site Recovery to replicate the web server virtual machines to the Canada East region. Deploy a secondary SQL Server virtual machine in the Canada East region and configure asynchronous SQL Server Always On Availability Groups to replicate the database.

Answer

Configure Azure Site Recovery to replicate the web server virtual machines to the Canada East region. Deploy a secondary SQL Server virtual machine in the Canada East region and configure asynchronous SQL Server Always On Availability Groups to replicate the database.
The correct strategy replicates the web servers using Azure Site Recovery and utilizes SQL Server native replication (Always On Availability Groups) for the database. This is necessary because the transaction log disk's write churn of 34 MB/s34\text{ MB/s} exceeds the limits of Azure Site Recovery (which tops out at 30 MB/s30\text{ MB/s} per Premium SSD v1 disk even under the high-churn policy). Furthermore, Azure Site Recovery generates crash-consistent recovery points at a minimum interval of 5 minutes5\text{ minutes}, which cannot satisfy the strict 10 second10\text{ second} RPO requirement. Deploying native database replication resolves both the churn threshold constraint and the low RPO objective.

Step-by-Step Solution

1
Analyze the database disk write churn and total VM write churn against Azure Site Recovery limits.
The database transaction log disk write churn of 34 MB/s34\text{ MB/s} exceeds the maximum supported single Premium SSD v1 disk limit (20 MB/s20\text{ MB/s} for standard tier, 30 MB/s30\text{ MB/s} for high-churn tier).
This determines if Azure Site Recovery is a viable replication option for the database virtual machine.
2
Compare the RPO requirements against the replication capabilities of Azure Site Recovery and Azure Backup.
The database RPO of 10 seconds10\text{ seconds} cannot be met by Azure Site Recovery (which has a recovery point frequency of several minutes) or Azure Backup (which operates on hourly/daily snapshots).
This rules out Azure Backup and standard virtual machine-level replication for the database tier.
3
Evaluate native database replication options for the SQL Server workload.
SQL Server Always On Availability Groups configured in asynchronous commit mode can continuously replicate database transactions to another region, satisfying the 10 second10\text{ second} RPO.
Native database replication is required to achieve low RPOs and handle high write churn workloads.
4
Select the correct combination of replication tools for the multi-tier application.
Use Azure Site Recovery for the low-churn web virtual machines (which easily meet the 4 hour4\text{ hour} RPO) and native SQL Server replication for the database tier.
This architecture meets both the workload performance limitations and the RPO/RTO business requirements.

Key Concept

Azure Site Recovery capacity limits and native database replication for low recovery point objectives.
Question 610Question

A digital marketing agency is designing an analytical data platform to query ad campaign click logs. The logs are uploaded daily as Parquet files to Azure Data Lake Storage (ADLS) Gen2, totaling 1.5 TB1.5\text{ TB} of new data per day. Analysts will run infrequent, ad-hoc exploratory T-SQL queries that must run directly against the storage account. The platform must survive a primary regional datacenter outage, minimize operational costs, and secure data access without utilizing long-lived access keys.

Which architecture should you recommend to meet these requirements?

Show answer & explanation

Answer: Azure Data Lake Storage Gen2 configured with Geo-Redundant Storage (GRS), queried using Azure Synapse serverless SQL pools with a system-assigned managed identity.

Answer

Azure Data Lake Storage Gen2 configured with Geo-Redundant Storage (GRS), queried using Azure Synapse serverless SQL pools with a system-assigned managed identity.
The correct architecture uses Geo-Redundant Storage (GRS) to ensure data survival during a primary datacenter outage, Azure Synapse serverless SQL pools to query the Parquet files on demand without paying for idle compute clusters, and a system-assigned managed identity to establish secure, passwordless authentication.

Step-by-Step Solution

1
Determine the storage redundancy level required for regional disaster resilience.
Geo-Redundant Storage (GRS) is selected.
The scenario requires that the data must survive a primary regional datacenter outage. Locally Redundant Storage (LRS) is vulnerable to localized regional outages.
2
Select the appropriate analytical query tool based on the query patterns and cost constraints.
Azure Synapse serverless SQL pools are selected.
Since the T-SQL queries are ad-hoc and infrequent, using a dedicated SQL pool would lead to unnecessary compute costs for idle clusters. Serverless SQL pools charge per query based on data processed, aligning with the cost minimization goal.
3
Select the secure authorization mechanism for accessing the storage account.
System-assigned managed identity is selected.
The requirements dictate avoiding long-lived access keys or SAS tokens. Managed identities provide automated credentials rotation and eliminate stored secrets.

Key Concept

Selecting Azure analytical storage and query components based on redundancy, cost profiles, and access security requirements.
Estimated Time:1m 30s
Question 611Question

A media streaming company is designing a container-based processing solution for transcribing audio files. The transcoder containers run as background tasks that can take up to 45 minutes to process large files. The solution must scale dynamically based on the number of audio files uploaded to Azure Blob Storage, scale to zero when no files are present, and minimize operational overhead. Which solution should you recommend?

Show answer & explanation

Answer: Azure Container Apps jobs

Answer

Azure Container Apps jobs
Azure Container Apps jobs are designed specifically for processing run-to-completion tasks. They natively support event-driven scaling (e.g., using KEDA scaling rules based on queue or storage metrics), allow executions to run beyond 10 minutes (up to 24 hours), and minimize administrative effort by running on a serverless platform where Azure manages the underlying infrastructure.

Step-by-Step Solution

1
Analyze the execution duration requirement of the workload.
The transcribing task can take up to 45 minutes, ruling out standard serverless options with a 10-minute limit.
Ensures the selected hosting environment supports long-running execution without timeout failures.
2
Evaluate operational overhead and scaling requirements.
The solution requires scaling to zero based on event triggers (Blob Storage uploads) and minimum operational overhead.
Rules out complex container orchestrators like Azure Kubernetes Service (AKS) which require cluster management.
3
Compare Azure Container Apps jobs against other Azure container solutions.
Azure Container Apps jobs support run-to-completion tasks, scale to zero, handle executions over 10 minutes, and run on a serverless platform.
Confirms the optimal service recommendation aligned with Microsoft Best Practices.

Key Concept

Selecting the appropriate Azure container hosting option based on workload duration, scaling requirements, and operational overhead.
Question 612Question

An organization needs to design a secure administration path for its development workloads. Developers must be able to establish Remote Desktop Protocol (RDP) connections to virtual machines over the internet. The solution must restrict public internet exposure by ensuring the virtual machines do not have public IP addresses, and it must avoid the management overhead of client-based virtual private network (VPN) software. Which service should you recommend to meet these requirements?

Show answer & explanation

Answer: Azure Bastion

Answer

Azure Bastion
Azure Bastion is a fully platform-managed PaaS service that provides secure and seamless RDP and SSH access to virtual machines directly through the Azure portal. Since it operates as a gateway inside the virtual network, VMs do not require public IP addresses, and administrators do not need to install client-side VPN software.

Step-by-Step Solution

1
Analyze the access requirement
Administrators need to connect to Azure VMs using RDP over the internet.
This establishes the protocol and target environment for the administration connection.
2
Evaluate the connectivity and agent constraints
The VMs must not have public IP addresses, and no VPN client software should be installed on client machines.
This rules out direct RDP exposure (which requires public IPs or NAT) and traditional Point-to-Site VPNs (which require VPN client software).
3
Select the appropriate Azure service
Azure Bastion satisfies these conditions by provisioning a managed gateway that brokers RDP/SSH traffic over HTTPS (SSL) directly in the browser.
Azure Bastion allows secure connectivity without public IPs on virtual machines and without client-side VPN components.

Key Concept

Azure Bastion provides secure, clientless RDP/SSH access to virtual machines within a virtual network without exposing public IPs.
Question 613Question

An organization is designing a hub-and-spoke virtual network topology in Azure to host a multi-tier web application. The topology consists of the following components:

* A hub virtual network named `vnet-eus-hub` (10.100.0.0/1610.100.0.0/16) hosting an Azure Firewall at IP address 10.100.10.410.100.10.4.
* A production spoke virtual network named `vnet-eus-prod` (10.101.0.0/1610.101.0.0/16) peered with the hub virtual network.
* Three subnets inside `vnet-eus-prod`:
* `subnet-web` (10.101.1.0/2410.101.1.0/24)
* `subnet-app` (10.101.2.0/2410.101.2.0/24)
* `subnet-db` (10.101.3.0/2410.101.3.0/24)

The design must satisfy the following routing requirements:
1. All outbound internet traffic from `subnet-web` must be inspected by the Azure Firewall in the hub.
2. All traffic between `subnet-web` and `subnet-app` must be inspected by the Azure Firewall in the hub.
3. Traffic between `subnet-app` and `subnet-db` must bypass the Azure Firewall and remain local within `vnet-eus-prod` to minimize latency.
4. You must minimize administrative overhead and avoid configuring redundant route rules.

Which route table configuration should you implement to meet the requirements?

Show answer & explanation

Answer: Create a route table for `subnet-web` with routes for 0.0.0.0/00.0.0.0/0 and 10.101.2.0/2410.101.2.0/24 pointing to Virtual Appliance (10.100.10.410.100.10.4). Create a separate route table for `subnet-app` with a route for 10.101.1.0/2410.101.1.0/24 pointing to Virtual Appliance (10.100.10.410.100.10.4). Do not associate a custom route table with `subnet-db`.

Answer

Create a route table for the web subnet with routes for 0.0.0.0/00.0.0.0/0 and the application subnet range pointing to the firewall, create a separate route table for the application subnet with a route for the web subnet range pointing to the firewall, and use default system routes for the database subnet.
The correct solution isolates the custom route tables to only the subnets that require traffic redirection, utilizing specific subnets (specifically 10.101.2.0/2410.101.2.0/24 and 10.101.1.0/2410.101.1.0/24) to route traffic between the web and application tiers through the firewall. Since the database tier does not have a custom route table associated, and no /16/16 route is added to the application subnet, traffic between the application and database tiers matches the default system route 10.101.0.0/1610.101.0.0/16 with next hop Local. Because this system route is more specific than the default 0.0.0.0/00.0.0.0/0 route, traffic between the application and database subnets bypasses the firewall, keeping database traffic local and avoiding high latency.

Step-by-Step Solution

1
Analyze routing priority rules in Azure Virtual Networks.
User-Defined Routes (UDRs) take precedence over default System Routes when they have matching prefixes. When multiple routes match a destination, Azure selects the route with the Longest Prefix Match (LPM).
Understanding LPM is essential to predict where packets will be forwarded when multiple route prefixes overlap.
2
Evaluate the requirement for internet traffic from the web subnet.
Adding a route for 0.0.0.0/00.0.0.0/0 with next hop Virtual Appliance (10.100.10.410.100.10.4) to a route table associated with the web subnet directs all internet-bound traffic to the Azure Firewall.
Since the internet system route has a /0/0 prefix, the custom 0.0.0.0/00.0.0.0/0 route overrides it.
3
Evaluate the requirement for web-to-application traffic.
To route web-to-app traffic through the firewall, the web subnet's route table needs a route for 10.101.2.0/2410.101.2.0/24 pointing to the firewall, and the application subnet's route table needs a route for 10.101.1.0/2410.101.1.0/24 pointing to the firewall.
Without these specific /24/24 routes, traffic between the web and application subnets would match the default local system route (10.101.0.0/1610.101.0.0/16 -> Local) because /16/16 is a longer prefix match than 0.0.0.0/00.0.0.0/0, bypassing the firewall.
4
Verify database tier isolation and local routing behavior.
By keeping the database subnet on default system routes and avoiding a broad 10.101.0.0/1610.101.0.0/16 UDR on the application subnet, traffic between the application subnet (10.101.2.0/2410.101.2.0/24) and the database subnet (10.101.3.0/2410.101.3.0/24) matches the default local route 10.101.0.0/1610.101.0.0/16 with next hop Local.
This keeps database traffic local, bypassing the firewall and avoiding high latency.

Key Concept

User-Defined Routes (UDR) precedence and Longest Prefix Match (LPM) routing in Azure Virtual Networks.
Question 614Question

You are designing a hub-and-spoke network topology in Azure. The hub virtual network, `vnet-hub-prod` (10.100.0.0/1610.100.0.0/16), contains an active Virtual Network Gateway connected to your on-premises datacenter. The spoke virtual network, `vnet-spoke-app` (10.101.0.0/1610.101.0.0/16), contains your application workloads. You configure virtual network peering between `vnet-hub-prod` and `vnet-spoke-app`. You need to ensure that the resources in `vnet-spoke-app` can communicate with the on-premises datacenter by using the gateway in `vnet-hub-prod`. Which two configurations should you perform to meet these requirements?

Select all that apply

Show answer & explanation

Answer: Configure the virtual network peering on `vnet-hub-prod` to allow gateway transit.; Configure the virtual network peering on `vnet-spoke-app` to use the remote virtual network's gateways.

Answer

To allow the spoke virtual network to use the virtual network gateway in the hub virtual network, you must configure the peering link on the hub virtual network to allow gateway transit, and configure the peering link on the spoke virtual network to use the remote virtual network's gateways.
To establish connectivity between a spoke virtual network and an on-premises network via a gateway in a peered hub, you must configure both ends of the peering link. First, the hub's peering link must be configured to allow gateway transit. Second, the spoke's peering link must be configured to use the remote virtual network's gateways. This tells Azure to route traffic from the spoke VNet to the hub's gateway.

Step-by-Step Solution

1
Configure the hub-side peering link settings.
Gateway transit is enabled on the peering from the hub VNet to the spoke VNet.
This permits the hub to share its gateway with the peered spoke VNet.
2
Configure the spoke-side peering link settings.
The option to use remote gateways is enabled on the peering from the spoke VNet to the hub VNet.
This tells the spoke VNet to route external traffic via the hub's gateway.

Key Concept

Virtual Network Gateway Transit in VNet Peering
Question 615Question

An organization is designing the identity security and authentication strategy for its Microsoft Entra ID tenant. You need to match the business and security requirements to the correct Microsoft Entra ID or Conditional Access feature. Match each requirement on the left to its corresponding feature on the right.

Click a left item, then click its matching right item

Items

Require users accessing sensitive applications from untrusted network locations to complete a multi-factor authentication (MFA) prompt.
Block access or require MFA for sign-in attempts that exhibit atypical travel patterns or malware-linked IP addresses.
Enforce read-only web-only access and prevent file downloads when users access SharePoint Online from unmanaged personal devices.
Allow users to authenticate in the cloud using their on-premises passwords, with authentication requests validated directly against local Active Directory domain controllers without storing hashes in the cloud.

Matches

Show answer & explanation

Answer

The business requirements are matched as follows: location-based MFA requirements match with Location conditions and Grant controls; risk-based sign-in blocking/MFA requirements match with Sign-in risk conditions; read-only access for unmanaged devices on SharePoint Online matches with App Enforced Restrictions session controls; and password validation against on-premises Active Directory without cloud hashes matches with Pass-through Authentication.
The correct matches align the scenarios with their proper Azure security and authentication mechanisms. Requiring MFA for untrusted locations matches Location conditions and Grant controls. Sign-in risks like atypical travel match Sign-in risk conditions. Restricting downloads on unmanaged devices matches App Enforced Restrictions. Validating passwords on-premises without cloud hashes matches Pass-through Authentication.

Step-by-Step Solution

1
Analyze the requirement for location-based MFA to determine which Conditional Access condition and control applies.
Identify that Location conditions define the network source, and Grant controls enforce the MFA requirement.
This matches the requirement of requiring MFA when users access applications from untrusted networks.
2
Analyze the requirement to detect atypical travel or malware-linked IP addresses during sign-in.
Identify that these behaviors are flagged as sign-in risks, which are handled using Sign-in risk conditions under Conditional Access.
This matches the requirement to enforce security controls based on real-time sign-in risk.
3
Analyze the requirement to restrict SharePoint Online downloads from unmanaged personal devices.
Identify that App Enforced Restrictions session controls allow SharePoint Online to limit session capabilities based on device compliance/management state.
This matches the requirement to prevent downloads and enforce a limited web-only session.
4
Analyze the authentication requirement that validates passwords on-premises without cloud hash storage.
Identify that Pass-through Authentication (PTA) routes password validation directly to on-premises domain controllers using agents, keeping password verification local.
This satisfies the hybrid identity authentication requirement without storing password hashes in Microsoft Entra ID.

Key Concept

Microsoft Entra ID Authentication methods and Conditional Access policies (including locations, risks, session controls, and hybrid authentication modes like Pass-through Authentication).
Estimated Time:1m 30s
Question 616Question

A logistics company is designing a global shipment tracking system that will run on Azure Cosmos DB for NoSQL. The application must process real-time coordinate updates from 500,000 active delivery vehicles. The workload is highly write-heavy, with an expected write-to-read ratio of 95:5. The system must support global distribution across three Azure regions with a 99.999% availability SLA for both reads and writes, keeping write latency under 10 milliseconds. You need to design the Cosmos DB configuration and choose a partition key to prevent hot partitions while meeting the SLA. Which configuration should you recommend?

Show answer & explanation

Answer: Enable multi-region writes, configure the account with Service-Managed Failover, and set the partition key to vehicleId.

Answer

Enable multi-region writes, configure the account with Service-Managed Failover, and set the partition key to vehicleId.
The correct configuration enables multi-region writes to achieve the necessary sub-10ms write latency and 99.999% SLA across multiple regions. By partitioning on vehicleId, which possesses high cardinality, the platform ensures that the heavy write workload is distributed uniformly across physical partitions, avoiding throughput bottlenecks and hot partitions.

Step-by-Step Solution

1
Evaluate write latency and SLA requirements.
Identified that multi-region writes are required.
With a write-to-read ratio of 95:5 and a sub-10ms global write latency target across three regions, clients must write to their closest local region. This setup is also necessary to meet the 99.999% write availability SLA.
2
Determine the partition key to prevent hot partitions.
Selected vehicleId as the partition key.
With 500,000 active delivery vehicles, vehicleId provides high cardinality. This ensures that the massive write volume is evenly distributed across many logical partitions, preventing physical partition limits from being exceeded.
3
Assess high availability and security configurations.
Discarded configurations utilizing LRS or long-lived SAS tokens.
Service-Managed Failover provides disaster recovery. LRS fails to support regional failover, and long-lived SAS tokens embedded in clients introduce major security management and revocation vulnerabilities.

Key Concept

Azure Cosmos DB partition key selection and global write replication configuration
Estimated Time:1m 30s
Question 617Question

A financial services firm is designing the Azure storage architecture for two distinct workloads using Azure Blob Storage:

1. Workload A (Transaction Logs): Must be resilient to the failure of a datacenter within the primary region without data loss, must be replicated to a secondary region to protect against regional disasters, and does not require read access to the secondary region unless a failover is initiated.
2. Workload B (Reporting Data): Must be resilient to the failure of a datacenter within the primary region without data loss, must be replicated to a secondary region, and must allow reporting applications to read data from the secondary region without waiting for a failover to be initiated.

Which two redundancy options should you select to meet the requirements for Workload A and Workload B? (Select two.)

Select all that apply

Show answer & explanation

Answer: Geo-zone-redundant storage (GZRS) for Workload A; Read-access geo-zone-redundant storage (RA-GZRS) for Workload B

Answer

Geo-zone-redundant storage (GZRS) for Workload A and Read-access geo-zone-redundant storage (RA-GZRS) for Workload B.
Selecting Geo-zone-redundant storage (GZRS) for Workload A and Read-access geo-zone-redundant storage (RA-GZRS) for Workload B meets all requirements. Workload A needs zonal redundancy in the primary region to prevent data loss from a single datacenter failure and asynchronous replication to a secondary region, without needing read access to the secondary, making GZRS the correct choice. Workload B has the same replication requirements but also requires read-only access to the secondary region without initiating a failover, which requires RA-GZRS.

Step-by-Step Solution

1
Analyze the requirements for Workload A.
Workload A requires datacenter outage resilience in the primary region without data loss (which requires Zone-Redundant Storage, ZRS, at the primary region), replication to a secondary region (which requires Geo-replication), and no read access to the secondary region without failover. This points to Geo-zone-redundant storage (GZRS).
Selecting GZRS ensures ZRS-level replication at the primary site and asynchronous replication to the secondary site.
2
Analyze the requirements for Workload B.
Workload B requires datacenter outage resilience in the primary region without data loss (which requires ZRS at the primary region), replication to a secondary region (which requires Geo-replication), and read access to the secondary region without waiting for a failover. This points to Read-access geo-zone-redundant storage (RA-GZRS).
Selecting RA-GZRS combines the zonal redundancy in the primary region with read-only access to the secondary region without initiating a failover.

Key Concept

Understanding Azure storage redundancy configurations and how they protect against datacenter and regional outages, as well as enabling secondary region read access.
Question 618Question

You are designing the serverless hosting infrastructure for an enterprise application that contains two distinct workloads:

* Workload 1: An HTTP-triggered API that processes incoming vendor requests. The API must access a backend database located in a secured Azure Virtual Network (VNet). The traffic is highly intermittent, with several hours of inactivity followed by unpredictable spikes. To minimize operating costs, the solution must scale to zero instances and incur no compute charges when idle.
* Workload 2: A queue-triggered background job that performs daily inventory synchronization. Each execution takes approximately 18 minutes to complete. The job must run on a serverless compute model that scales to zero when the queue is empty, and it must not experience timeout failures.

Which two hosting plans should you recommend to meet the requirements for both workloads? (Select two.)

Select all that apply

Show answer & explanation

Answer: Azure Functions Flex Consumption plan for Workload 1; Azure Functions Flex Consumption plan for Workload 2

Answer

The correct hosting plans are the Azure Functions Flex Consumption plan for Workload 1 and the Azure Functions Flex Consumption plan for Workload 2.
The correct plans are the Azure Functions Flex Consumption plan for Workload 1 and the Azure Functions Flex Consumption plan for Workload 2. For Workload 1, the Flex Consumption plan provides native virtual network integration without any baseline instance charge, scaling down to zero cost during idle periods. For Workload 2, the Flex Consumption plan supports unbounded execution timeouts for queue-triggered functions (configured via host.json) and scales down to zero when the queue is empty, ensuring the 18-minute run completes without timeout errors and costs nothing when idle.

Step-by-Step Solution

1
Analyze Workload 1 requirements for outbound network connectivity and idle pricing behavior.
Workload 1 needs native outbound VNet integration and must scale to zero compute instances with zero idle costs. The standard Consumption plan is ruled out because it lacks VNet support. The Premium plan and Dedicated plans are ruled out because they incur baseline charges even when idle. The Flex Consumption plan supports native VNet integration and scales to zero cost when idle.
Ensures the database can be reached securely without incurring unnecessary infrastructure costs during idle periods.
2
Analyze Workload 2 requirements for execution timeout limits and scaling capabilities.
Workload 2 runs a daily batch job that requires 18 minutes. The standard Consumption plan has a strict 10-minute timeout limit, which would cause execution failure. The Premium and Dedicated plans can run for 18 minutes but charge continuously, violating the idle cost requirement. The Flex Consumption plan allows unbounded execution limits for non-HTTP triggers and scales to zero when no messages are present.
Ensures the 18-minute batch job executes successfully without timing out and only incurs billing during runtime.
3
Select the correct combination of options representing Flex Consumption for both Workload 1 and Workload 2.
Options representing the Azure Functions Flex Consumption plan for Workload 1 and Workload 2 are selected.
Both workloads achieve their required functional constraints at the lowest cost point using the Flex Consumption tier.

Key Concept

Azure Functions hosting plan selection based on virtual network integration, execution limits, and scale-to-zero billing behavior.
Question 619Question

An enterprise is designing a subscription governance and access control model for its Azure environment. The environment consists of three business units: Finance, Retail, and Logistics. Each business unit has separate development and production subscriptions.

The design must meet the following requirements:
- Enable central IT to enforce compliance policies across all subscriptions.
- Allow the security audit team to view resource configurations in all subscriptions without viewing data plane payloads.
- Allow business unit administrators to manage resources only within their respective subscriptions.
- Follow the principle of least privilege and minimize administrative overhead.

Which two actions should you include in the governance design? (Select TWO.)

Select all that apply

Show answer & explanation

Answer: Create a management group hierarchy under the Tenant Root Group with child management groups for each business unit, and assign the compliance policies at the parent management group level.; Create a Microsoft Entra ID group for the security audit team, and assign the Reader role to this group at the root management group level.

Answer

Create a management group hierarchy under the Tenant Root Group with child management groups for each business unit and assign policies at the parent management group level; also, create a Microsoft Entra ID group for the security audit team and assign the Reader role to this group at the root management group level.
The correct architecture uses a management group hierarchy to organize subscriptions by business unit and apply compliance policies centrally, ensuring inheritance and consistency. Access for the security audit team is granted by assigning the Reader role to a Microsoft Entra ID group at the management group level, which aligns with security group best practices and the principle of least privilege.

Step-by-Step Solution

1
Analyze the requirement for enforcing compliance policies across multiple subscriptions under different business units.
Determine that a management group hierarchy is the most efficient way to organize subscriptions and apply policy definitions, since policies assigned at a management group are inherited by all child subscriptions.
This reduces administrative overhead compared to assigning policies individually per subscription or resource group.
2
Analyze the access requirements for the security audit team.
Assign the Reader role, which permits viewing resource configurations but does not grant access to data plane contents, satisfying the least privilege principle.
Assigning this role to a Microsoft Entra ID group rather than individual users at the management group scope ensures scalability and adheres to identity best practices.
3
Evaluate the incorrect options to identify why they fail to meet best practices.
Identify that direct user assignments violate group-based RBAC principles, and using a Deny policy effect fails to satisfy automatic deployment requirements.
This confirms the selection of the two correct governance and identity configuration actions.

Key Concept

Azure Management Groups, subscription inheritance, and group-based RBAC assignment using the principle of least privilege.
Estimated Time:1m 30s
Question 620Question

An organization is designing a hub-and-spoke network topology in Azure. The hub virtual network, `vnet-hub-core` (address space: 10.1.0.0/1610.1.0.0/16), hosts a central network virtual appliance (NVA) at IP address 10.1.1.410.1.1.4 that provides firewall and inspection services. The spoke virtual network, `vnet-spoke-data` (address space: 10.2.0.0/1610.2.0.0/16), contains two subnets: `snet-db` (10.2.1.0/2410.2.1.0/24) hosting database servers, and `snet-app` (10.2.2.0/2410.2.2.0/24) hosting application servers. The networks are connected via virtual network peering.

The security policy requires that all outbound internet traffic from the database servers in `snet-db` must be inspected by the hub NVA. However, database servers must communicate directly with application servers in `snet-app` within the same virtual network without routing through the hub NVA, minimizing latency and transaction costs.

To achieve this configuration, a custom route table will be associated with the `snet-db` subnet. Which route configuration should be added to the route table?

Show answer & explanation

Answer: A route for 0.0.0.0/00.0.0.0/0 with the Next Hop Type set to Virtual Appliance and the Next Hop Address set to 10.1.1.410.1.1.4.

Answer

Configure a single route for 0.0.0.0/00.0.0.0/0 with the Next Hop Type set to Virtual Appliance and the Next Hop Address set to 10.1.1.410.1.1.4.
The correct approach is to add a default route for 0.0.0.0/00.0.0.0/0 pointing to the NVA's IP address. Azure Virtual Network routing uses the Longest Prefix Match (LPM) rule. The system-defined route for the spoke virtual network is 10.2.0.0/1610.2.0.0/16 (Virtual Network). Because the /16 prefix is more specific than the /0 prefix, traffic destined for the local application subnet (10.2.2.0/2410.2.2.0/24) will match the system route and bypass the NVA. Traffic destined for the internet, which does not match the local prefix, will fall back to the 0.0.0.0/00.0.0.0/0 route and go to the NVA.

Step-by-Step Solution

1
Determine the destination of the traffic that requires custom routing.
Outbound internet traffic corresponds to the address prefix 0.0.0.0/00.0.0.0/0.
The requirement specifies that only traffic destined for the internet must be inspected by the hub NVA.
2
Analyze how Azure routing matches IP addresses under default settings.
Azure uses Longest Prefix Match (LPM). The local virtual network has a system route for 10.2.0.0/1610.2.0.0/16.
LPM ensures that the route with the most specific prefix is selected to forward the packet.
3
Evaluate the interaction between the system route and the new user-defined route.
Traffic to 10.2.2.0/2410.2.2.0/24 matches the 10.2.0.0/1610.2.0.0/16 route (prefix length /16) instead of 0.0.0.0/00.0.0.0/0 (prefix length /0).
Since the local virtual network route prefix (/16) is longer than the default route prefix (/0), local traffic stays within the VNet and bypasses the NVA, satisfying both requirements.

Key Concept

Longest Prefix Match in Azure Routing
Estimated Time:2m 0s
PreviousPage 31 / 60Next