Courseiva

Microsoft Azure Solutions Architect Expert AZ-305 (AZ-305) — Questions 526–600

795 questions total · 11 pages · All types, answers revealed

Page 7

Page 8 of 11

Page 9
526
MCQeasy

A company has a disaster recovery plan that requires testing failover of Azure VMs regularly without impacting the production environment. Which feature of Azure Site Recovery should they use?

A.Planned failover
B.Test failover
C.Unplanned failover
D.Failback
AnswerB

Test failover is the correct choice because it creates an isolated, non-production replica of the protected environment, allowing validation of recovery procedures without impacting live systems. It provides a safe, reversible mechanism to verify that recovery points and recovery time objectives can be met, making it the standard method for disaster recovery testing.

Why this answer

Test failover (Option B) is the correct feature for validating disaster recovery readiness without affecting the production environment. Azure Site Recovery's test failover creates an isolated copy of the replicated VMs in a separate virtual network, allowing you to run validation exercises, perform application testing, and verify recovery plans without any impact on the production VMs or ongoing replication. This ensures that the failover process works correctly while maintaining production continuity.

Exam trap

The trap here is that candidates often confuse 'test failover' with 'planned failover' because both involve controlled processes, but planned failover is intended for actual migration or maintenance and does impact production by shutting down source VMs, whereas test failover is purely for validation with zero production impact.

How to eliminate wrong answers

Option A (Planned failover) is wrong because it is used for migrating VMs from a primary to a secondary region with zero data loss, typically during planned maintenance or migration, and it does impact the production environment by shutting down source VMs. Option C (Unplanned failover) is wrong because it is designed for actual disaster scenarios where the primary site is unavailable; it initiates failover without prior synchronization and directly affects production by making the replica VMs the new primary, which would disrupt operations. Option D (Failback) is wrong because it is the process of returning workloads to the primary site after a failover has occurred, and it assumes the production environment has already been impacted by a previous failover event.

527
MCQeasy

A company wants to ensure that their Azure SQL Database can continue to serve read-write traffic if the primary region becomes unavailable. They require minimal data loss. What should they implement?

A.Use Azure Backup with cross-region restore
B.Deploy the database across two Availability Zones
C.Configure an auto-failover group with a secondary in another region
D.Read-scale replicas in the same region
AnswerC

An auto-failover group pairs a read-write primary database with a readable secondary server in another Azure region and exposes a single listener endpoint that automatically points to the current primary. The service continuously replicates data via active geo-replication and can automatically initiate failover when the primary becomes unhealthy, with a configurationurable grace period and forced/failover options. Because the secondary can be promoted to primary, this option preserves database availability even during a full regional outage.

Why this answer

An auto-failover group with a secondary in another region provides continuous read-write traffic capability during a regional outage with minimal data loss. The failover group uses asynchronous replication with a configurable grace period (default 1 hour) to balance performance and data loss, and upon failover, the secondary becomes the new primary with the same connection string, ensuring application transparency.

Exam trap

The trap here is that candidates confuse high availability within a region (Availability Zones) with disaster recovery across regions (geo-replication), or they mistakenly think read-scale replicas can handle write traffic during failover.

How to eliminate wrong answers

Option A is wrong because Azure Backup with cross-region restore is designed for point-in-time recovery of a database, not for real-time failover; it involves hours of recovery time and does not serve live read-write traffic during an outage. Option B is wrong because deploying across two Availability Zones protects only against zonal failures within the same region, not against a full regional outage; it cannot serve traffic if the entire primary region becomes unavailable. Option D is wrong because read-scale replicas in the same region are read-only and cannot accept write traffic; they are used for offloading read workloads, not for failover or write continuity.

528
MCQmedium

A company uses Microsoft Entra ID (Microsoft Entra ID) for identity management. They want to enforce that only devices compliant with security policies (e.g., BitLocker enabled, antivirus running) can access corporate cloud applications (Microsoft 365 and custom SaaS apps). They also need a dashboard to monitor device compliance status. Which Microsoft Entra ID feature(s) should they configure?

A.Conditional Access policies with device compliance conditions, and Microsoft Intune for compliance management
B.Microsoft Entra ID Identity Protection with user risk policies
C.Microsoft Entra ID Access Reviews
D.Microsoft Entra ID Device Registration only
AnswerA

Intune compliance policies define the security baseline a device must meet—such as minimum OS versions, BitLocker/FileVault encryption, and jailbreak/root detection—and report each device's compliance state in the Intune console. Conditional Access then consumes that state during authentication: if the policy requires 'Device to be marked as compliant,' Entra ID blocks or allows access based on the current Intune signal. This combination provides both the enforcement and the visibility of device health that the scenario demands.

Why this answer

Conditional Access policies in Microsoft Entra ID can enforce device compliance as a condition for granting access to cloud applications, while Microsoft Intune provides the device compliance policies (e.g., BitLocker, antivirus) and the dashboard to monitor compliance status. Together, they ensure only compliant devices can access corporate resources and provide visibility into device health.

Exam trap

The trap here is that candidates often confuse Identity Protection (user risk) with device compliance, or assume Device Registration alone is sufficient, missing the need for Intune to define and monitor compliance policies.

How to eliminate wrong answers

Option B is wrong because Microsoft Entra ID Identity Protection focuses on user and sign-in risk (e.g., leaked credentials, anonymous IP addresses), not device compliance status or enforcement. Option C is wrong because Microsoft Entra ID Access Reviews are used for periodic attestation of group memberships, application access, and role assignments, not for device compliance monitoring or conditional access based on device state. Option D is wrong because Microsoft Entra ID Device Registration only registers devices in the directory, but without Intune or Conditional Access, it cannot enforce compliance policies or provide a compliance dashboard.

529
Drag & Dropmedium

Drag and drop the steps to implement Azure Backup for an Azure virtual machine into the correct order.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

The correct sequence for implementing Azure Backup for an Azure VM is: first create a Recovery Services vault, then define a backup policy that specifies the backup schedule and retention, then assign the VM to the vault (which associates the VM with the vault and policy), then enable backup (which starts the protection), and finally test the backup to ensure it works correctly. This order ensures that each step has the necessary prerequisites completed before moving forward.

530
MCQeasy

A company deploys a web application on Azure VMs across availability zones. They need to distribute HTTPS traffic, offload SSL termination, and maintain session persistence. They do not require traffic inspection. Which Azure load balancing solution should they use?

A.Azure Application Gateway v2.
B.Azure Load Balancer (Standard).
C.Azure Traffic Manager.
D.Azure Front Door.
AnswerA

Azure Application Gateway v2 is the correct choice because it operates as a regional Layer 7 load balancer, directly supporting HTTPS termination, cookie-based session persistence (affinity), and HTTP health probes for backend VMs. Its v2 SKU is designed to span availability zones, enabling zone-redundant deployment across VM sets within a single region. Unlike global services, it stays in the region, minimizing latency while providing all required web-layer capabilities.

Why this answer

Azure Application Gateway v2 is the correct choice because it is a Layer 7 load balancer that supports HTTPS traffic distribution, SSL termination (offloading the decryption burden from backend VMs), and session persistence via cookie-based affinity. It meets all requirements without needing traffic inspection, which is optional and can be disabled.

Exam trap

The trap here is that candidates often confuse Azure Load Balancer (Layer 4) with Application Gateway (Layer 7), assuming any load balancer can handle SSL termination, but only Layer 7 solutions like Application Gateway or Front Door can offload SSL and maintain session persistence at the application layer.

How to eliminate wrong answers

Option B (Azure Load Balancer Standard) is wrong because it operates at Layer 4 (TCP/UDP) and cannot perform SSL termination or application-layer session persistence; it only distributes traffic based on IP and port. Option C (Azure Traffic Manager) is wrong because it is a DNS-based global traffic router that does not handle HTTPS traffic directly, SSL termination, or session persistence at the application layer. Option D (Azure Front Door) is wrong because it is a global Layer 7 service with built-in WAF and traffic inspection capabilities, which is unnecessary here and adds complexity; it also requires a custom domain for SSL termination, whereas Application Gateway v2 is a regional solution better suited for this scenario.

531
MCQmedium

You are designing a disaster recovery solution for an Azure IaaS workload. The application runs on Azure VMs in a single region and requires a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 4 hours. Which of the following is the most cost-effective approach to meet these requirements?

A.Configure geo-redundant storage (GRS) for the VM disks and manually attach them to new VMs in the secondary region.
B.Use Azure Front Door with a back-end pool containing VMs in both regions, and configure health probes to route traffic on failure.
C.Deploy Azure Site Recovery to replicate VMs to the secondary region with a replication policy that meets the RPO and RTO.
D.Use Azure Backup to back up VMs to a Recovery Services vault in the secondary region and perform restore during failover.
AnswerC

Azure Site Recovery provides asynchronous, continuous block-level replication with recovery points as frequent as every 30 seconds, comfortably satisfying the 15-minute RPO, while orchestrated failover to the paired region meets the 4-hour RTO. Unlike active-active or hot-standby designs, it keeps secondary-region compute costs near zero until failover, making it the most cost-effective fit.

Why this answer

Azure Site Recovery (ASR) provides orchestrated replication of Azure VMs to a secondary region with configurable RPO (as low as 30 seconds) and supports automated failover, meeting the 15-minute RPO and 4-hour RTO requirements. It is the most cost-effective because it replicates only changed blocks and does not require running standby VMs, unlike multi-region active deployments.

Exam trap

The trap here is that candidates confuse Azure Backup (which is for archival and long-term recovery) with Azure Site Recovery (which is for replication and rapid failover), leading them to choose Option D despite its inadequate RPO and RTO for disaster recovery scenarios.

How to eliminate wrong answers

Option A is wrong because manually attaching GRS-based disks to new VMs in the secondary region cannot guarantee a 15-minute RPO (GRS replication is asynchronous with a typical lag of hours) and the manual process would exceed the 4-hour RTO. Option B is wrong because Azure Front Door is a global load balancer for web traffic, not a disaster recovery replication tool; it does not replicate VM state or data, so it cannot meet RPO/RTO for IaaS workloads. Option D is wrong because Azure Backup is designed for long-term retention and point-in-time restores, with typical RPO of 24 hours for daily backups and restore times that can exceed 4 hours, making it unsuitable for the required 15-minute RPO and 4-hour RTO.

532
MCQmedium

A company has an Azure subscription with many resource groups. The security team requires that all diagnostic settings for every Azure resource be automatically configured to send logs to a central Log Analytics workspace. You need to design a solution that enforces this configuration at scale without manual intervention. What should you include in the design?

A.Use Azure Blueprints to assign a policy that audits diagnostic settings and manually remediate non-compliant resources.
B.Assign a built-in Azure Policy that uses the DeployIfNotExists effect to deploy diagnostic settings for each resource type.
C.Create an Azure Monitor alert rule that triggers an Azure Automation runbook to enable diagnostic settings when a resource is created.
D.Configure Azure Monitor diagnostic settings on each resource type using an ARM template and deploy it to all resource groups.
AnswerB

Azure Policy with DeployIfNotExists can automatically deploy diagnostic settings when a resource is created or updated. It evaluates the resource and, if the setting is missing, triggers a deployment to add it. This enforces compliance at scale across subscriptions and resource groups, meeting the requirement without manual effort.

Why this answer

Azure Policy with the DeployIfNotExists effect is designed to automatically deploy required configurations, such as diagnostic settings, when non-compliant resources are detected. It continuously evaluates resources and can remediate them, ensuring that all resources send logs to the central workspace without manual intervention. This provides scalable, consistent enforcement across the environment.

Exam trap

The trap here is assuming that Azure Monitor alerts or Azure Automation can automatically enforce configuration, when they are event-driven and require custom logic, unlike Azure Policy which provides declarative, continuous compliance.

533
MCQeasy

