Courseiva

Microsoft Azure Solutions Architect Expert AZ-305 (AZ-305) — Questions 76–150

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

Page 1

Page 2 of 11

Page 3
76
MCQhard

A financial services company needs to store sensitive transaction records in Azure for 7 years to meet regulatory compliance. The data must be immutable and cannot be deleted or modified during the retention period. Which Azure storage feature should you enable?

A.Blob versioning with lifecycle management
B.Soft delete for blob storage
C.Immutable blob with time-based retention policy
D.Legal hold on the storage container
AnswerC

A time-based retention policy on an immutable blob container enforces a WORM (write-once, read-many) model, prohibiting any deletion or modification of blobs until the specified retention interval has elapsed. The policy is enforced by Azure Storage and cannot be shortened or removed before expiry, ensuring data meets SEC 17a-4-style compliance requirements. It can be applied at the container level or to individual blob versions, and is protected from administrative tampering. This is the appropriate choice for a fixed retention period.

Why this answer

Immutable blob storage with a time-based retention policy enforces WORM (Write Once, Read Many) compliance, ensuring that data cannot be deleted or modified for a specified retention period. This meets the 7-year regulatory requirement for sensitive transaction records, as the policy locks the data at the blob level and prevents any overwrite or deletion, even by administrators with elevated permissions.

Exam trap

The trap here is that candidates confuse soft delete or versioning with immutability, not realizing that only immutable blob storage provides true WORM protection that prevents any modification or deletion during the retention period.

How to eliminate wrong answers

Option A is wrong because blob versioning with lifecycle management preserves previous versions of blobs but does not prevent deletion or modification of the current version; it only allows recovery of older versions, not immutability. Option B is wrong because soft delete for blob storage retains deleted blobs for a configurable period but does not prevent deletion in the first place; data can still be deleted (and later recovered), which violates the immutable requirement. Option D is wrong because a legal hold on the storage container prevents deletion of blobs only while the hold is active, but it does not enforce a fixed retention period and can be removed by an authorized user, failing the 7-year compliance mandate.

77
MCQmedium

Your organization uses Microsoft Entra ID and requires that all external users accessing resources must be approved by a designated reviewer. You need to automate the review process for external identities. What should you implement?

A.Microsoft Purview
B.Privileged Identity Management (PIM)
C.Microsoft Entra access reviews
D.Conditional Access
AnswerC

Microsoft Entra access reviews enables administrators to create recurring review campaigns for group memberships, enterprise application assignments, and role assignments. Reviewers can sign off on each user's access with a decision and justification, and results can be configured to automatically remove access when needed. This directly meets the requirement for periodic review of external users' access, making it the correct service for this scenario.

Why this answer

Microsoft Entra access reviews allow you to automate the periodic review of external identities, ensuring that only approved users retain access. This feature directly supports the requirement for a designated reviewer to approve or deny external users, with automated reminders and results. It is the correct choice because it is purpose-built for governance of external identities in Entra ID.

Exam trap

The trap here is confusing Privileged Identity Management (PIM) with access reviews, as both involve approvals, but PIM is for privileged roles while access reviews are for ongoing user access certification, especially for external identities.

How to eliminate wrong answers

Option A is wrong because Microsoft Purview is a data governance and compliance solution focused on data classification, labeling, and risk management, not on automating identity access reviews. Option B is wrong because Privileged Identity Management (PIM) manages just-in-time privileged role activation and approval, not the periodic review of all external identities. Option D is wrong because Conditional Access enforces access policies based on conditions like location or device state, but does not provide a workflow for designated reviewers to approve or deny external user access.

78
Multi-Selectmedium

Your company uses Microsoft Entra ID. You need to implement a governance strategy for guest users. Which TWO actions should you take? (Choose two.)

Select 2 answers
A.Create access reviews for guest users
B.Disable external identities
C.Block all guest user access
D.Enable self-service sign-up for guest users
E.Configure Microsoft Entra entitlement management
AnswersA, E

Access reviews in Microsoft Entra ID provide a planned, recurring recertification workflow for guest users, forcing owners to confirm or revoke each guest's access to sensitive resources. By assigning reviewers per access package or application, you can automatically remove stale or unauthorized external accounts, satisfying compliance requirements and enforcing the principle of least privilege. This is a core governance control because it operationalizes periodic oversight rather than relying on one-time provisioning decisions.

Why this answer

Access reviews for guest users (Option A) are a core governance control in Microsoft Entra ID, allowing administrators to periodically review and confirm or revoke guest access. This ensures that guest accounts remain necessary and compliant with security policies, directly addressing the governance requirement.

Exam trap

The trap here is that candidates may confuse blocking or disabling guest access (Options B and C) with governance, when the correct approach involves reviewing and managing guest access through reviews and entitlement management.

79
MCQeasy

A company needs to back up an Azure virtual machine that runs a file server. They want to restore individual files quickly without restoring the entire VM. Which backup option should they use?

A.Azure File Sync with cloud tiering.
B.Azure Backup using MARS agent with file and folder backup.
C.Azure Backup for Azure VMs with file-level restore.
D.Azure Backup for Azure VMs with instant restore.
AnswerC

Azure Backup for Azure VMs with file-level restore is the correct choice because it captures full VM snapshots via the Azure Backup extension and stores them in a Recovery Services vault. The file-level restore feature mounts the selected recovery point as a disk (via a temporary recovery VM or an iSCSI target) so you can browse the file system and recover individual files or folders without restoring the entire virtual machine. This provides the granularity you need—backing up the whole Azure VM while still enabling point-in-time file recovery. It also supports both Windows and Linux VMs through a simple portal workflow or PowerShell.

Why this answer

Azure Backup for Azure VMs with file-level restore (option C) is correct because it allows you to mount the VM's backup as a drive on a designated recovery machine using iSCSI, enabling you to browse and copy individual files without restoring the entire VM. This meets the requirement for quick, granular file recovery from a VM backup.

Exam trap

The trap here is confusing 'instant restore' (which speeds up full VM recovery) with 'file-level restore' (which provides granular file access from a VM backup), leading candidates to pick option D when they need individual file recovery.

How to eliminate wrong answers

Option A is wrong because Azure File Sync with cloud tiering is a synchronization and caching solution for on-premises file servers, not a backup service; it does not provide point-in-time restore of individual files from a VM backup. Option B is wrong because the MARS agent with file and folder backup is designed for on-premises Windows servers or Azure VMs running Windows, but it requires installing the agent inside the VM and does not leverage the native Azure VM backup chain; it also cannot restore files from a VM-level backup snapshot. Option D is wrong because Azure Backup for Azure VMs with instant restore refers to the ability to restore a full VM quickly from a snapshot without waiting for vault transfer, but it does not provide file-level granularity; you would still need to restore the entire VM or use file-level restore to access individual files.

80
MCQhard

Refer to the exhibit. You run a KQL query against Azure Cosmos DB diagnostics logs. The query shows increasing latency for Query operations over time. Which is the most likely root cause?

A.A query is consuming increasing RU over time, possibly due to a hot partition
B.The Cosmos DB account has reached its storage limit
C.The Cosmos DB account is being throttled due to insufficient RUs
D.There is network latency between the client and the Cosmos DB endpoint
AnswerA

Increasing RU per query commonly signals a hot partition: a single partition key receives disproportionate request volume, forcing that physical partition to consume more throughput and causing cross-partition query scans. As relevant documents accumulate under one key, the query's logical operations grow, which raises RU charge while response time climbs. Monitor per-partition metrics and Query RU/min to confirm.

Why this answer

The query latency increase over time, combined with the fact that the query is consuming more Request Units (RU) per execution, strongly indicates a hot partition. In Azure Cosmos DB, a hot partition occurs when a disproportionate amount of traffic hits a single physical partition, causing that partition's RU budget to be exhausted while others remain underutilized. This leads to increased latency for queries targeting that partition, as the partition's resources become saturated.

Exam trap

The trap here is that candidates often confuse throttling (Option C) with latency degradation, but throttling is an immediate rejection (HTTP 429), not a gradual latency increase; the key clue is the 'increasing latency over time' combined with 'increasing RU consumption,' which points to a hot partition, not a capacity issue.

How to eliminate wrong answers

Option B is wrong because Cosmos DB has no fixed storage limit; it scales horizontally, and storage limits are tied to provisioned throughput, not a hard cap that would cause increasing latency. Option C is wrong because throttling (HTTP 429) would cause immediate errors or retries, not a gradual increase in latency over time; the query would either succeed or fail, not slowly degrade. Option D is wrong because network latency between client and endpoint would manifest as a constant baseline delay, not a trend of increasing latency; it would not correlate with query RU consumption.

81
MCQmedium

A company is building a big data analytics platform that will process structured, semi-structured, and unstructured data using Azure Synapse Analytics and other tools. They need a storage layer that supports hierarchical namespaces and fine-grained access control at the directory level. Which Azure storage solution should they use?

A.Azure Blob Storage
B.Azure Data Lake Storage Gen2
C.Azure Files
D.Azure Cosmos DB
AnswerB

Azure Data Lake Storage Gen2 is the correct choice because it combines the scalability and cost-effectiveness of Blob Storage with a hierarchical namespace that organizes data into directories, enabling efficient atomic operations and fast path-based access. It also supports POSIX-compliant ACLs at both file and directory levels, allowing fine-grained security that matches the needs of multi-tenant analytics workloads. Its native integration with Hadoop, Spark, Databricks, and Azure Synapse makes it the optimal storage layer for big data analytics, as it provides high throughput and parallel processing capabilities.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it combines Azure Blob Storage with a hierarchical namespace, enabling directory-level access control lists (ACLs) and POSIX-compliant permissions. This is essential for the big data analytics platform described, as it must support structured, semi-structured, and unstructured data with fine-grained access control at the directory level, which Azure Synapse Analytics can directly query via ABFS (Azure Blob File System) driver.

Exam trap

The trap here is that candidates often confuse Azure Blob Storage with ADLS Gen2, assuming blob storage supports hierarchical namespaces natively, but it requires explicit enabling of the hierarchical namespace feature, which is only available in ADLS Gen2 accounts.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage does not support a hierarchical namespace by default; it uses a flat namespace, which prevents directory-level ACLs and requires workarounds for folder-like structures. Option C is wrong because Azure Files provides SMB file shares with directory-level access, but it is designed for lift-and-shift file shares and lacks the hierarchical namespace and POSIX ACLs needed for big data analytics with Azure Synapse. Option D is wrong because Azure Cosmos DB is a NoSQL database for globally distributed, low-latency applications, not a storage layer for hierarchical namespace and directory-level ACLs; it uses a document or graph model, not a file system.

82
Multi-Selecteasy

Your company uses Microsoft Entra ID for identity management. You need to implement a solution that automatically blocks sign-ins from risky users and requires multi-factor authentication (MFA) when a sign-in risk is detected. Which TWO services should you use? (Choose two.)

Select 2 answers
A.Microsoft Purview
B.Microsoft Entra ID Protection
C.Microsoft Defender XDR
D.Microsoft Intune
E.Conditional Access policies
AnswersB, E

Microsoft Entra ID Protection is the dedicated identity risk engine that continuously analyzes user and sign-in behavior using signals such as leaked credentials, impossible travel, anomalous token usage, and unfamiliar properties. It calculates user risk and sign-in risk levels and automatically remediates or responds to these risks by requiring MFA or password change, or by blocking access via Conditional Access policies. This makes it the correct service for detecting risky users and risky sign-ins in a Microsoft Entra ID environment.

Why this answer

Microsoft Entra ID Protection (B) is the service that detects sign-in risks (e.g., anonymous IP, atypical travel) and labels users or sign-ins as risky. Conditional Access policies (E) then enforce automated responses, such as blocking the sign-in or requiring MFA, based on the risk level from Entra ID Protection. Together, they provide the detection and enforcement mechanism described in the requirement.

Exam trap

The trap here is that candidates often confuse Microsoft Defender XDR (which includes identity threat detection) with the policy enforcement layer, but only Conditional Access policies can apply the automated MFA or block action based on risk from Entra ID Protection.

83
MCQeasy

A retail company runs its e-commerce platform on Azure VMs. The application uses Azure SQL Database. You are designing a business continuity plan. The company wants to minimize recovery time for a regional outage. Which Azure service should you use to replicate the VMs to a secondary region?

A.Azure Traffic Manager
B.Azure Backup
C.Azure Load Balancer
D.Azure Site Recovery
AnswerD

Azure Site Recovery is the correct service for this scenario because it orchestrates continuous, asynchronous replication of Azure VM disks to a secondary region, enabling a low Recovery Point Objective (RPO) of a few seconds and a Recovery Time Objective (RTO) of minutes. It captures disk changes and can generate application-consistent recovery points, then provides one-click planned or unplanned failover, test failover, and failback. This makes Site Recovery the Azure-native solution for ensuring the e-commerce platform can be brought online in a secondary region after a disaster, which matches the requirement to replicate VMs.

Why this answer

Azure Site Recovery (ASR) orchestrates replication, failover, and failback of Azure VMs from a primary to a secondary region, enabling rapid recovery during a regional outage. It provides continuous replication with a recovery point objective (RPO) of seconds and a recovery time objective (RTO) of minutes, directly meeting the requirement to minimize recovery time for the e-commerce platform's VMs.

Exam trap

The trap here is that candidates often confuse Azure Backup's point-in-time restore capability with Site Recovery's continuous replication and orchestrated failover, mistakenly thinking backups alone can achieve the low RTO required for a regional disaster.

How to eliminate wrong answers

Option A is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that distributes incoming traffic across endpoints, but it does not replicate or protect VM state or data; it only routes users to healthy endpoints. Option B is wrong because Azure Backup provides crash-consistent or application-consistent backups to a Recovery Services vault, but it is designed for point-in-time restore and long-term retention, not for continuous replication with low RTO for a full regional failover. Option C is wrong because Azure Load Balancer distributes network traffic within a region or across availability zones, but it does not replicate VMs or their data to a secondary region; it operates at Layer 4 and has no replication or disaster recovery capability.

84
MCQmedium

A company deploys a web application on multiple Azure VMs in a single region. They need to distribute incoming HTTP and HTTPS traffic across the VMs, offload SSL/TLS termination, and maintain session persistence (sticky sessions) so that all requests from a user session go to the same backend VM. Which Azure load balancing solution should they use?

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

Azure Application Gateway is the best fit here because it operates at Layer 7 (HTTP/S) and can route traffic based on URL paths or host headers. More importantly, it performs SSL termination and enforces cookie-based session affinity, ensuring that a client's subsequent requests are consistently directed to the same backend VM. It also offers a Web Application Firewall and integrates tightly with VM scale sets in a regional VNet, making it ideal for a multi-VM web application in a single region.

Why this answer

Azure Application Gateway is a Layer 7 load balancer that can distribute HTTP/HTTPS traffic, offload SSL/TLS termination, and support session persistence via cookie-based affinity (sticky sessions). These capabilities directly match the requirements, making it the correct choice.

Exam trap

The trap here is that candidates often confuse Azure Load Balancer (Layer 4) with Application Gateway (Layer 7), assuming that any load balancer can handle SSL termination and sticky sessions, but only Layer 7 solutions like Application Gateway or Front Door provide these features.

How to eliminate wrong answers

Option B (Azure Load Balancer) is wrong because it operates at Layer 4 (TCP/UDP) and cannot perform SSL/TLS termination or inspect HTTP/HTTPS traffic for session persistence. Option C (Azure Traffic Manager) is wrong because it is a DNS-based traffic router that directs traffic across regions, not within a single region, and it does not handle SSL termination or sticky sessions. Option D (Azure Front Door) is wrong because it is a global Layer 7 load balancer and CDN designed for multi-region distribution, not for a single-region deployment, and its session affinity uses different mechanisms (e.g., ARR affinity) that are not optimized for intra-region VM load balancing.

85
Multi-Selecthard

Which THREE of the following are required components for a disaster recovery solution using Azure Site Recovery for on-premises Hyper-V VMs?

Select 3 answers
A.A Recovery Services vault in the target Azure region.
B.A replication policy that defines retention and recovery points.
C.The Azure Site Recovery Provider installed on each Hyper-V host.
D.Azure Backup Server installed on-premises.
E.An ExpressRoute connection from on-premises to Azure.
AnswersA, B, C

The Recovery Services vault in the target Azure region is the central management and storage container for all Azure Site Recovery (ASR) data. It stores the replication configuration, recovery points, and journaled data that are needed to bring up virtual machines on Azure during failover. Without it, there is no logical destination for the replicated Hyper-V VMs and no coordination point for the replication workflow. Its placement in the target region is critical because replication data always flows from on-premises to that region, and failover must be able to occur there.

Why this answer

A Recovery Services vault in the target Azure region is required because it serves as the central management and storage container for replication data, configuration settings, and recovery points. Azure Site Recovery (ASR) uses this vault to orchestrate replication, failover, and failback for on-premises Hyper-V VMs to Azure. Without a vault in the target region, there is no destination to store replicated data or manage the recovery process.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery with Azure Backup, assuming that Azure Backup Server (MABS) is needed for replication, when in fact ASR is a separate service with its own provider and does not require any backup server.

86
MCQhard

Your company is designing a data lake solution using Azure Data Lake Storage Gen2. The solution must support hierarchical namespace for efficient directory operations, and must provide encryption at rest using customer-managed keys stored in Azure Key Vault. Which steps must you take to enable customer-managed key encryption for the storage account?

A.Create the storage account with a user-assigned managed identity, then enable hierarchical namespace, and configure encryption.
B.Create the storage account without hierarchical namespace, then enable it later, and configure encryption with Key Vault.
C.Create the storage account and specify customer-managed key encryption during creation using the Azure portal.
D.Create the storage account with hierarchical namespace enabled, then assign a system-assigned managed identity, and configure encryption with Azure Key Vault.
AnswerD

This is the correct sequence because the hierarchical namespace is an immutable account-level feature that must be set when the storage account is created for Azure Data Lake Storage Gen2. After creation, a system-assigned managed identity should be assigned to the account so it can authenticate to Azure Key Vault for customer-managed key encryption. Finally, encryption is configured using that Key Vault, completing a valid and supported data lake solution.

Why this answer

Azure Data Lake Storage Gen2 requires hierarchical namespace to be enabled at account creation time, and customer-managed key encryption with Azure Key Vault requires a system-assigned managed identity to be assigned to the storage account after creation. The system-assigned identity is used to authenticate to Key Vault for key access, and encryption with customer-managed keys can be configured post-creation via the Azure portal or PowerShell.

Exam trap

The trap here is that candidates assume customer-managed key encryption can be configured during storage account creation, but Azure requires it to be set post-creation after a managed identity is assigned, and hierarchical namespace must be enabled at creation time.

How to eliminate wrong answers

Option A is wrong because a user-assigned managed identity is not required; a system-assigned managed identity is the correct identity type for customer-managed key encryption with Key Vault, and hierarchical namespace must be enabled during creation, not after. Option B is wrong because hierarchical namespace cannot be enabled after the storage account is created; it must be specified at creation time. Option C is wrong because customer-managed key encryption cannot be specified during storage account creation in the Azure portal; it must be configured after the account is created, and a managed identity must be assigned first.

87
MCQmedium

A company uses Azure SQL Database for a critical OLTP workload. They need a disaster recovery solution that automatically fails over to a secondary region with an RPO of 5 seconds and an RTO of 1 hour. What should they implement?

A.Azure SQL Database zone-redundant configuration
B.Azure SQL Database active geo-replication
C.Azure SQL Database auto-failover groups
D.Azure SQL Managed Instance failover groups
AnswerC

Auto-failover groups replicate databases to a secondary region and provide a listener endpoint that redirects connections automatically during an outage. This delivers the required sub-five-second RPO and one-hour RTO without manual intervention, unlike geo-restore or active geo-replication alone.

Why this answer

Auto-failover groups in Azure SQL Database provide automatic failover across regions, leveraging active geo-replication under the hood. This combination achieves an RPO of up to 5 seconds (from active geo-replication) and an RTO of 1 hour (from the auto-failover group). Active geo-replication alone does not automate failover, which is required for the disaster recovery solution.

Zone-redundant configuration protects only within a region, not cross-region. Managed Instance failover groups are for Azure SQL Managed Instance, not for Azure SQL Database, and have different RPO/RTO characteristics.

Exam trap

The trap is that candidates may pick active geo-replication (option B) thinking it provides automatic failover, but it only replicates data. The automatic failover capability is provided by auto-failover groups (option C). The question requires both the RPO from replication and the RTO from automatic failover, so auto-failover groups are the correct answer.

How to eliminate wrong answers

Option A is wrong because zone-redundant configuration protects against datacenter failures within a single region, not against a regional disaster, and does not provide cross-region failover or meet the RPO/RTO requirements. Option C is wrong because auto-failover groups use active geo-replication under the hood but add group-level failover orchestration; however, the question asks what to implement, and active geo-replication is the underlying technology that directly provides the specified RPO of 5 seconds and RTO of 1 hour, while auto-failover groups are an optional management layer. Option D is wrong because Azure SQL Managed Instance failover groups are designed for managed instances, not for Azure SQL Database single databases or elastic pools, and the question specifies Azure SQL Database.

88
MCQhard

Your Azure subscription contains multiple virtual machines (VMs) that run a line-of-business application. You need to configure alerts when the CPU usage exceeds 90% for more than 5 minutes. Additionally, the alert must automatically trigger a runbook to scale out the application. Which Azure service should you use to create this alert?

A.Azure Automation
B.Azure Logic Apps
C.Azure Monitor metric alert
D.Azure Autoscale
AnswerC

An Azure Monitor metric alert continuously evaluates one or more VM metrics—such as CPU percentage, memory pressure, or disk IOPS—against a defined threshold and firing condition. When the alert fires, its action group can contain an Automation runbook, webhook, or ITSM ticket, so this is the appropriate service to trigger custom remediation on the VMs.

Why this answer

Azure Monitor metric alerts can evaluate resource metrics like CPU usage at a specified frequency and trigger actions when a threshold (e.g., 90%) is breached for a given duration (e.g., 5 minutes). The alert can invoke an Automation runbook via an action group, enabling automatic scaling of the application. This is the correct service because it directly supports metric-based alerting with multi-condition evaluation and action group integration.

Exam trap

The trap here is that candidates confuse Azure Monitor metric alerts with Azure Autoscale, assuming Autoscale can both alert and trigger runbooks, when in fact Autoscale only performs scaling actions based on its own rules and does not generate alerts or invoke runbooks.

How to eliminate wrong answers

Option A is wrong because Azure Automation is a service for authoring and running runbooks, but it does not itself evaluate metrics or generate alerts; it can only be triggered by an alert action group. Option B is wrong because Azure Logic Apps is a workflow orchestration service that can respond to alerts via connectors, but it is not the native alerting service for metric thresholds and would require additional configuration to evaluate CPU usage. Option D is wrong because Azure Autoscale is a scaling service that can automatically adjust resources based on metrics, but it does not create alerts or trigger runbooks; it directly scales resources without an intermediate alerting step.

89
Multi-Selecteasy

Which TWO of the following are valid data storage solutions for an Azure-based microservices architecture that requires high throughput and low latency? (Choose two.)

Select 2 answers
A.Azure Table Storage
B.Azure Cosmos DB
C.Azure Files
D.Azure Cache for Redis
E.Azure SQL Database
AnswersB, D

Azure Cosmos DB is a fully managed, globally distributed, multi-model database that exposes multiple APIs, including Core (SQL), MongoDB, Cassandra, Gremlin, and Table. It provides comprehensive SLAs for single-digit-millisecond read and write latency at the 99th percentile, supports multi-region writes and automatic horizontal partitioning, and scales throughput independently as request units, which makes it a proven valid data storage solution for demanding microservices.

Why this answer

Azure Cosmos DB is a fully managed NoSQL database that provides single-digit millisecond read and write latencies at the 99th percentile, guaranteed by SLAs. It supports multiple APIs (SQL, MongoDB, Cassandra, Gremlin, Table) and can be configured for high throughput with automatic indexing, making it ideal for microservices that require fast, scalable data access.

Exam trap

The trap here is that candidates often confuse Azure Table Storage (a basic key-value store) with Azure Cosmos DB's Table API (which offers much higher performance and SLAs), or they overlook that Azure Cache for Redis is a caching layer, not a primary data store, but it is a valid storage solution for high-throughput, low-latency access patterns in microservices.

90
MCQmedium

Your organization is building a serverless application that processes events from Azure Event Hubs and stores results in Azure Cosmos DB. The processing logic must be scalable and cost-effective, with no idle costs. Which compute service should you use?

A.Azure Functions
B.Azure Container Instances
C.Azure Logic Apps
D.Azure Kubernetes Service
AnswerA

Azure Functions is a true serverless compute service designed for event-driven architectures. It runs on the consumption plan where you pay only for execution time while the platform automatically scales out in response to incoming events and scales to zero when idle, eliminating idle cost. Tight integration with Azure triggers (e.g., HTTP, Event Grid, Service Bus, Blob) makes it the optimal choice for high-throughput, short-lived processing tasks where granular scaling and cost efficiency are required.

Why this answer

Azure Functions is the correct choice because it provides a serverless, event-driven compute service that can be triggered directly by Azure Event Hubs. It scales automatically based on the number of events, and you only pay for execution time, resulting in zero idle costs. This makes it ideal for processing streaming events in a cost-effective, scalable manner without managing infrastructure.

Exam trap

The trap here is that candidates often confuse Azure Functions with Azure Logic Apps, assuming both are serverless, but Logic Apps is designed for workflow integration and not for high-throughput, event-stream processing, leading to incorrect cost and performance assumptions.

How to eliminate wrong answers

Option B (Azure Container Instances) is wrong because it is a container orchestration service that incurs costs for running containers even when idle, and it lacks native Event Hubs integration without additional code or a custom trigger. Option C (Azure Logic Apps) is wrong because it is a workflow orchestration service designed for integrating applications and services, not for high-throughput event processing; it would introduce latency and higher costs per execution compared to Functions. Option D (Azure Kubernetes Service) is wrong because it requires a managed Kubernetes cluster that incurs ongoing costs for nodes even when no events are being processed, and it adds unnecessary complexity for a simple event-processing workload.

91
MCQmedium

A company uses Microsoft Entra ID. They want to grant a user temporary access to the Global Administrator role for a specific task. The access must require approval from a manager and automatically expire after 4 hours. Which Microsoft Entra ID feature should they use?

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

Microsoft Entra ID Privileged Identity Management (PIM) is the correct service because it enables just-in-time, time-bound activation of privileged Entra ID roles. With PIM, you can make a user eligible for a role, and the user can activate it for a configured maximum duration, optionally requiring business justification and approval from designated approvers. Once the activation time expires, the role is automatically deactivated, so the user no longer has the elevated permissions. PIM also provides audit logs and access reviews, but its core value is exactly the time-limited, approval-based elevation scenario described in the requirement.

Why this answer

Microsoft Entra ID Privileged Identity Management (PIM) provides just-in-time (JIT) privileged access, allowing users to activate roles like Global Administrator for a limited time. It supports approval workflows (manager approval) and configurable activation duration (e.g., 4 hours), making it the correct choice for temporary, approved, time-bound role elevation.

Exam trap

The trap here is confusing PIM's JIT activation with Conditional Access policies, which control access to applications but not role elevation, or with Access Reviews, which are for periodic recertification rather than temporary activation.

How to eliminate wrong answers

Option A is wrong because Conditional Access enforces policies based on signals like location or device state to control access to resources, but it does not provide time-bound role activation or approval workflows for privileged roles. Option B is wrong because Identity Protection detects and remediates identity-based risks (e.g., leaked credentials, sign-in anomalies) and does not manage role activation or approval. Option D is wrong because Access Reviews automate periodic attestation of group memberships or role assignments but do not support on-demand, temporary activation with approval and automatic expiration.

92
MCQeasy

You are designing a business continuity solution for a mission-critical Azure Kubernetes Service (AKS) cluster. The cluster hosts a stateful application that uses Azure Disks for persistent volumes. You need to ensure that the application can be recovered in a secondary region within 1 hour of a regional failure. What should you use to replicate the persistent volumes?

A.Azure Disk Backup with geo-redundant storage
B.Azure Backup with disk snapshot policies
C.Azure File Sync to replicate the disk content
D.Azure Site Recovery with replication of the AKS node VMs and attached disks
AnswerD

Azure Site Recovery with replication of the AKS node VMs and attached disks continuously replicates the entire VM and its managed disks to the secondary region, maintaining a ready-to-start copy that can be failed over within a defined RPO and RTO. It provides orchestrated failover, recovery plans, and test failover capabilities, allowing you to safely validate the DR process. While you may need to redeploy or reconfigure the AKS control plane after failover, the replicated node disks ensure your applications' state and data are present, making ASR the only option here that truly delivers a business continuity DR mechanism.

Why this answer

Azure Site Recovery (ASR) can replicate Azure VMs and their attached managed disks to a secondary region. For an AKS cluster, replicating the node VMs and their attached Azure Disks ensures that the persistent volumes (backed by Azure Disks) are available in the secondary region. Combined with AKS cluster deployment in the secondary region, this meets the 1-hour recovery time objective (RTO) for a stateful application.

Exam trap

The trap here is that candidates often choose Azure Backup or Disk Backup options because they associate 'backup' with disaster recovery, but these solutions lack the continuous replication and automated failover required to meet a 1-hour RTO for stateful workloads.

How to eliminate wrong answers

Option A is wrong because Azure Disk Backup with geo-redundant storage provides backup copies in a paired region but does not support continuous replication or automated failover, making it unsuitable for a 1-hour RTO. Option B is wrong because Azure Backup with disk snapshot policies creates point-in-time snapshots, not continuous replication, and recovery from snapshots typically exceeds 1 hour due to manual restore steps. Option C is wrong because Azure File Sync replicates file shares, not Azure Disks; it cannot replicate the block-level data of a disk attached to an AKS node.

93
MCQeasy

A company is planning to migrate its on-premises Active Directory to Microsoft Entra ID. They have a complex on-premises infrastructure with multiple forests and over 50,000 users. They need to synchronize identities and enable single sign-on (SSO) for Office 365. What should you recommend?

A.Microsoft Entra Connect Cloud Sync
B.Microsoft Entra Connect Health
C.Microsoft Entra ID synchronization
D.Microsoft Entra Connect Sync
AnswerD

Microsoft Entra Connect Sync supports multi-forest topologies and synchronises identities from multiple on-premises forests into Microsoft Entra ID, scaling beyond 50,000 users. It also enables SSO for Microsoft 365 through password hash synchronisation or pass-through authentication.

Why this answer

Microsoft Entra Connect Sync is the appropriate tool for synchronizing identities from a complex on-premises infrastructure with multiple forests and over 50,000 users to Microsoft Entra ID. It supports full identity synchronization, password hash synchronization, pass-through authentication, and federation for SSO to Office 365, and it can handle multi-forest environments with advanced configuration options. Microsoft Entra Connect Health only monitors the synchronization infrastructure and does not perform identity synchronization.

Exam trap

The trap is confusing Microsoft Entra Connect Cloud Sync with Microsoft Entra Connect Sync. Cloud Sync is a lightweight synchronization option suited to simple, small environments, while the full Sync version is required for complex, large environments such as multiple forests with 50,000+ users.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra Connect Cloud Sync is designed for simpler, smaller environments (typically fewer than 50,000 users) and does not support multi-forest synchronization or advanced SSO configurations like federation. Option B is wrong because 'Microsoft Entra Connect' is a generic term that encompasses both Cloud Sync and Sync; the question requires the specific tool for complex multi-forest environments, which is Entra Connect Sync. Option C is wrong because 'Microsoft Entra ID synchronization' is not a specific product or tool; it is a general concept, and the question asks for a specific recommendation.

94
MCQmedium

Your company has a hybrid identity solution with Microsoft Entra ID Connect syncing on-premises Active Directory to Microsoft Entra ID. You need to design a business continuity solution for the identity service in case of an on-premises outage. The solution must allow users to authenticate and access cloud applications even if the on-premises domain controllers are unavailable. Which feature should you enable?

A.Federation with AD FS in a secondary on-premises site
B.Password hash synchronization
C.Seamless Single Sign-On
D.Pass-through authentication with an agent in a secondary on-premises site
AnswerB

Password hash synchronization (PHS) is the only option that meets the requirement for pure cloud authentication without any on-premises runtime dependency. Azure AD Connect synchronizes a SHA256 hash of the user's AD password (derived from the MD4 hash) to Azure AD; at sign-in, Azure AD validates the credentials locally in the cloud with no call back to on-premises domain controllers. This eliminates the need for on-premises servers during authentication, while still allowing Azure AD to enforce conditional access and other cloud policies.

Why this answer

Password hash synchronization (PHS) is the correct choice because it synchronizes password hashes from on-premises Active Directory to Microsoft Entra ID, enabling cloud authentication even when on-premises domain controllers are unavailable. During an on-premises outage, users can still authenticate against Entra ID using their synced credentials, ensuring continued access to cloud applications without dependency on local infrastructure.

Exam trap

The trap here is that candidates often confuse Seamless SSO or Pass-through authentication as providing offline authentication, but neither works without on-premises infrastructure, whereas password hash synchronization is the only option that enables cloud authentication independently of on-premises domain controllers.

How to eliminate wrong answers

Option A is wrong because federation with AD FS in a secondary on-premises site still relies on on-premises infrastructure; if the primary site fails, the secondary site must be operational, and AD FS itself introduces additional complexity and dependency on local servers. Option C is wrong because Seamless Single Sign-On (SSO) is a feature that provides automatic sign-in when users are on corporate devices connected to the corporate network, but it does not provide authentication during an on-premises outage—it still requires the password hash or other authentication method to be validated. Option D is wrong because Pass-through authentication (PTA) requires an agent installed on-premises to validate credentials against on-premises Active Directory; if the on-premises domain controllers are unavailable, the PTA agent cannot authenticate users, even if a secondary site agent exists, unless that secondary site is also fully operational.

95
MCQeasy

A company uses Microsoft Entra ID. They need to grant external partners access to an internal application for a limited time (30 days). The access must be approved by a manager from the partner's organization. After the period ends, access should automatically be removed. The company also wants to send email reminders 7 days before expiration. Which Microsoft Entra ID feature should they use?

A.Microsoft Entra ID Access Reviews
B.Microsoft Entra ID Entitlement Management
C.Microsoft Entra ID Conditional Access
D.Microsoft Entra ID Identity Protection
AnswerB

Microsoft Entra ID Entitlement Management uses access packages with an expiration policy, automatically removing access after 30 days. It supports connected organisations, letting the partner's manager approve requests, and sends email notifications 7 days before expiry — satisfying the time-bound, externally approved access requirement.

Why this answer

Microsoft Entra ID Entitlement Management is the correct feature because it provides automated access lifecycle management for external users, including time-limited access packages, approval workflows (including external manager approval), and automatic expiration with email notifications. This directly matches the requirement for 30-day access with partner manager approval and 7-day reminder emails.

Exam trap