A company deploys a web application on multiple Azure virtual machines (VMs) in a single region. The application receives HTTP and HTTPS traffic. They need to distribute the traffic across the VMs, offload SSL/TLS termination, and ensure that client requests from the same user session are always sent to the same backend VM (session persistence). Additionally, they need to route requests based on URL paths (e.g., /api/* to one pool, /images/* to another). Which Azure load balancing solution should they use?

A.Azure Load Balancer
B.Azure Application Gateway
C.Azure Front Door
D.Azure Traffic Manager
AnswerB

Azure Application Gateway is a layer-7 load balancer specifically designed for HTTP(S) traffic. It supports SSL termination (and end-to-end SSL), cookie-based session affinity, URL path-based routing to different backend pools, and integrates with the Web Application Firewall (WAF). This makes it the correct choice for the company's stated requirements, as it directly handles application-level routing and persistence without the complexity of a global service.

Why this answer

Azure Application Gateway is the correct choice because it is a layer-7 load balancer that supports SSL/TLS termination, URL path-based routing, and session persistence (sticky sessions) via cookies. These features directly match the requirements for distributing HTTP/HTTPS traffic, offloading SSL, routing requests based on URL paths, and maintaining user session affinity to the same backend VM.

Exam trap

The trap here is that candidates often confuse Azure Load Balancer (layer 4) with Application Gateway (layer 7), assuming any load balancer can handle SSL termination and URL routing, but only layer-7 solutions like Application Gateway provide these application-level features.

How to eliminate wrong answers

Option A is wrong because Azure Load Balancer operates at layer 4 (TCP/UDP) and cannot perform SSL/TLS termination, URL path-based routing, or session persistence based on HTTP cookies. Option C is wrong because Azure Front Door is a global layer-7 load balancer and CDN designed for multi-region traffic distribution, not for routing within a single region, and it does not support URL path-based routing to separate backend pools in the same region. Option D is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that operates at layer 3/4 and cannot offload SSL/TLS, route based on URL paths, or provide session persistence.

534
MCQhard

A company uses Microsoft Entra ID (Microsoft Entra ID) Premium P2. They need to automatically detect users whose credentials have been leaked and require them to reset their password at their next sign-in. Additionally, they want to block sign-ins from anonymous IP addresses (e.g., Tor network). Which combination of Microsoft Entra ID features should they enable to meet both requirements?

A.Conditional Access with MFA policy and Identity Protection sign-in risk policy
B.Identity Protection user risk policy and sign-in risk policy
C.Privileged Identity Management and Conditional Access
D.Microsoft Entra ID Connect Health and Identity Protection
AnswerB

Identity Protection's user risk policy evaluates signals such as leaked credentials and, when the user risk score is elevated, automatically requires the user to perform a secure password change during sign-in. Its sign-in risk policy independently assesses real-time signals, including anonymous IP addresses, and can block the sign-in. Together, these two policies directly and automatically enforce both stated requirements, making this the correct answer.

Why this answer

Identity Protection user risk policy can automatically detect leaked credentials and force a password reset at next sign-in, while the sign-in risk policy can block sign-ins from anonymous IP addresses (e.g., Tor). These two policies together address both requirements without needing additional Conditional Access or MFA policies.

Exam trap

The trap here is that candidates confuse Conditional Access with Identity Protection risk policies, not realizing that leaked credential detection and anonymous IP blocking are native Identity Protection risk policies, not Conditional Access controls.

How to eliminate wrong answers

Option A is wrong because Conditional Access with MFA policy does not detect leaked credentials or block anonymous IPs; it only enforces MFA based on conditions, not risk. Option C is wrong because Privileged Identity Management (PIM) manages just-in-time privileged access and does not detect leaked credentials or block anonymous IPs; Conditional Access alone cannot detect leaked credentials without Identity Protection. Option D is wrong because Microsoft Entra ID Connect Health monitors synchronization health and does not provide user risk or sign-in risk policies for leaked credentials or anonymous IP blocking.

535
Multi-Selecthard

Which THREE considerations are important when designing a data storage solution for a high-throughput IoT ingestion pipeline in Azure?

Select 3 answers
A.Network latency between devices and Azure
B.Ingestion throughput limits of the storage service
C.Data retention and archival policies
D.Partitioning strategy to distribute load
E.Data consistency levels required by downstream consumers
AnswersB, C, D

Every Azure storage service, such as Blob Storage or Data Lake Storage Gen2, publishes specific scalability targets for ingress requests per second and bandwidth. Although Azure can consume high volumes, a streaming data lake intake must be verified against peak event rates; otherwise, the service throttles writes, causing backlog and data loss if IoT devices have limited buffering. Choosing partition layouts, multiple storage accounts, or premium capacity is directly tied to these limits.

Why this answer

Azure Storage services like Blob Storage and Event Hubs have defined ingestion throughput limits (e.g., up to 20 MB/s per partition or 1 MB/s per ingress for standard-tier Event Hubs). Exceeding these limits causes throttling (HTTP 429 errors) and data loss, making throughput capacity a critical design consideration for high-throughput IoT pipelines.

Exam trap

The trap here is confusing network-level considerations (latency, bandwidth) with storage-level design constraints (throughput limits, partitioning), leading candidates to select Option A instead of focusing on the storage service's inherent ingestion capacity.

536
MCQeasy

A company runs a web application on Azure VMs in a single region. The application must scale out automatically based on CPU utilization. The VMs are behind an Azure Load Balancer. Which Azure service should they use to automatically add or remove VMs based on demand?

A.Azure Virtual Machine Scale Sets
B.Azure App Service
C.Azure Functions
D.Azure Batch
AnswerA

Azure Virtual Machine Scale Sets (VMSS) is the correct choice because it directly manages a group of identical VMs as a single pool, providing automatic horizontal scaling based on performance metrics like CPU or memory utilization, custom metrics, or scheduled times. It integrates natively with Azure Load Balancer and Application Gateway to distribute incoming web traffic across the VM instances, making it ideal for a web application hosted on Azure VMs. VMSS also supports manual scaling, automatic scale rules, and health monitoring to replace unhealthy instances, ensuring high availability and elastic capacity for fluctuating web workloads.

Why this answer

Azure Virtual Machine Scale Sets (VMSS) is the correct service because it provides automatic scaling of identical VM instances based on metrics like CPU utilization. When you configure an autoscale rule on a VMSS, it automatically adds or removes VM instances behind the Azure Load Balancer, ensuring the application scales out or in based on demand without manual intervention.

Exam trap

The trap here is that candidates often confuse Azure App Service's autoscale feature (which scales the number of App Service instances, not VMs) with the requirement to scale VMs behind a load balancer, leading them to select App Service instead of VMSS.

How to eliminate wrong answers

Option B (Azure App Service) is wrong because it is a platform-as-a-service (PaaS) offering for web apps, not a service that manages VMs behind a load balancer; it does not allow you to run custom VMs with full control over the OS. Option C (Azure Functions) is wrong because it is a serverless compute service for event-driven code, not designed for long-running web applications on VMs, and it does not integrate with Azure Load Balancer for VM-level scaling. Option D (Azure Batch) is wrong because it is a job-scheduling and compute-management service for large-scale parallel and HPC workloads, not for automatically scaling VMs behind a load balancer based on CPU utilization.

537
MCQmedium

Your organization has multiple Azure subscriptions. You need to create a central view of policy compliance across all subscriptions. What should you use?

A.Azure Monitor
B.Azure Policy compliance dashboard
C.Azure Resource Graph
D.Azure Blueprints
AnswerB

The Azure Policy compliance dashboard is the native portal surface in Azure Policy that aggregates compliance states for all policies, initiatives, and assignments, and it can scope the view to a management group, subscription, or resource group. It uses the policy evaluation pipeline to mark resources as compliant or noncompliant against definitions, then shows rollups and drill-downs so administrators can identify offending resources and exemptions. This precisely meets the need to see compliance across multiple subscriptions.

Why this answer

The Azure Policy compliance dashboard provides a centralized view of policy compliance across all subscriptions in a management group or tenant. It aggregates compliance data from all assigned policies and initiatives, allowing you to filter by subscription, policy definition, or compliance state. This is the native tool designed specifically for cross-subscription policy compliance monitoring.

Exam trap

The trap here is that candidates often confuse Azure Policy compliance dashboard with Azure Monitor or Azure Resource Graph, thinking either can serve as a central compliance viewer, but only the Policy dashboard provides the out-of-the-box aggregated view across subscriptions without requiring custom queries or workbooks.

How to eliminate wrong answers

Option A is wrong because Azure Monitor is a platform for collecting, analyzing, and acting on telemetry data from cloud and on-premises environments, not for viewing policy compliance across subscriptions. Option C is wrong because Azure Resource Graph is a query engine for exploring Azure resources and their properties, but it does not provide a pre-built compliance dashboard or aggregate policy compliance states across subscriptions. Option D is wrong because Azure Blueprints is used for orchestrating the deployment of resource templates, policies, and role assignments to create compliant environments, not for viewing ongoing compliance status.

538
MCQhard

Refer to the exhibit. You need to enable public access to the storage account for a specific IP address while keeping the default action as Deny. What should you do?

A.Set the bypass to None to allow all traffic.
B.Set the networkAcls to an empty list to remove restrictions.
C.Add an IP rule with the specific IP address to the ipRules array.
D.Change the defaultAction to Allow and remove the Deny rule.
AnswerC

With defaultAction set to Deny, only traffic explicitly matched by an IP rule in the ipRules array is allowed. Adding a rule with the specific public IP address (or CIDR range) and action Allow creates a narrow exception for that source, while all other public traffic continues to be denied. This is the standard way to enable public access for a particular client while maintaining a secure, deny-by-default posture; the rule permits only the specified IP and does not alter the default behavior.

Why this answer

The Azure Storage account firewall allows you to create IP rules that grant access to specific public IP addresses or ranges while keeping the default action as Deny. By adding an IP rule with the specific IP address to the `ipRules` array, you explicitly allow that IP through the firewall, and all other traffic is denied by the default rule. This is the standard method to enable selective public access without changing the default deny behavior.

Exam trap

The trap here is that candidates often think they must change the default action to Allow and then add a Deny rule, but Azure Storage firewall does not support explicit Deny rules for IP addresses—only Allow rules—so the correct approach is to keep the default as Deny and add an Allow rule for the specific IP.

How to eliminate wrong answers

Option A is wrong because setting the bypass to 'None' would not allow all traffic; it would actually prevent any Azure services from bypassing the firewall, but it does not affect IP-based access rules and would still require explicit IP rules to allow traffic. Option B is wrong because setting the `networkAcls` to an empty list would remove all network ACL rules, including any IP rules, leaving only the default action (Deny) in effect, which would block all traffic including the specific IP address. Option D is wrong because changing the `defaultAction` to Allow would permit all public traffic, which violates the requirement to keep the default action as Deny and only allow the specific IP address.

539
MCQeasy

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to generate periodic reports of user sign-ins and audit activities for compliance. They want to store the logs for 1 year. Which Azure service should they use?

A.Microsoft Entra ID sign-in logs and audit logs with retention set to 1 year in the Azure portal
B.Azure Monitor Log Analytics workspace with Microsoft Entra ID diagnostic settings
C.Azure Storage account with lifecycle management
D.Azure Event Hubs for streaming
AnswerB

This is the correct answer because Microsoft Entra ID diagnostic settings can stream sign-in and audit logs directly to an Azure Monitor Log Analytics workspace. Log Analytics supports configurable retention periods up to 730 days (with options for longer-term archival), and its KQL query engine enables you to generate custom reports, dashboards, and alerts directly on the historical log data. This combined long-term storage and querying capability exactly satisfies the company's requirement to generate reports on sign-in and audit activity.

Why this answer

Microsoft Entra ID sign-in and audit logs are retained for only 30 days by default. To store them for 1 year, you must route the logs via diagnostic settings to an Azure Monitor Log Analytics workspace, which allows configurable retention up to 2 years (or more with a commitment tier). This is the only native Azure service that supports long-term retention of Entra ID logs for compliance reporting.

Exam trap

The trap here is that candidates assume the Azure portal's retention slider for Entra ID logs can be extended beyond 30 days, but Microsoft intentionally limits it to 30 days to force the use of diagnostic settings and Log Analytics for long-term retention.

How to eliminate wrong answers

Option A is wrong because the Azure portal's retention setting for Entra ID sign-in and audit logs only allows a maximum of 30 days; you cannot set it to 1 year directly in the portal. Option C is wrong because while an Azure Storage account with lifecycle management can store logs for 1 year, it does not support querying or generating periodic compliance reports—it is a cold storage solution, not a reporting tool. Option D is wrong because Azure Event Hubs is a real-time streaming service for log ingestion, not a storage or reporting solution; it cannot retain logs for 1 year or generate periodic reports.

540
MCQhard

Refer to the exhibit. You are reviewing a Bicep template for a storage account. You need to ensure that the storage account is only accessible via HTTPS and uses TLS 1.2. Which property validates this requirement?

A.type: Microsoft.Storage/storageAccounts
B.accessTier: Hot
C.supportsHttpsTrafficOnly: true and minimumTlsVersion: TLS1_2
D.name: stprod001
AnswerC

Configuring supportsHttpsTrafficOnly to true enforces that all client requests to the storage account must be made over HTTPS, causing any HTTP request to be rejected. The minimumTlsVersion property set to TLS1_2 further ensures that connections use at least TLS version 1.2, blocking older protocols such as TLS 1.0 and 1.1. Together, these two properties provide complete transport security enforcement, which is exactly what the requirement asks for.

Why this answer

The `supportsHttpsTrafficOnly` property enforces that all traffic to the storage account must use HTTPS, and the `minimumTlsVersion` property set to `TLS1_2` ensures that only TLS 1.2 or higher is accepted. Together, these two properties satisfy the requirement of HTTPS-only access with TLS 1.2, as defined in the Azure Storage security baseline.

Exam trap

The trap here is that candidates often confuse `supportsHttpsTrafficOnly` with a simple boolean toggle and forget that `minimumTlsVersion` is a separate, required property to enforce the specific TLS version, leading them to select an option that only partially addresses the requirement.

How to eliminate wrong answers

Option A is wrong because the `type` property only declares the resource provider and type (`Microsoft.Storage/storageAccounts`), not any security settings for HTTPS or TLS. Option B is wrong because `accessTier: Hot` controls the storage tier (Hot, Cool, Archive) for blob data, not transport security protocols. Option D is wrong because the `name` property simply assigns the storage account name (`stprod001`) and has no effect on HTTPS or TLS enforcement.

541
MCQeasy

A company deploys a critical multi-tier application on Azure VMs. The application includes a database tier that must be recovered to the same point in time as the application tier after a disaster. They use Azure Site Recovery (ASR) for disaster recovery to a secondary region. They also need to run a custom script after failover to update connection strings. Which ASR feature should they use?

A.Recovery plans with pre-actions and post-actions
B.Replication policies with application-consistent snapshots
C.Multi-VM consistency groups
D.Azure Backup with cross-region restore
AnswerA

Recovery plans with pre-actions and post-actions are the correct answer because Azure Site Recovery's recovery plans provide orchestrated failover beyond simple replication. They allow you to group VMs into fault domains and specify a sequence for failover, ensuring critical tiers come online before dependent ones. Pre-actions and post-actions execute custom scripts or Azure Automation runbooks automatically at specific points in the sequence, enabling tasks such as changing connection strings, updating DNS, or health checks. This combination of ordering and automated script execution is exactly what the company needs to recover a multi-tier application cohesively.

Why this answer

Recovery plans in Azure Site Recovery allow you to define pre-actions and post-actions, which can run custom scripts (e.g., PowerShell) after failover to update connection strings. This ensures the application tier can connect to the recovered database tier, meeting the requirement for a custom script execution after failover. The other options do not provide the ability to run custom scripts as part of the failover sequence.

Exam trap

The trap here is that candidates often confuse multi-VM consistency groups (which ensure crash-consistent recovery across VMs) with the ability to run post-failover scripts, but only recovery plans provide the orchestration layer for custom actions like updating connection strings.

How to eliminate wrong answers

Option B is wrong because replication policies with application-consistent snapshots ensure data consistency for crash-consistent recovery but do not allow running custom scripts after failover. Option C is wrong because multi-VM consistency groups ensure all VMs in a group fail over to a consistent point in time, but they do not provide a mechanism to execute post-failover scripts. Option D is wrong because Azure Backup with cross-region restore provides backup-based recovery, not real-time replication, and does not support custom script execution as part of a failover orchestration.

542
MCQeasy

A company plans to migrate on-premises SQL Server databases to Azure. They need to minimize changes to existing applications and want to use the latest features of SQL Server. Which Azure data service should they use?

A.SQL Server on Azure Virtual Machines
B.Azure SQL Managed Instance
C.Azure SQL Database
D.Azure Cosmos DB
AnswerB

As a PaaS offering, Azure SQL Managed Instance delivers near-virtual-machine-level compatibility with instance-scoped features such as SQL Server Agent, linked servers, and CLR, allowing most databases to be migrated with minimal or no application changes. It also offloads administrative tasks—like patching, backups, and availability—to Azure while keeping the database in a VNet for isolated networking.

Why this answer

Azure SQL Managed Instance is the correct choice because it provides near 100% compatibility with on-premises SQL Server, enabling a lift-and-shift migration with minimal application changes. It also supports the latest SQL Server features, such as native JSON support, temporal tables, and intelligent query processing, while offloading infrastructure management to Azure.

Exam trap

The trap here is that candidates often choose Azure SQL Database thinking it is the most modern PaaS option, but they overlook the requirement to minimize application changes, which SQL Managed Instance satisfies by offering the highest compatibility with on-premises SQL Server.

How to eliminate wrong answers

Option A is wrong because SQL Server on Azure Virtual Machines requires you to manage the VM, OS, and SQL Server patches, which does not minimize changes but adds operational overhead, and it does not provide the latest SQL Server features automatically (you must manually upgrade). Option C is wrong because Azure SQL Database is a PaaS offering that may require application changes due to differences in T-SQL syntax, database scoped configurations, and lack of instance-level features like SQL Agent jobs, cross-database queries, and CLR integration. Option D is wrong because Azure Cosmos DB is a NoSQL database service that does not support SQL Server features, T-SQL, or relational schemas, requiring significant application rewrites.

543
MCQmedium

You are designing a solution to securely store and manage secrets for multiple applications deployed in Azure. The solution must support automated rotation of secrets and provide audit logging. Which Azure service should you use?

A.Microsoft Entra ID application registration
B.Azure App Service Key Vault references
C.Azure Key Vault with managed identity and rotation policy
D.Azure Automation with PowerShell runbooks
AnswerC

Azure Key Vault with a managed identity and an enabled rotation policy is the correct choice because it natively supports secret lifecycle management: the rotation policy automatically creates new versions of the secret on a schedule or by proximity to expiry, the managed identity provides secure, passwordless authentication for workloads to access those secrets without embedding credentials, and Key Vault's diagnostic settings enable audit logging of all secret operations for compliance and monitoring.

Why this answer

Azure Key Vault with a managed identity and a rotation policy is the correct choice because it provides a centralized, secure store for secrets, supports automated rotation via built-in policies or custom logic, and integrates with Azure Monitor for audit logging. Managed identities eliminate the need for hard-coded credentials, and the rotation policy ensures secrets are automatically updated without manual intervention.

Exam trap

The trap here is that candidates often confuse 'Key Vault references' (which only retrieve secrets at runtime) with the full secret management lifecycle (which includes automated rotation and audit logging), leading them to select Option B instead of the comprehensive solution in Option C.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra ID application registration is used for identity and access management, not for storing secrets or automating their rotation; it lacks a built-in secret rotation mechanism and audit logging for secret lifecycle events. Option B is wrong because Azure App Service Key Vault references are a feature that allows an app to reference secrets from Key Vault at runtime, but they do not provide automated rotation or audit logging themselves—they rely on Key Vault for those capabilities. Option D is wrong because Azure Automation with PowerShell runbooks can be used to rotate secrets, but it is not a dedicated secret management service; it requires custom scripting, lacks native audit logging integration, and does not provide the same level of secure storage and access policies as Key Vault.

544
MCQhard

You manage a globally distributed application using Azure Cosmos DB. You need to design a business continuity strategy that ensures zero data loss and automatic failover in case of a regional outage. The application must continue to serve reads and writes during a region failure. What should you recommend?

A.Use Azure Cosmos DB accounts with a single write region and enable service-managed failover.
B.Use Azure Cosmos DB accounts with multi-region writes but disable automatic failover and rely on manual failover.
C.Configure single-region writes with strong consistency and enable automatic failover.
D.Configure multi-region writes with eventual consistency and enable automatic failover.
AnswerD

Multi-region writes with automatic failover provide zero data loss and continuous availability for both reads and writes.

Why this answer

Azure Cosmos DB multi-region writes with automatic failover ensure zero data loss and continuous availability for both reads and writes during a regional outage. Writes are accepted in multiple regions and asynchronously replicated, eliminating a single point of failure. Option A is incorrect because a single write region with service-managed failover may lose writes that were not replicated before the failover.

Option B is incorrect because disabling automatic failover requires manual intervention, which does not meet the automatic failover requirement and can still result in data loss. Option C is incorrect because single-region writes, even with strong consistency, will lose writes if the region fails before replication completes.

545
MCQmedium

A company plans to deploy a multi-tier application on Azure. The web tier requires SSL termination and health probes. The application tier must be isolated from the internet. The database tier requires high availability. They want to minimize administrative overhead and use Azure native services. Which architecture should they recommend?

A.Azure Application Gateway for web tier, Azure Load Balancer (internal) for application tier, and Azure SQL Database with active geo-replication
B.Azure Front Door for web tier, Azure Load Balancer for database tier, and SQL Server on Azure VMs with Always On
C.Azure Traffic Manager for web tier, Azure Application Gateway for database tier, and Azure SQL Database with failover groups
D.Azure Application Gateway for web tier, Azure Load Balancer (internal) for application tier, and Azure SQL Database with geo-restore
AnswerA

Azure Application Gateway is the correct ingress for the web tier because it performs L7 functions such as SSL termination, cookie affinity, and WAF rules while routing HTTP traffic to backend web apps. An internal Standard Load Balancer then distributes L4 network traffic among application-tier VMs, keeping that tier private from the internet. Azure SQL Database with active geo-replication maintains a readable secondary in a different Azure region, which supports a low-RPO manual or managed failover for business continuity. Together these services align with a typical multi-tier architecture and provide both high availability and regional resiliency.

Why this answer

Azure Application Gateway provides SSL termination and health probes for the web tier, an internal Azure Load Balancer isolates the application tier from the internet, and Azure SQL Database with active geo-replication offers high availability with automatic failover, minimizing administrative overhead by using PaaS services.

Exam trap

The trap here is that candidates often confuse Azure Front Door or Traffic Manager with Application Gateway for SSL termination and health probes, or assume that geo-restore provides the same automatic high availability as active geo-replication, leading them to choose options that either lack required features or increase administrative overhead.

How to eliminate wrong answers

Option B is wrong because Azure Front Door is a global load balancer for web traffic, but it does not natively provide SSL termination for a single-region web tier, and using Azure Load Balancer for the database tier is inappropriate as it does not offer database-level high availability; SQL Server on Azure VMs with Always On requires significant administrative overhead. Option C is wrong because Azure Traffic Manager is a DNS-based traffic router that does not perform SSL termination or health probes for the web tier, and Azure Application Gateway is not designed for the database tier; Azure SQL Database with failover groups is a valid HA option but the web tier architecture is incorrect. Option D is wrong because Azure SQL Database with geo-restore does not provide automatic high availability; it requires manual restore from a geo-redundant backup, which does not meet the requirement for minimal administrative overhead and active failover.

546
MCQeasy

You need to design a solution to monitor the performance of an Azure SQL Database. You want to create a dashboard that shows the top 10 queries by CPU usage over the last hour. What should you use?

A.Azure Monitor Workbooks
B.Power BI
C.Azure SQL Analytics
D.Log Analytics
AnswerC

Azure SQL Analytics is the correct choice because it is a cloud monitoring solution built specifically for Azure SQL Database, elastic pools, and managed instances. It connects to Azure Monitor to collect resource utilization, wait stats, deadlocks, and query performance data, then presents it through prebuilt dashboards that show DTU/CPU, storage, IO, and session trends. These dashboards are ready to use without manual configuration, giving immediate visibility into SQL performance.

Why this answer

Azure SQL Analytics is a dedicated monitoring solution for Azure SQL Database that provides built-in views and dashboards for top queries by CPU, duration, and other performance metrics. It leverages the Query Store and DMVs to surface the top 10 queries by CPU usage over the last hour without requiring custom queries or additional configuration.

Exam trap

The trap here is that candidates confuse Azure SQL Analytics (a dedicated monitoring solution) with Log Analytics (the underlying data platform) or Azure Monitor Workbooks (a general-purpose dashboard tool), assuming any of them can provide the same pre-built top queries view without additional effort.

How to eliminate wrong answers

Option A is wrong because Azure Monitor Workbooks are customizable, interactive dashboards but do not provide pre-built, out-of-the-box views for top queries by CPU; they require manual configuration of KQL queries to extract that data. Option B is wrong because Power BI is a business analytics service for creating reports from various data sources, not a native Azure SQL monitoring tool, and it would require complex data export and transformation to replicate the built-in top queries view. Option D is wrong because Log Analytics is the underlying data store and query engine for Azure Monitor logs, but it does not offer a ready-made dashboard for top queries by CPU; you would need to write custom KQL queries and build visualizations from scratch.

547
MCQmedium

You are designing a monitoring solution for a hybrid environment with on-premises servers and Azure VMs. You need to collect security events and performance data centrally, and create custom alerts. The solution must use the same agent for both environments. Which agent should you deploy?

A.Log Analytics agent (MMA)
B.Azure Monitor Agent
C.Microsoft Dependency Agent
D.Azure Diagnostics extension
AnswerB

Azure Monitor Agent (AMA) is the next-generation, unified agent designed to replace the Log Analytics agent for both Azure VMs and on-premises servers via Azure Arc. It provides a single agent to collect performance, event, security, and custom telemetry, with granular control through Data Collection Rules (DCRs) that separate data collection from configuration. AMA supports multi-homing by sending data to multiple Log Analytics workspaces simultaneously, making it the appropriate and recommended choice for a hybrid environment.

Why this answer

Azure Monitor Agent (AMA) is the correct choice because it is the next-generation agent that replaces the legacy Log Analytics agent (MMA) and supports both Windows and Linux machines in hybrid and Azure environments. It collects security events and performance data into a single Log Analytics workspace and enables custom alert rules via data collection rules (DCRs), all with a single agent deployment.

Exam trap

The trap here is that candidates often confuse the Log Analytics agent (MMA) as the 'standard' hybrid agent, not realizing it is being replaced by Azure Monitor Agent, which is the only agent that meets the 'same agent for both environments' requirement with unified data collection rules.

How to eliminate wrong answers

Option A is wrong because the Log Analytics agent (MMA) is legacy and will be deprecated by August 2024; it requires separate agents for different data types and does not support the same unified data collection rules as Azure Monitor Agent. Option C is wrong because the Microsoft Dependency Agent is used exclusively for service map and VM insights topology data, not for general security event or performance data collection, and it must be paired with another agent (MMA or AMA) to function. Option D is wrong because the Azure Diagnostics extension is designed for Azure VMs only, collecting boot diagnostics and guest OS metrics to Azure Storage or Event Hubs, not for hybrid on-premises servers, and it does not support custom alerts via Log Analytics workspaces.

548
Multi-Selectmedium

You are designing a disaster recovery solution for a multi-tier web application on Azure VMs. The solution must meet an RPO of 15 minutes and an RTO of 1 hour. The application includes a SQL Server database. Which THREE actions should you take? (Choose THREE.)

Select 3 answers
A.Use Azure Backup for the SQL Server database with 1-hour backup frequency.
B.Use Azure Premium SSD managed disks for the VMs to ensure low latency replication.
C.Configure SQL Server Always On Availability Groups with synchronous commit between regions.
D.Deploy read-scale replicas of the SQL Server in the secondary region.
E.Configure Azure Site Recovery to replicate the web and app tier VMs to a secondary region.
AnswersB, C, E

Azure Premium SSD managed disks deliver single-digit millisecond latencies and high IOPS, which are essential for sustaining synchronous or continuous replication traffic between the primary and secondary regions without storage-level bottlenecks. When VMs are replicated via Azure Site Recovery or contain SQL Server transaction log replicas, the underlying disk performance directly influences replication lag; Premium SSD ensures that I/O operations are not throttled, helping maintain an RPO below 15 minutes. This makes Premium SSD a supported and recommended configuration for I/O-sensitive replication workloads.

Why this answer

Azure Premium SSD managed disks provide low-latency, high-throughput storage that is essential for synchronous replication in SQL Server Always On Availability Groups. The synchronous commit mode requires fast disk I/O to avoid transaction delays, and Premium SSDs meet the sub-millisecond latency needed to achieve an RPO of 15 minutes and RTO of 1 hour across regions.

Exam trap

The trap here is that candidates often confuse Azure Backup's 1-hour backup frequency with the ability to meet a 15-minute RPO, not realizing that backup frequency is the interval between backups, not the recovery point granularity, and that synchronous replication (Always On) is required for sub-hour RPOs.

549
MCQeasy

You need to design a storage solution for a website that hosts static content (HTML, CSS, JavaScript) and requires low-cost, scalable storage with integrated CDN delivery. Which Azure service should you use?

A.Azure Files with SMB protocol
B.Azure Content Delivery Network only
C.Azure Blob Storage with static website hosting and Azure CDN
D.Azure App Service
AnswerC

Blob Storage with static website hosting natively serves HTML, CSS, JavaScript, and images over HTTPS from a public endpoint, with configurable index and error documents. Adding Azure CDN in front provides global edge caching, custom domain support, automated TLS, and DDoS mitigation. This combination is cost-effective for static assets because storage and bandwidth scale elastically while requiring no virtual machines or always-on application runtime.

Why this answer

Azure Blob Storage with static website hosting provides a cost-effective, scalable storage solution for static content (HTML, CSS, JavaScript). By enabling Azure CDN on top of the storage account, you achieve low-latency global content delivery and offload traffic from the origin, reducing costs and improving performance for end users.

Exam trap

The trap here is that candidates often confuse Azure Files (a managed file share) with Blob Storage (object storage) for static web hosting, or mistakenly think Azure CDN alone can store content without an origin service.

How to eliminate wrong answers

Option A is wrong because Azure Files with SMB protocol is designed for file shares that require SMB access (e.g., lift-and-shift apps, legacy file servers), not for serving static web content with CDN integration. Option B is wrong because Azure Content Delivery Network alone is a delivery service, not a storage service; it requires an origin (like Blob Storage) to cache and serve content. Option D is wrong because Azure App Service is a PaaS compute service for hosting web applications, not a dedicated static content storage solution, and it incurs higher costs and unnecessary overhead for purely static content.

550
MCQeasy

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to automatically detect sign-ins from users with leaked credentials and prompt those users to reset their password during the next sign-in. Which Microsoft Entra ID feature should they enable?

A.Microsoft Entra ID Identity Protection
B.Conditional Access
C.Privileged Identity Management (PIM)
D.Microsoft Entra ID B2B
AnswerA

Microsoft Entra ID Identity Protection detects leaked-credential sign-ins through its leaked credentials detection signal and can enforce a user risk policy requiring password reset at next sign-in. This satisfies the requirement for automatic detection and remediation without manual monitoring.

Why this answer

Microsoft Entra ID Identity Protection includes a 'Leaked Credentials' detection capability that continuously monitors for credentials exposed in known data breaches. When a user's credentials are detected as leaked, Identity Protection can automatically trigger a password reset during the next sign-in, ensuring the compromised credentials are no longer usable.

Exam trap

The trap here is that candidates often confuse Conditional Access (which can enforce password changes via a 'Require password change' grant control) with Identity Protection, but Conditional Access alone cannot detect leaked credentials—it only enforces policies after a risk is detected by Identity Protection.

How to eliminate wrong answers

Option B (Conditional Access) is wrong because Conditional Access enforces access policies based on signals like location or device compliance, but it does not natively detect leaked credentials or trigger password resets. Option C (Privileged Identity Management) is wrong because PIM manages just-in-time privileged role activation and access reviews, not credential compromise detection. Option D (Microsoft Entra ID B2B) is wrong because B2B is designed for external user collaboration and guest access, not for detecting leaked credentials or enforcing password resets.

551
MCQeasy

Your organization uses Microsoft Purview to govern data across Azure and on-premises sources. You need to ensure that sensitive data, such as credit card numbers, is automatically detected and classified in Azure Blob Storage. Which Purview feature should you configure?

A.Microsoft Sentinel
B.Data catalog search
C.Data classification scanning with built-in sensitive information types
D.Data lineage tracking
AnswerC

Data classification scanning in Microsoft Purview uses system data source scanners to inspect structured and unstructured content, and it applies built-in sensitive information types (for example, credit card numbers, social security numbers, or email addresses) and custom classification rules to the sampled data. When a scan matches a defined pattern or classifier, Purview records those classification labels and can propagate them to associated assets, columns, or files, enabling downstream governance policies. Because this capability directly identifies sensitive data within the content, it is the correct answer for automatically classifying sensitive data across your data estate.

Why this answer

Microsoft Purview's data classification scanning can be configured to automatically detect sensitive data like credit card numbers using built-in sensitive information types (e.g., Credit Card Number). When a scan is run against Azure Blob Storage, Purview identifies and classifies the data based on these predefined patterns, enabling governance and compliance.

Exam trap

The trap here is that candidates often confuse Microsoft Sentinel (a SIEM) with Purview's classification capabilities, or assume data lineage or catalog search can perform content inspection, when only classification scanning with sensitive information types can automatically detect sensitive data.

How to eliminate wrong answers

Option A is wrong because Microsoft Sentinel is a Security Information and Event Management (SIEM) tool for threat detection and response, not for data classification or governance. Option B is wrong because Data catalog search is a feature for discovering and searching assets already registered in Purview, not for automatically detecting or classifying sensitive data. Option D is wrong because Data lineage tracking captures how data moves and transforms across systems, but it does not perform content inspection or classification of sensitive information.

552
MCQeasy

A company wants to collect metrics and logs from all Azure resources in their subscription, including custom metrics from their applications, and create dashboards and alerts. Which Azure service should they use as the primary monitoring platform?

A.Azure Monitor
B.Azure Log Analytics
C.Azure Application Insights
D.Azure Service Health
AnswerA

Azure Monitor is the comprehensive, unified monitoring service that acts as the single pipeline for collecting platform metrics, activity logs, resource logs, and custom telemetry across all Azure resources. It stores metric data in a time-series database and log data in Log Analytics workspaces, then provides a unified query experience, dashboards, and alerting actions. This centralization is what makes it the correct answer for collecting both metrics and logs from every resource in an Azure environment.

Why this answer

Azure Monitor is the correct primary monitoring platform because it serves as the single, unified ingestion and analysis service for all metrics and logs across Azure resources, including custom metrics from applications via the Application Insights SDK or the custom metrics API. It provides a consolidated workspace for creating dashboards, setting alerts, and querying data, making it the foundational service for observability in Azure.

Exam trap

The trap here is that candidates often confuse Azure Monitor with its sub-services like Log Analytics or Application Insights, failing to recognize that Azure Monitor is the umbrella service that encompasses both metrics and logs, while the others are specialized components within it.

How to eliminate wrong answers

Option B (Azure Log Analytics) is wrong because it is a component within Azure Monitor that stores and queries log data, not the overarching monitoring platform; it lacks native support for metrics and dashboards without Azure Monitor as the parent. Option C (Azure Application Insights) is wrong because it is a subset of Azure Monitor focused specifically on application performance monitoring (APM) for live web apps, not a platform for collecting infrastructure metrics or logs from all Azure resources. Option D (Azure Service Health) is wrong because it only provides personalized alerts and guidance for Azure service issues and planned maintenance, not the collection of metrics, logs, or custom application data.

553
MCQmedium

Your organization uses Microsoft Entra ID and has a hybrid identity deployment with Active Directory Domain Services (AD DS) on-premises. You need to synchronize user identities to Microsoft Entra ID, but you must ensure that password hashes are never stored in the cloud. Which synchronization method should you use?

A.Password Hash Sync
B.Federation with AD FS
C.Pass-through Authentication (PTA)
D.Azure AD Connect Cloud Sync
AnswerC

Pass-through Authentication (PTA) is the correct method because it validates users' passwords directly against on-premises Active Directory through a lightweight authentication agent. The password is never written to or stored in Entra ID; it is transmitted to the on-prem agent and only a success/failure response is returned. This satisfies the 'no password hashes in the cloud' requirement exactly and also works with Seamless SSO to provide a user-friendly sign-in experience.

Why this answer

Pass-through Authentication (PTA) is the correct choice because it validates user passwords directly against on-premises Active Directory without ever storing password hashes in Azure AD. This meets the requirement that password hashes are never stored in the cloud, as PTA uses an agent on-premises to authenticate users, and only the validation result is sent to Azure AD.

Exam trap

The trap here is that candidates often confuse Pass-through Authentication with Password Hash Sync, assuming that any synchronization method must store password hashes in the cloud, but PTA avoids this by performing real-time validation without hash storage.

How to eliminate wrong answers

Option A is wrong because Password Hash Sync synchronizes a hash of the user's password to Azure AD, which directly violates the requirement that password hashes are never stored in the cloud. Option B is wrong because Federation with AD FS does not store password hashes in Azure AD, but it introduces a separate federation infrastructure and is not primarily a synchronization method; the question asks for a synchronization method, and AD FS is an identity federation service, not a synchronization tool. Option D is wrong because Azure AD Connect Cloud Sync uses Password Hash Sync by default and can also support Pass-through Authentication, but it is a lightweight synchronization agent that still stores password hashes in the cloud if Password Hash Sync is enabled; the question requires a method that ensures password hashes are never stored, which is not guaranteed by Cloud Sync alone.

554
MCQmedium

A company stores large amounts of log data in Azure Blob Storage. Logs are accessed frequently for the first 30 days, then rarely accessed afterward, but must be retained for 7 years for compliance. The company wants to minimize storage costs. They need to configure automatic data movement and retention policies. Which combination of Azure Blob Storage access tiers and lifecycle management policy should they use?

A.Use Hot tier for 30 days, then use Cool tier for 7 years, with a lifecycle rule to delete after 7 years.
B.Use Hot tier for 30 days, then use Archive tier for the remaining period, with a lifecycle rule to delete after 7 years.
C.Use Cool tier for 30 days, then use Archive tier for 7 years, no lifecycle rule needed.
D.Use Archive tier immediately, with a lifecycle rule to delete after 7 years.
AnswerB

Hot tier provides low-latency access during the frequent access period. Archive tier provides the lowest storage cost for data that is rarely accessed. A lifecycle policy can automatically move data from Hot to Archive after 30 days and delete it after 7 years.

Why this answer

It uses the Hot tier for the first 30 days to handle frequent access, then automatically moves data to the Archive tier via a lifecycle management rule to minimize costs for rarely accessed data, and finally deletes the blobs after 7 years to meet compliance retention requirements. The Archive tier offers the lowest storage cost for long-term retention, making it ideal for logs that are rarely accessed after the initial period.

Exam trap

The trap here is that candidates often choose the Cool tier for long-term retention because they underestimate the cost savings of the Archive tier for data that is rarely accessed over many years, or they forget that a lifecycle rule is necessary to enforce deletion after the compliance period.

How to eliminate wrong answers

Option A is wrong because moving data to the Cool tier after 30 days does not minimize storage costs as effectively as the Archive tier for 7 years of rare access; the Cool tier has higher storage costs than Archive and is intended for data accessed less frequently but still with some latency requirements, not for long-term archival. Option C is wrong because starting with the Cool tier for the first 30 days is suboptimal since logs are accessed frequently during that period, and the Hot tier is more cost-effective for frequent access; additionally, a lifecycle rule is required to delete data after 7 years to enforce compliance retention. Option D is wrong because placing data directly into the Archive tier from the start incurs high retrieval costs and latency for the first 30 days when logs are accessed frequently, violating the requirement to minimize costs and access performance.

555
MCQeasy

You need to design a storage solution for an application that stores large amounts of unstructured data that is accessed frequently for the first 30 days, then rarely after that. Compliance requirements mandate that data be retained for 7 years. Which of the following is the most cost-effective storage solution?

A.Use Azure Files with snapshots and keep files in the Premium tier for 30 days, then move to Standard tier.
B.Use Azure Managed Disks with read-only snapshots and delete snapshots after 7 years.
C.Use Azure Blob Storage with lifecycle management to transition blobs from Hot to Cool to Archive tiers.
D.Store all data in Blob Storage Hot tier and delete after 7 years.
AnswerC

Azure Blob Storage is purpose-built for massive amounts of unstructured object data, offering essentially limitless scale and REST-based access. Lifecycle management lets you define rules to automatically move blobs from Hot to Cool after a set number of days based on last modification, and then from Cool to Archive after a longer period, which optimizes cost while preserving all data. Archive tier provides the lowest storage price for rarely accessed data, and with rehydration you can still retrieve it when needed, making this the most scalable and cost-effective design for long-term retention.

Why this answer

Azure Blob Storage lifecycle management allows you to automatically transition blobs from Hot to Cool after 30 days (once the initial frequent access period ends), and then to Archive after an additional period of low access (e.g., another 30 days) to meet the 7-year retention requirement at the lowest cost. The Archive tier provides the cheapest storage for rarely accessed data, while Hot and Cool tiers optimize for the initial high-access period.

Exam trap

The trap here is that candidates often choose Azure Files or Managed Disks because they associate 'storage' with file shares or disks, but Blob Storage's tiered lifecycle management is the only option that provides automated, cost-optimized transitions for unstructured data with long-term retention.

How to eliminate wrong answers

Option A is wrong because Azure Files Premium tier is designed for low-latency, high-performance workloads (e.g., SQL Server, file shares) and is not cost-effective for large-scale unstructured data; moving to Standard tier still incurs higher costs than Blob Storage tiers, and snapshots do not provide automated tiering. Option B is wrong because Azure Managed Disks are block-level storage for VMs, not optimized for unstructured data; read-only snapshots are incremental and billed per stored data, and deleting them after 7 years does not address the need for cost-effective tiering during the retention period. Option D is wrong because storing all data in the Hot tier for 7 years is significantly more expensive than using Cool and Archive tiers for rarely accessed data, violating the cost-effectiveness requirement.

556
MCQhard

A multinational company uses Microsoft Entra ID with a custom domain. They need to implement a governance strategy for Microsoft 365 groups, ensuring that group expiration policies are enforced and that group owners receive renewal notifications. What should you configure?

A.Microsoft Purview compliance portal – Data Lifecycle Management
B.Microsoft Entra ID – Group settings (Expiration policy)
C.Microsoft Intune – Device compliance policies
D.Microsoft Sentinel – Analytics rules
AnswerB

Microsoft Entra ID – Group settings (Expiration policy) is the correct administrative location because Microsoft 365 group expiration is a tenant-level policy that is enforced by Microsoft Entra ID. In the Entra admin center, you navigate to Identity > Groups > Group settings and configure the 'Expiration policy' to set a fixed validity period (e.g., 180 or 365 days) for all Microsoft 365 groups, with the option to send renewal notifications to group owners. This policy directly controls group lifecycle by automatically expiring inactive groups, and it can also be managed via Microsoft Graph or PowerShell (New-UnifiedGroupExpirationPolicy). This is the native mechanism provided by Microsoft for this exact scenario.

Why this answer

Microsoft Entra ID's Group settings include an expiration policy specifically designed to enforce lifecycle management for Microsoft 365 groups. This policy allows administrators to set a group expiration period (e.g., 180, 365 days) and automatically sends renewal notification emails to group owners before expiration, enabling them to renew the group if needed. This directly meets the requirement for enforcing group expiration and renewal notifications.

Exam trap

The trap here is that candidates often confuse Microsoft Purview's data lifecycle management with group lifecycle management, or mistakenly think Intune or Sentinel can handle group expiration policies, when in fact only Microsoft Entra ID's group settings provide the specific expiration and renewal notification functionality.

How to eliminate wrong answers

Option A is wrong because Microsoft Purview compliance portal – Data Lifecycle Management focuses on retention and deletion of content (e.g., emails, documents) based on labels, not on managing the lifecycle of Microsoft 365 groups or sending renewal notifications to group owners. Option C is wrong because Microsoft Intune – Device compliance policies are used to enforce security and compliance requirements on managed devices (e.g., requiring encryption, PIN), not to manage group expiration or renewal notifications. Option D is wrong because Microsoft Sentinel – Analytics rules are used for security detection and threat hunting by analyzing logs and alerts, not for configuring group expiration policies or sending renewal notifications.

557
MCQeasy

A company uses Microsoft Entra ID for identity management. They want to ensure that users accessing sensitive data from unmanaged devices are prompted for multifactor authentication (MFA) and must accept a terms-of-use. Which policy should be configured?

A.Terms-of-use policy
B.Conditional Access policy
C.Identity Protection policy
D.Privileged Identity Management (PIM) policy
AnswerB

Conditional Access is the correct policy mechanism because it combines signals—such as device platform, join state, compliance status, and location—into conditions that apply at sign-in. You can target unmanaged devices by using a device filter for 'not hybrid Azure AD joined' or 'not compliant', and then require both MFA and an accepted terms-of-use as grant controls. This gives you a single policy that enforces authentication strength and consent only when the device is unmanaged.

Why this answer

Conditional Access policies in Microsoft Entra ID allow granular control over access based on conditions such as device state (managed vs. unmanaged). By configuring a policy that targets unmanaged devices, you can enforce MFA and require acceptance of a terms-of-use before granting access to sensitive data. This directly meets the requirement without needing separate policies for MFA and terms-of-use.

Exam trap

The trap here is that candidates often confuse a standalone Terms-of-use policy (Option A) with the ability to enforce it conditionally, not realizing that Conditional Access is required to tie the terms-of-use acceptance to a specific condition like unmanaged devices.

How to eliminate wrong answers

Option A is wrong because a Terms-of-use policy alone only creates and displays the terms document; it cannot enforce MFA or trigger based on device state. Option C is wrong because Identity Protection policies focus on risk-based signals (e.g., leaked credentials, sign-in anomalies) and do not natively enforce terms-of-use acceptance or device-based conditions. Option D is wrong because Privileged Identity Management (PIM) policies manage just-in-time access and approval workflows for privileged roles, not general user access conditions like device state or MFA enforcement.

558
MCQeasy

Your company is migrating on-premises applications to Azure. You need to ensure that users can sign in using their existing on-premises Active Directory credentials without duplicating accounts. Which identity solution should you recommend?

A.Microsoft Entra B2B collaboration
B.Microsoft Entra External ID
C.Microsoft Entra Connect
D.Microsoft Entra Domain Services
AnswerC

Microsoft Entra Connect is the correct tool for hybrid identity synchronization because it is an on-premises component that synchronizes users, groups, and other directory objects from your Active Directory to Microsoft Entra ID. It supports multiple sign-on methods—password hash synchronization, pass-through authentication, and federation (e.g., AD FS)—so users retain their existing on-premises credentials when accessing Microsoft 365 and other Azure-integrated apps. It also handles ongoing incremental sync, deprovisioning, and device writeback, making it the primary identity bridge between on-prem AD and the cloud.

Why this answer

Microsoft Entra Connect (formerly Azure AD Connect) is the correct solution because it synchronizes on-premises Active Directory identities to Microsoft Entra ID, enabling users to sign in with their existing credentials via password hash synchronization, pass-through authentication, or federation. This avoids duplicating accounts by maintaining a single identity source of truth, with optional seamless single sign-on (SSO) for a transparent experience.

Exam trap

The trap here is that candidates often confuse Microsoft Entra Domain Services (which provides domain-join capabilities for Azure VMs) with identity synchronization, but it does not sync user credentials for cloud app authentication.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra B2B collaboration is designed for external guest users (e.g., partners or vendors) to access your applications using their own identities, not for synchronizing existing on-premises AD users. Option B is wrong because Microsoft Entra External ID is a customer-facing identity platform for external consumer or customer scenarios, not for integrating an organization's own on-premises Active Directory. Option D is wrong because Microsoft Entra Domain Services provides managed domain services (e.g., LDAP, Kerberos, NTLM) for Azure VMs without domain-joining them to an on-premises DC, but it does not synchronize user credentials from on-premises AD for cloud app sign-in.

559
MCQhard

Refer to the exhibit. A company is analyzing Azure Storage diagnostic logs using this KQL query. They notice a high number of GetBlob operations on BlockBlobs. The storage account is used for a web application that serves static content. What should they recommend to reduce the number of GetBlob operations?

A.Implement Azure Blob Storage life cycle management to move data to the archive tier.
B.Use Azure File Sync to cache files on-premises.
C.Enable Azure CDN or Azure Front Door to cache content.
D.Enable Azure Storage Analytics logging to track operations.
AnswerC

Placing Azure CDN or Azure Front Door in front of the blob storage account caches frequently requested content at edge locations, so clients are served cached copies without contacting the storage account. This reduces the number of direct read operations against the blob endpoint, lowering transaction costs and improving response latency. Cache headers, such as Cache-Control, determine the duration and effectiveness of the cache, making this a practical solution for repeated content access.

Why this answer

Enabling Azure CDN or Azure Front Door caches static content at edge locations, reducing the number of direct GetBlob operations against the storage account. This offloads repeated requests from the origin storage, lowering both operational costs and latency for the web application.

Exam trap

The trap here is that candidates may confuse logging (Option D) or lifecycle management (Option A) as solutions to reduce operations, when they only provide monitoring or cost optimization for infrequently accessed data, not a reduction in read requests.

How to eliminate wrong answers

Option A is wrong because lifecycle management moves data to the archive tier, which is designed for cold data and incurs high retrieval costs and latency—it does not reduce GetBlob operations for frequently accessed static content. Option B is wrong because Azure File Sync caches files on-premises for hybrid scenarios, but the question involves a web application serving static content from Azure Storage, not on-premises file sharing; it does not reduce GetBlob operations in Azure. Option D is wrong because enabling Storage Analytics logging tracks operations but does not reduce them; it only provides visibility into existing traffic.

560
MCQeasy

A company has an on-premises data center and wants to connect it to Azure with a dedicated, private network connection that is not routed over the public internet. They also need a higher service-level agreement (SLA) compared to VPN-based connections. Which Azure service should they use?

A.Azure VPN Gateway
B.Azure ExpressRoute
C.Azure Bastion
D.Azure Virtual WAN
AnswerB

Azure ExpressRoute establishes a logical private connection to Azure through a connectivity provider or direct peering, with traffic that never traverses the public internet. It uses BGP sessions over dedicated or co-located circuits, offering enterprise-grade reliability, high bandwidth (up to 100 Gbps), and native geographic redundancy across peering locations. The 99.95% SLA for dedicated circuits plus predictable latency make it the correct choice for a dedicated, private hybrid connection.

Why this answer

Azure ExpressRoute provides a dedicated, private connection from on-premises to Azure that bypasses the public internet, ensuring lower latency, higher reliability, and a 99.95% SLA (for dedicated circuits) compared to VPN-based connections. This meets the requirement for a private network connection with a higher SLA than VPN Gateway, which relies on internet-based IPSec tunnels with a 99.9% SLA.

Exam trap

The trap here is that candidates often confuse Azure Virtual WAN as a direct replacement for ExpressRoute, but Virtual WAN is a management overlay that still requires ExpressRoute or VPN as the underlying transport, not a dedicated private connection itself.

How to eliminate wrong answers

Option A (Azure VPN Gateway) is wrong because it uses IPSec tunnels over the public internet, which does not provide a dedicated private connection and has a lower SLA (99.9%) than ExpressRoute. Option C (Azure Bastion) is wrong because it is a PaaS service for secure RDP/SSH access to Azure VMs via the browser, not a hybrid connectivity solution between on-premises and Azure. Option D (Azure Virtual WAN) is wrong because it is a networking service that aggregates branch connectivity, but it still requires an underlying connectivity method (VPN or ExpressRoute) to provide the dedicated private link; by itself, it does not offer a dedicated private connection or the higher SLA specified.

561
MCQhard

Refer to the exhibit. You are deploying an ARM template to configure backup for an Azure Web App. The deployment fails with an error: 'The resource 'Microsoft.Web/sites/config' cannot be nested under a parent resource that is not deployed.' What is the MOST LIKELY cause?

A.The parent web app resource is not defined in the template
B.The storageAccountUrl property uses a reference() that cannot be resolved
C.The apiVersion '2022-03-01' is not supported for this resource type
D.The backup schedule frequency interval is invalid
AnswerA

In an ARM template, a child resource such as Microsoft.Web/sites/config/backup cannot be deployed unless its parent web app resource (Microsoft.Web/sites) is either defined in the same template or already exists in the resource group. Since the template omits the parent web app resource, Azure Resource Manager cannot resolve the resource identifier and the deployment fails with a validation error. To fix it, you must include the web app in the template and add a dependsOn relationship, or use an existing resource reference with the proper scope.

Why this answer

The error indicates that the ARM template is trying to define a child resource (Microsoft.Web/sites/config) under a parent web app that has not been deployed within the same template. In ARM templates, nested resources require the parent resource to be defined in the same template, typically with a dependsOn element or by nesting the child resource inside the parent's resources array. Since the parent web app is missing from the template, the deployment fails because the resource manager cannot resolve the parent scope.

Exam trap

The trap here is that candidates may confuse a missing parent resource with other common ARM deployment errors, such as invalid API versions or function resolution issues, rather than recognizing the specific nesting constraint error message.

How to eliminate wrong answers

Option B is wrong because a reference() function that cannot be resolved would produce a different error, such as 'Unable to evaluate the template function', not a nesting error. Option C is wrong because apiVersion '2022-03-01' is a valid and supported version for Microsoft.Web/sites/config; the error is unrelated to API version support. Option D is wrong because an invalid backup schedule frequency interval would cause a validation error on the backup configuration itself, not a parent-child nesting error.

562
Multi-Selecteasy

Which TWO Azure services can be used to implement a serverless event-driven architecture that processes messages from a queue and stores results in a database? (Choose two.)

Select 2 answers
A.Azure Logic Apps
B.Azure Event Grid
C.Azure Service Bus
D.Azure Functions
E.Azure Batch
AnswersA, D

Azure Logic Apps is a serverless workflow integration service that can be triggered directly by queue messages from Service Bus or Storage queues. It provides a visual designer with hundreds of connectors, enabling you to orchestrate multi-step workflows across different systems without writing code. Because it runs on demand and scales automatically per execution, it is a valid serverless processing solution for queue-based workloads.

Why this answer

Azure Logic Apps is correct because it provides a serverless workflow engine that can be triggered by a queue (e.g., Azure Service Bus queue or Storage queue) and then process messages using built-in connectors to write results into a database like Azure SQL Database or Cosmos DB. It supports event-driven execution without managing infrastructure, making it ideal for orchestrating message processing and persistence.

Exam trap

The trap here is that candidates often confuse Azure Event Grid or Service Bus as compute services that can process messages and store results, when in reality they are only messaging/event routing layers that require a separate compute service (like Functions or Logic Apps) to perform the actual processing and database writes.

563
MCQhard

A large enterprise is designing a data analytics platform in Azure that will ingest terabytes of data daily from multiple sources, including IoT devices, social media feeds, and internal databases. The data must be stored in a raw format for future processing, and then transformed and aggregated for reporting. The company requires low-latency querying for real-time dashboards and the ability to run complex batch analytics using Spark. The solution must also provide a unified data governance layer for cataloging and lineage tracking. Which combination of Azure services should the company choose to meet all these requirements with minimal operational overhead?

A.Azure Cosmos DB, Azure Stream Analytics, and Azure Analysis Services
B.Azure Blob Storage, Azure HDInsight, and Azure Data Factory
C.Azure SQL Database, Azure Databricks, and Azure Data Catalog
D.Azure Data Lake Storage, Azure Synapse Analytics, and Microsoft Purview
AnswerD

Azure Data Lake Storage Gen2 supplies the required raw landing zone: it combines Blob scalability with a hierarchical namespace and granular POSIX ACLs, enabling governed storage from bytes to petabytes. Azure Synapse Analytics is the analytical core, offering serverless SQL to query raw ADLS files in place, dedicated pools for high-performance warehouse workloads, and built-in Spark for batch transformations--all without separate infrastructure to manage. Microsoft Purview completes the platform by automatically scanning these assets, classifying sensitive data, and capturing end-to-end lineage so downstream analytics can be audited and trusted. Together these services deliver storage, real-time and historical query, batch processing, and governance in one integrated solution.

Why this answer

Azure Data Lake Storage provides scalable, cost-effective raw storage for terabytes of daily data, Azure Synapse Analytics offers both low-latency querying for real-time dashboards and Spark-based batch analytics, and Microsoft Purview delivers a unified data governance layer with cataloging and lineage tracking. This combination minimizes operational overhead by integrating storage, compute, and governance into a single, managed platform.

Exam trap

The trap here is that candidates may choose Azure HDInsight or Azure Databricks for Spark processing, overlooking that Azure Synapse Analytics natively integrates Spark with SQL and governance via Purview, reducing operational overhead compared to managing separate clusters.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a NoSQL database optimized for transactional workloads, not for storing terabytes of raw data or running complex batch analytics with Spark, and Azure Analysis Services is a semantic model layer that does not provide data governance or lineage tracking. Option B is wrong because Azure HDInsight requires manual cluster management and lacks native low-latency querying for real-time dashboards, and Azure Data Factory is an orchestration tool that does not offer unified governance or cataloging. Option C is wrong because Azure SQL Database is a relational database not designed for raw data storage at terabyte scale or Spark-based batch analytics, and Azure Data Catalog is a legacy service that has been superseded by Microsoft Purview, lacking advanced lineage tracking.

564
MCQeasy

You need to configure a monitoring solution for Azure virtual machines that collects performance counters, event logs, and enables alerting based on CPU usage exceeding 90%. Which Azure service should you use?

A.Azure Policy
B.Microsoft Sentinel
C.Azure Monitor
D.Azure Update Manager
AnswerC

Azure Monitor is the core monitoring service in Azure that ingests platform metrics, activity logs, and guest OS telemetry via agents like the Azure Monitor Agent. It supports metric and log-based alerts, custom workbooks, and dashboards for performance counters such as CPU %, memory, and disk I/O, making it the appropriate solution for this monitoring need.

Why this answer

Azure Monitor is the correct service because it provides a unified platform for collecting performance counters and event logs from Azure VMs via the Log Analytics agent or Azure Monitor Agent, and it supports metric-based alert rules that can trigger when CPU usage exceeds a defined threshold (e.g., 90%). This directly meets the requirements for monitoring, log collection, and alerting without additional services.

Exam trap

The trap here is that candidates often confuse Azure Monitor with Microsoft Sentinel because both involve log collection and alerts, but Sentinel is specifically for security incidents, not general performance monitoring and threshold-based alerting on metrics like CPU usage.

How to eliminate wrong answers

Option A is wrong because Azure Policy is a governance tool used to enforce compliance rules (e.g., requiring specific VM SKUs or tags) and does not collect performance counters, event logs, or generate CPU-based alerts. Option B is wrong because Microsoft Sentinel is a Security Information and Event Management (SIEM) solution focused on security threat detection and incident response, not general performance monitoring and alerting for CPU usage. Option D is wrong because Azure Update Manager is designed solely for managing OS updates and patches on VMs, with no capability to collect performance counters, event logs, or alert on CPU utilization.

565
MCQhard

A company runs a critical SQL Server database on an Azure virtual machine. They need a high-availability solution within a single region that provides automatic failover, zero data loss (synchronous replication), and support read-only routing for reporting workloads. Which solution should they implement?

A.SQL Server Always On Availability Group with synchronous replication across availability zones
B.SQL Server Always On Failover Cluster Instance (FCI) with shared disks
C.Azure SQL Database Managed Instance with active geo-replication
D.Azure SQL Database with active geo-replication
AnswerA

An Always On Availability Group is correct because it replicates the database at the data-page level to a secondary replica using synchronous commit, so every transaction is hardened on both replicas before being acknowledged and automatic failover can occur with zero data loss. Because the secondary replica maintains a separate copy of the database, it can be configured as readable, allowing reporting and backup workloads to be offloaded from the primary. Deployed across availability zones, this protects against complete zone failure while remaining fully compatible with SQL Server on Azure VMs.

Why this answer

SQL Server Always On Availability Group with synchronous replication across availability zones meets all requirements: it provides automatic failover, zero data loss through synchronous commit mode, and supports read-only routing by directing reporting workloads to readable secondary replicas. This solution operates within a single Azure region using availability zones for high availability.

Exam trap

The trap here is that candidates confuse synchronous replication (used in Always On Availability Groups) with asynchronous replication (used in geo-replication), and fail to recognize that read-only routing is a feature exclusive to Availability Groups, not Failover Cluster Instances or geo-replication solutions.

How to eliminate wrong answers

Option B is wrong because a Failover Cluster Instance (FCI) with shared disks does not support read-only routing for reporting workloads; FCI provides a single instance with no readable secondary replicas. Option C is wrong because Azure SQL Database Managed Instance with active geo-replication uses asynchronous replication, which cannot guarantee zero data loss, and it is designed for cross-region disaster recovery, not single-region high availability. Option D is wrong because Azure SQL Database with active geo-replication also uses asynchronous replication, resulting in potential data loss, and it is a cross-region solution, not a single-region high-availability solution.

566
MCQmedium

A company uses Azure SQL Database (Premium tier) for their application. They need to offload reporting queries to a read-only copy of the database to reduce load on the primary. The read-only copy must be kept in sync synchronously within the same Azure region. They also need automated failover to the read-only copy if the primary fails. Which Azure SQL Database feature should they enable?

A.Active geo-replication
B.Auto-failover groups
C.Read Scale-Out
D.Database copy
AnswerC

Read Scale-Out uses the built-in, always-on secondary replica that is automatically maintained in the same region for Premium and Business Critical service tiers. The replica is kept synchronously updated with the primary, meaning reporting queries can be routed to the read-only endpoint with minimal lag. This feature also supports automatic failover, so the read-only replica can become the new primary if the current primary fails, making it a proper solution for in-region read offload.

Why this answer

Read Scale-Out is the correct feature because it offloads reporting queries to a read-only replica that stays synchronously committed within the same Azure region. It also provides automated failover to the read-only replica if the primary database fails, meeting both the synchronous sync and failover requirements for Premium-tier Azure SQL Database.

Exam trap

The trap here is that candidates confuse cross-region disaster recovery features (Active geo-replication and Auto-failover groups) with in-region high availability and read-scale capabilities, overlooking that Read Scale-Out is the only option that provides synchronous replication and automated failover within the same Azure region.

How to eliminate wrong answers

Option A is wrong because Active geo-replication creates asynchronous replicas in different Azure regions, not synchronous replicas within the same region, and it does not support automated failover. Option B is wrong because Auto-failover groups rely on Active geo-replication and are designed for cross-region failover with asynchronous replication, not for synchronous in-region read-only offloading. Option D is wrong because Database copy creates a point-in-time snapshot that is not kept in sync synchronously and does not provide automated failover.

567
MCQmedium

A company is deploying a web application on Azure App Service. The application must authenticate users with their Microsoft Entra ID credentials. The development team wants to use the Microsoft Authentication Library (MSAL) for authentication. Which App Service authentication feature should they use to simplify integration?

A.Use Application Insights to capture authentication logs
B.Use Azure API Management to handle authentication
C.Use Azure AD B2C for identity management
D.Configure the App Service authentication / authorization feature to use Microsoft Entra ID
AnswerD

Configuring the App Service authentication/authorization feature, also known as Easy Auth, is the correct approach because it natively integrates with Microsoft Entra ID and handles sign-in, token validation, and session management without custom code. It runs as a middleware layer in the platform, redirects unauthenticated users to Entra ID, and injects user claims into the application. This is the simplest, most secure method for an internal enterprise app.

Why this answer

The App Service authentication / authorization feature (also known as Easy Auth) provides a built-in, code-free integration with Microsoft Entra ID. By enabling this feature and configuring it to use Microsoft Entra ID, the App Service automatically handles token validation, session management, and redirects, allowing the development team to use MSAL on the client side for sign-in without writing server-side authentication logic.

Exam trap

The trap here is that candidates often overcomplicate the solution by choosing Azure API Management or Azure AD B2C, not realizing that App Service's built-in authentication feature is specifically designed to simplify integration with Microsoft Entra ID and MSAL without additional infrastructure.

How to eliminate wrong answers

Option A is wrong because Application Insights is a monitoring and diagnostics service that captures telemetry data (including authentication logs), but it does not handle authentication or simplify integration with MSAL. Option B is wrong because Azure API Management is an API gateway that can enforce authentication policies, but it is an additional layer that adds complexity and is not the simplest way to integrate MSAL with App Service. Option C is wrong because Azure AD B2C is designed for customer-facing identity management with social and local accounts, not for authenticating users with their existing Microsoft Entra ID credentials in a corporate scenario.

568
MCQeasy

You need to design a monitoring solution for a set of Azure virtual machines running a business-critical application. The solution must provide centralized log management, enable real-time analysis of security events, and support custom alerts for anomalous behavior. Which Azure service should you use?

A.Azure Log Analytics
B.Microsoft Defender for Cloud
C.Azure Monitor
D.Microsoft Sentinel
AnswerD

Microsoft Sentinel is a cloud-native, scalable SIEM (Security Information and Event Management) solution that builds on Azure Log Analytics to provide centralized log management, analysis, and custom alerting across your entire digital estate. It ingests data from hundreds of sources—Microsoft services, third-party firewalls, cloud workloads, and on-premises systems—then uses KQL queries, analytics rules, and machine learning to detect threats, and its SOAR capabilities automate incident response. Sentinel also offers entity behavior analytics and integrated threat intelligence, making it the only option listed that meets the stated requirement for a monitoring solution that includes log management, security analysis, and custom alerts.

Why this answer

Microsoft Sentinel is the correct choice because it is a cloud-native SIEM (Security Information and Event Management) and SOAR (Security Orchestration, Automation, and Response) solution that provides centralized log management, real-time security event analysis, and built-in support for custom analytics rules to detect anomalous behavior. Unlike Azure Monitor or Log Analytics, Sentinel is specifically designed for security-focused monitoring and can ingest logs from multiple sources, including Azure VMs, and use machine learning to identify threats.

Exam trap

The trap here is that candidates often confuse Azure Monitor (a general monitoring tool) with Microsoft Sentinel (a dedicated SIEM), failing to recognize that the question's emphasis on 'security events' and 'anomalous behavior' points to a security-specific solution, not just log aggregation.

How to eliminate wrong answers

Option A is wrong because Azure Log Analytics is a log storage and query service that lacks native SIEM capabilities such as real-time security event correlation and automated response; it requires additional services like Sentinel to provide security monitoring. Option B is wrong because Microsoft Defender for Cloud is a cloud security posture management (CSPM) and workload protection tool that focuses on vulnerability assessment and security recommendations, not centralized log management or custom alerting for anomalous behavior across all logs. Option C is wrong because Azure Monitor is a platform monitoring service for performance and availability metrics, not a SIEM; it does not provide real-time security event analysis or built-in threat detection rules.

569
MCQmedium

A company runs a SQL Server database on an Azure virtual machine. They need to increase the storage capacity and improve I/O performance for their transaction log. The current data disk is a standard HDD. They want to achieve higher IOPS and throughput without increasing the size of the VM (the VM size supports up to 8 data disks). The database workload is write-intensive on the transaction log. Which configuration should they implement?

A.Add additional standard HDD disks and configure a storage pool with simple (striping) layout
B.Replace the standard HDD disk with a premium SSD disk for the log drive
C.Add a premium SSD disk and configure a storage space with mirroring for the log drive
D.Use Azure Disk Encryption to improve performance
AnswerB

Replacing the Standard HDD with a Premium SSD for the log drive directly addresses the bottleneck because SQL Server transaction log writes are serial and must be durable before a transaction is acknowledged; even modest write latency directly lengthens commit times. Azure Premium SSDs deliver per-disk IOPS and throughput up to an order of magnitude higher than Standard HDDs, with consistent single-digit-millisecond latencies (and sub-millisecond with burst). This change also guarantees predictable performance levels via the Azure disk SLA, allowing the log I/O path to keep pace with checkpoint and commit activity without introducing any additional software layers. It is the most appropriate, focused action for a write-intensive log workload on an Azure VM.

Why this answer

Replacing the standard HDD with a premium SSD directly addresses the need for higher IOPS and throughput for a write-intensive transaction log. Premium SSDs provide consistent low-latency performance and significantly higher IOPS/throughput compared to standard HDDs, without requiring a VM size change. Since the VM supports up to 8 data disks, a single premium SSD can meet the performance requirements more effectively than adding more HDDs.

Exam trap

The trap here is that candidates may think striping (Option A) or mirroring (Option C) with premium disks is needed for performance, but for a single transaction log file, a single premium SSD is sufficient and simpler, while mirroring adds unnecessary write overhead and striping with HDDs still yields poor IOPS.

How to eliminate wrong answers

Option A is wrong because adding more standard HDD disks and striping them in a storage pool still uses slow HDDs, which cannot deliver the required IOPS and throughput for a write-intensive transaction log; striping improves throughput but not latency or IOPS per disk. Option C is wrong because adding a premium SSD with mirroring (instead of using it as a single log drive) introduces unnecessary redundancy that does not improve write performance for a transaction log, and mirroring reduces usable capacity and can add write overhead. Option D is wrong because Azure Disk Encryption only provides encryption at rest and does not affect I/O performance; it can even introduce a slight CPU overhead for encryption/decryption operations.

570
MCQeasy

A company plans to deploy a stateless web application on Azure virtual machines. They want to ensure that the application remains available in the event of a hardware failure within a single Azure datacenter. The VMs must be placed in a way that ensures they are on different physical servers and racks, but are still within the same datacenter. Which deployment strategy should they use?

A.Deploy the VMs in an Availability Set.
B.Deploy the VMs in different Availability Zones.
C.Deploy the VMs in a single Virtual Machine Scale Set with a large instance count.
D.Deploy each VM in a separate resource group.
AnswerA

An Availability Set logically groups VMs so Azure distributes them across multiple fault domains (racks with independent power and network) and update domains (groups that are rebooted sequentially during planned maintenance). This contains hardware failures and maintenance events to a subset of the VMs, keeping your stateless web app reachable. It is the correct choice because the requirement is to protect against hardware failure within a single Azure datacenter.

Why this answer

An Availability Set ensures that VMs are distributed across multiple fault domains (different physical servers, racks, and network switches) and update domains within a single Azure datacenter. This protects against hardware failures in that datacenter by guaranteeing that not all VMs are affected by the same local failure, while keeping them in the same datacenter for low-latency communication.

Exam trap

The trap here is that candidates often confuse Availability Zones (which span multiple datacenters) with Availability Sets (which operate within a single datacenter), leading them to select the zone-based option when the question explicitly requires staying within the same datacenter.

How to eliminate wrong answers

Option B is wrong because Availability Zones place VMs in physically separate datacenters within a region, not within the same datacenter, which adds cross-datacenter latency and is not required for the stated goal of surviving a single datacenter hardware failure. Option C is wrong because a single Virtual Machine Scale Set with a large instance count does not by itself enforce distribution across different physical servers and racks unless it is configured with an Availability Set or Availability Zones; a scale set without such placement constraints can place many VMs on the same physical host. Option D is wrong because deploying each VM in a separate resource group has no impact on physical placement or fault domain isolation; resource groups are logical containers for management and RBAC, not for infrastructure redundancy.

571
MCQmedium

A company runs a critical SQL Server database on an Azure virtual machine. They need a backup strategy that supports point-in-time restore down to the second and long-term retention of backups for 7 years to meet compliance. They want to offload backup management to Azure. Which backup solution should they use?

A.Azure Backup for SQL Server on Azure VM
B.Azure Site Recovery
C.SQL Server managed backup to Azure
D.Azure Disk Backup
AnswerA

Azure Backup for SQL Server on Azure VM is a fully managed backup service that integrates with the SQL Server IaaS Agent Extension, automating full, differential, and transaction log backups. It supports point-in-time restore with log backups taken every 15 minutes, and offers long-term retention policies for up to 10 years, meeting both operational recovery and compliance requirements. The centralized monitoring, alerting, and cross-subscription management capabilities make it the ideal choice for a critical SQL database.

Why this answer

Azure Backup for SQL Server on Azure VM provides native integration that supports point-in-time restore down to the second for SQL Server databases and allows configuring long-term retention (LTR) for up to 10 years, meeting the 7-year compliance requirement. It offloads backup management to Azure by automating backup schedules, retention policies, and restore operations without requiring manual scripting or third-party tools.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery (disaster recovery) with backup, or assume SQL Server managed backup to Azure provides the same integrated point-in-time and long-term retention capabilities as Azure Backup, when in fact Azure Backup offers a fully managed, portal-integrated solution with native SQL Server awareness.

How to eliminate wrong answers

Option B is wrong because Azure Site Recovery is a disaster recovery solution that replicates entire VMs for failover, not a backup service; it does not support point-in-time restore for SQL Server databases or long-term retention for compliance. Option C is wrong because SQL Server managed backup to Azure is a feature that manages backups to Azure Blob storage but requires manual configuration of retention policies and does not offer native point-in-time restore down to the second or integrated long-term retention management within the Azure portal. Option D is wrong because Azure Disk Backup provides crash-consistent backups of managed disks at the VM level, not application-consistent backups for SQL Server, and cannot perform point-in-time restore for database transactions or log backups.

572
MCQmedium

Refer to the exhibit. A custom role is created. A user assigned this role reports being unable to view the VM's boot diagnostics in the Azure portal. What is the most likely reason?

A.The user does not have permission to start or restart the VM
B.The VM is stopped and deallocated
C.The role lacks permissions to the diagnostics storage account
D.The role does not include Microsoft.Compute/virtualMachines/read
AnswerC

Boot diagnostics requires the user to have read access to the storage account that stores the diagnostic data, such as Microsoft.Storage/storageAccounts/listKeys/action or a data-plane reader role on that account. The custom role only grants Compute actions on the VM and omits Storage actions, so the portal cannot retrieve the screenshot from the diagnostics container. This missing storage-scope authorization is the exact reason the boot diagnostics image cannot be viewed.

Why this answer

Boot diagnostics in Azure require access to a storage account where the serial console output and screenshots are stored. Even if the user has Microsoft.Compute/virtualMachines/read permission on the VM, they must also have the appropriate role (e.g., Storage Blob Data Reader) on the diagnostics storage account to read the boot diagnostics data. Without this, the portal will show an error or blank boot diagnostics pane.

Exam trap

The trap here is that candidates assume boot diagnostics are a property of the VM itself, when in reality they are stored in a separate storage account that requires explicit permissions beyond the VM scope.

How to eliminate wrong answers

Option A is wrong because starting or restarting a VM is not a prerequisite for viewing boot diagnostics; boot diagnostics are historical logs and screenshots that can be accessed regardless of the VM's power state. Option B is wrong because a stopped and deallocated VM still retains its boot diagnostics data in the storage account; the user should still be able to view the last boot logs. Option D is wrong because Microsoft.Compute/virtualMachines/read is likely included in the custom role (otherwise the user would not be able to see the VM at all), and the issue is specifically about accessing the storage account, not the VM resource itself.

573
MCQmedium

A company has an on-premises Hyper-V environment with 20 virtual machines running various workloads. They want to use Azure as a disaster recovery site. The required recovery point objective (RPO) is 15 minutes, and the recovery time objective (RTO) is 2 hours. They want to automate failover and failback. Which Azure service should they use?

A.Azure Site Recovery
B.Azure Migrate
C.Azure Backup
D.Azure Recovery Services Vault
AnswerA

Azure Site Recovery is the only option that provides continuous, near-synchronous replication of Hyper-V VMs to Azure, with RPOs as low as 30 seconds and the ability to meet a 15-minute RPO. It uses the Azure Site Recovery Provider installed on the Hyper-V host and the Microsoft Recovery Services Agent, replicating VHDs to Azure storage while enabling orchestrated test failovers, planned/unplanned failovers, and failback. This is true disaster recovery, not backup or migration.

Why this answer

Azure Site Recovery (ASR) is the correct service because it provides orchestrated replication, failover, and failback for Hyper-V VMs to Azure as a DR site. It supports the required RPO of 15 minutes (using near-synchronous replication with change tracking) and RTO of 2 hours (via automated recovery plans), and it natively automates both failover and failback processes without additional scripting.

Exam trap

The trap here is that candidates confuse the Recovery Services Vault (a storage container) with the actual DR service (Azure Site Recovery), or they mistakenly think Azure Backup can meet low RPO/RTO requirements for disaster recovery when it is designed for backup, not replication with automated failover.

How to eliminate wrong answers

Option B (Azure Migrate) is wrong because it is designed for discovery, assessment, and migration of on-premises workloads to Azure, not for ongoing disaster recovery replication or automated failover/failback. Option C (Azure Backup) is wrong because it provides backup-based recovery with typical RPOs of 12-24 hours and RTOs measured in hours to days, and it does not support automated failover or failback orchestration. Option D (Azure Recovery Services Vault) is wrong because it is a storage container that holds backup data and replication settings, not a service that performs replication, failover, or failback; it is the underlying vault used by both Azure Backup and Azure Site Recovery, but the question asks for the service that automates DR, which is ASR.

574
MCQmedium

A company stores JSON documents for a mobile app backend. The data needs to be accessible from multiple global regions with low latency writes from any region. The app uses a client-side library that supports automatic conflict resolution for concurrent updates. Which Azure data service should they choose?

A.Azure Cosmos DB
B.Azure SQL Database
C.Azure Database for PostgreSQL
D.Azure Table Storage
AnswerA

Azure Cosmos DB is the correct choice because it provides native multi-region writes, enabling the same JSON document to be written and updated from any Azure region with automatic conflict resolution to handle concurrent edits. Its flexible schema and JSON-native indexing make it purpose-built for storing and querying mobile app backend documents, and it offers well-defined consistency levels and an SLA for availability and latency.

Why this answer

Azure Cosmos DB is correct because it provides multi-region writes with automatic conflict resolution, which directly matches the requirement for low-latency writes from any global region. Its multi-master replication model allows any region to accept writes, and the client-side library can use last-writer-wins (LWW) or custom conflict resolution policies to handle concurrent updates seamlessly.

Exam trap

The trap here is that candidates often confuse Azure SQL Database or Azure Database for PostgreSQL's read replicas with write capability, failing to recognize that only Cosmos DB offers true multi-region writes with built-in conflict resolution.

How to eliminate wrong answers

Option B (Azure SQL Database) is wrong because it does not natively support multi-region writes; it relies on a single primary region for writes, and geo-replication is read-only, so it cannot achieve low-latency writes from multiple regions. Option C (Azure Database for PostgreSQL) is wrong because it also uses a single-writer primary architecture; while read replicas can be distributed, writes must go to the primary region, introducing latency for global writes. Option D (Azure Table Storage) is wrong because it does not support multi-region writes; it offers only a single write region with read-only geo-redundant storage, and it lacks built-in conflict resolution for concurrent updates.

575
MCQmedium

A company needs to store sensor data from IoT devices. Each device sends a message every second. The data is time-series and will be queried for real-time dashboards and historical analysis. The solution must support high ingestion rates and low-latency queries on recent data. Which Azure service should they use?

A.Azure Blob Storage with Azure Data Lake Storage Gen2
B.Azure Cosmos DB with SQL API
C.Azure Event Hubs and Azure Data Explorer
D.Azure Table Storage
AnswerC

Azure Event Hubs and Azure Data Explorer form the native Azure pattern for IoT sensor data because Event Hubs offers high-throughput, low-latency event streaming with partitioning and auto-inflate, easily handling millions of sensor messages per second. Azure Data Explorer (ADX) is a purpose-built analytics engine for time-series and log data, using columnar storage and an optimized ingestion pipeline that can directly consume streams from Event Hubs. ADX's KQL query language delivers real-time aggregations over large temporal windows in sub-second latency, making it ideal for live dashboards. This combination decouples ingestion from analytics while providing end-to-end scalability and low operational overhead.

Why this answer

Azure Event Hubs is designed for high-throughput data ingestion from millions of IoT devices, capable of handling millions of events per second. Azure Data Explorer (ADX) is optimized for time-series data, providing sub-second query latency on recent data and efficient historical analysis. Together, they form a serverless pipeline that ingests sensor data via Event Hubs and stores it in ADX for real-time dashboards and long-term analytics.

Exam trap

The trap here is that candidates often choose Azure Cosmos DB (Option B) because they associate it with 'low latency' and 'IoT', but they overlook that Cosmos DB is not purpose-built for time-series data and lacks the ingestion throughput and query optimizations that Azure Data Explorer provides for this specific workload.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage with Data Lake Storage Gen2 is optimized for batch analytics and large file storage, not for high-frequency time-series ingestion or low-latency queries on recent data; it lacks native time-series indexing and real-time query capabilities. Option B is wrong because Azure Cosmos DB with SQL API is a multi-model NoSQL database designed for transactional workloads with flexible schemas, but it is not optimized for time-series data at high ingestion rates and can incur high RU costs for continuous writes; it also lacks native time-series functions like binning or retention policies. Option D is wrong because Azure Table Storage is a key-value store with limited query capabilities (only on partition and row keys), no support for time-series-specific operations, and high latency for range scans over timestamps, making it unsuitable for real-time dashboards and high-ingestion IoT workloads.

576
MCQmedium

A company uses Azure Kubernetes Service (AKS) to run a containerized microservices application. They need a disaster recovery solution that can automatically fail over to a secondary region if the primary region fails. The solution must minimize data loss for stateful workloads. What should they implement?

A.Azure Backup for AKS
B.Azure Front Door
C.Azure Traffic Manager
D.Azure Site Recovery
AnswerD

Azure Site Recovery provides continuous replication of virtual machines and their associated data disks across Azure regions. This technical mechanism ensures a low Recovery Point Objective (RPO), directly addressing the need to minimise data loss for stateful workloads running within AKS by replicating their underlying persistent storage. Furthermore, Site Recovery orchestrates automated failover to a secondary region, satisfying the requirement for automatic disaster recovery.

Why this answer

Azure Site Recovery (ASR) is the correct choice because it provides orchestrated replication and failover for Azure VMs and physical workloads, including stateful containers running on AKS. ASR can replicate persistent volumes and application data to a secondary region, enabling automated failover with minimal data loss by using crash-consistent or app-consistent recovery points.

Exam trap

The trap here is that candidates often confuse traffic routing services (Azure Front Door or Traffic Manager) with actual disaster recovery replication, overlooking that stateful workloads require data replication, not just traffic redirection.

How to eliminate wrong answers

Option A is wrong because Azure Backup for AKS only provides backup and restore capabilities, not automated failover to a secondary region; it is designed for point-in-time recovery, not continuous replication. Option B is wrong because Azure Front Door is a global load balancer and application delivery controller that routes HTTP/HTTPS traffic, but it does not replicate or fail over stateful workloads or persistent data. Option C is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that can redirect traffic to a secondary region, but it does not handle data replication or stateful workload failover; it only manages traffic routing at the DNS level.

577
MCQmedium

Refer to the exhibit. You are deploying an ARM template with the above parameters. After deployment, you need to ensure that the storage account automatically moves blobs that are not accessed for 30 days to the archive tier. What should you do?

A.Enable soft delete for blobs.
B.Change the 'accessTier' parameter value to 'Archive'.
C.Change the 'replication' parameter value to 'GRS'.
D.Add a lifecycle management policy rule to the storage account.
AnswerD

Adding a lifecycle management policy rule to the storage account is the precise mechanism required. These policies enable automated tiering of blobs based on user-defined rules. A specific rule can be configured to identify blobs that have not been accessed for 30 days and then automatically transition them to the archive tier, directly satisfying the requirement for automatic movement based on access time. This ensures efficient cost management for infrequently accessed data.

Why this answer

Azure Storage lifecycle management policies allow you to automatically move blobs to cooler tiers (like Archive) based on age or last access time. By adding a rule with a filter for blobs not accessed in 30 days and an action to tier to Archive, you meet the requirement without manual intervention or changing the default access tier.

Exam trap

The trap here is that candidates often confuse setting the default access tier (via 'accessTier' parameter) with automating tier transitions based on age, leading them to choose Option B instead of recognizing that lifecycle management policies are required for time-based auto-tiering.

How to eliminate wrong answers

Option A is wrong because soft delete for blobs protects against accidental deletion by retaining deleted blobs for a specified period; it does not move blobs to a different access tier. Option B is wrong because changing the 'accessTier' parameter to 'Archive' would set the default tier for new blobs, but it does not automatically move existing blobs that are not accessed for 30 days; lifecycle management is needed for time-based tier transitions. Option C is wrong because changing replication to GRS (geo-redundant storage) affects durability and disaster recovery, not the access tier of blobs based on access patterns.

578
MCQmedium

A company is designing a hybrid network solution connecting an on-premises data center to Azure. They require high availability with active-active routing and need to support up to 10 Gbps throughput. Which Azure service should they include in the design?

A.Site-to-Site VPN Gateway
B.Azure Virtual WAN
C.ExpressRoute FastPath
D.ExpressRoute Direct
AnswerD

ExpressRoute Direct provides a dedicated, private Layer-2 connection between your on-premises network and Microsoft's edge at a peering location, with port pairs available at 10 Gbps, 40 Gbps, or 100 Gbps. Since it delivers physical port-level bandwidth rather than a VPN gateway's aggregate limit, it easily satisfies the 10 Gbps throughput requirement. It also supports active-active routing by default through dual routers and BGP sessions, giving the required high availability with an SLA-backed redundant path.

Why this answer

ExpressRoute Direct provides dedicated, private connections from on-premises to Azure, supporting bandwidths up to 100 Gbps (10 Gbps easily). It enables active-active routing by using two circuits with BGP, meeting high availability and throughput requirements. ExpressRoute FastPath is a performance feature that reduces latency but is not a standalone service and does not itself provide active-active routing or guaranteed throughput; it requires an ExpressRoute circuit and does not replace the need for Direct when dedicated throughput is required.

Exam trap

A common mistake is assuming that ExpressRoute FastPath is a standalone service that can provide active-active routing and 10 Gbps throughput. In reality, FastPath is a feature that enhances performance but must be used with an existing ExpressRoute circuit. For dedicated bandwidth and native active-active routing, ExpressRoute Direct is the appropriate service.

How to eliminate wrong answers

Option A is wrong because Site-to-Site VPN Gateway is limited to a maximum throughput of approximately 1.25 Gbps per tunnel (aggregate up to 10 Gbps only with multiple tunnels and specific SKUs), and it relies on the public internet, which does not guarantee the consistent 10 Gbps throughput or the same SLA as a private connection. Option B is wrong because Azure Virtual WAN is a networking orchestration service that can aggregate multiple connection types, but it does not itself provide the high-throughput, dedicated private connectivity required; it would typically use ExpressRoute circuits underneath for such throughput, making it an architectural overlay rather than the direct service needed. Option D is wrong because ExpressRoute FastPath is a feature that improves network performance by bypassing the gateway for certain traffic flows, but it is not a standalone service; it must be enabled on an existing ExpressRoute circuit and does not itself provide the 10 Gbps throughput or active-active routing—it enhances performance after the circuit is in place.

579
MCQmedium

An application requires a highly available key-value store with sub-millisecond read and write latencies across multiple Azure regions. The data model is simple and does not require complex queries. Which Azure data store should they choose?

A.Azure SQL Database
B.Azure Table Storage
C.Azure Cosmos DB
D.Azure Cache for Redis
AnswerC

Azure Cosmos DB is a globally distributed, multi-model database purpose-built for key-value workloads, offering turnkey multi-region writes and a 99.999% availability SLA for multiple-region configurations. Requests are served with single-digit millisecond latencies, and you can select from multiple consistency levels (eventual, session, bounded staleness, strong) to trade consistency for performance. Cosmos DB supports key-value schemas through its core (SQL), Table API, Cassandra API, and MongoDB API, making it the only option that fully satisfies the combination of global scale, high availability, and low latency.

Why this answer

Azure Cosmos DB is the correct choice because it provides a globally distributed, multi-region key-value store with guaranteed sub-10-millisecond read and write latencies at the 99th percentile, and supports multiple consistency models including eventual consistency for even lower latency. Its turnkey global distribution enables active-active replication across Azure regions, meeting the high availability and sub-millisecond performance requirements without complex query support.

Exam trap

The trap here is that candidates often confuse Azure Cache for Redis as a primary data store due to its sub-millisecond performance, but it lacks global distribution and durability guarantees, making Cosmos DB the correct choice for a highly available, multi-region key-value store.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a relational database that requires complex schema design, does not natively support sub-millisecond key-value access patterns, and its geo-replication is not designed for active-active multi-region writes with single-digit millisecond latencies. Option B is wrong because Azure Table Storage is a NoSQL key-value store but it is not globally distributed by default, has higher latency (typically 10-50 ms), and does not offer sub-millisecond performance or multi-region write capabilities. Option D is wrong because Azure Cache for Redis is an in-memory cache that does not provide native multi-region replication or persistence guarantees required for a durable key-value store, and its primary use case is caching, not a fully managed globally distributed data store.

580
MCQmedium

A company needs to store audit logs for 7 years to meet compliance requirements. The logs are generated at a high volume and must be cost-effective. They need to run occasional queries on recent logs (less than 30 days old) but rarely on older ones. Which Azure storage solution should they recommend?

A.Azure Blob Storage with lifecycle management to Archive tier
B.Azure SQL Database
C.Azure Cosmos DB
D.Azure Log Analytics
AnswerA

Azure Blob Storage is an object storage service designed to hold massive amounts of unstructured data, making it ideal for high-volume audit logs. Lifecycle management can automatically move blobs from Hot to Cool to Archive based on age or last-modification time, so after 7 years the logs reside in the Archive tier, which offers the lowest storage cost. The Archive tier provides acceptable retrieval latency (minutes to hours) for compliance access, and optional immutability policies prevent tampering.

Why this answer

Azure Blob Storage with lifecycle management to the Archive tier is the correct solution because it provides a cost-effective storage hierarchy for high-volume audit logs. Lifecycle management can automatically move logs from the Hot or Cool tier to the Archive tier after 30 days, aligning with the requirement to keep recent logs queryable while minimizing costs for older logs that are rarely accessed. The Archive tier offers the lowest storage cost, making it ideal for 7-year retention of audit data.

Exam trap

The trap here is that candidates often choose Azure Log Analytics (Option D) because it is associated with logs, but they overlook its retention limits and high cost for long-term storage, failing to recognize that Azure Blob Storage with lifecycle management is the correct archival solution for compliance-driven retention.

How to eliminate wrong answers

Option B (Azure SQL Database) is wrong because it is a relational database designed for transactional workloads and structured queries, not for cost-effective storage of high-volume, append-only audit logs; its storage costs are significantly higher than blob storage for large data volumes. Option C (Azure Cosmos DB) is wrong because it is a NoSQL database optimized for low-latency, globally distributed applications, not for long-term, cost-efficient archival of audit logs; its provisioned throughput and storage costs make it prohibitively expensive for this use case. Option D (Azure Log Analytics) is wrong because it is a monitoring and analytics service designed for real-time log ingestion and querying, not for long-term archival storage; its retention limits (default 30 days, up to 2 years with additional cost) cannot meet the 7-year compliance requirement cost-effectively.

581
Multi-Selecteasy

Which TWO Azure services can be used to store unstructured data such as documents, images, and videos?

Select 2 answers
A.Azure Blob Storage
B.Azure Files
C.Azure SQL Database
D.Azure Data Lake Storage Gen2
E.Azure Cosmos DB
AnswersA, D

Azure Blob Storage is Microsoft's object storage solution, specifically engineered to store and serve massive amounts of unstructured data—such as images, videos, documents, logs, and backup files—at global scale. It exposes REST-based HTTP(S) endpoints, supports lifecycle management across hot/cool/archive access tiers, and provides cost-effective redundancy options. Because each object is addressed by a unique URL and stored without a required schema, Blob Storage is the canonical service for unstructured data in Azure.

Why this answer

Azure Blob Storage is designed for storing massive amounts of unstructured data, such as documents, images, and videos, as objects (blobs) in a flat namespace. It supports three types of blobs (block, append, and page) and provides REST APIs for access, making it ideal for scalable, cost-effective storage of binary and text data.

Exam trap

The trap here is that candidates often confuse Azure Files (a file share service) with unstructured storage, but Azure Files is for structured file sharing with SMB/NFS, not for object storage of documents, images, and videos.

582
MCQmedium

A company has several Azure Virtual Machines running Windows Server with critical applications. They need to back up these VMs to a secondary Azure region to protect against regional disasters. The backup must be application-consistent and support file-level restore. Which solution should they implement?

A.Azure Backup with geo-redundant storage (GRS) in a Recovery Services vault
B.Azure Site Recovery
C.Azure Snapshot of managed disks stored in a different region
D.Azure Managed Disk with incremental snapshots and manual cross-region copy
AnswerA

Azure Backup with GRS replicates backup data to a paired secondary region, satisfying the regional disaster requirement. Volume Shadow Copy Service (VSS) provides application-consistent snapshots of Windows Server workloads, and the Recovery Services vault supports file-level recovery from those snapshots.

Why this answer

Azure Backup with geo-redundant storage (GRS) in a Recovery Services vault is the correct solution because it provides application-consistent backups of Windows Server VMs using the Volume Shadow Copy Service (VSS) to ensure data integrity, and it supports file-level restore by allowing you to mount the backup as a drive to recover individual files. The GRS option replicates backup data to a paired secondary region, meeting the disaster recovery requirement without additional manual steps.

Exam trap

The trap here is that candidates confuse Azure Site Recovery (a replication/failover tool) with Azure Backup (a backup/restore tool), or assume that crash-consistent snapshots (Options C and D) are sufficient for application consistency and file-level restore, which they are not.

How to eliminate wrong answers

Option B (Azure Site Recovery) is wrong because it is designed for replication and failover of VMs for disaster recovery, not for backup—it does not support file-level restore from backup snapshots and is not a backup solution. Option C (Azure Snapshot of managed disks stored in a different region) is wrong because snapshots are crash-consistent, not application-consistent, and they do not support file-level restore natively; you would need to create a new disk from the snapshot to access files. Option D (Azure Managed Disk with incremental snapshots and manual cross-region copy) is wrong because incremental snapshots are also crash-consistent and require manual cross-region copy, which adds complexity and does not guarantee application consistency or built-in file-level restore capabilities.

583
MCQeasy

A company deploys a web application in two Azure regions for high availability. They need to automatically direct users to the nearest healthy region based on geographic location and endpoint health. Which Azure service should they use?

A.Azure Traffic Manager
B.Azure Load Balancer
C.Azure Application Gateway
D.Azure Front Door
AnswerA

Azure Traffic Manager is a DNS-based global load balancer that routes user requests to the most appropriate region based on routing methods like performance, priority, or geographic, and continuous health probes. Because it operates at the DNS layer, it simply returns the endpoint's IP address and does not proxy or terminate traffic, making it suitable for any application protocol. This enables simple, multi-region failover and geographic distribution as required by the company's two-region web application deployment.

Why this answer

Azure Traffic Manager is a DNS-based traffic load balancer that directs users to the nearest healthy region based on geographic location and endpoint health. It uses DNS resolution to route traffic to the closest available endpoint, making it ideal for global high-availability scenarios where users need automatic failover across regions.

Exam trap

The trap here is that candidates often confuse Azure Front Door with Traffic Manager because both can route traffic globally, but Front Door is an application delivery controller with integrated WAF and SSL offload, whereas Traffic Manager is a simpler DNS-based load balancer focused solely on geographic and health-based routing.

How to eliminate wrong answers

Option B (Azure Load Balancer) is wrong because it operates at Layer 4 (TCP/UDP) and distributes traffic within a single region, not across multiple regions or based on geographic location. Option C (Azure Application Gateway) is wrong because it is a regional Layer 7 load balancer with features like SSL termination and URL-based routing, but it does not provide global geographic routing or multi-region failover. Option D (Azure Front Door) is wrong because, while it offers global load balancing and geographic routing, it is primarily an HTTP/HTTPS application delivery platform with advanced web application firewall (WAF) capabilities; for simple DNS-based geographic routing and health monitoring, Traffic Manager is the correct and more lightweight choice.

584
MCQhard

A company runs a critical application on Azure VMs in the West US region. They want to protect against a regional disaster by replicating VMs to East US using Azure Site Recovery. They have both managed and unmanaged disks. They need to ensure that after failover, the recovery VMs are automatically placed in a specific availability set to support the application's multi-tier architecture. Additionally, they want to minimize downtime during planned failover. Which configuration should they use?

A.Configure a recovery plan that includes the VMs and specifies the target availability set and failover order
B.Set the target availability set in each VM's replication settings individually without a recovery plan
C.Use Azure Traffic Manager to route traffic to the secondary region after manual failover
D.Enable consistency groups across the VMs using a replication policy
AnswerA

A recovery plan in Azure Site Recovery groups all VMs into a single orchestrated failover unit, letting you specify the target availability set in the secondary region and defining the exact failover order. You can add pre/post-action runbooks to automate scripted steps, which minimizes downtime and ensures application-consistent startup during planned failover. Setting availability sets and boot order individually in VM replication settings lacks this coordinated sequencing, so the recovery plan is the appropriate DR orchestration mechanism.

Why this answer

A recovery plan in Azure Site Recovery allows you to group VMs, specify the target availability set, and define the failover order. This ensures that after failover, the recovery VMs are automatically placed in the specified availability set, supporting the application's multi-tier architecture. Additionally, recovery plans enable you to automate and sequence failover steps, minimizing downtime during planned failover by orchestrating the process efficiently.

Exam trap

The trap here is that candidates often confuse replication settings (like target availability set per VM) with recovery plans, not realizing that only recovery plans can enforce failover order and group-level placement, which is critical for multi-tier applications.

How to eliminate wrong answers

Option B is wrong because setting the target availability set in each VM's replication settings individually does not allow you to define a failover order or group VMs into a recovery plan, which is necessary for multi-tier application consistency and minimizing downtime. Option C is wrong because Azure Traffic Manager is a DNS-based traffic routing service that does not handle VM placement into availability sets or orchestrate failover sequencing; it only redirects traffic after failover is manually completed. Option D is wrong because consistency groups (multi-VM consistency) ensure crash-consistent or app-consistent recovery points across VMs but do not control target availability set placement or failover order; they are a replication policy feature, not a recovery plan substitute.

585
MCQeasy

A company has an on-premises data center and wants to connect it to Azure to extend their network. They require a dedicated, private, high-bandwidth connection that is not routed over the public internet. They also want a lower-cost backup connection for redundancy in case the primary connection fails. Which combination of connectivity options should they implement?

A.ExpressRoute as the primary connection and a Site-to-Site VPN as the backup connection.
B.Two ExpressRoute circuits from different service providers, both active.
C.Site-to-Site VPN as the primary connection and Point-to-Site VPN as the backup.
D.Azure VPN Gateway with active-passive mode and a second VPN Gateway for failover.
AnswerA

ExpressRoute is a private, dedicated connection that bypasses the public internet, providing consistent low latency, high bandwidth, and a 99.9% SLA. A Site-to-Site VPN over the public internet is significantly cheaper to maintain as a standby, and because it uses encrypted IPsec tunnels, it can serve as an adequate failover path if the ExpressRoute circuit goes down. This combination meets the requirement for a private primary path while keeping the backup cost-effective.

Why this answer

ExpressRoute provides a dedicated, private, high-bandwidth connection that bypasses the public internet, meeting the primary requirement. A Site-to-Site VPN over the internet serves as a cost-effective backup path for redundancy, as it uses encrypted tunnels over the public internet without the recurring costs of a second ExpressRoute circuit.

Exam trap

The trap here is that candidates often assume two ExpressRoute circuits are required for redundancy, overlooking the cost-effective alternative of using a Site-to-Site VPN as a backup, which still meets the redundancy requirement without the high cost of a second private connection.

How to eliminate wrong answers

Option B is wrong because two active ExpressRoute circuits from different providers provide high availability but at a higher cost, not a lower-cost backup. Option C is wrong because a Site-to-Site VPN as the primary connection does not meet the requirement for a dedicated, private, high-bandwidth connection not routed over the public internet; Point-to-Site VPN is for individual client connections, not site-to-site redundancy. Option D is wrong because Azure VPN Gateway with active-passive mode and a second VPN Gateway for failover still uses the public internet, failing the private connection requirement, and is more complex and costly than a single VPN Gateway with active-passive mode.

586
Multi-Selecteasy

Which TWO of the following are true about Azure Blob Storage access tiers?

Select 2 answers
A.The cool access tier has lower storage costs but higher access costs compared to the hot tier
B.The cool access tier is designed for data that is accessed more frequently than the hot tier
C.The archive access tier is suitable for data that is accessed daily
D.The archive access tier has the lowest storage costs but the highest retrieval latency
E.The hot access tier has the lowest storage costs
AnswersA, D

Cool is a lower-cost storage tier for data expected to remain for at least 30 days and be accessed only occasionally. It reduces capacity charges compared with Hot, but compensates with higher per-GB read/write and early-deletion fees, so access-heavy workloads become more expensive on Cool.

Why this answer

Azure Blob Storage's cool access tier is designed for infrequently accessed data, offering lower storage costs than the hot tier but higher access costs (per GB read/write) to compensate for the reduced storage price. This cost trade-off aligns with typical usage patterns where data is stored long-term but accessed less often.

Exam trap

The trap here is confusing the cost trade-off between storage and access—candidates often assume 'cool' means cheaper overall, but they miss that access costs are higher, and they mistakenly think archive supports daily access due to its low storage cost.

587
MCQmedium

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to automatically remove guest users who have not signed in for 60 days. Additionally, they must generate a report of all guest access for auditors. Which Microsoft Entra ID feature should they implement?

A.Access Reviews
B.Entitlement Management
C.Identity Protection
D.Terms of Use
AnswerA

Microsoft Entra Access Reviews are the right answer because they provide a recurring, attestation-based workflow to certify or deny access for users. You can scope a review to 'Guest users only' and set an inactivity threshold based on sign-in activity, so guests who haven't signed in by a certain date are automatically flagged and removed. When the review completes, you can auto-apply the results to remove denied guests from groups, applications, and directory roles, and every action is written to the Entra audit log for compliance evidence.

Why this answer

Access Reviews in Microsoft Entra ID allow administrators to create recurring reviews that automatically remove guest users who have not signed in within a specified period (e.g., 60 days) by configuring the 'Inactive users (in days)' setting. Additionally, Access Reviews generate a detailed report of all guest access decisions, which can be exported for auditors, meeting both requirements directly.

Exam trap

The trap here is that candidates often confuse Entitlement Management (which handles access packages) with Access Reviews (which handles periodic attestation and automated removal), missing that only Access Reviews directly support inactivity-based removal and audit reporting.

How to eliminate wrong answers

Option B (Entitlement Management) is wrong because it manages access packages and catalogs for resource provisioning but does not natively provide automated removal based on sign-in inactivity or generate audit reports for guest access. Option C (Identity Protection) is wrong because it focuses on detecting and remediating identity risks (e.g., compromised accounts, sign-in anomalies) rather than automating guest user lifecycle or producing access review reports. Option D (Terms of Use) is wrong because it enforces user consent to policies but lacks any capability to automatically remove inactive users or generate audit reports for guest access.

588
MCQhard

Refer to the exhibit. You deploy this ARM template to create a storage account in the West US region. The business continuity requirement states that if the primary region becomes unavailable, the storage account must be readable within 1 hour. What is the most important limitation of this configuration?

A.The storage account does not support read access in the secondary region, so manual failover is required, which may exceed the 1-hour RTO
B.The storage account uses GRS, which replicates data only to a secondary region within the same geography, not to a different region
C.The storage account only supports HTTPS traffic, which blocks replication
D.The storage account is configured with the Hot access tier, which prevents failover
AnswerA

This is correct because the ARM template likely creates an Azure Storage account with GRS (Geo-Redundant Storage), which does not provide read access to the secondary region—that capability requires RA-GRS (Read-Access Geo-Redundant Storage). GRS only asynchronously replicates data to the paired secondary region, so you must perform a manual account failover to promote the secondary to primary. This manual failover can take several hours (often 2–3+ hours) depending on Azure's workload, exceeding the 1-hour RTO specified. Since the secondary is not readable before failover, you cannot meet recovery objectives without a separate, active second-region copy.

Why this answer

The ARM template configures GRS (Geo-Redundant Storage), which replicates data to a secondary region but does not provide read access to that data unless a manual failover is initiated. Without read-access geo-redundant storage (RA-GRS), the storage account cannot be read in the secondary region within 1 hour of a primary region outage, as manual failover requires user intervention and may take longer than the RTO. The business continuity requirement demands readability within 1 hour, which is not guaranteed with standard GRS.

Exam trap

The trap here is that candidates often confuse GRS with RA-GRS, assuming that geo-redundant replication automatically provides read access to the secondary region, when in fact only RA-GRS offers that capability without manual failover.

How to eliminate wrong answers

Option B is wrong because GRS does replicate data to a secondary region within the same geography (e.g., paired region), which is a different region from the primary (West US), so this statement is factually incorrect. Option C is wrong because HTTPS traffic does not block replication; Azure Storage replication uses HTTPS for secure data transfer, and this setting is unrelated to replication functionality. Option D is wrong because the Hot access tier does not prevent failover; access tiers (Hot, Cool, Archive) affect storage costs and retrieval latency, not the ability to perform a failover or read from the secondary region.

589
MCQhard

Refer to the exhibit. An administrator runs the PowerShell script to enable replication for a VM. The script fails with an error that the VM is not found. What is the most likely cause?

A.The Recovery Services vault does not exist.
B.The protection container is not available.
C.The replication policy is not valid.
D.The Azure PowerShell context is not set to the subscription that contains the VM.
AnswerD

The script uses Get-AzVM to locate the virtual machine, and this cmdlet depends on the active Azure context — the subscription set by Set-AzContext or Select-AzSubscription. If the context points to a different subscription than the one holding the target VM, Get-AzVM returns no matching VM, causing the backup protection command to fail with 'VM not found' even though the vault, container, and policy are all visible in the current context. The solution is to explicitly set the context (e.g., Set-AzContext -SubscriptionId '...') before running the script.

Why this answer

The PowerShell script uses `Get-AzRecoveryServicesBackupItem` and `Enable-AzRecoveryServicesBackupProtection` to enable replication for a VM. If the Azure PowerShell context (set via `Set-AzContext` or `Connect-AzAccount`) is not targeting the subscription containing the VM, the cmdlets will not find the VM resource, resulting in a 'VM not found' error. This is the most likely cause because the script otherwise references a valid vault, container, and policy.

Exam trap

The trap here is that candidates may assume the error is due to a missing vault or policy, but the 'VM not found' error specifically points to a subscription context mismatch, not a resource existence issue.

How to eliminate wrong answers

Option A is wrong because if the Recovery Services vault did not exist, the error would be 'vault not found' or a resource-not-found exception, not 'VM not found'. Option B is wrong because the protection container is derived from the vault and VM discovery; if it were unavailable, the error would indicate container retrieval failure, not a missing VM. Option C is wrong because the replication policy is validated when enabling protection; an invalid policy would produce a policy-specific error, not a 'VM not found' error.

590
MCQmedium

A company runs a critical line-of-business application on Azure VMs within a single region. The application tier is deployed across multiple VMs. They need to protect against a failure of an entire Azure datacenter within that region. The solution should automatically distribute the VMs across physically separate locations with independent power, cooling, and networking. The company also requires the lowest possible latency between application and database tiers within the same location. Which deployment strategy should they use?

A.Deploy the VMs across multiple availability zones
B.Deploy the VMs in an availability set
C.Use Azure Site Recovery to replicate VMs to a paired region
D.Use Azure Proximity Placement Groups
AnswerA

Availability zones provide datacenter-level redundancy within a region. By placing VMs in different zones, the application can survive a single datacenter failure. This also allows low latency within the same zone for the database tier.

Why this answer

Availability zones are physically separate datacenters within an Azure region, each with independent power, cooling, and networking. Deploying the application tier VMs across multiple zones protects against an entire datacenter failure while keeping all resources within the same region, ensuring the lowest possible latency between application and database tiers when they are placed in the same zone.

Exam trap

The trap here is that candidates often confuse availability sets (which protect against rack failures) with availability zones (which protect against datacenter failures), or they incorrectly assume that cross-region replication via Site Recovery is the only way to achieve datacenter fault tolerance, ignoring the lower-latency option of multiple zones within the same region.

How to eliminate wrong answers

Option B is wrong because an availability set only protects against rack-level failures within a single datacenter, not against the failure of an entire datacenter. Option C is wrong because Azure Site Recovery to a paired region introduces cross-region latency, which does not meet the requirement for the lowest possible latency within the same location. Option D is wrong because Proximity Placement Groups are designed to reduce latency by co-locating VMs, but they do not provide protection against a full datacenter failure.

591
MCQmedium

A financial services company needs to store transaction logs for regulatory compliance. The logs must be stored in a cost-effective manner, and they must be immutable to prevent tampering. The logs are accessed infrequently but must be retained for 7 years. Which Azure storage solution should you recommend?

A.Azure Cosmos DB with time-to-live (TTL)
B.Azure Blob Storage with immutable storage policy and cool access tier
C.Azure SQL Database with long-term retention backup
D.Azure Files with share snapshots
AnswerB

Azure Blob Storage with an immutable storage policy (WORM) ensures that blobs cannot be modified or deleted for a user-specified retention interval, which directly meets the compliance requirements for tamper-proof financial transaction logs. The cool access tier offers low storage costs for data that is infrequently accessed—ideal for logs retained for regulatory audits—while still allowing blob versioning and lifecycle management for eventual archival or deletion. This combination delivers durable, scalable, and cost-effective storage optimised for append-only log workloads.

Why this answer

Azure Blob Storage with an immutable storage policy (WORM) ensures that transaction logs cannot be modified or deleted during the retention period, meeting compliance requirements. The cool access tier is cost-effective for infrequently accessed data, and the 7-year retention aligns with the policy's time-based retention. This combination provides both immutability and low-cost storage for long-term archival.

Exam trap

The trap here is that candidates may confuse Azure SQL Database long-term retention (which is for backup recovery, not immutable storage) with true immutability, or assume that any snapshot or TTL mechanism can satisfy regulatory immutability requirements when they actually allow deletion or modification.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB with TTL automatically deletes data after the TTL expires, which does not provide immutability and would delete logs before the 7-year retention period ends. Option C is wrong because Azure SQL Database long-term retention backup is designed for database recovery, not for storing immutable transaction logs, and it does not prevent tampering at the storage level. Option D is wrong because Azure Files share snapshots are point-in-time copies that can be deleted by the administrator, offering no immutability guarantee, and they are not cost-optimized for infrequent access over 7 years.

592
MCQeasy

A company has multiple virtual networks in different Azure regions. They need to connect all VNets together securely over the Microsoft backbone. They also need to connect to an on-premises data center via ExpressRoute. The solution should support transitive routing between all connected networks. Which Azure service should they use?

A.Azure Virtual Network Peering
B.Azure VPN Gateway
C.Azure Virtual WAN
D.Azure ExpressRoute Gateway
AnswerC

Azure Virtual WAN is the correct choice because it acts as a managed hub-and-spoke platform with automatic transitive routing between any connected VNets, regardless of region. Spoke VNets in different Azure regions can attach to the same Virtual WAN hub or to regional hubs, and traffic is routed over the Microsoft backbone with no need for manual peering or BGP. It also natively interconnects with VPN, ExpressRoute, and point-to-site gateways, making it the ideal centralized connectivity solution for multiple VNets.

Why this answer

Azure Virtual WAN is the correct choice because it provides a hub-and-spoke architecture that supports transitive routing between all connected networks (multiple VNets across regions and on-premises via ExpressRoute) over the Microsoft backbone. It natively integrates ExpressRoute and VPN gateways into a single managed service, enabling seamless connectivity and routing between any spoke VNet, branch, or on-premises site without requiring manual peering or gateway transit configuration.

Exam trap

The trap here is that candidates often choose Azure Virtual Network Peering (Option A) because they assume peering supports transitive routing, but Azure explicitly does not allow transitive routing through peered VNets unless you use a hub VNet with a network virtual appliance or enable gateway transit, which is not the same as native transitive routing.

How to eliminate wrong answers

Option A is wrong because Azure Virtual Network Peering does not support transitive routing; if you peer VNet A to VNet B and VNet B to VNet C, traffic cannot flow from A to C through B without additional configuration (e.g., a network virtual appliance or hub VNet). Option B is wrong because Azure VPN Gateway provides site-to-site or point-to-site connectivity over the public internet, not over the Microsoft backbone, and it does not natively support transitive routing between multiple VNets across regions without complex manual routing and additional gateways. Option D is wrong because Azure ExpressRoute Gateway is a component that connects a single VNet to an ExpressRoute circuit; it does not provide transitive routing between multiple VNets or across regions, and it requires additional services (like Virtual WAN or a hub VNet) to achieve full mesh connectivity.

593
Drag & Dropmedium

Drag and drop the steps to implement Azure AD Privileged Identity Management (PIM) for a role into the correct order.

Drag or tap steps into the slots.

Steps
Order
1Step 1
2Step 2
3Step 3
4Step 4

Why this order

Select role, configure settings, assign eligible members, set notifications, then test activation.

594
MCQhard

A financial services company is designing a data platform on Azure that must comply with strict regulatory requirements. The platform will store sensitive customer data in Azure SQL Database. The company needs to prevent data exfiltration and ensure that only authorized Microsoft Entra ID users can access the data. The solution must also encrypt data at rest and in transit. Which combination of Azure services should the company implement?

A.Azure SQL Database firewall rules, Transparent Data Encryption (TDE), and Always Encrypted
B.Azure SQL Database with IP firewall rules, TLS 1.2, and Azure Information Protection
C.Azure SQL Database with Managed Identity, Azure Private Link, and Transparent Data Encryption (TDE)
D.Azure SQL Database with Microsoft Entra ID authentication, Azure Key Vault, and Azure Storage Service Encryption
AnswerC

Azure Private Link exposes the SQL Database through a private IP address within the customer's virtual network, completely removing the public internet from the data path and sharply reducing the attack surface for exfiltration. Managed Identity allows an Azure resource, such as a function app or virtual machine, to authenticate to SQL Database via Microsoft Entra ID without embedding credentials in code or configuration, ensuring that only the intended service identity can connect. TDE adds defense-in-depth by encrypting data files, backups, and transaction logs at rest. This combination of private network routing plus a non-interactive, least-privilege workload identity directly addresses the requirement to prevent unauthorized data copying.

Why this answer

It combines Managed Identity for secure, password-free authentication to Azure SQL Database, Azure Private Link to eliminate public internet exposure and prevent data exfiltration, and Transparent Data Encryption (TDE) to encrypt data at rest. This trio directly addresses the regulatory requirements for access control, network isolation, and encryption without relying on less secure firewall rules or client-side encryption.

Exam trap

The trap here is that candidates often confuse network-level isolation (Private Link) with access control (firewall rules) or encryption methods (TDE vs. Always Encrypted), and mistakenly believe that IP firewall rules or client-side encryption alone satisfy exfiltration prevention requirements.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database firewall rules alone do not prevent data exfiltration (they only restrict source IPs, not destination) and Always Encrypted is a client-side encryption feature that does not protect data in transit between the client and the database. Option B is wrong because IP firewall rules are insufficient for preventing data exfiltration (they do not isolate the network path), TLS 1.2 only covers data in transit, and Azure Information Protection is a classification/labeling service, not a data-at-rest encryption mechanism for SQL Database. Option D is wrong because Azure Storage Service Encryption applies only to Azure Storage (Blob, Files, etc.), not to Azure SQL Database, and while Entra ID authentication and Key Vault are useful, they do not provide network-level exfiltration prevention.

595
MCQmedium

You are designing a globally distributed application that requires low-latency reads and writes for a web application with user session data. The solution must support multi-master writes and provide 99.999% availability. Which Azure data service meets these requirements?

A.Azure SQL Database
B.Azure Cosmos DB
C.Azure Cache for Redis
D.Azure Table Storage
AnswerB

Cosmos DB is the correct choice because it natively supports multiple write regions for a single database account, enabling active-active writes from any Azure region. This multi-master capability, combined with service-managed replication and configurable consistency levels (Strong, Bounded Staleness, Session, etc.), allows you to meet the 99.999% availability SLA when you enable multi-region writes. It is a fully durable, globally distributed NoSQL database, making it perfect for globally distributed applications that need write access in multiple regions and continuous availability.

Why this answer

Azure Cosmos DB is the correct choice because it natively supports multi-master writes across multiple regions, enabling low-latency reads and writes globally. It offers a 99.999% availability SLA when configured with multiple write regions, and its turnkey global distribution ensures user session data is replicated with consistency options tailored for web applications.

Exam trap

The trap here is that candidates often confuse Azure Cache for Redis's low-latency caching with a durable, multi-master data store, overlooking that it lacks persistence guarantees and multi-master write support required for 99.999% availability.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database supports only a single writable primary replica (active geo-replication provides readable secondaries but not multi-master writes), and its maximum availability SLA is 99.995% for Business Critical tier, not 99.999%. Option C is wrong because Azure Cache for Redis is an in-memory cache, not a durable data store; it does not support multi-master writes natively and its SLA is 99.9% for Standard tier, far below 99.999%. Option D is wrong because Azure Table Storage is a NoSQL key-value store that does not support multi-master writes; it offers only single-region writes with read-access geo-redundant storage (RA-GRS) for reads, and its SLA is 99.99% for reads but only 99.9% for writes, insufficient for the required availability.

596
MCQmedium

Refer to the exhibit. An administrator reviews the backup status of a VM. The last backup failed. What is the most likely cause?

A.The Recovery Services vault is in a different region.
B.The backup policy does not exist.
C.The source resource ID is missing.
D.The VM was deallocated at the time of backup.
AnswerD

Azure Backup cannot take a snapshot of a VM that is in the Deallocated (stopped) state, because the in-guest backup extension is not running and the VM's disks are not guaranteed to be in a consistent, attached state. When a backup job is initiated for a deallocated VM, the job is marked as failed with a warning, or in some cases it is skipped entirely, without affecting the policy or vault configuration. This is a well-known limitation, and the correct explanation for the failure shown in the exhibit.

Why this answer

When a VM is deallocated (stopped and deallocated in Azure), the Azure Backup service cannot create a VM-consistent snapshot because the VM is not running. Backup attempts for deallocated VMs will fail with an error indicating that the VM is not in a running state. This is a common cause of backup failures in Azure.

Exam trap

The trap here is that candidates may think a deallocated VM can still be backed up (since it still exists in Azure), but Azure Backup requires the VM to be in a running state to perform a successful backup.

How to eliminate wrong answers

Option A is wrong because Recovery Services vaults can back up VMs in any region; the vault and VM do not need to be in the same region for backup to work. Option B is wrong because if the backup policy did not exist, the backup would not have been scheduled at all, and the status would show 'No backup policy assigned' rather than a failed backup. Option C is wrong because the source resource ID is a required field for the backup job; if it were missing, the backup job would not have been created or would fail with a different error, not a generic failure.

597
MCQmedium

A company runs a critical application on Azure VMs in a single region. They need to ensure business continuity with an RPO of 1 hour and RTO of 4 hours. The application has dependencies on virtual networks, storage accounts, and other Azure resources. They want to use Azure Backup as the primary disaster recovery tool and must be able to restore the entire application in a secondary region if the primary region fails. Which backup strategy should they recommend?

A.Azure Backup for VMs with daily backups and cross-region restore
B.Azure Site Recovery with replication to a secondary region
C.Azure Backup for VMs with hourly backups and cross-region restore
D.Azure Backup for files with daily backups and geo-redundant storage
AnswerB

Correct. Azure Site Recovery provides continuous replication with low RPO and can orchestrate recovery of entire applications with dependencies.

Why this answer

Azure Site Recovery can replicate Azure VMs to a secondary region with an RPO as low as 15 minutes and an RTO of a few hours, meeting the 1-hour RPO and 4-hour RTO requirements. It also supports recovery plans that include virtual networks, storage accounts, and other dependencies, enabling restore of the entire application. Option C is incorrect because Azure Backup for VMs has a minimum backup frequency of every 4 hours for VM backups, not hourly, so it cannot achieve the required 1-hour RPO.

Exam trap

The trap is that candidates assume Azure Backup can achieve hourly backups for VMs, but the minimum backup frequency for VM backups is every 4 hours. Thus, for a 1-hour RPO, Azure Site Recovery (not Azure Backup) is required.

How to eliminate wrong answers

Option A is wrong because daily backups cannot achieve an RPO of 1 hour; the maximum backup frequency for daily backups is once per day, which would result in an RPO of up to 24 hours. Option B is wrong because Azure Site Recovery is a separate disaster recovery tool, not Azure Backup, and the question explicitly states they want to use Azure Backup as the primary disaster recovery tool. Option D is wrong because Azure Backup for files only protects file-level data, not the entire application including VMs, virtual networks, and storage accounts, and daily backups cannot meet the 1-hour RPO requirement.

598
MCQmedium

A company deploys a multi-tier application on Azure virtual machines. They need to implement disaster recovery using Azure Site Recovery. The recovery plan must ensure that the database VMs are started before the application VMs, and the application VMs before the web VMs. They also need to run a script after failover to update DNS records. Which ASR feature should they use?

A.Recovery Plan with manual steps
B.Recovery Plan with custom groups and script actions
C.Replication policy with crash-consistent snapshots
D.Azure Automation runbook
AnswerB

Custom groups in an Azure Site Recovery recovery plan provide strict ordering by letting you assign VMs to sequential groups; the plan starts each group only after the previous group completes. Script actions, implemented as Azure Automation runbooks or PowerShell commands, can be attached to each group to run post-failover steps such as waiting for the database tier to be ready or updating application configuration. This combination gives you automated, deterministic tier-by-tier startup without human intervention.

Why this answer

Azure Site Recovery (ASR) Recovery Plans allow you to orchestrate the order of VM failover by grouping VMs into custom groups and adding pre- and post-actions. By placing database VMs in Group 1, application VMs in Group 2, and web VMs in Group 3, you enforce the required startup sequence. Script actions (e.g., Azure Automation runbooks or PowerShell scripts) can be inserted at specific points in the plan to update DNS records after failover, making option B the correct choice.

Exam trap

The trap here is that candidates confuse a standalone Azure Automation runbook (which can run scripts but cannot enforce VM startup order) with a script action embedded in a Recovery Plan (which combines both ordering and script execution).

How to eliminate wrong answers

Option A is wrong because manual steps require human intervention during failover, which contradicts the need for an automated, reliable recovery plan that runs scripts to update DNS records. Option C is wrong because a replication policy with crash-consistent snapshots only controls the consistency of replicated data (ensuring crash-consistent recovery points) and does not provide any orchestration of VM startup order or post-failover scripting. Option D is wrong because an Azure Automation runbook is a script execution tool, but by itself it cannot define the multi-group startup sequence; it must be used as a script action within a Recovery Plan to achieve both ordering and automation.

599
MCQmedium

A company needs a fully managed NoSQL database for a JSON document-oriented application that requires low latency (single-digit milliseconds) for reads and writes at any scale. The application will run globally and needs multi-region writes with automatic failover. Which Azure data store should they use?

A.Azure Cosmos DB
B.Azure Table Storage
C.Azure SQL Database
D.Azure Cache for Redis
AnswerA

Azure Cosmos DB is the correct choice because it is a fully managed, multi-model NoSQL database with native JSON document support, schema-agnostic indexing, and an SQL-like query engine. It uniquely delivers multi-region writes with automatic failover, elastic horizontal partitioning and tunable consistency, backed by an industry-leading SLA of 99.999% availability and single-digit millisecond read/write latency at the 99th percentile. These capabilities are purpose-built for globally distributed JSON workloads requiring both durability and low-latency access.

Why this answer

Azure Cosmos DB is the correct choice because it is a fully managed NoSQL database that natively supports JSON documents, offers single-digit millisecond latency for reads and writes at any scale, and provides multi-region writes with automatic failover through its multi-master replication capability. Its global distribution model allows you to configure multiple write regions, ensuring high availability and low latency worldwide.

Exam trap

The trap here is that candidates often confuse Azure Table Storage (a simple key-value store) with a fully managed NoSQL database, overlooking that it lacks native JSON support, multi-region writes, and automatic failover capabilities required for global, low-latency applications.

How to eliminate wrong answers

Option B (Azure Table Storage) is wrong because it is a key-value store that does not natively support JSON documents or multi-region writes with automatic failover; it offers only eventual consistency and lacks the global distribution features required. Option C (Azure SQL Database) is wrong because it is a relational database that does not support JSON as a native document model and cannot provide multi-region writes with automatic failover; it is not a NoSQL solution. Option D (Azure Cache for Redis) is wrong because it is an in-memory cache, not a fully managed NoSQL database; it does not persist JSON documents durably and lacks multi-region write capabilities with automatic failover.

600
MCQhard

A company uses Microsoft Entra ID B2B to collaborate with external vendors. They want to enforce that external users must use multi-factor authentication (MFA) and access company resources only from compliant devices (e.g., managed by Intune). They also want to require a session timeout of 1 hour. Which combination of Microsoft Entra ID features should they use?

A.A
B.B
C.C
D.D
AnswerB

Microsoft Entra ID Conditional Access is the comprehensive policy engine that can enforce all the stated requirements during sign-in. A Conditional Access policy can require multi-factor authentication for external B2B users, require the device to be marked as compliant by integrating with Intune, and apply session controls that set sign-in frequency to force periodic reauthentication. These policies can be targeted to guest and external users specifically, making Conditional Access the right tool for controlling access in B2B collaboration scenarios.

Why this answer

It combines Conditional Access policies with session controls to enforce MFA, device compliance (via Intune), and a 1-hour session timeout. Conditional Access policies evaluate sign-in risk and require MFA and compliant devices, while the session control 'Sign-in frequency' can be set to 1 hour to enforce reauthentication. This meets all three requirements without relying on deprecated or separate features.

Exam trap

The trap here is that candidates often confuse Conditional Access session controls with token lifetime policies or think that Identity Protection alone can enforce device compliance, but only Conditional Access policies can combine MFA, device compliance, and session timeout in a single policy.

How to eliminate wrong answers

Option A is wrong because it uses Azure AD Identity Protection, which is designed for risk-based policies (e.g., risky sign-ins) but does not natively enforce device compliance or session timeout; it lacks the session control for a 1-hour timeout. Option C is wrong because it relies on Azure AD Privileged Identity Management (PIM), which manages just-in-time privileged access and does not enforce MFA or device compliance for external users accessing general resources. Option D is wrong because it uses Azure AD Terms of Use, which only requires acceptance of a policy document and cannot enforce MFA, device compliance, or session timeout.

Page 7

Page 8 of 11

Page 9

All pages