The trap here is confusing Entitlement Management (which handles the full lifecycle of external access with expiration and approvals) with Access Reviews (which is a periodic review tool, not an automated expiration mechanism).

How to eliminate wrong answers

Option A is wrong because Access Reviews are a periodic attestation mechanism that requires manual or semi-automated review cycles, not a one-time 30-day expiration with automatic removal and email reminders. Option C is wrong because Conditional Access enforces access policies (e.g., MFA, device compliance) in real time but does not manage access expiration, approval workflows, or automated email reminders. Option D is wrong because Identity Protection focuses on detecting and remediating identity-based risks (e.g., leaked credentials, sign-in anomalies) and does not handle external partner access lifecycle or time-bound approvals.

96
MCQmedium

Refer to the exhibit. You are analyzing Azure VM performance using Azure Monitor Logs. You run the KQL query shown. What is the purpose of the 'take 10' operator?

A.Limits the results to the first 10 rows after sorting by time.
B.Limits the time range to the last 10 hours.
C.Filters the results to only include the top 10 CPUs.
D.Samples the data to reduce query cost.
AnswerA

`take` in Kusto, also written as `limit`, returns exactly the first N rows from the result set that exists when the operator is evaluated. In this query, because `sort by time` (or `order by`) appears before `take`, the operator deterministically preserves the first 10 rows in chronological order, making it a row-count control rather than a time-window or aggregation operator. If there were no preceding sort, `take 10` could return arbitrary rows.

Why this answer

The 'take 10' operator in Kusto Query Language (KQL) returns a specified number of arbitrary rows from the query result set. When used after a sort operator (e.g., 'order by TimeGenerated desc'), it effectively limits the output to the first 10 rows of the sorted data, which in this context are the 10 most recent log entries. This is the standard behavior of 'take' in KQL, as it does not guarantee any specific order unless preceded by a sort.

Exam trap

The trap here is that candidates may confuse 'take' with time-based filtering (like 'where TimeGenerated > ago(10h)') or assume it samples data to reduce query costs, when in fact it simply limits the number of rows returned after the query has already processed the data.

How to eliminate wrong answers

Option B is wrong because 'take 10' does not filter by time range; it limits the number of rows returned, not the time span. Option C is wrong because 'take 10' does not filter by CPU count or any specific metric; it simply restricts the result set to 10 rows regardless of content. Option D is wrong because 'take 10' does not sample data to reduce cost; it retrieves actual rows from the result set, and cost is based on data scanned, not the number of rows returned after query execution.

97
Multi-Selectmedium

Which TWO Azure services can be used to automatically redirect traffic to an alternate region in the event of a regional outage? (Choose two.)

Select 2 answers
A.Azure Application Gateway
B.Azure Load Balancer
C.Azure Traffic Manager
D.Azure DNS
E.Azure Front Door
AnswersC, E

Azure Traffic Manager provides DNS-based global load balancing, using priority or performance routing to fail over to an alternate region when health probes detect an outage. This satisfies the stem's requirement for automatic redirection during a regional outage, since DNS responses point clients to a healthy regional endpoint.

Why this answer

Azure Traffic Manager (C) is a DNS-based global traffic load balancer that can route users to endpoints in different regions and, with priority routing plus endpoint monitoring, automatically fail over to an alternate region when the primary region's endpoint becomes unhealthy. Azure Front Door (E) is a global Layer 7 entry point that uses anycast, health probes, and origin groups to detect a regional outage and automatically redirect traffic to a healthy origin in another region. Azure Application Gateway (A) is a regional Layer 7 load balancer, so it can distribute traffic only among backends within its own region and cannot by itself redirect across regions during a regional outage.

Azure Load Balancer (B) is a regional Layer 4 load balancer scoped to a single region and has no global failover capability. Azure DNS (D) is a general-purpose authoritative DNS hosting service; it does not provide built-in health probing or automatic regional failover routing on its own.

Exam trap

The trap here is that candidates confuse regional load balancers (Application Gateway, Load Balancer) with global traffic routing services, forgetting that only DNS-based or Anycast-based services (Traffic Manager, Front Door) can redirect traffic across regions during an outage.

98
MCQhard

Your organization is designing a secure microservices architecture using Azure Kubernetes Service (AKS). The application must be compliant with PCI DSS, which requires strict network segmentation and encryption of data at rest and in transit. You need to design a solution that meets these requirements while minimizing operational overhead. The AKS cluster will be deployed in a virtual network. The application consists of multiple microservices that need to communicate with each other and with an Azure SQL Database. Some microservices are public-facing. Which design should you recommend?

A.Deploy AKS with a private API server, enable network policies, and use a service endpoint or private endpoint for Azure SQL Database.
B.Deploy AKS with a public API server and use Network Security Groups (NSGs) to restrict access.
C.Deploy AKS with a private API server and use a jump box for administration.
D.Deploy AKS with a public API server and disable network policies to simplify management.
AnswerA

A private API server removes the Kubernetes control plane from the public internet, so only authorized virtual networks can reach it. Enabling Azure Network Policies provides pod-level microsegmentation, restricting east-west traffic between microservices. Using a private endpoint or service endpoint for Azure SQL Database keeps database traffic on the Microsoft backbone, satisfying PCI DSS requirements that mandate private connectivity and defense in depth.

Why this answer

A private API server ensures the AKS control plane is inaccessible from the public internet, satisfying PCI DSS network segmentation. Enabling network policies (e.g., Calico or Azure Network Policy) enforces micro-segmentation between pods, and using a private endpoint for Azure SQL Database encrypts data in transit over the Microsoft backbone and isolates the database to the virtual network, meeting encryption and segmentation requirements with minimal operational overhead.

Exam trap

The trap here is that candidates may think a private API server alone is sufficient for compliance, but they overlook the need for network policies to enforce micro-segmentation between pods and a private endpoint for Azure SQL Database to meet data-in-transit encryption and isolation requirements.

How to eliminate wrong answers

Option B is wrong because a public API server exposes the Kubernetes control plane to the internet, violating PCI DSS network segmentation requirements; NSGs alone cannot prevent all attack vectors against the API server. Option C is wrong because while a private API server is used, relying on a jump box for administration adds unnecessary operational overhead and does not address the need for network policies to secure inter-microservice traffic or private connectivity to Azure SQL Database. Option D is wrong because a public API server and disabling network policies completely bypass both network segmentation and encryption requirements, leaving the cluster vulnerable and non-compliant with PCI DSS.

99
MCQmedium

Refer to the exhibit. You have an Azure Storage account with the settings shown. A developer reports that they cannot access the storage account from their Azure VM that is connected to subnet-a. The VM's subnet ID matches the one in the rule. What is the most likely cause of the issue?

A.The storage account requires HTTPS and the VM is using HTTP
B.The storage account does not have a firewall rule for the VM's public IP
C.The subnet does not have a service endpoint for Microsoft.Storage enabled
D.The storage account uses GRS replication which is not supported with network rules
AnswerC

Azure Storage virtual network rules are only effective when the client subnet has a service endpoint for `Microsoft.Storage` enabled. Without that service endpoint, the VM's outbound traffic to the storage account is source-NATed to its public IP, so the storage account sees a public internet address and the configured virtual network rule does not match. Enabling the service endpoint on the subnet is required to route traffic over the Azure backbone and present the VM's private IP to the storage account. This missing configuration is the direct cause of the connectivity failure described.

Why this answer

The most likely cause is that the subnet does not have a service endpoint for Microsoft.Storage enabled. When a storage account firewall rule allows access from a specific subnet, that subnet must have a service endpoint configured for Microsoft.Storage; otherwise, traffic from the VM is treated as originating from the VM's public IP and is blocked by the firewall. The exhibit shows a firewall rule for the subnet, but without the service endpoint, the rule is ineffective.

Exam trap

The trap here is that candidates assume adding a subnet rule in the storage account firewall is sufficient, but they overlook the prerequisite of enabling the Microsoft.Storage service endpoint on the subnet, which is a critical step for the rule to take effect.

How to eliminate wrong answers

Option A is wrong because the storage account requires HTTPS (port 443) and the VM using HTTP (port 80) would cause a different error (e.g., 400 Bad Request or connection refused), not a firewall block; the question states the developer 'cannot access' the storage account, which aligns with a network rule denial. Option B is wrong because the storage account has a firewall rule for the subnet (not the VM's public IP), and if the VM is connected to that subnet with a service endpoint, the public IP is irrelevant; the issue is the missing service endpoint, not a missing public IP rule. Option D is wrong because GRS replication is fully supported with network rules; Azure Storage network rules apply to the storage account endpoint regardless of replication type, and there is no restriction preventing GRS from working with firewall or service endpoint configurations.

100
MCQmedium

A company uses Azure Redis Cache to improve the performance of a web application. They need to ensure that cached data survives a failover to a secondary region. Which Azure Redis Cache tier should they choose?

A.Standard tier
B.Basic tier
C.Premium tier
D.Enterprise tier
AnswerC

The Premium tier is the appropriate choice because it includes built-in geo-replication, allowing you to link two cache instances in different regions to keep data synchronized and provide failover across regions. It also offers enterprise-grade features such as Redis persistence (RDB/AOF), clustering for scalability, and a 99.99% SLA, directly supporting both performance improvement and durable, geographically resilient caching. This tier meets the requirement without unnecessary architectural complexity, making it the correct answer.

Why this answer

The Premium tier of Azure Redis Cache supports geo-replication, which enables data to be replicated across paired regions. This ensures that cached data survives a failover to a secondary region, meeting the requirement for disaster recovery. The Standard tier only provides replication within a single region, while the Basic tier offers no replication at all.

Exam trap

The trap here is that candidates often confuse the Standard tier's in-region replication with cross-region disaster recovery, or they assume the Enterprise tier is always the best choice for high availability without considering the specific failover scenario described.

How to eliminate wrong answers

Option A is wrong because the Standard tier replicates data only within a single Azure region (two nodes in the same datacenter) and does not support cross-region failover. Option B is wrong because the Basic tier is a single-node cache with no replication, so all data is lost on any failure. Option D is wrong because the Enterprise tier (which uses Redis Enterprise) does support active geo-replication, but the Premium tier is the correct choice for the stated requirement as it provides passive geo-replication with a simpler configuration and is the tier explicitly designed for cross-region failover in the context of Azure Redis Cache.

101
Multi-Selectmedium

A company is designing a solution for storing sensitive financial records that must be retained for 7 years. The solution must meet the following requirements: - Data must be immutable during the retention period. - After the retention period, data must be automatically deleted. - The solution must minimize storage costs. Which two Azure services should the company use? (Choose two.)

Select 2 answers
A.Microsoft Purview Data Map
B.Azure Blob Storage lifecycle management
C.Azure NetApp Files with replication
D.Azure Blob Storage with immutable storage policy
E.Azure Files with snapshots
AnswersB, D

Azure Blob Storage lifecycle management automatically transitions blobs to Cool, Cold, or Archive tiers and executes user-defined deletion rules based on blob age, last modification, or index tags. For sensitive financial records that must be purged after a regulatory retention window, a lifecycle rule with an 'expire' action removes the blobs at the exact scheduled time, providing a cost-effective, fully managed deletion mechanism without manual cleanup.

Why this answer

Azure Blob Storage lifecycle management (B) is correct because it allows you to define rules to automatically delete blobs after a specified period, such as 7 years, minimizing storage costs by tiering or expiring data. Azure Blob Storage with immutable storage policy (D) is correct because it enforces WORM (Write Once, Read Many) immutability, preventing data modification or deletion during the retention period, which is essential for sensitive financial records.

Exam trap

The trap here is that candidates may think a single service like immutable storage alone handles deletion, but they overlook that immutability prevents deletion unless explicitly combined with lifecycle management to trigger automatic removal after the retention period ends.

102
MCQmedium

A company is designing a hybrid identity solution that allows users to access both on-premises applications and Microsoft 365 using a single identity. The solution must support legacy authentication protocols for on-premises apps and modern authentication for cloud apps. Which Azure service should the company use?

A.Active Directory Federation Services (AD FS)
B.Microsoft Entra Application Proxy
C.Microsoft Entra ID
D.Microsoft Entra Connect
AnswerB

Microsoft Entra Application Proxy is a cloud-managed reverse proxy that publishes on-premises web applications through your Microsoft Entra tenant without requiring a VPN or inbound firewall rules. It pre-authenticates users with Entra ID, supports MFA and Conditional Access, and can work with legacy apps that use Integrated Windows Authentication via Kerberos constrained delegation or forms-based authentication. The service installs a connector on-premises, which makes an outbound connection to the cloud, keeping internal endpoints hidden while providing modern identity controls.

Why this answer

Microsoft Entra Application Proxy provides secure remote access to on-premises web applications by publishing them through the Microsoft Entra ID service. It supports legacy authentication protocols (such as Integrated Windows Authentication) for on-premises apps while enabling modern authentication (OAuth 2.0, OpenID Connect) for cloud apps like Microsoft 365, all using a single identity from Microsoft Entra ID. This makes it the correct choice for a hybrid identity solution that bridges on-premises and cloud authentication requirements.

Exam trap

The trap here is that candidates often confuse Microsoft Entra Connect (a sync tool) with the application proxy capability, or assume AD FS is required for hybrid scenarios, but the question specifically requires support for legacy authentication protocols on on-premises apps, which Application Proxy handles through its connector and KCD integration.

How to eliminate wrong answers

Option A is wrong because Active Directory Federation Services (AD FS) is an on-premises federation service that provides single sign-on but requires additional infrastructure and does not natively support publishing on-premises apps with legacy authentication protocols through Microsoft Entra ID; it is more suited for federating identities rather than proxying legacy apps. Option C is wrong because Microsoft Entra ID alone is a cloud-based identity and access management service that does not include the reverse proxy functionality needed to expose on-premises applications with legacy authentication; it requires a separate service like Application Proxy for that purpose. Option D is wrong because Microsoft Entra Connect is a synchronization tool that syncs on-premises Active Directory objects to Microsoft Entra ID but does not provide application proxy capabilities or support legacy authentication protocols for on-premises apps.

103
MCQmedium

A company uses Microsoft Entra ID Premium P2. They need to automatically detect users with high-risk sign-ins (e.g., from anonymous IP addresses or leaked credentials) and require them to reset their password. Which Microsoft Entra ID feature should they configure?

A.Identity Protection
B.Privileged Identity Management
C.Conditional Access
D.Access Reviews
AnswerA

Identity Protection in Microsoft Entra ID Premium P2 continuously evaluates user and sign-in risk signals, such as leaked credentials and impossible travel. Its risk policies can automatically trigger a secure password change for high user risk, remediating compromised accounts without manual intervention. This automated remediation capability is exactly what the company needs.

Why this answer

Identity Protection is the correct feature because it is specifically designed to detect and remediate risky sign-ins, including those from anonymous IP addresses or leaked credentials. It uses machine learning to assign a risk level to each sign-in and user, and can automatically enforce password resets when high-risk events are detected, aligning with the requirement for automated detection and remediation.

Exam trap

The trap here is that candidates often confuse Conditional Access with Identity Protection, not realizing that Conditional Access is the enforcement engine that requires Identity Protection to first detect and assign the risk level, making Identity Protection the correct feature for automatic detection.

How to eliminate wrong answers

Option B (Privileged Identity Management) is wrong because it focuses on just-in-time access and approval workflows for privileged roles, not on detecting risky sign-ins or enforcing password resets for all users. Option C (Conditional Access) is wrong because while it can enforce policies based on sign-in risk, it does not automatically detect or assign risk levels; it relies on Identity Protection to provide the risk assessment. Option D (Access Reviews) is wrong because it is a governance tool for periodic review of group memberships or application access, not for real-time risk detection or password reset enforcement.

104
MCQhard

A company runs a multi-tier application on Azure VMs in the West US region. The application has web, application, and database tiers. They want to use Azure Site Recovery for disaster recovery to East US. They need to ensure that after failover, the web tier starts first, then the application tier, and finally the database tier after a consistency check. They also need to be able to perform non-disruptive DR drills. Which Azure Site Recovery capabilities should they use together?

A.Create a recovery plan with custom groups and scripts for startup order, and use test failover for DR drills
B.Use Azure Backup for the VMs and restore them in order after failover
C.Use an availability set to control startup order and use disaster recovery drills in a separate VNet
D.Use Azure Traffic Manager to route traffic after failover and manually start VMs in order
AnswerA

Azure Site Recovery recovery plans are the intended orchestration mechanism for multi-tier DR: you can define custom groups for application tiers and insert pre/post scripts (PowerShell or Azure Automation runbooks) so that VMs start in dependency order (e.g., database before web). Test failover executes these plans in an isolated test VNet with cloned recovery points, providing a non-disruptive, repeatable drill that validates the entire startup sequence without touching production.

Why this answer

Azure Site Recovery (ASR) recovery plans allow you to define custom groups and scripts to control the startup order of VMs after failover. By placing the web, application, and database tiers into separate groups with pre- and post-actions (e.g., PowerShell scripts), you can ensure the web tier starts first, then the application tier, and finally the database tier after a consistency check. ASR's test failover capability performs a non-disruptive DR drill by creating isolated copies of VMs in a separate VNet without impacting the production environment.

Exam trap

The trap here is that candidates may confuse Azure Backup's restore capabilities with ASR's orchestrated failover, or assume that availability sets or Traffic Manager can control startup sequencing, when only ASR recovery plans with custom groups and scripts provide the required ordered startup and non-disruptive DR drill functionality.

How to eliminate wrong answers

Option B is wrong because Azure Backup is designed for long-term retention and point-in-time restore, not for orchestrating multi-tier application startup order or performing non-disruptive DR drills with failover sequencing. Option C is wrong because availability sets control VM placement for high availability within a region, not startup order after failover, and they do not provide DR drill capabilities. Option D is wrong because Azure Traffic Manager handles DNS-based traffic routing, not VM startup sequencing, and manually starting VMs in order does not provide automated, scriptable orchestration or non-disruptive DR drills.

105
MCQeasy

Your company plans to migrate an on-premises application to Azure. The application requires low-latency access to a shared file system that supports SMB protocol. Which Azure storage solution should you recommend?

A.Azure Blob Storage
B.Azure Disk Storage
C.Azure Files
D.Azure Queue Storage
AnswerC

Azure Files is the correct answer because it offers fully managed file shares in the cloud that natively support the SMB (and NFS) protocol, enabling Windows, Linux, or macOS clients to mount the share with a standard UNC path or drive letter. It is designed for lift-and-shift scenarios: on-premises applications that rely on file shares can be migrated without code changes, and Azure Files integrates with Azure Active Directory Domain Services for identity-based access. This directly matches the requirement for a shared file system accessible via SMB.

Why this answer

Azure Files provides fully managed file shares in the cloud that support the SMB protocol, making it the ideal solution for migrating on-premises applications that require low-latency access to a shared file system. It allows you to lift and shift applications that rely on SMB file shares without code changes, and it can be accessed from Azure VMs or on-premises via SMB 3.0.

Exam trap

The trap here is that candidates often confuse Azure Blob Storage with file shares because both can store files, but Blob Storage does not support SMB protocol, which is the key requirement for this scenario.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage is an object storage solution designed for unstructured data (e.g., images, videos, backups) and does not support the SMB protocol; it uses REST APIs or NFS (preview) but not SMB. Option B is wrong because Azure Disk Storage provides block-level storage volumes for Azure VMs, but it is not a shared file system—it is attached to a single VM (unless using shared disks, which still do not provide native SMB file sharing). Option D is wrong because Azure Queue Storage is a messaging service for decoupling application components and does not provide file storage or SMB protocol support.

106
MCQhard

You are designing a storage strategy for a data analytics solution that processes large volumes of streaming data. The data must be stored in a cost-effective manner with low latency for hot data and infrequent access for cold data after 30 days. The solution must support both batch and interactive queries. Which combination of Azure storage services should you recommend?

A.Azure Data Lake Storage Gen2 with lifecycle management
B.Azure SQL Database with geo-replication
C.Azure Blob Storage with hot and cool access tiers
D.Azure Cosmos DB with multiple consistency levels
AnswerA

Azure Data Lake Storage Gen2 combines a hierarchical namespace with Azure Blob Storage's durable, scalable storage, giving analytics engines like Synapse, Databricks, and HDInsight native directory structures and POSIX-style access control. Lifecycle management policies can automatically transition data from hot to cool to archive tiers based on age or usage, slashing storage costs while keeping the data queryable for batch and interactive analytics. This makes it purpose-built for high-volume analytics pipelines where both performance and cost governance matter.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) combines the scalability and cost benefits of object storage with a hierarchical namespace, enabling both batch and interactive queries via services like Azure Synapse Analytics and Apache Spark. Lifecycle management policies can automatically transition hot data to cooler tiers (e.g., cool or archive) after 30 days, reducing costs for infrequently accessed cold data while maintaining low-latency access for hot data. This makes ADLS Gen2 the ideal choice for streaming data analytics that requires cost-effective tiered storage and supports diverse query patterns.

Exam trap

The trap here is that candidates often confuse Azure Blob Storage with ADLS Gen2, overlooking that the hierarchical namespace is essential for analytics workloads, and that lifecycle management alone on standard Blob Storage does not enable the same query performance or directory-level operations.

How to eliminate wrong answers

Option B is wrong because Azure SQL Database is a relational database optimized for transactional workloads, not for storing large volumes of streaming data or supporting batch/interactive analytics at scale; it lacks native lifecycle management for tiered storage and incurs higher costs for massive datasets. Option C is wrong because Azure Blob Storage with hot and cool access tiers does not natively support a hierarchical namespace, which is required for efficient batch and interactive queries in analytics scenarios; ADLS Gen2 provides this capability on top of Blob Storage. Option D is wrong because Azure Cosmos DB is a NoSQL database designed for low-latency, globally distributed transactional workloads, not for cost-effective tiered storage of large-scale streaming data; it lacks lifecycle management for cold data and is not optimized for batch analytics queries.

107
MCQhard

You are designing a high-availability solution for a stateful application that uses Azure NetApp Files (ANF) for persistent storage. The application must withstand a zonal failure within a region. What should you do?

A.Use Azure Files with zone-redundant storage (ZRS) and SMB multi-channel.
B.Use Azure NetApp Files cross-zone replication to replicate data between availability zones.
C.Use Azure Backup for ANF with daily snapshots stored in a different zone.
D.Deploy the application in an Availability Set and use ANF volumes with zone-redundant storage (ZRS).
AnswerB

Azure NetApp Files cross-zone replication continuously asynchronously replicates volume data from a primary ANF volume in one availability zone to a secondary volume in another zone, using NetApp SnapMirror technology. If the primary zone fails, you can mount the destination volume in the secondary zone, providing a much lower RTO than backup and true zonal resilience. This directly meets the high-availability requirement while staying within the ANF service, and the RPO is typically in the range of a few minutes.

Why this answer

Azure NetApp Files cross-zone replication asynchronously replicates volume data from a source zone to a destination zone within the same region, enabling failover if the primary zone fails. This meets the requirement for zonal failure tolerance while preserving the stateful application's persistent storage. Other options either lack native zone-redundant support for ANF or provide only backup, not continuous replication.

Exam trap

The trap here is that candidates confuse Azure Files ZRS (which is zone-redundant but not ANF) with Azure NetApp Files, or assume that backup snapshots alone provide high availability for zonal failures, when in fact continuous replication is required for minimal downtime and data loss.

How to eliminate wrong answers

Option A is wrong because Azure Files with ZRS provides zone-redundant storage but is a different service than Azure NetApp Files; the question specifically requires ANF for persistent storage, and Azure Files does not support the same protocols (e.g., NFSv3, SMB) or performance characteristics as ANF. Option C is wrong because Azure Backup for ANF with daily snapshots stored in a different zone provides point-in-time recovery, not continuous replication; it cannot achieve the required recovery point objective (RPO) for zonal failure and does not enable automatic failover. Option D is wrong because Azure NetApp Files does not support zone-redundant storage (ZRS); ANF volumes are zonal resources, and Availability Sets are for VMs, not storage; combining them does not provide zone-level redundancy for the storage layer.

108
MCQeasy

A company uses Azure Backup to protect their critical Azure VMs. An administrator accidentally deleted a file from one of the VMs. They need to restore that specific file quickly without restoring the entire VM. Which Azure Backup feature should they use?

A.Azure Backup full VM restore
B.Azure Backup file recovery
C.Azure Site Recovery
D.Azure Storage snapshots
AnswerB

Azure Backup file recovery is the correct feature because it directly addresses the need for rapid, granular restoration. From the Recovery Services vault, you select a restore point and run a script that mounts that backup as an iSCSI drive on a chosen or existing VM, allowing you to browse and copy specific files or folders instantaneously. This read-only mount works for both Windows and Linux VMs and avoids any full VM restore overhead, making it the fastest way to recover a single file.

Why this answer

Azure Backup's file recovery feature allows you to mount a recovery point as a drive on the VM (or another machine) using iSCSI, enabling you to browse and copy individual files without restoring the entire VM. This is the correct choice because it meets the requirement for a quick, granular restore of a single deleted file.

Exam trap

The trap here is that candidates may confuse Azure Backup's file recovery with Azure Site Recovery, thinking both provide granular restore, but Site Recovery is for replication and failover, not for point-in-time file recovery from backups.

How to eliminate wrong answers

Option A is wrong because full VM restore would recover the entire virtual machine, which is unnecessary and time-consuming for restoring a single file. Option C is wrong because Azure Site Recovery is designed for disaster recovery and replication of entire workloads to a secondary region, not for granular file-level recovery from backup snapshots. Option D is wrong because Azure Storage snapshots are a feature of Azure Storage accounts (blobs, files, disks) and are not directly integrated with Azure Backup's VM-level recovery points; they also require manual management and do not provide the iSCSI mount capability for file-level recovery.

109
Multi-Selectmedium

Your company is designing a hybrid network architecture to connect an on-premises data center to Azure. The requirements include: high availability, low latency, and cost optimization. Which TWO options should you recommend?

Select 2 answers
A.ExpressRoute Gateway
B.Single ExpressRoute circuit
C.Site-to-Site VPN
D.ExpressRoute Direct
E.Two ExpressRoute circuits from different providers
AnswersA, E

The ExpressRoute Gateway is the Azure-side virtual network gateway that terminates an ExpressRoute circuit and routes traffic between on-premises networks and Azure VNets. It provides low-latency, high-bandwidth connectivity by using a private, dedicated connection rather than the public internet, and it supports active-active mode to maintain availability even if one gateway instance fails. This is the essential component for hybrid connectivity, as it is the actual endpoint that enables traffic flow over ExpressRoute.

Why this answer

ExpressRoute Gateway is correct because it provides a dedicated, private connection from on-premises to Azure, bypassing the public internet for lower latency and more consistent performance. It supports high availability through active-active configurations and can be paired with multiple circuits for redundancy, meeting the hybrid network requirements.

Exam trap

The trap here is that candidates often assume a single ExpressRoute circuit is sufficient for high availability, but Azure requires at least two circuits from different providers to meet carrier-level redundancy, as a single circuit is a single point of failure.

110
MCQmedium

An enterprise data platform must store petabytes of raw files for analytics and support fine-grained access control through Microsoft Entra ID. Which storage solution should be selected?

A.Azure Queue Storage
B.Azure Disk Storage attached to one VM
C.Azure Cache for Redis
D.Azure Data Lake Storage Gen2
AnswerD

Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it combines Blob Storage's virtually unlimited scalability and durability with a hierarchical namespace, enabling directory-level rename and atomic operations. It integrates with Entra ID to enforce POSIX-like ACLs and RBAC, giving fine-grained, identity-based security over raw petabytes, and it is natively supported by analytics engines such as Apache Spark, Hive, and Azure Synapse. This makes it a true data lake capable of storing raw enterprise data at any volume while providing high-throughput access.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) combines a hierarchical namespace with Azure Blob Storage, enabling petabyte-scale storage for raw files and fine-grained access control via POSIX-like ACLs integrated with Microsoft Entra ID (formerly Azure AD). This makes it the ideal solution for enterprise analytics requiring both massive capacity and granular security.

Exam trap

The trap here is that candidates may confuse Azure Blob Storage (which lacks a hierarchical namespace and fine-grained ACLs) with ADLS Gen2, or assume that any Azure storage service can handle petabyte-scale analytics, ignoring the specific requirements for Entra ID integration and granular permissions.

How to eliminate wrong answers

Option A is wrong because Azure Queue Storage is a messaging service for asynchronous communication between application components, not a storage solution for raw analytics files, and it lacks the hierarchical namespace and Entra ID-based ACLs needed for fine-grained access control. Option B is wrong because Azure Disk Storage attached to a single VM is limited to the VM's capacity (typically terabytes, not petabytes), is not designed for multi-user analytics access, and requires the VM's OS to manage access, which does not natively integrate with Entra ID for fine-grained control. Option C is wrong because Azure Cache for Redis is an in-memory data store for caching and low-latency access, not a durable storage system for petabytes of raw files, and it does not support Entra ID-based ACLs for file-level permissions.

111
MCQhard

A company runs a mission-critical application on Azure virtual machines (VMs) in the West US region. The application consists of multiple VMs that must be recovered in a specific order during a disaster: database VM first, then application VMs, then web VMs. They also require that after failover to East US, the VMs retain their private IP addresses to avoid DNS updates. The recovery point objective (RPO) is 5 minutes and recovery time objective (RTO) is 30 minutes. The company needs to perform quarterly disaster recovery tests without impacting production. Which combination of Azure Site Recovery features should they configure?

A.Use crash-consistent replication, recovery plans with manual ordering, and target network with same IP address range
B.Use app-consistent replication, recovery plans with pre/post scripts for ordering, and static IP address assignment in failover settings
C.Use multi-VM consistency groups, recovery plans with automation runbooks, and Azure Traffic Manager to redirect traffic
D.Use application-consistent replication, recovery plans with pre/post scripts for ordering, and target network with different IP address range and DNS updates
AnswerB

App-consistent replication uses VSS on Windows or equivalent application quiescing on Linux to flush memory and pending I/O, producing a recovery point that is both VM-consistent and application-consistent, which is essential for a mission-critical database and supports an RPO of seconds. Recovery plans with pre/post scripts automate the ordering of failover steps, such as starting dependent applications or running validation scripts, eliminating manual sequencing delays. Static IP address assignment in the failover settings republishes the original private IPs on the target subnet, satisfying the explicit IP-retention requirement without DNS changes. This combination delivers the required data integrity, automated orchestration, and network continuity.

Why this answer

The requirement for an RPO of 5 minutes and RTO of 30 minutes necessitates application-consistent replication, which ensures database and application integrity. The need to recover VMs in a specific order is met by recovery plans with pre/post scripts, which allow custom actions (e.g., starting the database VM first, then application, then web). Static IP address assignment in failover settings ensures that VMs retain their private IP addresses after failover to East US, avoiding DNS updates.

Exam trap

The trap here is that candidates often confuse crash-consistent replication (which is faster but not application-safe) with application-consistent replication, or they assume that manual ordering in recovery plans is sufficient without realizing that pre/post scripts are required for complex multi-tier dependencies and that static IP assignment is needed to retain IP addresses across regions.

How to eliminate wrong answers

Option A is wrong because crash-consistent replication cannot achieve a 5-minute RPO for a mission-critical application with database VMs, as it does not guarantee application consistency; also, manual ordering in recovery plans is not sufficient for complex multi-tier recovery sequences. Option C is wrong because multi-VM consistency groups ensure crash consistency across VMs but do not provide the application-consistent replication needed for the 5-minute RPO, and Azure Traffic Manager is for traffic routing, not for retaining private IP addresses or ordering recovery. Option D is wrong because using a target network with a different IP address range and DNS updates contradicts the requirement to retain private IP addresses to avoid DNS updates.

112
Multi-Selecthard

Which THREE of the following are considerations when designing a storage solution for a high-availability application on Azure?

Select 3 answers
A.Recovery Point Objective (RPO) and Recovery Time Objective (RTO)
B.Use of zone-redundant storage (ZRS) for within-region resilience
C.Data encryption at rest using Azure Storage Service Encryption
D.Data striping with RAID 0 for performance
E.Use of geo-redundant storage (GRS) for cross-region disaster recovery
AnswersA, B, E

RPO and RTO are the foundational metrics that drive the replication and failover architecture for any Azure workload. RPO defines the maximum acceptable data loss measured in time, which dictates the frequency of synchronous or asynchronous replication between source and target. RTO defines the maximum acceptable downtime, which determines the required failover automation, testing cadence, and the choice between active-active and active-passive designs. Together, these metrics force explicit trade-offs between cost, complexity, and resilience, making them the first consideration for designing high availability and disaster recovery.

Why this answer

RPO and RTO are fundamental design considerations for any high-availability application. RPO defines the maximum acceptable data loss (measured in time), which directly influences the choice of backup frequency and replication type (e.g., synchronous vs. asynchronous). RTO defines the maximum acceptable downtime, which dictates the failover mechanism and infrastructure redundancy (e.g., active-passive vs. active-active).

Both metrics must be explicitly defined before selecting a storage redundancy tier or disaster recovery strategy.

Exam trap

The trap here is confusing security features (encryption at rest) or performance optimizations (RAID 0) with high-availability design requirements, leading candidates to select options that are valid in other contexts but irrelevant to uptime and disaster recovery.

113
MCQmedium

A company runs a global e-commerce platform on Azure VMs in a single region. They need to replicate the VMs to a secondary region for disaster recovery. Recovery must be possible within 30 minutes of a failure. The VMs run custom software that must be started in a specific order (database tier before web tier). Which Azure service should they use to meet both the replication and orchestration requirements?

A.Azure Site Recovery with recovery plans
B.Azure Backup with cross-region restore
C.Azure Migrate with replication
D.Azure Automation runbooks
AnswerA

Azure Site Recovery performs continuous block-level replication of Azure VMs to a secondary region, providing a low RPO; recovery plans group VMs into logical tiers, specify failover order, and can execute pre/post scripts, which lets the whole e-commerce stack fail over predictably within a 30-minute RTO. Recovery plans also allow manual or test failovers, so the response is organized rather than ad hoc.

Why this answer

Azure Site Recovery (ASR) with recovery plans is the correct choice because it provides both VM replication to a secondary region and the ability to orchestrate the startup order of VMs. Recovery plans allow you to group VMs into tiers (e.g., database and web) and define dependencies, ensuring the database tier starts before the web tier. ASR meets the 30-minute recovery time objective (RTO) by enabling failover to the secondary region within that timeframe.

Exam trap

The trap here is that candidates often confuse Azure Backup (which is for data protection and long-term retention) with Azure Site Recovery (which is for replication and failover), and overlook the orchestration requirement that only recovery plans can fulfill.

How to eliminate wrong answers

Option B is wrong because Azure Backup with cross-region restore is designed for long-term data retention and point-in-time recovery, not for orchestrating multi-tier application startup order or meeting a 30-minute RTO for full VM failover. Option C is wrong because Azure Migrate is a tool for assessing and migrating on-premises workloads to Azure, not for ongoing replication or disaster recovery orchestration. Option D is wrong because Azure Automation runbooks can execute scripts to start VMs in order, but they do not provide the underlying VM replication to a secondary region, which is required for disaster recovery.

114
MCQhard

A global logistics company is designing a solution that ingests telemetry data from thousands of IoT devices. The data must be processed in near real-time to detect anomalies and trigger alerts. The company wants to use a serverless, event-driven architecture that can scale automatically and minimize operational overhead. Which Azure service should the solutions architect use for the stream processing component?

A.Azure Event Hubs with Capture enabled
B.Azure Functions with an Event Hub trigger
C.Azure Stream Analytics
D.Azure Logic Apps with an IoT Hub connector
AnswerC

Azure Stream Analytics is a fully managed, serverless stream processing service that can analyze and process high volumes of streaming data from sources like IoT Hub or Event Hubs. It supports SQL-like queries for real-time analytics, anomaly detection, and can trigger alerts by outputting to services like Azure Functions or Logic Apps. It scales automatically and requires no infrastructure management.

Why this answer

Azure Stream Analytics is a serverless stream processing service that excels at real-time analytics on streaming data. It can ingest from IoT Hub or Event Hubs, apply SQL-like queries for anomaly detection, and output alerts to various destinations. It scales automatically and eliminates the need to manage infrastructure, aligning with the company's requirements for a serverless, event-driven architecture.

Exam trap

The trap here is assuming that Azure Functions is always the best serverless choice, but for complex stream processing with built-in operators, Stream Analytics is more appropriate.

115
MCQmedium

You have an Azure subscription that contains 100 virtual machines. You need to monitor the virtual machines for security vulnerabilities and receive recommendations. What should you use?

A.Microsoft Defender for Cloud
B.Azure Monitor
C.Microsoft Sentinel
D.Microsoft Defender XDR
AnswerA

Microsoft Defender for Cloud is the correct choice because it natively provides continuous vulnerability assessment for Azure VMs via its built-in Qualys scanner or the integrated Microsoft Defender for Servers plan. It identifies missing patches, misconfigurations, and potential security issues, then offers actionable remediation recommendations and hardening guidance. Beyond vulnerability scanning, it also delivers compliance assessments. Its recommendations are directly generated from resource configuration analysis and threat signals, making it the only listed service designed for cloud security posture management and vulnerability detection.

Why this answer

Microsoft Defender for Cloud (formerly Azure Security Center) provides unified security management and advanced threat protection across hybrid cloud workloads. It continuously assesses your virtual machines for security vulnerabilities, misconfigurations, and missing updates, then delivers actionable recommendations and a secure score to prioritize remediation. This directly matches the requirement to monitor VMs for vulnerabilities and receive recommendations.

Exam trap

The trap here is that candidates confuse Azure Monitor (which monitors performance and availability) with security monitoring, or assume Microsoft Sentinel (a SIEM) is the correct tool for vulnerability scanning, when in fact Defender for Cloud is the dedicated service for security posture management and vulnerability assessment.

How to eliminate wrong answers

Option B is wrong because Azure Monitor is a platform for collecting and analyzing telemetry data (metrics, logs) from resources, but it does not perform vulnerability scanning or provide security recommendations—it lacks the built-in vulnerability assessment and secure score features. Option C is wrong because Microsoft Sentinel is a cloud-native SIEM/SOAR solution for aggregating security logs, detecting threats, and orchestrating incident response; it does not natively scan VMs for vulnerabilities or generate compliance recommendations. Option D is wrong because Microsoft Defender XDR (formerly Microsoft 365 Defender) is an extended detection and response solution that correlates signals across endpoints, email, and identities, but it is not designed for vulnerability assessment of Azure VMs and does not provide the same centralized security posture management as Defender for Cloud.

116
MCQhard

You are reviewing a Conditional Access policy for a Microsoft Entra ID tenant. The exhibit shows the policy configuration. Users report that they are prompted for MFA every hour even when using approved Microsoft applications. The security team wants to reduce MFA prompts but maintain security. What should you modify?

A.Enable 'persistentBrowser' session control
B.Change cloudAppSecurityType to 'blockDownloads'
C.Remove the 'approvedApplication' grant control
D.Increase the signInFrequency value to 24 hours
AnswerD

Increasing the signInFrequency value to 24 hours directly reduces how often a user must re-authenticate, because this setting dictates the maximum time allowed between credential entries for all assigned apps. By setting it to a full day, users will only be challenged once within any 24-hour window, alleviating the frequent MFA prompts while still requiring periodic verification to maintain a reasonable security baseline. This is the correct adjustment because it targets the exact parameter that controls prompt cadence without weakening other access controls.

Why this answer

The sign-in frequency control in Conditional Access determines how often a user must re-authenticate. Increasing the value from 1 hour to 24 hours directly reduces the frequency of MFA prompts while still requiring re-authentication daily, balancing security and user experience. This change applies to approved Microsoft applications as configured in the policy.

Exam trap

The trap here is that candidates confuse session controls like 'persistentBrowser' with sign-in frequency, assuming that keeping the browser session alive will also reduce MFA prompts, but sign-in frequency is a separate, explicit time-based re-authentication control that overrides session persistence.

How to eliminate wrong answers

Option A is wrong because enabling 'persistentBrowser' session control keeps the browser session alive but does not affect the sign-in frequency for MFA prompts; it only prevents re-authentication for browser-based sessions, not for all approved applications. Option B is wrong because changing cloudAppSecurityType to 'blockDownloads' is a session control for Microsoft Defender for Cloud Apps that restricts data exfiltration, not a mechanism to reduce MFA prompt frequency. Option C is wrong because removing the 'approvedApplication' grant control would eliminate the requirement that only approved Microsoft applications can be used, potentially allowing non-approved apps and increasing security risk, not reducing MFA prompts.

117
Matchingmedium

Match each Azure identity service to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

Cloud-based identity and access management

Customer identity and access management for apps

Managed domain services like LDAP and Kerberos

Role-based access control for Azure resources

Policy-based evaluation to enforce access controls

Why these pairings

Azure AD is the core identity service for Microsoft cloud. Azure AD B2B enables external collaboration, Azure AD B2C serves customer-facing apps, and Azure AD DS provides domain services for VMs. Common confusions include swapping B2C with Azure AD or B2B with AD DS.

118
MCQmedium

A gaming company is developing a multiplayer online game that requires a low-latency data store for player profiles, inventory, and session state. The data is accessed globally, and the solution must support millions of concurrent players. The company expects write-heavy workloads with occasional reads. The solution must provide single-digit millisecond latency for reads and writes. The company also needs to run analytics on the data to understand player behavior, but analytics queries can tolerate higher latency (minutes). Which Azure data storage solution should the company recommend for the transactional data?

A.Azure SQL Database with active geo-replication
B.Azure Redis Cache with persistence
C.Azure Cosmos DB with multiple write regions
D.Azure Table Storage with geo-redundancy
AnswerC

Azure Cosmos DB with multiple write regions (multi-master) enables every region to accept writes, and each write is replicated asynchronously to all other regions with conflict resolution policies (e.g., last-writer-wins, custom). This delivers single-digit-millisecond read and write latencies at the 99th percentile anywhere in the world because the client can target the nearest region for both reads and writes. The service provides 99.999% availability with SLAs, automatic failover, and a choice of consistency levels, making it the correct fit for globally distributed, always-on multiplayer game state.

Why this answer

Azure Cosmos DB with multiple write regions is the correct choice because it provides global distribution with multi-master writes, delivering single-digit millisecond latency for both reads and writes at any scale. It supports millions of concurrent players via automatic and elastic scaling, and its change feed enables analytics with higher latency tolerance by streaming data to Azure Synapse or HDInsight without impacting transactional performance.

Exam trap

The trap here is that candidates often choose Azure Redis Cache (Option B) because of its low latency, but they overlook that it is a cache, not a durable transactional store, and cannot serve as the primary data store for player profiles and inventory with global write-heavy workloads.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database with active geo-replication supports only a single writable primary, creating a bottleneck for write-heavy global workloads, and its latency for writes can exceed single-digit milliseconds due to synchronous replication overhead. Option B is wrong because Azure Redis Cache with persistence is an in-memory cache, not a durable transactional data store; it lacks native support for complex queries, indexing, and global multi-write replication, and its persistence model can introduce data loss or higher latency under write-heavy loads. Option D is wrong because Azure Table Storage with geo-redundancy offers eventual consistency and higher latency (typically 10-50 ms) for writes, lacks native multi-region write support, and does not provide the single-digit millisecond latency required for real-time player interactions.

119
MCQeasy

A media company stores raw video files and processed output in Azure. These files are accessed via REST APIs by a processing application. After processing, the files are rarely accessed but must be retained. To minimize costs, the company wants to automatically move files to a cheaper storage tier after 30 days and archive them after 90 days. Which Azure storage solution and feature should they use?

A.Azure Blob Storage with lifecycle management policies
B.Azure Files with snapshot schedules
C.Azure Disk Storage with incremental snapshots
D.Azure NetApp Files with snapshot policies
AnswerA

Blob Storage is the only service here with built-in lifecycle management that can automatically transition media files across hot, cool, cold, and archive tiers based on age or last modification. For raw videos and processed output, rules can move older data to cool after 30 days and to archive after 90 days, optimizing cost without manual intervention. Access tiers are native to blobs, so this directly fits the requirement.

Why this answer

Azure Blob Storage with lifecycle management policies is correct because it allows you to define rules that automatically transition blobs from the hot tier to the cool tier after 30 days and then to the archive tier after 90 days. This directly meets the cost-minimization requirement for rarely accessed files that must be retained, as lifecycle management automates tier transitions without manual intervention.

Exam trap

The trap here is that candidates may confuse Azure Files or Azure NetApp Files with object storage, not realizing that only Azure Blob Storage supports REST API access and automated lifecycle tiering to cool and archive tiers.

How to eliminate wrong answers

Option B is wrong because Azure Files is a fully managed file share accessed via SMB or NFS, not REST APIs, and snapshot schedules provide point-in-time recovery, not automated tiering between storage tiers. Option C is wrong because Azure Disk Storage provides block-level storage for VMs with incremental snapshots for backup, not object storage with lifecycle tiering, and it does not support REST API access for media files. Option D is wrong because Azure NetApp Files offers high-performance NFS/SMB volumes with snapshot policies for data protection, but it lacks built-in lifecycle management to automatically move data to cheaper tiers like cool or archive.

120
MCQhard

A company has multiple Azure virtual networks (VNets) in different regions and an on-premises data center connected via ExpressRoute. They need to implement a hub-and-spoke topology where a hub VNet hosts shared network virtual appliances (NVAs) for traffic inspection. All traffic between spokes and between spokes and on-premises must be routed through the hub. The company wants to minimize the administrative overhead of configuring and maintaining routing. Which Azure solution should they implement?

A.Use Azure Virtual WAN with a secured virtual hub.
B.Use VNet peering with user-defined routes (UDRs) in each spoke and Azure Route Server.
C.Create a single large VNet and use network security groups (NSGs) to isolate traffic.
D.Use Azure Firewall in the hub VNet and configure forced tunneling via custom routes.
AnswerA

Azure Virtual WAN provides a managed hub-and-spoke architecture with automatic routing. A secured virtual hub can integrate NVAs or Azure Firewall, and it handles transitive routing between spokes and on-premises without manual route tables or UDRs.

Why this answer

Azure Virtual WAN with a secured virtual hub is the correct choice because it provides a managed hub-and-spoke topology with built-in routing, eliminating the need for manual user-defined routes (UDRs) and route tables. The secured virtual hub includes Azure Firewall for traffic inspection, and all inter-spoke and on-premises traffic is automatically routed through the hub via the Virtual WAN routing engine, which uses the Border Gateway Protocol (BGP) to propagate routes dynamically. This minimizes administrative overhead by centralizing routing and security management.

Exam trap

The trap here is that candidates often choose VNet peering with UDRs (Option B) because it is a familiar pattern for hub-and-spoke, but they overlook that Azure Virtual WAN is the managed service designed to eliminate the administrative overhead of manual routing, especially when multiple regions and on-premises connectivity are involved.

How to eliminate wrong answers

Option B is wrong because using VNet peering with UDRs in each spoke and Azure Route Server still requires manual configuration and maintenance of UDRs for each spoke to force traffic through the hub NVAs, which increases administrative overhead and does not provide a fully managed routing solution. Option C is wrong because creating a single large VNet and using NSGs to isolate traffic violates the hub-and-spoke requirement for traffic inspection through NVAs; NSGs are stateless or stateful filters that do not route traffic through a central inspection point, and a single VNet cannot span multiple regions natively without additional complexity. Option D is wrong because using Azure Firewall in the hub VNet with forced tunneling via custom routes still requires manual UDR configuration on each spoke subnet to direct traffic to the firewall, and it does not provide the automated, scalable routing that Azure Virtual WAN offers for multi-region and on-premises connectivity.

121
MCQhard

Your company has a large number of IoT devices sending telemetry to Azure IoT Hub. The data must be processed in near real-time to detect anomalies and trigger alerts. Additionally, the processed data must be stored in a time-series database for historical analysis. Which combination of Azure services should you recommend?

A.Azure Functions and Azure SQL Database
B.Azure HDInsight and Azure Cosmos DB
C.Azure Data Factory and Azure Blob Storage
D.Azure Stream Analytics and Azure Data Explorer
AnswerD

Azure Stream Analytics is a fully managed, serverless stream-processing engine that uses SQL-like syntax to run continuous queries over IoT Hub or Event Hubs data, enabling real-time filtering, windowed aggregations, and pattern detection. Azure Data Explorer (ADX) is a fast, fully managed analytics database specifically optimized for time-series and telemetry data, with native time-based partitioning, high-cardinality grouping, and built-in time-series functions (e.g., series_decompose) for trend and anomaly analysis. This combination is ideal for IoT telemetry: Stream Analytics handles the real-time processing and ingestion while ADX provides low-latency, interactive storage and exploration, making it the correct answer.

Why this answer

Azure Stream Analytics provides real-time stream processing to detect anomalies and trigger alerts from IoT Hub telemetry. Azure Data Explorer (ADX) is a fully managed, high-performance time-series database optimized for storing and analyzing large volumes of time-stamped data, making it the ideal choice for historical analysis. Together, they meet both the near real-time processing and time-series storage requirements.

Exam trap

The trap here is that candidates often confuse Azure Stream Analytics with Azure Data Factory or Azure Functions, mistakenly thinking batch or serverless compute can handle near real-time stream processing, while overlooking that Azure Data Explorer is the only Azure service purpose-built for time-series storage and analytics at scale.

How to eliminate wrong answers

Option A is wrong because Azure Functions is a serverless compute service for event-driven code, not a stream processing engine, and Azure SQL Database is a relational database not optimized for time-series data ingestion or query performance at IoT scale. Option B is wrong because Azure HDInsight is a big data analytics platform (e.g., Spark, Hadoop) that introduces significant latency and operational overhead for near real-time processing, and Azure Cosmos DB is a multi-model NoSQL database that lacks native time-series optimizations like automatic retention policies and time-based partitioning. Option C is wrong because Azure Data Factory is an orchestration and ETL service for batch data movement, not real-time stream processing, and Azure Blob Storage is an object store with no time-series indexing or query capabilities.

122
MCQeasy

A company needs to store video files for a media streaming application. The files are accessed frequently for the first 30 days, then rarely after that. The solution must minimize storage costs while ensuring low-latency access during the initial period. Which storage tier should be used for the first 30 days?

A.Azure Blob Storage Hot tier
B.Azure Blob Storage Cool tier
C.Azure Premium Blob Storage
D.Azure Blob Storage Archive tier
AnswerA

Azure Blob Storage Hot tier is the default and optimal choice for video files that are accessed frequently, such as during the first 30 days of a media streaming workload. It provides low latency (milliseconds) and high throughput for continuous streaming, with storage costs that are lower than Premium or Archive tiers while still being performant. Unlike Cool or Archive tiers, Hot tier has no minimum storage duration or retrieval charges, making it cost-efficient for sustained, high-frequency read operations.

Why this answer

Azure Blob Storage Hot tier is designed for data that is accessed frequently, offering low-latency access (typically under 10 milliseconds for first-byte read) and the highest storage cost but lowest access cost. Since the video files require low-latency access during the first 30 days, the Hot tier meets the performance requirement while minimizing overall cost compared to Premium Blob Storage, which is optimized for sub-millisecond latency and higher IOPS scenarios.

Exam trap

The trap here is that candidates often choose the Cool tier thinking it balances cost and access, but they overlook that Cool tier has higher access costs and a 30-day early deletion penalty, making it more expensive than Hot for frequent access during the first 30 days.

How to eliminate wrong answers

Option B is wrong because the Cool tier has higher access costs and a 30-day early deletion penalty, making it suboptimal for frequent access during the first 30 days; it is designed for data accessed infrequently (about once a month or less). Option C is wrong because Azure Premium Blob Storage provides sub-millisecond latency via SSDs and is intended for high-transaction workloads, not for minimizing storage costs for frequently accessed video files; it would be significantly more expensive than the Hot tier. Option D is wrong because the Archive tier has the lowest storage cost but the highest access latency (hours to rehydrate) and is intended for data that is rarely accessed (less than once a year); it cannot provide low-latency access during the first 30 days.

123
MCQhard

A company is designing a solution for a global e-commerce platform that requires low-latency access to product catalog data from multiple regions. The data is read-heavy with occasional updates. The solution must support automatic scaling and provide high availability. Which Azure service should you recommend?

A.Azure SQL Database with active geo-replication
B.Azure Cosmos DB with multi-region writes
C.Azure Table Storage
D.Azure Cache for Redis
AnswerB

Azure Cosmos DB with multi-region writes is purpose-built for global distribution, offering turnkey active-active replication across any number of Azure regions. It provides single-digit-millisecond read and write latencies at the 99th percentile, automatic and elastic scaling of throughput and storage, and multiple well-defined consistency models, so a global e-commerce platform can serve users from their nearest region with low latency and high availability, while also supporting multi-region write concurrency for true active-active operation.

Why this answer

Azure Cosmos DB with multi-region writes is the correct choice because it provides global distribution with turnkey multi-master replication, enabling low-latency reads and writes from any Azure region. It supports automatic scaling through request units (RU/s) and offers 99.999% high availability with multiple well-defined consistency levels, making it ideal for a read-heavy, globally distributed e-commerce catalog with occasional updates.

Exam trap

The trap here is that candidates often confuse Azure SQL Database's active geo-replication (which supports only a single write region) with true multi-region writes, or they assume a cache like Redis can serve as the primary data store for a globally distributed, read-heavy workload with occasional updates.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database with active geo-region replication supports only a single writable primary replica; all other regions are read-only secondaries, which cannot handle occasional writes from multiple regions with low latency. Option C is wrong because Azure Table Storage is a NoSQL key-value store that lacks native multi-region write support, automatic scaling is limited to partition-level throughput, and it does not provide the sub-10-millisecond latency guarantees required for a global e-commerce platform. Option D is wrong because Azure Cache for Redis is an in-memory cache, not a primary data store; it does not persist data by default, cannot serve as the authoritative source for product catalog updates, and lacks built-in multi-region write capabilities.

124
MCQmedium

A global e-commerce company runs a web application in multiple Azure regions. They need to distribute incoming HTTPS traffic across regional deployments to provide low latency and high availability. The solution must support SSL offloading, Web Application Firewall (WAF) policies, and content caching to reduce backend load. They also need to route users to the nearest healthy backend region. Which Azure service should they use?

A.Azure Traffic Manager
B.Azure Front Door
C.Azure Application Gateway
D.Azure Content Delivery Network (CDN)
AnswerB

Azure Front Door is the correct choice because it is a true global layer 7 load balancer that terminates TLS at its edge points of presence, offloading encryption processing from the origin web servers. It includes an integrated web application firewall (WAF) capable of inspecting requests before they reach backend applications, and it offers edge caching for static and dynamic content. Additionally, Front Door uses Anycast and intelligent routing to direct each user's request to the nearest available and healthy regional backend, providing automatic global failover and path-based routing that satisfy all requirements of a multi-region e-commerce deployment.

Why this answer

Azure Front Door is the correct choice because it is a global, scalable entry point that provides HTTPS traffic distribution across multiple Azure regions with low latency, SSL offloading, WAF policies, and content caching. It uses Anycast-based routing to direct users to the nearest healthy backend region, meeting all the requirements for high availability and performance.

Exam trap

The trap here is that candidates often confuse Azure Traffic Manager (DNS-level routing) with Azure Front Door (HTTP/HTTPS-level routing), overlooking the need for SSL offloading, WAF, and content caching, which Traffic Manager cannot provide.

How to eliminate wrong answers

Option A (Azure Traffic Manager) is wrong because it operates at the DNS level and does not support SSL offloading, WAF policies, or content caching; it only routes traffic based on DNS responses without inspecting the HTTP/HTTPS payload. Option C (Azure Application Gateway) is wrong because it is a regional load balancer that provides SSL offloading and WAF, but it cannot distribute traffic across multiple regions or route users to the nearest healthy backend region globally. Option D (Azure Content Delivery Network (CDN)) is wrong because it focuses on caching static content at edge locations and does not provide SSL offloading, WAF, or intelligent routing to the nearest healthy backend region for dynamic traffic.

125
MCQmedium

A company is deploying an internal web application on Azure VMs. The application requires SSL offloading, session stickiness, and URL-based routing (e.g., /api/* to one backend, /app/* to another). The solution must operate within a single Azure region and must not be exposed to the public internet. Which Azure load balancing solution should they use?

A.A
B.B
C.C
D.D
AnswerC

Azure Application Gateway can be deployed as an internal (private) application gateway with a private frontend IP address inside the VNet, keeping the application fully internal. It offers native Layer 7 features including SSL termination (offloading), cookie-based session affinity, and URL path-based routing through listener and rule configurations. This makes it the only option that satisfies all three requirements—SSL offloading, session stickiness, and URL-based routing—within an internal network boundary.

Why this answer

Azure Application Gateway v2 is the correct choice because it provides SSL offloading (SSL termination at the gateway), session stickiness (cookie-based affinity), and URL-based routing (path-based routing rules) within a single Azure region. It can be deployed with a private IP address only, ensuring it is not exposed to the public internet, meeting all requirements.

Exam trap

The trap here is that candidates often confuse Azure Front Door with Application Gateway, but Front Door is a global service requiring public endpoints and multi-region support, whereas Application Gateway can be deployed privately within a single region.

How to eliminate wrong answers

Option A is wrong because Azure Load Balancer operates at Layer 4 (TCP/UDP) and cannot perform SSL offloading or URL-based routing; it only distributes traffic based on IP and port. Option B is wrong because Azure Traffic Manager is a DNS-based global load balancer that operates across regions and requires public endpoints; it cannot provide SSL offloading or URL-based routing within a single region. Option D is wrong because Azure Front Door is a global Layer 7 load balancer with SSL offloading and URL routing, but it is designed for multi-region deployments and requires public internet exposure; it cannot be restricted to a single region with private-only access.

126
MCQmedium

Your company runs a critical e-commerce application on Azure Virtual Machines (VMs) in a single region. You need to design a disaster recovery (DR) solution that meets a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 1 hour for the application tier. The application uses Azure SQL Database (single database). Which combination of Azure services should you recommend to meet the RPO and RTO?

A.Use Azure Site Recovery for VMs and Azure SQL Database read-scale replicas
B.Use Azure Backup for VM replication and Azure SQL Database auto-failover groups
C.Use Azure Front Door with regional load balancing and Azure SQL Database geo-restore
D.Use Azure Site Recovery for VM replication to a secondary region and Azure SQL Database active geo-replication
AnswerD

Azure Site Recovery continuously replicates Azure VMs to a secondary region, providing crash-consistent and app-consistent recovery points with an RPO typically under 15 minutes, and it supports orchestrated failover to meet the required RTO. Azure SQL Database active geo-replication asynchronously replicates transactions to a fully readable secondary database in another region, offering an RPO of about 5 seconds and manual failover capability with minimal recovery time. Together, these services deliver the low RPO/RTO needed for a critical online transaction processing application, making this the correct solution.

Why this answer

Azure Site Recovery provides VM replication to a secondary region with RPO as low as 15 seconds and RTO typically under 1 hour, meeting the 15-minute RPO and 1-hour RTO. Azure SQL Database active geo-replication creates a readable secondary database in another region with an RPO of 5 seconds or less and supports manual failover within minutes, satisfying the stated RPO and RTO. This combination ensures both compute and database tiers can be recovered in the secondary region within the required timeframes.

Exam trap

The trap here is that candidates often confuse Azure Backup (a backup service with longer RPO/RTO) with Azure Site Recovery (a replication service for DR), or they mistakenly think read-scale replicas or geo-restore can meet aggressive RPO/RTO requirements when they are designed for different purposes.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database read-scale replicas are designed for read-only workload offloading, not disaster recovery; they do not support failover and cannot meet the RPO/RTO for a single database DR scenario. Option B is wrong because Azure Backup for VM replication is a backup solution, not a replication service, and its RPO is typically 12-24 hours with RTO measured in hours or days, failing the 15-minute RPO and 1-hour RTO. Option C is wrong because Azure Front Door with regional load balancing provides traffic routing and health probing but does not replicate VMs or databases; Azure SQL Database geo-restore restores from backups with an RPO of 1 hour and RTO of 12-24 hours, which does not meet the required 15-minute RPO and 1-hour RTO.

127
Multi-Selecteasy

You are designing a highly available architecture for a web application that runs on Azure VMs. The solution must distribute incoming traffic across multiple VMs in an availability set. Which TWO Azure components should you include? (Choose two.)

Select 2 answers
A.Azure Load Balancer
B.Azure Traffic Manager
C.Azure Front Door
D.Availability Set
E.Azure Application Gateway
AnswersA, D

Azure Load Balancer is a layer 4 (TCP/UDP) load balancer that distributes traffic to virtual machines in a backend pool within the same Azure region. It uses health probes to detect VM availability and automatically routes traffic only to healthy instances, providing regional high availability. Because the scenario only requires distributing web traffic across VMs in one region, Load Balancer meets the requirement without introducing unnecessary global or application-layer complexity.

Why this answer

Azure Load Balancer (A) is correct because it distributes incoming traffic across multiple VMs in an availability set at the transport layer (TCP/UDP), providing high availability by rerouting traffic away from failed instances. An availability set (D) is required to ensure VMs are placed in different fault domains and update domains, protecting against hardware failures and planned maintenance. Together, they form the core of a highly available architecture for VMs within a single Azure region.

Exam trap

The trap here is that candidates often confuse the regional, layer-4 Azure Load Balancer with the global, layer-7 Azure Front Door or Application Gateway, or mistakenly think Traffic Manager can distribute traffic within a single region, when it is designed for cross-region DNS-based routing.

128
MCQmedium

A company runs a critical application on Azure VMs in a single region. The application uses Azure SQL Database as its data store. The company needs a disaster recovery solution that can fail over the entire application stack (VMs and database) to another region with a Recovery Point Objective (RPO) of 5 minutes and a Recovery Time Objective (RTO) of 1 hour. The solution must be automated and minimize manual steps. Which combination of Azure services should they implement?

A.Azure Site Recovery for VMs and active geo-replication with auto-failover groups for Azure SQL Database
B.Azure Backup for VMs and Azure SQL Database backup to another region
C.Azure Site Recovery for VMs and Azure DNS for database failover
D.Azure Load Balancer for VMs and Azure SQL Database failover groups
AnswerA

Azure Site Recovery continuously replicates the source VMs to the secondary region using a recovery point objective (RPO) as low as a few seconds, easily satisfying the 5-minute RPO requirement, and its recovery plans orchestrate compute failover to meet the 1-hour RTO. Active geo-replication for Azure SQL Database maintains a readable secondary replica in the paired region and, when combined with an auto-failover group, automatically redirects connections to the secondary on outage with an RPO of 5 seconds and an RTO typically under 1 hour. Together, these two services provide a cohesive disaster recovery solution for both the IaaS VM tier and the PaaS database tier, with asynchronous replication that meets the stated recovery objectives.

Why this answer

Azure Site Recovery (ASR) orchestrates replication and automated failover of Azure VMs to a secondary region, meeting the RTO of 1 hour. Active geo-replication with auto-failover groups for Azure SQL Database provides a readable secondary replica in another region with an RPO of 5 seconds (well under the 5-minute requirement) and enables automatic failover without manual intervention. Together, they automate the entire application stack failover, minimizing manual steps.

Exam trap

The trap here is that candidates often confuse Azure Backup (which is for data recovery, not failover) with Azure Site Recovery (which is for full-stack disaster recovery), or they assume DNS or load balancers alone can handle database failover without understanding that database replication is required first.

How to eliminate wrong answers

Option B is wrong because Azure Backup for VMs and Azure SQL Database backup to another region provides point-in-time restore but does not support automated failover; restoring from backup would take hours, exceeding the 1-hour RTO, and the RPO would be limited to the backup schedule (typically 24 hours). Option C is wrong because Azure DNS for database failover does not handle database replication or failover; it only manages DNS records, leaving the database unreplicated and requiring manual steps to redirect traffic, which fails the automation requirement. Option D is wrong because Azure Load Balancer distributes traffic but does not replicate VMs or databases; it cannot fail over VMs to another region, and Azure SQL Database failover groups alone (without active geo-replication) do not provide the required RPO of 5 minutes—failover groups require geo-replication to be configured separately.

129
Multi-Selecthard

A company is designing a backup strategy for Azure resources. They have the following resources: Azure VMs, Azure SQL Database, and Azure Files shares. They need to meet the following requirements: 1) Backup of VMs must be application-consistent. 2) SQL Database backups must be retained for 10 years. 3) Azure Files backups must support soft delete. Which THREE services or features should they use?

Select 3 answers
A.Azure Backup
B.Soft delete for Azure Files
C.Long-term retention (LTR) for Azure SQL Database
D.Azure Site Recovery
E.Azure Policy
AnswersA, B, C

Azure Backup is the native backup service that creates application-consistent recovery points for Azure VMs using VSS for Windows and file-system-consistent snapshots for Linux. Recovery points are stored in a Recovery Services vault or Backup vault, and you can define backup policies for schedule and retention, enabling point-in-time restores across disks or the entire VM. This is a true backup solution because it preserves historical versions of data independent of live replication.

Why this answer

Azure Backup is the correct service for VM backups because it supports application-consistent backups for Windows VMs via Volume Shadow Copy Service (VSS) and for Linux VMs via file-system-consistent snapshots with pre/post-scripts, ensuring that applications are in a consistent state at the time of backup. This directly meets requirement 1.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery (disaster recovery) with Azure Backup (backup), or assume Azure Policy can enforce backup configurations, but only the specific services listed (Azure Backup, soft delete for Azure Files, and LTR for SQL Database) directly address the stated requirements.

130
MCQmedium

A company wants to analyze IoT sensor data from millions of devices in near real-time and store the raw data for batch processing. Which combination of Azure services should they use?

A.Azure Event Hubs and Azure Synapse Analytics
B.Azure IoT Hub and Azure Cosmos DB
C.Azure Data Lake Storage and Azure Stream Analytics
D.Azure Event Hubs and Azure Blob Storage
AnswerD

Event Hubs is a fully managed, high-throughput event ingestion service that accepts millions of messages per second with low latency, making it ideal for collecting IoT telemetry. Blob Storage offers massively scalable, cost-effective object storage that preserves the raw event bodies exactly as received, providing a durable data lake foundation for subsequent analytical processing. Together they satisfy the core requirement of ingesting and storing raw sensor data before any transformation or querying.

Why this answer

Azure Event Hubs is a highly scalable data streaming platform and event ingestion service capable of ingesting millions of events per second from IoT devices in near real-time. Azure Blob Storage provides cost-effective, durable object storage for the raw data, which can then be used for batch processing with services like Azure Data Lake Analytics or Azure Synapse. This combination directly meets the requirements for near real-time ingestion and raw data storage for batch processing.

Exam trap

The trap here is that candidates often confuse Azure IoT Hub with Azure Event Hubs, assuming IoT Hub is required for all IoT scenarios, but Event Hubs is the correct choice for high-throughput, near real-time event ingestion without device management overhead.

How to eliminate wrong answers

Option A is wrong because Azure Synapse Analytics is primarily a data warehouse for structured analytics, not optimized for storing raw, unstructured IoT data for batch processing; using it for raw storage would be costly and unnecessary. Option B is wrong because Azure IoT Hub is a device management and messaging service, not a high-throughput event ingestion pipeline for near real-time analytics, and Azure Cosmos DB is a NoSQL database for transactional workloads, not designed for storing massive volumes of raw data for batch processing. Option C is wrong because Azure Data Lake Storage is a storage service, not an ingestion service; it cannot ingest and buffer streaming data in near real-time, and Azure Stream Analytics is a real-time processing engine, not a storage solution for raw data.

131
MCQmedium

Refer to the exhibit. You deploy an Azure SQL Database with a secondary replica in another region using the ARM template shown. You need to ensure that the database can fail over automatically with zero data loss. What is missing?

A.Configure long-term backup retention.
B.Disable readScaleOut on the primary database.
C.Create a failover group that includes both databases.
D.Set zoneRedundant to true on the primary database.
AnswerC

Creating a failover group that includes both the primary and secondary databases establishes an active geo-replication relationship and exposes a single read-write listener endpoint plus a read-only endpoint. When the primary database experiences an outage, the group automatically initiates failover to the secondary, and applications can reconnect using the same group-level FQDN (or the FailoverPartner modifier) without code changes. This is the correct Azure SQL Database feature for managing automatic, cross-region failover with near-zero data loss based on the configured grace period.

Why this answer

A failover group is required to enable automatic failover between the primary and secondary replicas in Azure SQL Database. Without a failover group, the secondary replica exists as a readable copy but cannot automatically take over during a disaster. The failover group also supports the ability to achieve zero data loss by using the 'GracePeriodWithDataLoss' setting or by ensuring synchronous replication is configured, which is part of the failover group's properties.

Exam trap

The trap here is that candidates often confuse a geo-replicated secondary replica (which only provides readable standby) with a failover group (which adds automatic failover and a listener endpoint), leading them to think the secondary replica alone is sufficient for automatic failover.

How to eliminate wrong answers

Option A is wrong because long-term backup retention (LTR) is for point-in-time restore of backups beyond the default retention period, not for automatic failover or zero data loss. Option B is wrong because disabling readScaleOut on the primary database only affects whether the secondary replica is used for read-only workloads; it does not impact automatic failover or data loss prevention. Option D is wrong because setting zoneRedundant to true on the primary database provides high availability within a single region by replicating across availability zones, but it does not enable cross-region automatic failover or guarantee zero data loss across regions.

132
MCQmedium

A company deploys a web application on Azure VMs across multiple availability zones in a region. They need to distribute incoming traffic across VMs in all zones, maintain session persistence, and support SSL offloading and URL-based routing (e.g., /api/* to one pool, /app/* to another). Which Azure load balancing solution should they use?

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

Azure Application Gateway is a regional, layer-7 web traffic load balancer that understands HTTP(S) and offers native SSL termination (offloading), URL/path-based routing, multi-site hosting, cookie-based session affinity, and a built-in Web Application Firewall (WAF). This makes it the appropriate choice for a web application spread across multiple Azure VMs within the same region, because it can inspect each request's URL and steer it to the right backend pool. Its ability to offload encryption, rewrite HTTP headers, and perform health checks at the application layer matches the stated requirements precisely, and it is commonly deployed in front of VM scale sets for web workloads.

Why this answer

Azure Application Gateway is the correct choice because it is a Layer 7 (HTTP/HTTPS) load balancer that supports SSL offloading, URL-based routing (e.g., /api/* and /app/* to different backend pools), and session persistence (cookie-based affinity). It can distribute traffic across VMs in multiple availability zones within a region, meeting all stated requirements.

Exam trap

The trap here is that candidates often confuse Azure Load Balancer (Layer 4) with Application Gateway (Layer 7), assuming all load balancers support HTTP-level features like URL routing and SSL offloading, but only Layer 7 solutions do.

How to eliminate wrong answers

Option A is wrong because Azure Load Balancer operates at Layer 4 (TCP/UDP) and does not support SSL offloading or URL-based routing; it cannot inspect HTTP paths. Option C is wrong because Azure Traffic Manager is a DNS-based global traffic router that distributes traffic across regions, not within a single region, and it does not support SSL offloading or URL-based routing. Option D is wrong because Azure Front Door is a global Layer 7 service that supports SSL offloading and URL-based routing but is designed for multi-region distribution, not for distributing traffic across VMs within a single region's availability zones.

133
MCQhard

Refer to the exhibit. A role assignment has a condition that controls blob deletion. A user assigned this role tries to delete a blob with tag 'Project' set to 'ProjectB'. What will happen?

A.The deletion is allowed because the condition only applies to write operations
B.The deletion is allowed because the condition does not affect blob deletion
C.The deletion is denied because the blob does not have the required tag
D.The deletion is denied because the condition version is 2.0 and not supported
AnswerC

The role assignment condition permits blob deletion only when the blob carries the required tag value. Because the blob's 'Project' tag is set to 'ProjectB' rather than the value the condition expects, the condition evaluates false and the delete operation is blocked.

Why this answer

The role assignment condition likely requires the blob to have the tag 'Project' set to a specific value (e.g., 'ProjectA'). Since the blob in question has the tag 'Project' set to 'ProjectB', the condition is not satisfied, and the deletion is denied. Option C correctly identifies this mismatch.

Exam trap

The trap is that candidates may focus on the action type or condition version, but the key is the tag value mismatch. The condition requires a specific tag value, and the blob has a different one, leading to denial.

How to eliminate wrong answers

Option A is wrong because the condition explicitly targets the delete action (Microsoft.Storage/storageAccounts/blobServices/containers/blobs/delete), not just write operations, so it does apply to blob deletion. Option B is wrong because the condition directly affects blob deletion by requiring a specific tag value; it does not leave deletion unaffected. Option D is wrong because condition version 2.0 is fully supported in Azure RBAC for storage actions, and the version does not cause denial.

134
MCQmedium

A company uses Microsoft Entra ID (Microsoft Entra ID). They want to automatically detect sign-in attempts from anonymous IP addresses and sign-ins from unfamiliar locations. When such a risk is detected, they want to block the sign-in or require multi-factor authentication (MFA) in real time. Additionally, they need a dashboard that provides a summary of risk events and allows investigation. Which Microsoft Entra ID feature should they use?

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

Microsoft Entra ID Identity Protection is the risk detection engine that continuously analyzes sign-ins and user behavior, flagging events such as leaked credentials, impossible travel, and anonymous IP addresses. It assigns a risk level to both users and individual sign-ins and surfaces these findings on a dashboard with detailed investigation tools. These risk levels are then consumed by Conditional Access policies to enforce remediation like password reset or blocking access. Without Identity Protection, there is no risk signal source for other services to act on.

Why this answer

Microsoft Entra ID Identity Protection is the correct feature because it automatically detects sign-in risks such as anonymous IP addresses and unfamiliar locations, and can trigger real-time remediation actions like blocking the sign-in or requiring MFA. It also provides a risk dashboard and investigation capabilities, directly matching the requirements for risk detection, automated response, and reporting.

Exam trap

The trap here is that candidates often confuse Conditional Access as the detection mechanism, but Conditional Access is only the enforcement layer; Identity Protection is the actual detection engine that generates the risk signals used by Conditional Access.

How to eliminate wrong answers

Option B is wrong because Conditional Access is a policy engine that enforces access controls based on conditions, but it does not itself detect risks like anonymous IPs or unfamiliar locations; it relies on Identity Protection to provide risk signals. Option C is wrong because Privileged Identity Management (PIM) focuses on just-in-time privileged role activation and access governance, not on detecting sign-in risks from anonymous IPs or unfamiliar locations. Option D is wrong because Access Reviews are used for periodic attestation of group memberships or role assignments, not for real-time risk detection or automated sign-in blocking.

135
MCQmedium

A company runs a critical SQL Server database on an Azure virtual machine in the West US region. They need a disaster recovery solution that replicates the database to a secondary region (East US) with a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 2 hours. The solution must also support non-disruptive disaster recovery drills. The company currently uses SQL Server Standard Edition. Which Azure service should they implement?

A.Azure Site Recovery
B.SQL Server Always On Availability Groups
C.Azure Backup with cross-region restore
D.Azure SQL Database geo-replication
AnswerA

Azure Site Recovery replicates the entire Azure VM at the block level to a secondary region, achieving an RPO as low as 30 seconds for SQL Server when app-consistent snapshots are enabled through the SQL Server VSS writer. It provides a dedicated test failover capability that provisions the replica in an isolated VNet without any impact on production, fully satisfying the non-disruptive drill requirement. ASR works with SQL Server Standard Edition on IaaS and supports orchestrated recovery plans for multi-tier failover, making it the only option here that meets all stated RPO/RTO criteria with minimal operational overhead.

Why this answer

Azure Site Recovery (ASR) replicates the entire VM, including the SQL Server database, to the secondary region with an RPO as low as 15 minutes and an RTO of 2 hours when using a recovery plan. It supports non-disruptive disaster recovery drills by allowing test failovers that run in an isolated network without impacting the production environment. This makes ASR the correct choice for a SQL Server Standard Edition VM requiring cross-region DR with drills.

Exam trap

The trap here is that candidates often choose SQL Server Always On Availability Groups without realizing that Standard Edition lacks the necessary features (e.g., readable secondaries, multi-database support) to meet the RPO/RTO and drill requirements, or they mistakenly think Azure SQL Database geo-replication can be applied to a SQL Server VM.

How to eliminate wrong answers

Option B is wrong because SQL Server Always On Availability Groups requires SQL Server Enterprise Edition for the advanced features needed to meet the RPO/RTO, and Standard Edition only supports basic availability groups with a single database and no readable secondaries, which cannot achieve the required 15-minute RPO or support non-disruptive drills. Option C is wrong because Azure Backup with cross-region restore provides point-in-time backups with an RPO of typically 12-24 hours (not 15 minutes) and an RTO that can exceed 2 hours due to restore time, plus it does not support live, non-disruptive disaster recovery drills. Option D is wrong because Azure SQL Database geo-replication is a PaaS feature that cannot be applied to a SQL Server running on an Azure VM (IaaS); it only works with Azure SQL Database managed instances or single databases.

136
MCQmedium

A company runs critical Azure VMs. They want to protect against accidental deletion or corruption of data by implementing a retention policy for Azure Backup. They need to keep daily backups for 30 days, weekly backups for 12 weeks, and monthly backups for 12 months. Which Azure Backup feature should they configure?

A.Immutable vault
B.Backup policy with long-term retention
C.Backup tiering
D.Soft delete
AnswerB

A backup policy in Azure Backup is the mechanism that defines both the backup frequency (when recovery points are created) and the retention rules that govern how long each recovery point is kept. By specifying a daily backup with 30 days retention, a weekly backup with 12 weeks retention, and a monthly backup with 12 months retention, the policy can create and automatically prune recovery points according to these exact schedules. This directly satisfies the stated requirement for different retention durations across daily, weekly, and monthly recovery points.

Why this answer

A backup policy with long-term retention (LTR) in Azure Backup allows you to define granular retention rules for daily, weekly, monthly, and yearly backup points. This directly meets the requirement to keep daily backups for 30 days, weekly for 12 weeks, and monthly for 12 months by configuring the retention duration for each frequency in the backup policy.

Exam trap

The trap here is that candidates confuse Immutable vault or Soft delete with retention policies, but those features address data protection from deletion or tampering, not the ability to specify granular retention durations for different backup frequencies.

How to eliminate wrong answers

Option A is wrong because Immutable vault protects backup data from being deleted or overwritten before its retention period expires, but it does not provide the ability to configure different retention durations for daily, weekly, and monthly backups. Option C is wrong because Backup tiering moves older recovery points to a lower-cost storage tier (e.g., from hot to cold or archive), but it does not define or enforce retention durations; it is a cost-optimization feature, not a retention policy. Option D is wrong because Soft delete provides a safety net by retaining deleted backup data for a default period (14 days) to allow recovery from accidental deletion, but it does not allow you to specify custom retention periods like 30 days daily, 12 weeks weekly, or 12 months monthly.

137
MCQeasy

Your company has a Microsoft Entra ID tenant with 10,000 users. You plan to grant external partners access to a specific SharePoint Online site using Microsoft Entra B2B collaboration. You need to ensure that partners can authenticate using their own corporate credentials. What should you configure?

A.Cross-tenant synchronization
B.Conditional Access policy for guest users
C.Microsoft Entra B2B collaboration with external identities
D.Microsoft Entra guest user accounts with password
AnswerC

Microsoft Entra B2B collaboration is the external-identities feature that lets you invite external users to access resources while they authenticate with their own identity provider, such as a corporate Azure AD tenant, Microsoft account, or a social IdP. This creates a guest user object in your tenant but the actual sign-in occurs at the partner's home tenant, and your tenant accepts the resulting token. This satisfies the requirement of allowing partner users to use their own credentials without managing passwords for them.

Why this answer

Microsoft Entra B2B collaboration allows external partners to authenticate using their own corporate credentials (such as Azure AD, Microsoft account, or other identity providers) without requiring a separate password or local account. This is the correct solution because it directly supports the requirement for partners to use their own identity providers, enabling seamless access to the SharePoint Online site via guest user invitations.

Exam trap

The trap here is that candidates often confuse Cross-tenant synchronization (Option A) with B2B collaboration, but Cross-tenant synchronization is for internal multi-tenant scenarios, not for granting external partners access with their own credentials.

How to eliminate wrong answers

Option A is wrong because Cross-tenant synchronization is designed to synchronize users between two Azure AD tenants for internal collaboration, not for granting external partners access to a specific SharePoint site with their own credentials. Option B is wrong because a Conditional Access policy for guest users controls access conditions (e.g., MFA, device compliance) after the guest user is already invited, but it does not enable authentication with the partner's own corporate credentials. Option D is wrong because creating guest user accounts with passwords would require partners to manage separate credentials, defeating the purpose of using their own corporate identities and violating the principle of federated authentication.

138
MCQeasy

A company needs to store and retrieve large binary files (e.g., images and videos) for a web application. The data must be accessible via HTTPS URLs and support both public read access for anonymous users and private access for administrators. The solution must be highly durable and cost-effective for storing terabytes of data. Which Azure storage solution should they recommend?

A.Azure Blob Storage
B.Azure Files
C.Azure Queue Storage
D.Azure Table Storage
AnswerA

Azure Blob Storage is the correct choice because it is an object storage service purpose-built for massive amounts of unstructured data, including large binary files like images and videos. It exposes every blob via a unique HTTP/HTTPS URL, allowing both private access (using stored access policies or shared access signatures) and public access at the container or blob level, which is ideal for direct retrieval by clients or browsers. Blob Storage also scales to exabytes, offers tiered storage (hot, cool, archive) to optimize cost, and integrates with Azure CDN to serve media at scale, making it the de facto solution for storing and serving binary content.

Why this answer

Azure Blob Storage is the correct choice because it is designed for storing large amounts of unstructured data, such as images and videos, and supports both public anonymous read access (via a public container or blob-level access policy) and private access (via shared access signatures or Azure AD authentication). It provides HTTPS URL access for direct retrieval, offers 99.9999999999% (11 nines) durability for hot and cool tiers, and is cost-effective for terabytes of data due to its tiered storage options (hot, cool, archive).

Exam trap

The trap here is that candidates may confuse Azure Files (a managed file share) with Blob Storage because both can store files, but Azure Files uses SMB/NFS protocols and is not designed for direct HTTPS URL access or public anonymous read for large binary objects.

How to eliminate wrong answers

Option B (Azure Files) is wrong because it provides fully managed file shares accessible via SMB and NFS protocols, not HTTPS URLs for direct binary object retrieval, and is optimized for shared file access rather than large-scale unstructured blob storage. Option C (Azure Queue Storage) is wrong because it is a messaging service for asynchronous communication between application components, not for storing or retrieving binary files. Option D (Azure Table Storage) is wrong because it is a NoSQL key-value store for structured data, not for large binary files like images and videos.

139
MCQmedium

A company is designing a backup strategy for a critical Azure SQL Database. The database is used in a production environment and the company requires the ability to restore to any point within the last 35 days with a maximum granularity of 5 minutes. Which backup configuration should the company choose?

A.Use Azure Backup for SQL Server in Azure VM
B.Configure point-in-time restore with a retention period of 35 days and a backup frequency of 5 minutes
C.Use Azure SQL Database automatic backups with a retention period of 35 days
D.Configure geo-redundant backup with long-term retention
AnswerC

Azure SQL Database automatic backups provide the exact capabilities required: full, differential, and transaction log backups are taken automatically, and you can configure the retention period for point-in-time restore (PITR) up to 35 days. With automatic backups, you can restore to any point in time within the retention period at 5-minute granularity, which satisfies the requirement of a 5-minute recovery point objective (RPO). This is the correct and simplest approach because no external backup solution is needed.

Why this answer

Azure SQL Database's built-in automatic backups provide point-in-time restore (PITR) with a configurable retention period of up to 35 days and a default backup frequency that enables restore granularity of 5 minutes. This meets the requirement without additional configuration or cost, as automatic backups are enabled by default and include differential and transaction log backups every 5-10 minutes.

Exam trap

The trap here is that candidates confuse the configurable backup frequency of Azure Backup for VMs with the automatic, service-managed backup schedule of Azure SQL Database, leading them to select Option B or A when the native PITR feature already meets the requirement.

How to eliminate wrong answers

Option A is wrong because Azure Backup for SQL Server in Azure VM is designed for SQL Server running on virtual machines, not for Azure SQL Database (a PaaS service), and it does not offer the native 5-minute granularity or 35-day retention without custom policy configuration. Option B is wrong because point-in-time restore is a feature of Azure SQL Database automatic backups, not a separate configuration; you cannot set a backup frequency of 5 minutes manually—the frequency is determined by the service's transaction log backup schedule. Option D is wrong because geo-redundant backup with long-term retention addresses disaster recovery and archival retention beyond 35 days, not the granular point-in-time restore requirement within 35 days.

140
MCQmedium

A company has multiple on-premises sites and Azure VNets in different regions. They need to connect all networks with a single mesh topology, ensuring that any network can communicate with any other network directly. They also want to minimize administrative overhead. Which Azure service should they use?

A.Azure Virtual WAN
B.Azure VPN Gateway
C.Azure ExpressRoute
D.Azure Peering Service
AnswerA

Azure Virtual WAN is the correct choice because it provides a cloud-native mesh connectivity solution built on a hub-and-spoke architecture with regional hubs. It automates the creation of any-to-any connections between branch offices, remote users, and VNets, with integrated routing that eliminates the need to manually configure individual VPN tunnels or peer each VNet. Virtual WAN uses the Microsoft backbone for transit, ensuring consistent low-latency routing across regions and on-premises sites, and supports both Site-to-Site VPN and ExpressRoute in a single managed topology.

Why this answer

Azure Virtual WAN is the correct choice because it provides a managed, global mesh network that automatically connects on-premises sites and Azure VNets across regions using a hub-and-spoke architecture with built-in transitive routing. This eliminates the need to manually configure individual VPN gateways or ExpressRoute circuits for each pair of networks, directly supporting the requirement for any-to-any direct communication with minimal administrative overhead.

Exam trap

The trap here is that candidates often confuse Azure VPN Gateway's ability to create multiple site-to-site connections with a true mesh topology, overlooking that VPN Gateway lacks automatic transitive routing and requires manual configuration for any-to-any connectivity, whereas Virtual WAN provides this natively.

How to eliminate wrong answers

Option B (Azure VPN Gateway) is wrong because it only creates point-to-site or site-to-site connections between individual networks; it does not natively support a full mesh topology without complex, manual configuration of multiple VPN tunnels and route tables, which increases administrative overhead. Option C (Azure ExpressRoute) is wrong because it provides private, dedicated connectivity between on-premises sites and Azure, but it does not inherently create a mesh between multiple on-premises sites or VNets; additional routing and gateway configurations are required to achieve transitive connectivity. Option D (Azure Peering Service) is wrong because it is designed to optimize connectivity to Microsoft cloud services over the internet, not to create a mesh network between customer-owned on-premises sites and Azure VNets.

141
MCQhard

A data platform must support analytical queries over petabytes of files in a data lake, while preserving hierarchical namespaces and fine-grained ACLs. Which storage service should you design around?

A.Azure Data Lake Storage Gen2.
B.Azure Files premium shares.
C.Azure Table Storage.
D.Azure Queue Storage.
AnswerA

Azure Data Lake Storage Gen2 is correct because it combines Azure Blob Storage's durable, scalable object storage with a hierarchical namespace, enabling true file/directory semantics such as atomic rename and POSIX-like access control lists (ACLs). It is specifically engineered as a scalable data lake for petabyte-scale analytical workloads, supporting parallel-processing engines like Azure Synapse, Databricks, and Hadoop via ABFS (Azure Blob File System) driver. This design optimizes throughput for full-scan analytical queries and allows incremental directory-level operations, making it the default storage platform for enterprise data platforms.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it combines a hierarchical namespace with POSIX-like ACLs, enabling fine-grained access control at the file and directory level while supporting petabyte-scale analytical workloads. It is built on Azure Blob Storage, providing high-throughput and parallel processing for big data analytics engines like Azure Synapse, Spark, and Hadoop.

Exam trap

The trap here is that candidates may confuse Azure Files (which also supports ACLs) with ADLS Gen2, overlooking that Azure Files is optimized for shared file access (SMB/NFS) and not for petabyte-scale analytical data lake workloads with hierarchical namespace and POSIX ACLs.

How to eliminate wrong answers

Option B is wrong because Azure Files premium shares provide SMB/NFS file shares with ACLs but are designed for low-latency, IOPS-intensive workloads (e.g., lift-and-shift apps), not for petabyte-scale analytical queries over a data lake. Option C is wrong because Azure Table Storage is a NoSQL key-value store for structured, semi-structured data at scale, but it lacks a hierarchical namespace and does not support file-level ACLs or analytical query patterns over files. Option D is wrong because Azure Queue Storage is a messaging service for decoupling application components, not a storage service for data lake analytics or hierarchical namespace management.

142
MCQmedium

A multinational company stores large amounts of unstructured data (documents, images) that must be read with low latency from multiple global regions. Data is written primarily in one region but read globally. Cost optimization is a key requirement. Which Azure storage replication option should they use?

A.Azure Blob Storage with geo-redundant storage (GRS)
B.Azure Blob Storage with read-access geo-redundant storage (RA-GRS)
C.Azure Files with premium shares
D.Azure NetApp Files
AnswerB

RA-GRS extends GRS by providing a read-only endpoint at the secondary region, so clients can retrieve data directly from the geo-replicated copy without waiting for a failover. This lets the storage account serve low-latency reads in both the primary and the paired secondary regions while still using standard, cost-effective blob storage rather than premium tiers. Note that the secondary is eventually consistent, and there can be a slight replication delay, but for most unstructured content such as documents and media this is an acceptable trade-off.

Why this answer

B is correct because RA-GRS provides geo-redundant storage with read access to the secondary region, enabling low-latency reads from multiple global regions while maintaining cost efficiency. The data is written primarily in one region, but RA-GRS allows read requests to be served from the secondary region without additional compute costs, meeting the global read requirement.

Exam trap

The trap here is that candidates often confuse GRS with RA-GRS, assuming geo-redundancy alone provides read access to the secondary region, but GRS requires a manual failover to enable reads, while RA-GRS allows reads from the secondary region at all times.

How to eliminate wrong answers

Option A is wrong because GRS provides geo-redundant storage but does not allow read access to the secondary region, so reads from other regions would still be served from the primary region, increasing latency. Option C is wrong because Azure Files with premium shares is designed for high-performance file shares with low latency but uses locally redundant storage (LRS) or zone-redundant storage (ZRS), not geo-replication, and is cost-prohibitive for large-scale unstructured data. Option D is wrong because Azure NetApp Files is a high-performance file service for enterprise workloads (e.g., SAP, HPC) with NFS/SMB protocols, not optimized for cost-effective global read access of unstructured data, and uses LRS or ZRS by default.

143
Matchingmedium

Match each Azure storage redundancy option to its description.

Drag a concept onto its matching description — or click a concept then click the description.

Concepts
Matches

3 copies within a single datacenter

3 copies across 3 availability zones in a region

LRS in primary region + LRS in paired secondary region

GRS with read access to secondary region

ZRS in primary region + LRS in paired secondary region

Why these pairings

Azure Storage offers several redundancy options: LRS (local), ZRS (zone), GRS (geo), and RA-GRS (geo with read access). Common confusions include mixing LRS and ZRS, or assuming all geo-replicated options provide read access.

144
MCQmedium

Your company is deploying a web application that experiences unpredictable traffic spikes. You need to ensure the application can handle sudden increases in load automatically without manual intervention and minimize costs during low traffic periods. Which Azure service should you use?

A.Azure App Service with manual scale-out
B.Azure Functions with consumption plan
C.Virtual Machine Scale Set with autoscale
D.Azure Container Instances
AnswerC

Virtual Machine Scale Sets with autoscale rules are the correct choice because they automatically adjust the number of VM instances based on metrics like CPU percentage, memory, or custom thresholds. This enables horizontal scaling to handle traffic spikes by adding instances and also scaling in during low demand to reduce costs. The approach is ideal for hosting web applications that require full control over the VM image, dependencies, or infrastructure-level configuration.

Why this answer

Virtual Machine Scale Sets with autoscale rules can automatically adjust the number of VM instances based on demand. Option A (Azure App Service with manual scaling) does not autoscale automatically. Option B (Azure Functions) is for event-driven workloads, not web apps.

Option D (Azure Container Instances) does not autoscale natively.

145
Multi-Selecthard

Which THREE of the following are valid strategies for designing a disaster recovery plan for Azure Virtual Desktop? (Choose three.)

Select 3 answers
A.Use Azure Front Door to route RDP traffic to the secondary region
B.Use Azure File Sync to replicate FSLogix profile shares to a secondary region
C.Pre-deploy a secondary host pool in the DR region and use Azure Traffic Manager to redirect connections
D.Rely on Azure Backup to restore session hosts in the secondary region
E.Replicate session host VMs to a secondary region using Azure Site Recovery
AnswersB, C, E

Azure File Sync replicates the file hierarchy from a primary SMB share to a file share in the secondary region, keeping FSLogix profile containers available to users after failover. Because FSLogix profiles are stored as VHDX files in file shares, sync copies them without needing a backup restore, and the DR region's session hosts simply attach to the synced share. This preserves persistent user state and is a valid DR strategy when combined with compute failover.

Why this answer

Option B is correct because Azure File Sync can replicate the SMB file shares that host FSLogix profile containers and Office container VHDX files to a secondary region, giving users access to their profiles during a regional failover. Option C is correct because pre-deploying a secondary host pool in the DR region and using Azure Traffic Manager (or a similar global load balancer) to redirect user connections is a standard AVD multi-region DR pattern that reduces recovery time. Option E is correct because Azure Site Recovery can continuously replicate session host VMs to a secondary region so they can be failed over and brought online as replacement session hosts during a disaster.

Option A is not valid because Azure Front Door does not proxy RDP traffic (TCP 3389); it is an HTTP/HTTPS layer-7 service, and AVD clients connect to the gateway/broker, not through Front Door. Option D is not a valid DR strategy because Azure Backup restores data and VMs but does not provide the low-RTO regional failover or the AVD control-plane/broker redirection needed for a disaster recovery plan.

Exam trap

The trap here is that candidates often confuse Azure Front Door (an HTTP/HTTPS load balancer) with Azure Traffic Manager (a DNS-based traffic router that can handle RDP traffic), leading them to incorrectly select Option A instead of Option C.

146
MCQeasy

A company has multiple Azure virtual networks (VNets) in different Azure regions and an on-premises data center connected via ExpressRoute. They want to connect all VNets to each other and to the on-premises network securely over the Microsoft global backbone. They also want to simplify management by using a single orchestration interface. Which Azure service should they use?

A.Azure Virtual WAN
B.VNet peering
C.Azure VPN Gateway
D.Azure ExpressRoute
AnswerA

Azure Virtual WAN deploys regional hubs that are connected by a Microsoft-backbone mesh, enabling any-to-any transit between spokes, branches, and on-premises sites without manually defining each pairing. Each hub aggregates VPN, ExpressRoute, and point-to-site gateways, and route propagation is automatically managed with virtual hub routing tables, so organizations can scale to multiple VNets and regions with a single orchestration plane. This is exactly the centralized multi-region interconnection and branch integration the scenario requires.

Why this answer

Azure Virtual WAN is correct because it provides a hub-and-spoke architecture that connects branch offices, VNets, and on-premises networks over the Microsoft global backbone. It offers a single orchestration interface for managing connectivity, routing, and security policies across multiple regions and ExpressRoute circuits, meeting the requirement for secure, global connectivity with simplified management.

Exam trap

The trap here is that candidates often confuse VNet peering (which is point-to-point) with the hub-and-spoke model of Virtual WAN, or assume ExpressRoute alone can connect multiple VNets, missing the requirement for a single orchestration interface and transitive routing across regions.

How to eliminate wrong answers

Option B (VNet peering) is wrong because it only connects two VNets directly and does not provide a single orchestration interface for multiple VNets across regions; it also requires manual transitive routing configuration and does not natively integrate with ExpressRoute for on-premises connectivity. Option C (Azure VPN Gateway) is wrong because it creates site-to-site VPN tunnels over the public internet, not over the Microsoft global backbone, and does not offer a unified management interface for multiple VNets and ExpressRoute connections. Option D (Azure ExpressRoute) is wrong because it only provides a dedicated private connection from on-premises to Azure, but does not connect multiple VNets to each other or offer a single orchestration interface for managing inter-VNet and hybrid connectivity.

147
MCQmedium

Your company runs a critical workload on Azure Virtual Machines in a single region. You need to design a disaster recovery solution that meets a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 1 hour. The solution should minimize cost. What should you recommend?

A.Configure Azure Backup with geo-redundant storage.
B.Deploy an active-passive pair of VMs using SQL Server Always On availability groups.
C.Use Azure Storage with read-access geo-redundant storage (RA-GRS) and failover the VMs.
D.Implement Azure Site Recovery with replication to a secondary region.
AnswerD

Azure Site Recovery (ASR) is purpose-built for disaster recovery of Azure VMs, replicating the entire VM to a secondary region with an RPO that can be as low as 15 seconds and typically well under the required 15 minutes. It provides crash-consistent and app-consistent snapshot replication, automated failover, failback, and recovery plans, enabling predictable RTO. This makes ASR the correct, cost-effective option that fully satisfies the stated 15-minute RPO requirement.

Why this answer

Azure Site Recovery (ASR) provides continuous replication of Azure VMs to a secondary region, enabling failover within minutes. With replication intervals as low as 30 seconds for crash-consistent and 5 minutes for app-consistent snapshots, it comfortably meets the 15-minute RPO, and the orchestrated failover process can achieve the 1-hour RTO. ASR is the native Azure service designed for this exact scenario, minimizing cost by only charging for replication traffic and storage in the secondary region.

Exam trap

The trap here is that candidates confuse Azure Backup (which is for backup/restore) with Azure Site Recovery (which is for disaster recovery/failover), assuming that geo-redundant storage alone can provide VM-level DR, when in fact it only protects storage data, not compute or application state.

How to eliminate wrong answers

Option A is wrong because Azure Backup is designed for long-term retention and point-in-time restore, not for rapid failover; its RTO is typically measured in hours or days, not 1 hour, and it does not provide continuous replication to meet a 15-minute RPO. Option B is wrong because SQL Server Always On availability groups are a database-level HA/DR solution that only protects SQL Server workloads, not the entire VM or other applications, and it requires significant licensing and infrastructure costs. Option C is wrong because RA-GRS is a storage redundancy option that provides read-only access to data in a secondary region; it does not replicate the VM configuration, operating system, or application state, and failover of VMs is not supported by this service.

148
Multi-Selecthard

Your company has a hybrid identity environment with Microsoft Entra ID and on-premises Active Directory. You need to design a solution to monitor changes to privileged groups in both directories and ensure that any unauthorized changes trigger an automated response. Which THREE services should you include in the design?

Select 3 answers
A.Microsoft Sentinel
B.Microsoft Purview
C.Microsoft Entra Identity Protection
D.Group Policy Management Console
E.Microsoft Defender for Identity
AnswersA, C, E

Microsoft Sentinel ingests audit and sign-in logs from Microsoft Entra ID and on-premises Active Directory, correlates privileged group changes, and runs automation rules or playbooks that trigger an automated response when unauthorised modifications are detected.

Why this answer

Microsoft Sentinel (A) is correct because it is the cloud-native SIEM/SOAR platform that ingests audit and directory logs from both Microsoft Entra ID and on-premises Active Directory (via connectors and agents), correlates privileged group change events, and uses analytics rules plus playbooks (Logic Apps) to trigger automated responses such as disabling accounts or notifying admins. Microsoft Entra Identity Protection (C) is correct because it detects risky sign-ins and risky users, including risk detections tied to privileged account compromise, and can feed those signals into Conditional Access or Sentinel so that unauthorized privileged activity is flagged and remediated automatically. Microsoft Defender for Identity (E) is correct because it monitors on-premises Active Directory Domain Services traffic and events (e.g., via the sensor on domain controllers) to detect suspicious changes to privileged groups such as Domain Admins, and it forwards alerts to Defender XDR/Sentinel for automated response.

Microsoft Purview (B) is not included because it focuses on data governance, compliance, and information protection rather than real-time monitoring and automated response to directory privilege changes. Group Policy Management Console (D) is not included because it is an administrative tool for creating and managing GPOs, not a monitoring or automated-response service for privileged group modifications.

Exam trap

The trap here is that candidates often confuse Microsoft Purview (data governance) with Microsoft Defender for Cloud Apps (which can monitor group changes in SaaS apps) or assume Entra Identity Protection covers group membership monitoring, but neither Purview nor Identity Protection is designed for auditing or responding to privileged group modifications in hybrid directories.

149
MCQmedium

You are designing a disaster recovery solution for a critical application hosted in Azure VMs. The primary region is East US. The application requires a recovery time objective (RTO) of 30 minutes and a recovery point objective (RPO) of 15 minutes. Which Azure service should you use to replicate the VMs?

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

Azure Site Recovery orchestrates continuous, block-level replication of Azure VMs to a secondary region by using a mobility service extension that copies every write to a cache storage account and then to replicated managed disks. In Azure-to-Azure scenarios, this provides an RPO of 15–30 seconds, while crash-consistent and app-consistent snapshots are taken to balance performance and data loss. Recovery plans enable you to define failover sequences, execute runbooks or scripts, and update DNS or load balancer settings, which can compress RTO to minutes with predictable, testable outcomes. That coordination of replication state and application failover is exactly what makes Site Recovery the appropriate choice for a critical workload's DR solution.

Why this answer

Azure Site Recovery (ASR) orchestrates replication, failover, and failback of Azure VMs between regions, meeting the RTO of 30 minutes and RPO of 15 minutes by using continuous replication with crash-consistent or app-consistent snapshots. It is the native Azure service designed specifically for disaster recovery of IaaS workloads with granular recovery objectives.

Exam trap

The trap here is that candidates often confuse Azure Backup (which is for long-term retention and archival) with Azure Site Recovery (which is for replication and rapid failover), failing to recognize that Backup's default RPO of 24 hours cannot satisfy sub-hour recovery objectives.

How to eliminate wrong answers

Option A is wrong because Azure Front Door is a global load balancer and application delivery service that routes HTTP/HTTPS traffic, not a VM replication or disaster recovery service; it cannot replicate VM state or meet RPO/RPO requirements. Option B is wrong because Azure Backup provides backup and restore of VMs with a typical RPO of 1 day (daily snapshots) and RTO measured in hours, far exceeding the required 15-minute RPO and 30-minute RTO. Option C is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that directs user traffic to endpoints based on routing methods, but it does not replicate VM data or provide failover of compute and storage; it only controls traffic routing.

150
MCQeasy

A company needs to provide secure access to Azure resources for remote employees. They want to enforce multi-factor authentication and conditional access policies. The solution should not require a VPN connection. Which Azure service should they implement?

A.Microsoft Intune
B.Azure VPN Gateway
C.Azure Bastion
D.Microsoft Entra ID
AnswerD

Microsoft Entra ID is the foundational identity and access management (IAM) service for Azure and acts as the central authentication and authorization control plane. It authenticates users, issues access tokens via OAuth 2.0 and OpenID Connect, and enforces Conditional Access policies, including MFA, device compliance, and risk detection. All Azure Resource Manager and data-plane access ultimately depends on Entra ID tokens, making it the correct identity-based solution for secure access to Azure resources.

Why this answer

Microsoft Entra ID (formerly Azure Active Directory) provides identity and access management services that include multi-factor authentication (MFA) and conditional access policies. These capabilities allow you to enforce security requirements like MFA and device compliance before granting access to Azure resources, all without requiring a VPN connection. Entra ID acts as the identity provider and policy engine, making it the correct choice for this scenario.

Exam trap

The trap here is that candidates often confuse network-level security services (like VPN Gateway or Bastion) with identity-level security services (like Entra ID), mistakenly thinking a VPN is required to enforce MFA or conditional access, when in fact Entra ID handles these controls at the authentication layer without any network tunnel.

How to eliminate wrong answers

Option A is wrong because Microsoft Intune is a mobile device management (MDM) and mobile application management (MAM) service; it does not natively enforce MFA or conditional access policies on its own—it relies on Entra ID for those controls. Option B is wrong because Azure VPN Gateway creates an encrypted tunnel between on-premises networks and Azure, but the requirement explicitly states no VPN is needed, and VPN Gateway does not enforce MFA or conditional access policies at the identity level. Option C is wrong because Azure Bastion provides secure RDP/SSH access to Azure VMs without exposing public IPs, but it does not enforce MFA or conditional access policies—it is a jump server service, not an identity and access management solution.

Page 1

Page 2 of 11

Page 3

All pages