Courseiva

Microsoft Azure Solutions Architect Expert AZ-305 (AZ-305) — Questions 451–525

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

Page 6

Page 7 of 11

Page 8
451
MCQeasy

Your company has Azure virtual machines running a critical application. You need to back up these VMs daily and retain backups for 7 years. The solution must be cost-effective and support application-consistent backups. What should you use?

A.Azure Backup
B.Azure Files backup
C.Azure Site Recovery
D.Azure VM snapshots stored in Azure Storage
AnswerA

Azure Backup is the native managed backup service for Azure VMs. It installs a backup extension on each VM and coordinates VSS (Volume Shadow Copy) on Windows or file-system-consistent snapshots on Linux, then transfers the VM's disks to a Recovery Services vault. It provides a configurable backup policy (daily or weekly) with long-term retention, and allows application-consistent, crash-consistent point-in-time restores of entire VMs or individual disks. Because it is fully managed and integrated with Azure Policy and monitoring, it is the correct choice for a critical application that needs reliable recoverability.

Why this answer

Azure Backup is the correct choice because it provides a native, cost-effective backup solution for Azure VMs that supports application-consistent backups via the Volume Shadow Copy Service (VSS) for Windows and file-system-consistent backups for Linux. It allows you to configure a backup policy with daily backups and a retention duration of up to 99 years, easily meeting the 7-year requirement. Azure Backup also integrates with Azure Recovery Services vault, offering centralized management and long-term retention at a lower cost than other disaster recovery or snapshot-based approaches.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery (disaster recovery) with Azure Backup (backup), or assume that VM snapshots are sufficient for long-term retention, overlooking the need for application consistency and cost-effective lifecycle management.

How to eliminate wrong answers

Option B is wrong because Azure Files backup is designed to back up Azure file shares, not Azure VMs, and does not provide application-consistent backups for VM workloads. Option C is wrong because Azure Site Recovery is a disaster recovery solution focused on replication and failover for business continuity, not a backup service; it does not support long-term retention policies like 7 years and is more expensive for daily backup needs. Option D is wrong because Azure VM snapshots stored in Azure Storage are crash-consistent by default, not application-consistent, and managing snapshots for daily backups over 7 years would be complex and costly due to manual lifecycle management and lack of native backup policy integration.

452
Multi-Selectmedium

Your organization uses Azure Monitor to collect metrics from Azure resources. You need to create a custom metric alert that triggers when the average CPU usage of a specific virtual machine exceeds 80% for 10 minutes. Which TWO components are required? (Choose two.)

Select 2 answers
A.Metric alert rule
B.Automation runbook
C.Action group
D.Log Analytics workspace
E.Diagnostic setting
AnswersA, C

This is the core resource that continuously evaluates a specified metric (e.g., percentage CPU) against a threshold (e.g., >80%) over a given aggregation window (e.g., 5 minutes). It defines the target resource, metric name, operator, threshold, and evaluation frequency, and it triggers a state change when the condition is met. Without a metric alert rule, no alert is generated from the metric stream.

Why this answer

A metric alert rule is required because it defines the condition (average CPU > 80%) and the evaluation frequency (every 1 minute over a 10-minute aggregation window) that triggers the alert. Without the rule, Azure Monitor has no logic to evaluate the metric data and fire the alert.

Exam trap

The trap here is that candidates often confuse the required components for creating an alert (the rule and the action group) with optional components like diagnostic settings or runbooks, which are only needed for advanced scenarios or log-based alerts.

453
MCQmedium

Your company runs a mission-critical application on Azure Virtual Machines in a single region. You need to design a monitoring solution that provides proactive alerts for performance degradation and allows the operations team to analyze historical trends. The solution must minimize cost and operational overhead. You have an existing Log Analytics workspace. What should you include in the design?

A.Enable VM insights in Azure Monitor and use its live map and performance views for historical analysis.
B.Configure Azure Autoscale for the VMs based on CPU metrics and use Azure Monitor for logging.
C.Deploy Application Insights on each VM and use its built-in alerts for performance.
D.Enable Azure Monitor on all VMs using the Azure Monitor agent. Create metric alerts for high CPU and memory usage. Use Log Analytics to query and analyze historical performance data.
AnswerD

Enable the Azure Monitor agent on all VMs to collect guest OS performance counters (CPU, memory, disk) and forward them to a Log Analytics workspace. Metric alerts can then be configured on these performance counters for near-real-time proactive notification when thresholds are breached. The historical data in the workspace can be queried with Kusto Query Language to analyze long-term trends and capacity forecasting. This combination gives low-overhead, proactive alerting plus powerful historical analysis, and is the standard Azure Well-Architected approach for VM monitoring.

Why this answer

It uses the Azure Monitor agent to collect performance data from VMs, enabling metric alerts for proactive notification of high CPU and memory usage, while leveraging the existing Log Analytics workspace for cost-effective historical analysis. This approach minimizes operational overhead by using a single agent and native Azure Monitor features without additional services or complex configurations.

Exam trap

The trap here is that candidates may confuse VM insights (which offers rich visualizations but limited historical analysis) with the full monitoring solution required, or mistakenly think Application Insights is appropriate for VM-level performance monitoring when it is designed for application telemetry.

How to eliminate wrong answers

Option A is wrong because VM insights provides live map and performance views for real-time monitoring but is not designed for deep historical trend analysis, and its prebuilt performance charts have limited retention without Log Analytics. Option B is wrong because Azure Autoscale is for automatically scaling VM instances based on metrics, not for monitoring performance degradation or analyzing historical trends; it also does not address the requirement for proactive alerts and historical analysis. Option C is wrong because Application Insights is primarily for application-level monitoring (e.g., web apps, APIs) and requires instrumenting each application, which adds cost and complexity; it is not suitable for OS-level performance metrics like CPU and memory on VMs.

454
MCQmedium

A company runs a critical application on Azure Kubernetes Service (AKS) in a single region. The application is stateless and uses an Azure SQL Database with active geo-replication for database DR. They need to ensure the AKS cluster can failover to a secondary region with an RTO of 15 minutes and an RPO of 5 seconds for the database. What should they recommend for the AKS cluster?

A.Deploy AKS clusters in two regions and use Azure Traffic Manager to route traffic.
B.Deploy a single AKS cluster with pods spread across availability zones within the region.
C.Use Azure Site Recovery to replicate the AKS cluster to another region.
D.Back up the AKS cluster configuration and container images to a geo-redundant storage account.
AnswerA

Traffic Manager provides DNS-based global load balancing. With AKS clusters in two regions, Traffic Manager can direct users to the healthy region, achieving the required RTO. The database DR is handled separately by active geo-replication.

Why this answer

Deploying AKS clusters in two regions with Azure Traffic Manager enables active-passive or active-active failover. Traffic Manager uses DNS-based routing to direct traffic to the secondary region when the primary fails, meeting the RTO of 15 minutes. The stateless application can be redeployed or scaled in the secondary cluster, while the Azure SQL Database with active geo-replication ensures an RPO of 5 seconds by continuously replicating transactions.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery as a solution for AKS DR, but Site Recovery only supports IaaS VMs, not managed Kubernetes services, making multi-region AKS clusters with Traffic Manager the correct approach.

How to eliminate wrong answers

Option B is wrong because spreading pods across availability zones within a single region protects against zonal failures but not against a regional outage, which is required for cross-region DR. Option C is wrong because Azure Site Recovery does not support replicating AKS clusters; it is designed for IaaS VMs, not managed Kubernetes services. Option D is wrong because backing up cluster configuration and container images to geo-redundant storage provides data backup but does not enable automated failover or meet the RTO of 15 minutes, as manual restoration would be required.

455
MCQhard

You are designing a data lake for advanced analytics in Azure. The data includes structured, semi-structured, and unstructured data. The solution must support schema-on-read and have the ability to query using SQL. Which Azure service should you choose?

A.Azure Blob Storage.
B.Azure SQL Database.
C.Azure Data Lake Storage Gen2.
D.Azure Cosmos DB.
AnswerC

Azure Data Lake Storage Gen2 (ADLS Gen2) is built on Azure Blob Storage but adds a hierarchical namespace, giving it file system semantics such as atomic directory renames and POSIX-like access control lists. It supports every data type and applies schema-on-read, meaning raw data is ingested without ETL and can be queried on demand by engines like Azure Synapse, Databricks, and PolyBase. Its native integration with SQL querying, including serverless SQL pools, makes it the optimal foundation for a scalable, high-performance data lake for advanced analytics.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) combines Blob Storage with a hierarchical namespace, enabling schema-on-read for structured, semi-structured, and unstructured data. It supports SQL-based querying via Azure Synapse Analytics, Azure Databricks, or PolyBase, making it ideal for advanced analytics scenarios.

Exam trap

The trap here is that candidates confuse Azure Blob Storage's object storage capabilities with the hierarchical namespace and SQL query support of ADLS Gen2, or they mistakenly choose Azure SQL Database for its SQL familiarity without recognizing it requires a predefined schema.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage lacks a hierarchical namespace and native SQL querying capabilities; it requires additional services like Azure Data Lake Analytics for SQL queries. Option B is wrong because Azure SQL Database is a relational database requiring a fixed schema (schema-on-write), not schema-on-read, and is not designed for unstructured or semi-structured data at scale. Option D is wrong because Azure Cosmos DB is a NoSQL database optimized for low-latency, globally distributed workloads with schema-on-read via SQL API, but it is not a data lake solution and does not natively support unstructured data like large files or binary objects.

456
MCQmedium

A company plans to deploy multiple virtual machines (VMs) across two Azure regions for high availability. The VMs will host a stateless web application that must be accessible via a single DNS endpoint. The solution must automatically route traffic to the nearest region with available capacity and provide failover if a region becomes unhealthy. Which Azure service should they use to meet these requirements?

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

Azure Traffic Manager is a DNS-based global load balancer that routes incoming DNS requests to the most appropriate regional endpoint based on routing methods such as performance, geographic, weighted, or priority. It continuously monitors endpoint health and can automatically redirect traffic away from failed or overloaded regions, ensuring high availability and capacity-aware distribution across multiple VMs in different regions.

Why this answer

Azure Traffic Manager is a DNS-based traffic load balancer that distributes traffic to the nearest region with available capacity using the Performance traffic-routing method, and it automatically fails over to the next healthy endpoint when a region becomes unhealthy. It operates at the DNS level, returning the appropriate endpoint IP based on the client's DNS resolver location and endpoint health probes, making it ideal for stateless web applications requiring a single DNS endpoint across regions.

Exam trap

The trap here is that candidates often confuse Azure Front Door (Layer 7, HTTP/HTTPS) with Traffic Manager (DNS-based, any protocol), but the requirement for a single DNS endpoint and region-level failover without specifying HTTP makes Traffic Manager the correct choice.

How to eliminate wrong answers

Option B (Azure Front Door) is wrong because it is an HTTP/HTTPS application delivery controller that provides global load balancing with SSL offload and path-based routing, but it operates at Layer 7 and requires HTTP traffic, whereas the question does not specify HTTP-only traffic and Traffic Manager works at DNS level for any protocol. Option C (Azure Load Balancer) is wrong because it operates at Layer 4 and distributes traffic only within a single region, not across multiple Azure regions. Option D (Azure Application Gateway) is wrong because it is a regional Layer 7 load balancer with HTTP/HTTPS features and cannot route traffic across multiple regions or provide global failover.

457
Multi-Selecthard

Which THREE considerations are important when designing a storage solution for Azure Virtual Desktop (AVD) user profiles using FSLogix? (Choose three.)

Select 3 answers
A.Use Azure Files as the storage solution.
B.Use a public endpoint for profile storage.
C.Provision sufficient IOPS for user profiles.
D.Enable geo-redundant storage (GRS) for disaster recovery.
E.Ensure low latency between session hosts and storage.
AnswersA, C, E

Azure Files is the correct storage solution for Azure Virtual Desktop (AVD) because it provides fully managed SMB 3.0 file shares, which are a prerequisite for FSLogix profile containers. FSLogix loads user profiles as VHDX files mounted over SMB, and Azure Files natively supports this with identity-based authentication via Active Directory Domain Services or Microsoft Entra ID. This integration allows you to keep profiles in a secure, cloud-native share that scales with your session host environment.

Why this answer

Azure Files is the recommended storage solution for FSLogix profile containers in AVD because it supports SMB protocol, which FSLogix requires for proper locking and concurrent access. It also integrates natively with Azure Active Directory for identity-based access control, eliminating the need for domain-joined storage. This ensures seamless user profile roaming across session hosts with minimal latency when deployed in the same region.

Exam trap

The trap here is that candidates often confuse geo-redundant storage (GRS) as a necessary disaster recovery feature for user profiles, but FSLogix containers are stateless or backed up via alternative methods, and GRS introduces consistency risks that are incompatible with the real-time locking requirements of FSLogix.

458
MCQeasy

A company runs a web application on Azure VMs in a single region. They need to ensure that if the region fails, the VMs are replicated to another region and can be started automatically. Which Azure service should they use?

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

Azure Site Recovery is the correct choice because it replicates Azure VM disks continuously from the primary region to a configured recovery region, enabling a recovery plan that automates failover and VM startup during a regional outage. It maintains near-synchronous RPO and flexible RTO, and you can test failover with isolated networks to validate readiness. It is a true disaster recovery service designed to bring the entire workload up in another region.

Why this answer

Azure Site Recovery (ASR) orchestrates replication, failover, and failback of Azure VMs from one region to another. It continuously replicates VM disks to the target region and, upon failover, automatically starts the replicated VMs, meeting the requirement for regional disaster recovery with automated startup.

Exam trap

The trap here is that candidates confuse Azure Backup (which provides point-in-time restores but not automated regional failover) with Azure Site Recovery (which provides continuous replication and automated VM startup), or they mistakenly think Traffic Manager or Load Balancer can handle VM replication and startup when they only manage traffic routing.

How to eliminate wrong answers

Option B (Azure Backup) is wrong because it is designed for backup and restore of VM data to a Recovery Services vault, not for continuous replication and automated startup of VMs in another region; it requires manual restore and does not provide automatic VM startup after failover. Option C (Azure Traffic Manager) is wrong because it is a DNS-based traffic load balancer that routes incoming traffic to healthy endpoints across regions, but it does not replicate VMs or start them automatically after a regional failure. Option D (Azure Load Balancer) is wrong because it distributes traffic within a single region at the transport layer (Layer 4) and does not provide cross-region replication or automated VM startup.

459
MCQmedium

You need to design a storage solution for a global e-commerce application that requires low-latency access to product catalog data across multiple Azure regions. The data is read-heavy and updates are rare. Which service should you use for the primary data store?

A.Azure SQL Database with active geo-replication
B.Azure Table Storage
C.Azure Redis Cache
D.Azure Cosmos DB
AnswerD

Azure Cosmos DB is the correct choice because it provides turnkey global distribution with the ability to add any number of read and write regions around the world, and it offers multiple well-defined consistency levels that let you balance strong consistency and low latency per request. Each region is fully manageable, writes are accepted anywhere and conflict resolution can be configured to handle concurrent updates, giving single-digit millisecond latencies while maintaining high availability through automatic failover. This makes it a natural fit for a global e-commerce platform that needs fast, reliable access from anywhere.

Why this answer

Azure Cosmos DB is the correct choice because it provides globally distributed, multi-region writes and reads with turnkey data replication and guaranteed single-digit-millisecond latency at the 99th percentile. Its multi-homing API and automatic failover capabilities make it ideal for a read-heavy, rarely updated global e-commerce catalog that requires low-latency access across multiple Azure regions.

Exam trap

The trap here is that candidates often confuse a caching layer (Redis) with a globally distributed primary store, or assume that a relational database with geo-replication (Azure SQL) is suitable for any multi-region scenario, ignoring the specific read-heavy, rare-update pattern that Cosmos DB is optimized for.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database with active geo-replication is designed for transactional workloads with frequent writes and strong consistency, not for a read-heavy, rarely updated catalog; its geo-replication adds latency and cost overhead for read-only scenarios. Option B is wrong because Azure Table Storage is a NoSQL key-value store that lacks native global distribution and multi-region replication, resulting in higher latency for cross-region reads and no built-in low-latency guarantees. Option C is wrong because Azure Redis Cache is an in-memory cache, not a durable primary data store; it is used to accelerate reads from a backing database, not to serve as the authoritative source of truth for product catalog data.

460
MCQmedium

A company wants workload deployments to access Azure resources without storing client secrets in CI/CD variables. The pipeline runs from GitHub Actions. Which identity design should be used?

A.A shared user account with MFA disabled
B.A storage account access key
C.Workload identity federation with Microsoft Entra ID
D.A long-lived app registration client secret
AnswerC

Workload identity federation with Microsoft Entra ID lets an external workload (for example, a GitHub Actions job or a Kubernetes pod) present a token from its own trusted identity provider to Entra ID in exchange for an Entra access token. This uses OAuth 2.0 client credentials grant flow with no client secret, because the federated credential defines trust by issuer, subject, and audience. The resulting short-lived tokens can be scoped to Azure resources or Microsoft Graph, eliminating long-lived secrets and enabling automated rotation through the source identity provider.

Why this answer

Workload identity federation with Microsoft Entra ID allows GitHub Actions to exchange an OpenID Connect (OIDC) token for an Azure access token, eliminating the need to store client secrets in CI/CD variables. This design uses short-lived tokens and federated identity credentials, aligning with the principle of zero-trust and secretless authentication.

Exam trap

The trap here is that candidates may choose a long-lived client secret (Option D) thinking it is the standard way to authenticate, overlooking the requirement to avoid storing secrets and the modern OIDC-based federation approach.

How to eliminate wrong answers

Option A is wrong because a shared user account with MFA disabled violates security best practices and does not eliminate secrets; it still requires storing credentials in CI/CD variables. Option B is wrong because a storage account access key is a static secret that must be stored in CI/CD variables, and it provides broad, unmonitored access to the storage account. Option D is wrong because a long-lived app registration client secret is a static secret that must be stored in CI/CD variables, defeating the requirement to avoid storing secrets.

461
MCQeasy

A company is deploying a multi-tier web application on Azure VMs. The web tier must be accessible from the internet, while the application and database tiers must be isolated within the virtual network. The solution must provide SSL termination, web application firewall (WAF) capabilities, and URL-based routing. Which Azure service should they use to expose the web tier?

A.Use an Azure Load Balancer and configure NSGs on each subnet.
B.Use Azure Firewall to inspect all traffic and allow internet traffic to the web tier.
C.Use Azure Application Gateway with WAF, and configure NSGs to restrict traffic between tiers.
D.Use Azure Front Door to expose the web tier and NSGs for internal isolation.
AnswerC

Azure Application Gateway is a Layer 7 regional load balancer that provides SSL termination, WAF, URL-based routing, and cookie-based session affinity, making it the appropriate entry point for the web tier. By enabling WAF, it actively blocks common web vulnerabilities such as SQL injection and cross-site scripting before they reach the backend. Complementing this with NSGs on each subnet enforces network-level isolation, ensuring that only the web tier can communicate with the app tier on specific ports (e.g., 8080/tcp) and that the app tier cannot initiate outbound connections to the internet. This combination of application-layer protection and subnet-level access control exactly matches the requirement to restrict traffic between tiers while securely exposing the web tier.

Why this answer

Azure Application Gateway is a Layer 7 load balancer that provides SSL termination, a web application firewall (WAF), and URL-based routing, making it ideal for exposing a web tier to the internet. By placing the gateway in front of the web tier and configuring network security groups (NSGs) on the application and database subnets, you can isolate internal tiers while 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 a basic load balancer can handle SSL termination and WAF, when in fact those features require Layer 7 capabilities.

How to eliminate wrong answers

Option A is wrong because Azure Load Balancer operates at Layer 4 and cannot perform SSL termination, WAF inspection, or URL-based routing; it only distributes traffic based on IP and port. Option B is wrong because Azure Firewall is a stateful Layer 3/4 firewall that does not provide SSL termination or URL-based routing, and it is not designed to act as a reverse proxy for web tiers. Option D is wrong because Azure Front Door is a global Layer 7 service that excels at CDN and cross-region routing but does not natively support URL-based routing within a single virtual network; it is typically used for global load balancing, not for internal tier isolation with NSGs.

462
MCQmedium

A company runs several Azure virtual machines (VMs) that host SQL Server databases. The databases are stored on data disks attached to the VMs. The company needs to back up the databases and VMs separately. They require application-consistent backups for SQL Server to ensure transactional integrity. Additionally, they need to retain backups for up to 7 years to meet compliance requirements. The solution must minimize administrative overhead and support long-term retention of database backups. Which Azure service or feature should they use for the database backups?

A.Azure Backup for Azure VMs with application-consistent snapshots
B.Azure Backup for SQL Server in Azure VMs
C.Azure Site Recovery
D.Azure Files
AnswerB

Azure Backup for SQL Server in Azure VMs is a SQL-aware backup solution that leverages SQL Server's VDI and VSS integration to deliver true application-consistent backups for each database. It orchestrates full, differential, and transaction log backups, enabling point-in-time restore to any second within the retention window. The service supports granular database-level restore, so you can recover one database without affecting others, and offers retention up to 10 years using the archive tier, comfortably exceeding the 7-year requirement. Its built-in management of backup schedules, retention ranges, and restore operations makes it the only option that fully satisfies the database-specific backup needs.

Why this answer

Azure Backup for SQL Server in Azure VMs is the correct choice because it provides native, application-consistent backups specifically for SQL Server databases running on Azure VMs. It integrates directly with SQL Server VSS writer to ensure transactional integrity, supports long-term retention up to 10 years (exceeding the 7-year requirement), and minimizes administrative overhead by automating backup scheduling, retention management, and point-in-time restore. This service is purpose-built for SQL Server database backups, separate from VM-level backups.

Exam trap

The trap here is that candidates often confuse 'application-consistent snapshots' at the VM level with true SQL Server–aware database backups, overlooking that VM-level backups do not guarantee SQL Server transactional integrity or support database-level restore and long-term retention policies.

How to eliminate wrong answers

Option A is wrong because Azure Backup for Azure VMs with application-consistent snapshots backs up the entire VM (including OS and data disks) but does not provide SQL Server–aware, database-level backup granularity or transactional integrity for SQL Server databases; it only ensures file-system consistency, not application consistency for SQL Server. Option C is wrong because Azure Site Recovery is a disaster recovery solution focused on replication and failover for business continuity, not a backup service for long-term retention or application-consistent database backups. Option D is wrong because Azure Files is a managed file share service for storing files, not a backup solution; it lacks SQL Server–aware backup capabilities, application-consistent snapshot support, and long-term retention policies for databases.

463
MCQmedium

A company is migrating a large on-premises SQL Server database to Azure SQL Managed Instance. They need to minimize downtime during migration. The database is 500 GB and the network link is 1 Gbps. Which migration approach should they recommend?

A.Use Azure Database Migration Service with online migration
B.Perform offline backup and restore
C.Use transactional replication
D.Export BACPAC and import
AnswerA

Azure Database Migration Service online mode performs an initial full copy of your schema and data, then continuously replays changes from the source SQL Server transaction log to keep the target Azure SQL database synchronized. This allows you to run the source in production while the subscription catches up, and you can manually cut over with a controlled stop of writes, limiting downtime to minutes. It is specifically designed for large databases like 500 GB because it avoids a single, protracted offline export and uses a scalable staging area in Azure Blob Storage.

Why this answer

Azure Database Migration Service (DMS) with online migration mode uses continuous change data capture (CDC) to synchronize ongoing changes from the on-premises SQL Server to Azure SQL Managed Instance, minimizing downtime to a brief cutover window. This approach is ideal for a 500 GB database over a 1 Gbps link, as it avoids the lengthy full data transfer required by offline methods.

Exam trap

The trap here is that candidates often assume offline backup and restore is the simplest and fastest method, but they overlook the 'minimize downtime' requirement, which makes online migration via DMS the only correct choice despite its added complexity.

How to eliminate wrong answers

Option B is wrong because offline backup and restore requires taking the source database offline for the entire duration of the backup transfer and restore, which for a 500 GB database over 1 Gbps would cause significant downtime (hours), failing the minimize-downtime requirement. Option C is wrong because transactional replication requires manual setup of publishers, distributors, and subscribers, and while it can reduce downtime, it is more complex to configure and manage for a full database migration compared to DMS, and it does not natively handle schema changes or large-scale migrations as efficiently. Option D is wrong because exporting a BACPAC file involves a full database export and import, which locks tables during export and requires the database to be mostly offline, resulting in substantial downtime for a 500 GB database over 1 Gbps.

464
Multi-Selectmedium

Your organization has a critical application running on Azure Virtual Machines. You need to design a backup and disaster recovery strategy. Which TWO options should you include in your design to meet a Recovery Point Objective (RPO) of 15 minutes and a Recovery Time Objective (RTO) of 1 hour? (Choose two.)

Select 2 answers
A.Store data in Azure Files and use Azure File Sync for replication.
B.Implement Azure Site Recovery with replication to a secondary region.
C.Use Azure Traffic Manager to distribute traffic between regions.
D.Configure Azure Backup for daily backups with geo-redundant storage.
E.Enable application-consistent snapshots for the VMs within the replication policy.
AnswersB, E

Azure Site Recovery (ASR) continuously replicates Azure VMs to a secondary region using the Mobility service, capturing data changes at near-synchronous intervals. ASR supports recovery point objectives (RPO) as low as 15 seconds (and up to 15 minutes depending on workload), with recovery time objectives (RTO) of minutes when using Azure's orchestrated failover and recovery plans. This directly satisfies the stated 15-minute RPO and fast RTO, making it the correct primary disaster recovery solution for critical VMs.

Why this answer

Azure Site Recovery (ASR) replicates Azure VMs to a secondary region with configurable recovery points. By enabling application-consistent snapshots within the replication policy, you can achieve an RPO of 15 minutes (snapshot frequency) and an RTO of 1 hour (failover time), meeting the stated requirements.

Exam trap

The trap here is that candidates often confuse Azure Backup (daily snapshots) with Azure Site Recovery (continuous replication), or assume that geo-redundant storage alone satisfies the RPO, when in fact the 15-minute RPO requires near-continuous replication and application-consistent snapshots.

465
MCQeasy

You need to design a storage solution for a large-scale media streaming application. The application serves video files to users worldwide. The solution must minimize latency for end-users and optimize content delivery costs. Which Azure service combination should you use?

A.Azure Cosmos DB with multi-region writes
B.Azure NetApp Files with Azure Front Door
C.Azure Blob Storage with Azure Content Delivery Network (CDN)
D.Azure Files with Azure File Sync
AnswerC

Azure Blob Storage is object storage designed for petabytes of unstructured data, making it ideal for hosting video files, with support for HTTP range requests, lifecycle tiering, and secure streaming via SAS or anonymous read-only containers. Azure Content Delivery Network (CDN) caches video content at point-of-presence (PoP) edge locations, so users receive low-latency playback and at the same time egress from the origin blob storage is reduced, lowering network transfer costs. Together they deliver scale-to-zero bandwidth, high availability, and cost-efficient global media distribution. This is the only option that matches both storage semantics and content acceleration needs.

Why this answer

Azure Blob Storage is optimized for storing large, unstructured data like video files, and when paired with Azure Content Delivery Network (CDN), it caches content at edge nodes worldwide. This combination minimizes latency for global users by serving videos from the nearest point of presence (PoP) and reduces egress costs by offloading traffic from the origin storage to the CDN's distributed network.

Exam trap

The trap here is that candidates confuse Azure Front Door (a global load balancer with HTTP caching) with a full CDN, but for static video content, Azure CDN (or Azure Front Door's CDN profile) is the correct service because it provides dedicated edge caching and egress cost optimization, whereas Front Door's primary role is application acceleration and routing.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a NoSQL database designed for transactional workloads with multi-region writes, not for storing and serving large binary video files; it lacks the cost-effective blob storage and CDN integration needed for media streaming. Option B is wrong because Azure NetApp Files provides high-performance NFS/SMB file shares for enterprise applications, not a globally distributed content delivery mechanism; Azure Front Door is a global load balancer and application accelerator, not a caching CDN optimized for static content like video files. Option D is wrong because Azure Files with Azure File Sync is designed for hybrid file sharing and synchronization across on-premises and cloud, not for low-latency global video streaming; it lacks edge caching and does not optimize egress costs for large-scale media delivery.

466
MCQmedium

Your organization uses Microsoft Entra ID and Azure Key Vault. You need to ensure that a custom application can securely access secrets in Key Vault without storing credentials in code. The application runs on an Azure Virtual Machine. What should you use?

A.Store the Key Vault URL and connection string in the application configuration
B.Create a service principal and upload a certificate to the VM
C.Assign a system-assigned managed identity to the VM
D.Use a shared access signature (SAS) token
AnswerC

Assigning a system-assigned managed identity to the VM is the most secure and least operationally complex approach because Azure automatically creates an identity tied to the VM's lifecycle, and you can grant that identity access to Azure Key Vault via an access policy or Azure RBAC. The application uses the Azure SDK to acquire an access token from the Azure Instance Metadata Service (IMDS) with no credentials stored in code, configuration, or on disk. This identity is automatically rotated by Azure, eliminating the need to manage or store any secrets, and it aligns with best practices for Azure workloads.

Why this answer

A system-assigned managed identity for Azure Virtual Machines allows the application to authenticate to Azure Key Vault without storing any credentials in code. Azure automatically manages the identity's lifecycle and tokens, enabling the VM to obtain an access token from Azure AD (now Microsoft Entra ID) to call Key Vault's REST API. This aligns with the principle of zero-trust and eliminates the need for service principals or certificates in the application.

Exam trap

The trap here is that candidates may confuse SAS tokens (used for Azure Storage) with Key Vault authentication, or mistakenly think that a service principal with a certificate is the most secure option, overlooking the fully managed, credential-less nature of managed identities.

How to eliminate wrong answers

Option A is wrong because storing the Key Vault URL and connection string in application configuration still exposes credentials (the connection string) in code or config files, violating the requirement to avoid storing credentials. Option B is wrong because creating a service principal and uploading a certificate to the VM requires manual certificate management, rotation, and storage of the certificate on the VM, which introduces credential management overhead and security risks. Option D is wrong because a shared access signature (SAS) token is used for delegating access to Azure Storage resources, not for authenticating to Azure Key Vault; Key Vault does not support SAS tokens for authentication.

467
Multi-Selectmedium

Your company has an Azure subscription that contains 100 virtual machines (VMs). You are designing a monitoring solution that must meet the following requirements: - Alert when any VM's CPU usage exceeds 90% for 15 minutes. - Alert when any VM's available memory drops below 1 GB. - Provide a centralized dashboard showing real-time performance metrics for all VMs. Which TWO Azure services should you include in the solution? (Choose two.)

Select 2 answers
A.Azure Policy
B.Microsoft Sentinel
C.Azure Monitor
D.Azure Monitor Workbooks
E.Azure Automation
AnswersC, D

Azure Monitor is the foundational monitoring service in Azure, collecting platform metrics and logs from resources, including virtual machines. When the Azure Diagnostics extension or Log Analytics agent is enabled, it captures guest OS metrics such as CPU percentage and memory utilization. Azure Monitor natively supports metric alerts that fire when a threshold is exceeded and can trigger action groups to send notifications or start automation. This makes it the primary correct service for the scenario's real-time performance monitoring and alerting need.

Why this answer

Azure Monitor is the core service for collecting, analyzing, and acting on telemetry from Azure resources. It can collect CPU and memory metrics from VMs via the Azure Monitor Agent, and its alerting engine can trigger actions when CPU exceeds 90% for 15 minutes or available memory drops below 1 GB, meeting both alerting requirements.

Exam trap

The trap here is that candidates often confuse Azure Monitor Workbooks with Azure Dashboards or Power BI, but Workbooks are the correct service for creating a centralized, real-time performance dashboard that integrates directly with Azure Monitor alerts and metrics.

468
MCQmedium

Your company has an Azure subscription that contains a hub virtual network and multiple spoke virtual networks connected via VNet peering. You need to ensure that all traffic between spokes is routed through a network virtual appliance (NVA) in the hub. The NVA is configured with IP forwarding enabled. What should you configure in the spoke virtual networks?

A.Deploy a VPN gateway in each spoke and configure site-to-site VPNs.
B.Configure NSG rules to block direct spoke-to-spoke traffic.
C.Add route tables to the spoke subnets with a default route (0.0.0.0/0) pointing to the NVA's private IP.
D.Enable BGP on the VNet peerings.
AnswerC

Adding route tables to the spoke subnets with a default route (0.0.0.0/0) pointing to the NVA's private IP is correct because it creates a user-defined route (UDR) that overrides the system route for peered VNets. When the next hop type is set to 'Virtual appliance' and the NVA's private IP is specified, all outbound traffic from that subnet—including traffic destined for other spoke VNets—is forced through the NVA in the hub. This works because UDRs take precedence over the automatically propagated routes from VNet peering. To ensure spoke-to-spoke traffic flows correctly, the NVA must have IP forwarding enabled, and the hub subnet containing the NVA must allow the traffic.

Why this answer

Adding a route table to the spoke subnets with a default route (0.0.0.0/0) pointing to the NVA's private IP forces all outbound traffic from the spoke, including traffic destined for other spokes, to be forwarded to the NVA. The NVA, with IP forwarding enabled, can then inspect and route the traffic to the target spoke. This ensures the desired traffic flow through the hub without requiring any changes to the VNet peering configuration.

Exam trap

The trap here is that candidates often confuse NSG rules (which filter traffic) with route tables (which direct traffic), leading them to choose Option B, but NSGs cannot force traffic through an NVA—they only allow or deny traffic at the subnet or NIC level.

How to eliminate wrong answers

Option A is wrong because deploying a VPN gateway in each spoke and configuring site-to-site VPNs would create a mesh of encrypted tunnels between spokes, bypassing the NVA entirely and adding unnecessary complexity and cost. Option B is wrong because NSG rules block traffic at the network layer but do not redirect traffic; they would drop spoke-to-spoke traffic rather than route it through the NVA, which does not meet the requirement. Option D is wrong because enabling BGP on VNet peerings is not supported in Azure; BGP is used with VPN gateways or ExpressRoute, not with VNet peering, and it cannot force traffic through an NVA.

469
MCQeasy

Your organization plans to use Azure Policy to enforce tagging on all resources. The tags must include 'CostCenter' and 'Environment'. Resources that do not have these tags should be automatically remediated. What should you use?

A.A policy with 'append' effect
B.A policy with 'audit' effect
C.A policy with 'deployIfNotExists' effect and a remediation task
D.A policy with 'deny' effect
AnswerC

DeployIfNotExists is evaluated periodically and can trigger a template deployment when a resource lacks the required tag, and a remediation task can be started after the policy is assigned to proactively fix all existing non-compliant resources. The remediation task uses managed identity to modify those resources by executing the linked ARM template that attaches the tag, bringing the current inventory into compliance without requiring a manual update. This combination is the only one among the choices that both detects and corrects pre-existing resources.

Why this answer

The 'deployIfNotExists' effect is correct because it allows Azure Policy to evaluate resources for missing tags and then deploy a remediation task that automatically adds the required tags. This effect is specifically designed for scenarios where non-compliance can be corrected by deploying or modifying resources, such as adding tags via a policy definition that triggers a remediation task.

Exam trap

The trap here is that candidates often confuse 'append' with 'deployIfNotExists', thinking that 'append' can remediate existing resources, but 'append' only applies during resource creation or update, not to already deployed resources.

How to eliminate wrong answers

Option A is wrong because the 'append' effect adds tags only during resource creation or update, but it does not automatically remediate existing resources that are already missing the tags. Option B is wrong because the 'audit' effect only logs non-compliance without any automatic remediation, requiring manual intervention. Option D is wrong because the 'deny' effect prevents creation or update of resources that do not have the required tags, but it does not remediate existing non-compliant resources.

470
MCQhard

A financial services company is migrating its on-premises SAP HANA database to Azure. The database requires high IOPS and low latency with a capacity of 4 TB. They need to choose a storage solution that supports SAP HANA certified configurations. Which Azure storage solution should they use?

A.Azure Premium SSD v2
B.Azure Ultra Disk Storage
C.Azure Standard HDD
D.Azure NetApp Files
AnswerB

Azure Ultra Disk Storage is the correct choice because it is certified for SAP HANA and delivers the extreme performance the service expects: IOPS, throughput, and latency can be independently provisioned and dynamically adjusted without downtime. This lets a financial services company configure a volume that matches SAP's performance benchmarks for transaction workloads, with sub-millisecond read latency and up to thousands of IOPS. Ultra Disk is the only Azure managed disk besides Premium SSD v1 that meets SAP HANA's production support requirements.

Why this answer

Azure Ultra Disk Storage is the correct choice because it is the only Azure managed disk that is SAP HANA certified for high IOPS and sub-millisecond latency, which is critical for SAP HANA workloads. It supports up to 300,000 IOPS and 2,000 MB/s throughput per disk, and can be provisioned with up to 64 TB capacity, easily covering the 4 TB requirement. Premium SSD v2 is not SAP HANA certified for production databases, and Azure NetApp Files, while offering high performance, is not a managed disk and requires specific NFS configurations that may not meet SAP HANA's strict certification requirements for block storage.

Exam trap

The trap here is that candidates often assume Premium SSD v2 is the best choice for all high-performance workloads, but SAP HANA has specific certification requirements that exclude Premium SSD v2 for production databases, making Ultra Disk the only correct option among the managed disks listed.

How to eliminate wrong answers

Option A is wrong because Azure Premium SSD v2, despite offering high IOPS and low latency, is not certified by SAP for SAP HANA production workloads; SAP HANA requires specific disk types like Ultra Disk or Premium SSD (v1) for certified configurations. Option C is wrong because Azure Standard HDD provides low IOPS and high latency, which cannot meet the performance demands of SAP HANA databases requiring high IOPS and low latency. Option D is wrong because Azure NetApp Files is a file-based NFS storage solution, not a block storage managed disk, and while it can be used with SAP HANA, it requires additional configuration and is not the direct Azure managed disk solution that is SAP HANA certified for high IOPS and low latency block storage.

471
MCQmedium

Your organization uses Microsoft Entra ID. You need to enforce multifactor authentication (MFA) for all guest users accessing a specific SharePoint Online site. What is the most efficient way to achieve this?

A.Use SharePoint site permissions to require MFA.
B.Create a Conditional Access policy targeting guest users and the SharePoint Online app.
C.Enable MFA per-user for each guest account.
D.Configure Microsoft Entra Entitlement Management to require MFA.
AnswerB

Conditional Access evaluates sign-in signals and enforces MFA at authentication time, scoped to guest user identities and the SharePoint Online cloud app. This targets exactly the required population and resource in one policy, avoiding per-site configuration or broader tenant-wide MFA enforcement.

Why this answer

Conditional Access policies in Microsoft Entra ID allow you to enforce MFA specifically for guest users when they access the SharePoint Online app. This is the most efficient approach as it targets the exact user group (guests) and the specific application (SharePoint Online) without requiring per-user configuration or additional licensing overhead.

Exam trap

The trap here is that candidates often confuse SharePoint site permissions with identity-level security controls, assuming that MFA can be enforced at the site level, when in fact MFA must be enforced through Entra ID Conditional Access policies.

How to eliminate wrong answers

Option A is wrong because SharePoint site permissions control access at the site level but cannot enforce MFA; MFA is an identity-level security requirement managed by Entra ID, not SharePoint. Option C is wrong because enabling MFA per-user for each guest account is inefficient, requires manual management, and does not scale; it also lacks the granularity to target only the specific SharePoint Online site. Option D is wrong because Microsoft Entra Entitlement Management manages access packages and approval workflows, not MFA enforcement; it can require MFA as part of an access package policy, but that is not the most efficient or direct method for enforcing MFA on a single SharePoint site.

472
MCQhard

Contoso Ltd. is a global retail company with headquarters in New York and operations in Europe and Asia. They are migrating their on-premises SQL Server databases to Azure. The databases include a customer database (500 GB), an orders database (2 TB), and a product catalog database (100 GB). The customer database requires high read throughput with sub-10 ms latency for global users. The orders database must support complex queries and reporting with point-in-time restore capability up to 35 days. The product catalog is updated infrequently but must be available for read-heavy workloads with strong consistency. Contoso wants to minimize costs while meeting performance and compliance requirements. They also need to support hybrid deployments for databases that must remain on-premises due to data sovereignty laws. You need to design a data storage solution. Which combination of Azure services and configurations should you recommend?

A.Azure SQL Managed Instance for all databases with geo-replication for customer DB; use failover groups for global distribution; Azure Data Sync for hybrid
B.Azure SQL Database Hyperscale for all databases; use geo-replication for customer DB; Azure SQL Server on Azure VMs for hybrid
C.Azure Cosmos DB with multiple write regions for customer DB; Azure SQL Database Business Critical for orders; Azure SQL Database serverless for product catalog; Azure SQL Managed Instance with managed instance link for hybrid
D.Azure SQL Database Business Critical for customer DB with geo-replication; Azure SQL Database Hyperscale for orders; Azure SQL Database serverless for product catalog; Azure SQL Managed Instance for hybrid
AnswerC

Azure Cosmos DB with multiple write regions gives every regional endpoint the ability to accept reads and writes with single-digit millisecond latency, enabling the global customer database to meet sub-10 ms performance through multi-homing and tunable consistency. Business Critical tier for orders provides SQL Server-compatible T-SQL, ACID transactions, and low-latency local Always On availability, which is appropriate for complex order queries and strict transactional guarantees. Serverless product catalog avoids fixed compute costs for an intermittently queried reference dataset, while Managed Instance with the managed instance link provides near-real-time bidirectional replication between Azure and existing on-premises SQL Server to satisfy the hybrid footprint.

Why this answer

It matches each database's workload to the optimal Azure service: Cosmos DB with multiple write regions provides global low-latency reads and writes for the customer DB; Azure SQL Database Business Critical offers the complex query support and point-in-time restore up to 35 days for the orders DB; Azure SQL Database serverless minimizes cost for the infrequently updated product catalog; and Azure SQL Managed Instance with managed instance link enables hybrid deployment for on-premises databases subject to data sovereignty laws.

Exam trap

The trap here is that candidates often assume Azure SQL Database Hyperscale is a one-size-fits-all solution for large databases, overlooking its limitations with point-in-time restore duration and complex query performance, and fail to recognize that Cosmos DB is the only Azure service designed for global low-latency reads with multiple write regions.

How to eliminate wrong answers

Option A is wrong because Azure SQL Managed Instance does not support geo-replication or failover groups for global distribution; those features are for Azure SQL Database, not Managed Instance. Option B is wrong because Azure SQL Database Hyperscale does not support point-in-time restore up to 35 days (max is 7 days by default, extendable to 35 only with additional configuration that increases cost) and is not optimal for complex queries and reporting due to its page server architecture. Option D is wrong because Azure SQL Database Business Critical for the customer DB lacks the global low-latency read throughput that Cosmos DB provides, and Azure SQL Database Hyperscale for the orders DB does not natively support point-in-time restore up to 35 days without extra cost and complexity.

473
MCQeasy

A company has multiple Azure virtual networks (VNets) in different regions. They want to connect all VNets to each other securely over the Microsoft backbone network, and also connect to their on-premises data center via ExpressRoute. What is the simplest Azure solution to enable connectivity between all VNets and on-premises?

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

Azure Virtual WAN is a managed hub-and-spoke service built on the Microsoft global backbone. Each regional Virtual Hub automatically routes traffic between all connected VNets and branch sites (VPN or ExpressRoute) with transitive any-to-any connectivity, so a spoke VNet only needs to connect to its regional hub rather than peer directly with every other VNet. This design makes it the preferred solution when multiple VNets in different regions must communicate while also integrating on-premises connectivity without manual route management.

Why this answer

Azure Virtual WAN is the simplest solution because it provides a hub-and-spoke architecture that automatically connects all VNets and on-premises sites over the Microsoft backbone network. It natively integrates ExpressRoute and VPN gateways into a single managed service, eliminating the need to manually configure multiple peering or gateway connections.

Exam trap

The trap here is that candidates often assume VNet peering or a single ExpressRoute circuit can provide transitive connectivity between all VNets and on-premises, but they forget that VNet peering is non-transitive and ExpressRoute alone does not route between VNets without additional gateways or a hub.

How to eliminate wrong answers

Option B (VNet peering) is wrong because it only connects two VNets directly and does not provide transitive routing; to connect multiple VNets and on-premises, you would need a mesh of peerings and a gateway in each VNet, which is complex and not scalable. Option C (ExpressRoute) is wrong because it only connects on-premises to Azure, not VNets to each other; it requires additional gateways or peering to enable inter-VNet connectivity. Option D (VPN Gateway) is wrong because it only provides site-to-site VPN connectivity to on-premises, not transitive routing between VNets; you would need multiple VPN gateways and complex routing to connect all VNets.

474
MCQmedium

A company has Azure virtual networks (VNets) in three different Azure regions and an on-premises data center connected via ExpressRoute. They need to connect all VNets to each other and to on-premises over the Microsoft global backbone. They also require centralized management of routing and the ability to enforce security policies such as forced tunneling for internet-bound traffic. Which Azure service should they use?

A.Azure Virtual Network Manager
B.Azure Virtual WAN
C.Azure Firewall
D.Azure Route Server
AnswerB

Azure Virtual WAN is Microsoft's global transit networking service that builds a hub-and-spoke architecture with virtual hubs deployed in each region. Each virtual hub contains integrated VPN, ExpressRoute, and (optionally) Azure Firewall components, and the hubs are interconnected via Microsoft's high-speed backbone, enabling VNet-to-VNet, branch-to-VNet, and remote-user-to-VNet connectivity. It automatically manages routing tables, supports forced tunneling, and provides centralized policy management, making it the correct choice when you need reliable global transit between VNets in three different regions and on-premises connectivity.

Why this answer

Azure Virtual WAN is the correct choice because it provides a hub-and-spoke architecture that connects VNets across regions and on-premises via the Microsoft global backbone, with built-in centralized routing management and the ability to enforce security policies like forced tunneling through integrated Azure Firewall or third-party NVAs. It meets all requirements: multi-region VNet connectivity, ExpressRoute integration, and centralized policy control.

Exam trap

The trap here is that candidates often confuse Azure Virtual Network Manager (a connectivity configuration tool) with Azure Virtual WAN (a full SD-WAN solution), overlooking that Virtual WAN provides the actual routing, global transit, and integrated security enforcement required for multi-region and hybrid connectivity.

How to eliminate wrong answers

Option A is wrong because Azure Virtual Network Manager manages network group membership and connectivity configurations (like mesh or hub-and-spoke) but does not provide built-in routing management, forced tunneling, or direct integration with ExpressRoute for global backbone connectivity. Option C is wrong because Azure Firewall is a stateful firewall service that enforces security policies and forced tunneling, but it does not provide the underlying connectivity between VNets and on-premises or centralized routing management across regions. Option D is wrong because Azure Route Server enables dynamic route exchange between NVAs and Azure VNets but does not provide the global connectivity fabric, centralized routing management, or forced tunneling enforcement required for multi-region and on-premises integration.

475
MCQmedium

A company deploys a web application on Azure VMs across multiple availability zones in the East US region. They need to distribute incoming HTTPS traffic across the VMs, offload SSL termination, and ensure that client requests from the same user session are sent to the same backend VM (session persistence). Which Azure load balancing solution should they choose?

A.Azure Application Gateway v2 with cookie-based affinity
B.Azure Load Balancer Standard with source IP affinity
C.Azure Traffic Manager with performance routing
D.Azure Front Door with session affinity
AnswerA

Azure Application Gateway v2 is the correct choice because it operates at Layer 7, allowing it to terminate SSL/TLS and inspect HTTP headers and cookies. With cookie-based affinity, the gateway sets a session cookie to bind a client to the same backend VM for the duration of the session, which is essential for stateful web applications. Additionally, v2 supports zone-redundant deployment, enabling automatic distribution of traffic across VMs placed in different availability zones.

Why this answer

Azure Application Gateway v2 is the correct choice because it is a Layer 7 load balancer that can offload SSL termination, distribute HTTPS traffic, and support cookie-based session affinity (also known as sticky sessions). Cookie-based affinity ensures that all requests from the same user session are routed to the same backend VM by injecting an Application Gateway-managed cookie into the client's response. This meets all three requirements: HTTPS traffic distribution, SSL offloading, and session persistence.

Exam trap

The trap here is that candidates often confuse Azure Load Balancer (Layer 4) with Application Gateway (Layer 7), assuming that 'session persistence' alone is enough, but they overlook the explicit requirement for SSL termination, which only a Layer 7 solution like Application Gateway can provide.

How to eliminate wrong answers

Option B is wrong because Azure Load Balancer Standard operates at Layer 4 (TCP/UDP) and cannot offload SSL termination; it also supports source IP affinity for session persistence, but that is not cookie-based and does not handle HTTPS termination. Option C is wrong because Azure Traffic Manager is a DNS-level traffic router that does not perform SSL termination or session persistence; it only directs traffic based on routing methods like performance, priority, or geographic, and does not inspect HTTP/HTTPS payloads. Option D is wrong because Azure Front Door does support session affinity and SSL offloading, but it is a global load balancer and CDN service designed for multi-region distribution, not for distributing traffic across VMs within a single Azure region (East US) across availability zones; it adds unnecessary latency and complexity for a regional-only deployment.

476
MCQhard

You are designing a governance strategy for multiple Azure subscriptions. You need to ensure that all resources in a specific subscription are deployed only in the West US region. Additionally, any new resource group must contain a tag named 'Environment' with a value of 'Production'. What combination of Azure Policy initiatives should you assign?

A.Assign the 'Allowed Locations' policy to the management group and the 'Require a tag on resource groups' policy to the subscription
B.Assign the 'Allowed Locations' policy and the 'Require a tag on resource groups' policy to the subscription
C.Assign the 'Allowed Locations' policy to the subscription and the 'Inherit a tag from the resource group' policy to the management group
D.Assign a single Azure Policy definition that includes both the allowed location and require tag effects
AnswerB

This is correct because both policies are assigned at the subscription scope, directly targeting the specific subscription that needs governance. 'Allowed Locations' restricts where resources can be deployed, and 'Require a tag on resource groups' mandates that each resource group carry a required tag, satisfying the dual constraints of location and tagging without affecting other subscriptions.

Why this answer

It assigns both the 'Allowed Locations' policy and the 'Require a tag on resource groups' policy directly to the subscription. The 'Allowed Locations' policy restricts resource deployment to the West US region, while the 'Require a tag on resource groups' policy ensures that every new resource group includes the 'Environment' tag with a value of 'Production'. Assigning both policies at the subscription scope meets both requirements without unnecessary inheritance or scope issues.

Exam trap

The trap here is that candidates often confuse the 'Require a tag on resource groups' policy with the 'Inherit a tag from the resource group' policy, mistakenly thinking inheritance will enforce the tag on the resource group itself, when in fact inheritance applies tags to resources within the group, not to the group itself.

How to eliminate wrong answers

Option A is wrong because assigning the 'Allowed Locations' policy to the management group would apply the restriction to all subscriptions under that management group, not just the specific subscription, and the 'Require a tag on resource groups' policy at the subscription level is correct but the location policy scope is too broad. Option C is wrong because the 'Inherit a tag from the resource group' policy applies tags from the resource group to its resources, not to the resource group itself, so it does not enforce the required tag on the resource group. Option D is wrong because there is no single Azure Policy definition that combines both the 'Allowed Locations' and 'Require a tag on resource groups' effects; these are separate policy definitions that must be assigned individually.

477
MCQeasy

Your company has a hybrid infrastructure with on-premises servers and Azure virtual machines. You need to design a backup strategy that includes on-premises file servers and Azure VMs. The solution must support long-term retention for compliance (7 years) and provide immediate recovery for recent versions. What should you include in the design?

A.Use Azure Storage account snapshots for on-premises files and Azure VM snapshots for VMs.
B.Deploy Azure Backup with the Microsoft Azure Recovery Services (MARS) agent for on-premises and the Azure Backup extension for VMs.
C.Set up Azure File Sync to sync on-premises files to Azure Files, then back up the Azure file shares.
D.Use Azure Site Recovery for both on-premises servers and Azure VMs.
AnswerB

Azure Backup is the correct service because it unifies protection for both sides of the hybrid infrastructure in a single Recovery Services vault. For on-premises files and system state, the MARS agent runs on Windows servers and sends encrypted backups to the vault; for Azure VMs, the Azure Backup extension coordinates with the VM's guest OS to create application-consistent snapshots. Backup policies in Azure Backup allow configurable retention up to 99 years, which easily satisfies the 7-year compliance mandate, and the vault provides centralized monitoring, alerting, and long-term archival across all protected workloads.

Why this answer

Azure Backup with the MARS agent provides long-term retention (up to 99 years) and supports on-premises file servers, while the Azure Backup extension for Azure VMs offers application-consistent snapshots and instant recovery for recent versions. This combination meets the 7-year compliance requirement and immediate recovery needs without additional infrastructure.

Exam trap

The trap here is confusing synchronization (Azure File Sync) or disaster recovery (Azure Site Recovery) with backup, leading candidates to overlook Azure Backup's native support for both on-premises and Azure VMs with long-term retention.

How to eliminate wrong answers

Option A is wrong because Azure Storage account snapshots are not a backup solution; they lack granular file-level recovery, long-term retention policies, and cannot protect on-premises file servers directly. Option C is wrong because Azure File Sync is a synchronization tool, not a backup service; it does not provide point-in-time recovery or retention policies for compliance, and backing up Azure file shares separately still requires a backup solution like Azure Backup. Option D is wrong because Azure Site Recovery is designed for disaster recovery (replication and failover) with short retention (typically up to 72 hours), not for long-term backup retention of 7 years or immediate file-level recovery.

478
MCQhard

A company uses Azure Cosmos DB with a single write region. They need to ensure business continuity with an RPO of 5 seconds and RTO of 1 minute in case of a regional outage. What configuration should they use?

A.Enable multi-region writes with automatic failover
B.Enable automatic failover from a single write region to a read region
C.Deploy Cosmos DB in an availability zone-enabled region
D.Use manual failover to a secondary read region
AnswerA

Enabling multi-region writes with automatic failover makes every participating region a writable replica, so writes can be served by any region and replicated asynchronously with conflict resolution based on LSNs. Because no region is a passive secondary that must be promoted, automatic failover simply redirects traffic without waiting for data catch-up, achieving an RPO of 0 and an RTO of seconds. This is the only option that fully satisfies the requirement for near-zero data loss and automatic cross-region failover.

Why this answer

Multi-region writes with automatic failover allows any Azure Cosmos DB region to accept writes, and if the primary region fails, the SDK automatically routes write requests to the next nearest region. This configuration can achieve an RPO of 0 (no data loss) and an RTO of less than a minute, which exceeds the required RPO of 5 seconds and RTO of 1 minute. The key is that with multi-region writes, there is no need to promote a read region to a write region, eliminating the failover delay and potential data loss.

Exam trap

The trap here is that candidates often assume automatic failover from a single write region is sufficient, but they overlook that the default replication lag guarantee is 5 minutes, which fails the strict RPO requirement, and that multi-region writes are the only way to achieve sub-minute RTO and near-zero RPO for regional outages.

How to eliminate wrong answers

Option B is wrong because enabling automatic failover from a single write region to a read region can result in an RPO of up to 5 minutes (due to the 5-minute replication lag guarantee) and an RTO of up to 15 minutes, which does not meet the required 5-second RPO and 1-minute RTO. Option C is wrong because deploying Cosmos DB in an availability zone-enabled region provides high availability within a single region but does not protect against a full regional outage, so it cannot meet the RPO/RTO requirements for a regional disaster. Option D is wrong because manual failover to a secondary read region requires human intervention, leading to an RTO that is typically minutes to hours, far exceeding the 1-minute RTO, and the RPO can be up to 5 minutes due to replication lag.

479
Multi-Selecteasy

Which TWO Azure services provide native support for change data capture (CDC) to stream database changes to other systems?

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

Azure Cosmos DB is a correct answer because it exposes a native change feed directly from the container, implemented as an append-only, ordered per logical partition log that captures item inserts, updates, and deletes. This change feed is consumed via the Cosmos DB SDK, Azure Functions trigger, or the Change Feed Processor library, delivering at-least-once semantics and automatic paging. This is a first-class CDC facility for a multi-model NoSQL database, distinct from a SQL-based CDC implementation.

Why this answer

Azure Cosmos DB provides native change feed support, which is a persistent, ordered log of changes (inserts, updates, deletes) that can be streamed to downstream systems via the Change Feed processor or Azure Functions. This makes it a correct answer for change data capture (CDC) scenarios.

Exam trap

The trap here is that candidates may confuse Azure Synapse Link for Azure Cosmos DB (an analytical store) with a native CDC service, when in fact it relies on the underlying change feed but is not itself a CDC streaming solution.

480
MCQmedium

A company is migrating a MongoDB-compatible application to Azure. The application requires low-latency reads and writes globally. It needs to support multi-region writes so that updates can be made from any region with automatic conflict resolution. The data is JSON documents that can vary in schema. The company wants a fully managed database service with native support for MongoDB APIs. Which Azure data service should they choose?

A.Azure SQL Database
B.Azure Cosmos DB with the API for MongoDB
C.Azure Database for MongoDB
D.Azure Cache for Redis
AnswerB

Azure Cosmos DB with the API for MongoDB is a native implementation of the MongoDB wire protocol on a globally distributed, multi-model NoSQL database service. It enables existing MongoDB drivers to connect directly while gaining Cosmos DB's turnkey global distribution, multiple consistency levels, and SLA-backed performance. It supports both shared and dedicated throughput, and features like automatic indexing and conflict resolution for multi-region writes.

Why this answer

Azure Cosmos DB with the API for MongoDB is the correct choice because it provides a fully managed, globally distributed database service that natively supports the MongoDB wire protocol. It offers multi-region writes with automatic conflict resolution using last-writer-wins (LWW) or custom conflict resolution policies, ensuring low-latency reads and writes globally. Its schema-agnostic nature handles JSON documents with varying schemas, meeting all stated requirements.

Exam trap

The trap here is that candidates may confuse 'Azure Database for MongoDB' (which does not exist) with Azure Cosmos DB's API for MongoDB, or incorrectly assume that a relational database like Azure SQL Database can handle schema-flexible JSON documents with global multi-region writes.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a relational database that does not support MongoDB APIs, JSON document storage with varying schemas, or multi-region writes with automatic conflict resolution. Option C is wrong because Azure Database for MongoDB does not exist as a native Azure service; the correct service is Azure Cosmos DB with the API for MongoDB, and this option represents a common misconception of a separate service. Option D is wrong because Azure Cache for Redis is an in-memory caching service, not a fully managed database for persistent JSON document storage, and it does not support MongoDB APIs or multi-region writes.

481
Multi-Selecthard

Which THREE components are required to monitor and audit Azure resource changes using Azure Monitor?

Select 3 answers
A.An Application Insights resource
B.A Log Analytics workspace
C.Diagnostic settings on resources to send logs to the workspace
D.Azure Activity Log export to the workspace
E.Azure Policy with audit effect
AnswersB, C, D

A Log Analytics workspace is the fundamental aggregation and analysis destination that underpins Azure Monitor auditing and monitoring. It stores log data from Activity Log exports, resource diagnostic settings, and many other sources, enabling near-real-time log queries with Kusto Query Language (KQL), Azure Monitor alert rules, and workbooks. Without a workspace, there is no centralized, queryable store to retain and correlate audit traces, making it an essential component for any monitoring and auditing scenario in Azure.

Why this answer

A Log Analytics workspace is required because it serves as the central repository where Azure Monitor collects and stores log data from various sources, including diagnostic settings and activity logs. Without a workspace, there is no destination for the logs to be ingested, queried, or analyzed, making it an essential component for monitoring and auditing resource changes.

Exam trap

The trap here is that candidates often confuse Azure Policy’s audit effect as a direct logging mechanism, when in fact it only evaluates compliance and requires diagnostic settings to send its data to a Log Analytics workspace for auditing.

482
MCQmedium

A financial services company runs a critical SQL Server database on Azure Virtual Machines. They require a disaster recovery solution with an RPO of less than 15 seconds and an RTO of less than 1 hour. Which technology should they implement?

A.Azure Site Recovery
B.SQL Server Always On Availability Groups
C.Azure Backup for SQL Server
D.Geo-redundant backups
AnswerB

SQL Server Always On Availability Groups is correct because, with synchronous-commit mode, every transaction committed on the primary replica is hardened on a secondary replica before acknowledgment, yielding an RPO of zero. The secondary is kept in a continuously recovered state, and automatic failover with a listener can be completed within seconds to minutes, comfortably satisfying both sub-15-second RPO and sub-1-hour RTO. This is a database-level, application-aware solution that maintains transaction consistency, unlike storage or VM-level alternatives.

Why this answer

SQL Server Always On Availability Groups provide synchronous data replication at the database level, enabling an RPO of less than 15 seconds by committing transactions on both primary and secondary replicas simultaneously. With automatic failover and a secondary replica in a different Azure region, the RTO can be under 1 hour, meeting the critical requirements for a SQL Server workload on Azure VMs.

Exam trap

The trap here is that candidates often confuse Azure Site Recovery's VM-level replication with database-level replication, assuming it can meet low RPO/RTO for SQL Server, but it cannot achieve sub-15-second RPO because it replicates at the hypervisor level with inherent lag.

How to eliminate wrong answers

Option A is wrong because Azure Site Recovery replicates entire VMs at the hypervisor level, not the database level, and its typical RPO is around 30 seconds to several minutes, failing to meet the sub-15-second requirement. Option C is wrong because Azure Backup for SQL Server is a backup solution, not a real-time replication or disaster recovery technology; it provides point-in-time restores with RPOs measured in minutes or hours, not seconds. Option D is wrong because geo-redundant backups (e.g., GRS) offer recovery points that are typically hours old (due to backup schedules and replication lag), and they require a full restore process, resulting in RTOs far exceeding 1 hour.

483
MCQhard

Refer to the exhibit. You are reviewing an Azure Site Recovery replicated item for a VM. The replication health is Normal, and the last recovery point is at 10:30 AM. The primary region experiences a failure at 10:35 AM. You initiate a failover at 10:40 AM. What is the maximum potential data loss?

A.5 minutes of data
B.15 minutes of data
C.0 minutes of data
D.10 minutes of data
AnswerA

The recovery point created at 10:30 is the most recent point that can be used for failover. Since the failure occurred at 10:35, all changes made between 10:30 and 10:35 are not replicated to the recovery point and are therefore lost. This matches Azure Site Recovery's typical 5-minute Recovery Point Objective (RPO) for asynchronous replication, so the maximum data loss is exactly the 5-minute gap between the last consistent recovery point and the failure time.

Why this answer

The last recovery point was at 10:30 AM, and the failover was initiated at 10:40 AM. Since the failure occurred at 10:35 AM, any data written between 10:30 AM and 10:35 AM (5 minutes) that was not yet replicated to the recovery point is lost. Azure Site Recovery replicates asynchronously, so the maximum potential data loss equals the time between the last successful recovery point and the failure event.

Exam trap

The trap here is confusing the time between the last recovery point and the failover initiation (10 minutes) with the actual data loss window, which is bounded by the failure time, not the failover time.

How to eliminate wrong answers

Option B (15 minutes) is wrong because it incorrectly assumes data loss from the last recovery point at 10:30 AM to the failover at 10:40 AM, but the failure at 10:35 AM stops new writes, so only 5 minutes of unreplicated data exists. Option C (0 minutes) is wrong because Azure Site Recovery uses asynchronous replication, not synchronous, so there is always a potential for data loss between recovery points. Option D (10 minutes) is wrong because it miscalculates the window as the time from the last recovery point (10:30 AM) to the failover initiation (10:40 AM), ignoring that the failure at 10:35 AM halts data generation.

484
MCQeasy

A company is deploying a containerized microservices application on Azure Kubernetes Service (AKS). The application requires persistent storage that can be attached to pods and supports dynamic provisioning. Which Azure storage solution should they use?

A.Azure Blob Storage
B.Azure Files
C.Azure NetApp Files
D.Azure Disks
AnswerD

Azure Disks are managed block-storage volumes that integrate natively with AKS through the built-in managed-csi StorageClass, allowing persistent volume claims to be dynamically created and attached. They provide consistent, low-latency performance with configurable SKUs, which is exactly what a containerized microservices application needs for stateful workloads. Since each pod can have its own disk and the CSI driver automates provisioning, Azure Disks is the correct and most common choice for AKS persistent volumes.

Why this answer

Azure Disks is the correct choice because it provides block-level storage volumes that can be dynamically provisioned via the AKS built-in StorageClass, supporting ReadWriteOnce access mode required for a single pod in a containerized microservices application. Azure Disks integrate directly with Kubernetes PersistentVolumeClaims (PVCs) for dynamic provisioning, offering low-latency, high-performance storage suitable for stateful workloads.

Exam trap

The trap here is that candidates often confuse Azure Files (shared file storage) with Azure Disks (block storage), assuming that 'persistent storage' always means file shares, but for single-pod dynamic provisioning in AKS, Azure Disks are the native and optimal choice.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage is object storage accessed via HTTP/HTTPS, not block storage, and does not support direct attachment to pods via Kubernetes PV/PVC without a CSI driver or sidecar, making it unsuitable for dynamic provisioning in AKS. Option B is wrong because Azure Files provides SMB/NFS file shares that support ReadWriteMany access, but for a single-pod persistent storage scenario, Azure Disks offer lower latency and are more cost-effective; Azure Files is typically used for shared access across multiple pods, not single-pod dynamic provisioning. Option C is wrong because Azure NetApp Files is a premium enterprise-grade file service with high cost and complexity, overkill for standard AKS persistent storage, and requires additional configuration for dynamic provisioning compared to the native Azure Disks integration.

485
MCQhard

An Azure SQL Database supports a customer-facing application. The company requires automatic failover to a paired region with minimal administrative action. Which feature should be recommended?

A.Zone-redundant storage only
B.Auto-failover group
C.SQL elastic pool only
D.Azure Backup vault only
AnswerB

Auto-failover groups are the correct solution because they implement geo-replication between an Azure SQL Database in a primary region and a readable secondary replica in a different Azure region. Through a logical DNS-based listener endpoint, the service automatically redirects application connections to the secondary during a regional outage, enabling seamless failover with minimal downtime. This directly satisfies the cross-region availability requirement.

Why this answer

Auto-failover groups in Azure SQL Database enable automatic, synchronous or asynchronous replication of databases to a paired region, with a built-in listener endpoint that handles transparent failover. This meets the requirement for minimal administrative action because failover can be triggered automatically based on the built-in grace period and health monitoring, without manual intervention.

Exam trap

The trap here is that candidates often confuse zone-redundant storage (which protects against zone failures within a region) with cross-region failover, or mistakenly think an elastic pool provides disaster recovery capabilities when it is only a management unit for performance and cost.

How to eliminate wrong answers

Option A is wrong because zone-redundant storage only protects against an availability zone failure within a single region, not a full regional outage, and does not provide automatic failover to a paired region. Option C is wrong because an SQL elastic pool is a resource management construct for scaling and managing multiple databases within a single server, not a disaster recovery or failover feature. Option D is wrong because Azure Backup vault is used for long-term backup retention and point-in-time restore, not for automatic failover or continuous replication to a paired region.

486
MCQmedium

You are designing a governance solution for a Microsoft Azure environment that contains multiple subscriptions. You need to ensure that all resources are compliant with corporate security policies. The solution must automatically remediate non-compliant resources. What should you include in the design?

A.Azure RBAC custom roles
B.Azure Policy with DeployIfNotExists effect
C.Azure Resource Graph queries
D.Azure Blueprints
AnswerB

Azure Policy with the DeployIfNotExists effect evaluates resources against policy definitions and, when a non-compliant resource lacks a required configuration, triggers a deployment to remediate it automatically. This deployment is performed by a managed identity defined in the policy assignment, and remediation tasks can be run on demand or continuously to fix existing and newly created resources. Because it couples compliance assessment with actual resource modification, it directly satisfies the requirement for automated governance remediation.

Why this answer

Azure Policy with the DeployIfNotExists effect is the correct choice because it automatically remediates non-compliant resources by triggering a deployment (e.g., via a template) when a resource is created or updated and does not meet the policy condition. This ensures continuous compliance with corporate security policies without manual intervention, as the effect can also be assigned a remediation task to fix existing resources.

Exam trap

The trap here is that candidates often confuse Azure Policy's audit-only effects (like AuditIfNotExists) with the automatic remediation capability, or they mistakenly think Azure Blueprints can handle ongoing compliance enforcement, when in fact Blueprints are a one-time deployment orchestration tool and do not provide continuous remediation.

How to eliminate wrong answers

Option A is wrong because Azure RBAC custom roles control who can access and manage resources (authorization), not what configurations those resources must comply with (governance), and they cannot automatically remediate non-compliant resources. Option C is wrong because Azure Resource Graph queries are used for exploring and querying resources across subscriptions at scale, but they are read-only and cannot enforce or remediate compliance. Option D is wrong because Azure Blueprints are used to orchestrate the deployment of resource groups, policies, role assignments, and ARM templates as a package, but they do not automatically remediate non-compliant resources after deployment; remediation requires Policy effects like DeployIfNotExists.

487
Multi-Selectmedium

Which TWO Azure services can be used to provide a fully managed DNS solution that supports custom domains and DNSSEC?

Select 1 answer
A.Azure Front Door
B.Azure DNS
C.Azure Traffic Manager
D.Azure App Service
E.Azure Public IP address
AnswersB

Correct. Azure DNS is a fully managed DNS service that supports custom domains (via DNS zone delegation) and DNSSEC, providing secure and authoritative name resolution.

Why this answer

Azure DNS is a fully managed DNS hosting service that provides name resolution using Microsoft Azure infrastructure and supports custom domains via DNS zone delegation. Azure DNS DNSSEC support is currently limited (preview/not generally available for all scenarios). However, the stem asks for TWO services, and only Azure DNS among the listed options is a full DNS hosting solution.

Azure Front Door and Traffic Manager provide DNS-based traffic routing but are not DNS hosting services and do not support DNSSEC zone management. Azure App Service and Azure Public IP addresses do not provide DNS hosting. Because only one option satisfies the criteria, the question as written is invalid and should be reworded to ask for a single service.

Exam trap

Candidates often mistake Azure Front Door or Traffic Manager for DNS hosting services because they use DNS-based routing, but neither provides full DNS zone management or DNSSEC support. The real trap is recognizing that only Azure DNS is a managed DNS hosting service among these options.

488
MCQhard

Refer to the exhibit. You are reviewing an Azure Policy definition. Which virtual machines will be denied?

A.No virtual machines because the condition is invalid
B.All virtual machines regardless of SKU
C.Only virtual machines with SKU Standard_DS2_v2
D.All virtual machines except those with SKU Standard_DS2_v2
AnswerD

This is the correct behavior. The policy definition evaluates the field 'Microsoft.Compute/virtualMachines/sku.name' and applies the deny effect when that value is 'notEquals' to Standard_DS2_v2. As a result, any virtual machine using another SKU will be denied, while a Standard_DS2_v2 VM will be allowed. This is a common pattern for restricting compute SKUs to an approved allowlist using Azure Policy.

Why this answer

The Azure Policy definition uses a 'deny' effect with a condition that checks if the virtual machine's SKU field is not equal to 'Standard_DS2_v2'. This means any VM whose SKU does not match 'Standard_DS2_v2' will be denied. Only VMs with the exact SKU 'Standard_DS2_v2' will be allowed, making option D correct.

Exam trap

The trap here is that candidates may misinterpret 'notEquals' as denying the specified SKU, when in fact it denies everything except that SKU, leading them to incorrectly choose option C.

How to eliminate wrong answers

Option A is wrong because the condition 'notEquals' is a valid Azure Policy condition operator, so the policy is not invalid. Option B is wrong because the policy specifically denies VMs that do not match the specified SKU, not all VMs. Option C is wrong because the policy denies VMs that are not 'Standard_DS2_v2', not only those with that SKU; it actually allows VMs with that SKU.

489
MCQmedium

Your company plans to migrate on-premises file servers to Azure. The solution must support SMB protocol and integrate with Microsoft Entra ID for authentication. You need to choose a service that provides fully managed file shares accessible from multiple Azure regions. Which Azure service should you use?

A.Azure Disk Storage
B.Azure Files
C.Azure NetApp Files
D.Azure Blob Storage
AnswerB

Azure Files is a fully managed file share service that supports both SMB and NFS protocols, enabling users to map shares in Windows or Linux without managing underlying infrastructure. It integrates with Microsoft Entra ID for Kerberos-based authentication and Azure RBAC for share-level permissions, and it offers features like Azure File Sync to extend on-premises file servers. Its simplicity, low operational overhead, and protocol compatibility make it the ideal PaaS choice for migrating typical on-premises file servers to Azure.

Why this answer

Azure Files provides fully managed SMB file shares that can be accessed from multiple Azure regions using the SMB 3.0 protocol. It integrates natively with Microsoft Entra ID (formerly Azure AD) for Kerberos-based authentication, allowing on-premises identities to access shares without additional domain controllers. This makes it the correct choice for migrating on-premises file servers to a multi-region, identity-aware managed file service.

Exam trap

The trap here is that candidates often confuse Azure NetApp Files (which also supports SMB and Entra ID) as the fully managed option, but Azure NetApp Files is a first-party NetApp service requiring more administrative overhead and is not as straightforward for simple multi-region file shares as Azure Files.

How to eliminate wrong answers

Option A is wrong because Azure Disk Storage provides block-level volumes attached to a single VM, not managed file shares accessible via SMB from multiple regions. Option C is wrong because Azure NetApp Files offers NFS and SMB protocols but is a high-performance, enterprise-grade file service that is not fully managed in the same sense as Azure Files and requires a delegated subnet, making it less suitable for simple multi-region file share scenarios. Option D is wrong because Azure Blob Storage is an object storage service that does not support the SMB protocol natively (it uses REST APIs or NFS 3.0 preview) and cannot integrate with Microsoft Entra ID for SMB authentication.

490
MCQmedium

A company runs a critical SQL Server database on Azure Virtual Machines in a single region. They need a disaster recovery solution across regions with a recovery point objective (RPO) of zero. The database is update-intensive with frequent writes. Which configuration should they implement?

A.SQL Server Always On Availability Group with asynchronous commit.
B.SQL Server Always On Availability Group with synchronous commit across regions.
C.Azure Site Recovery to another region.
D.Deploy the VMs in a different availability zone within the same region.
AnswerB

Synchronous commit ensures all transactions are committed on both the primary and secondary replicas before acknowledging the commit to the application. If configured across regions, this provides zero data loss (RPO=0). But network latency can affect write performance.

Why this answer

SQL Server Always On Availability Group with synchronous commit across regions ensures zero data loss because transactions are committed on both the primary and secondary replicas before the primary acknowledges the commit. This meets the RPO of zero, even though it introduces latency due to cross-region synchronization. For an update-intensive workload, synchronous commit is the only option that guarantees no data loss at the cost of increased write latency.

Exam trap

The trap here is that candidates often choose asynchronous commit (Option A) thinking it is sufficient for DR, but the RPO of zero explicitly requires synchronous commit, despite the performance trade-off.

How to eliminate wrong answers

Option A is wrong because asynchronous commit does not guarantee zero data loss; it allows transactions to be committed on the primary without waiting for the secondary, so the secondary can lag behind, violating the RPO of zero. Option C is wrong because Azure Site Recovery replicates at the VM level using crash-consistent or app-consistent snapshots, which cannot achieve an RPO of zero for a high-write database due to replication intervals and potential data loss between snapshots. Option D is wrong because deploying in different availability zones within the same region does not provide cross-region disaster recovery; it only protects against zonal failures within the same region, not a regional outage.

491
MCQeasy

A company deploys a web application on Azure VMs. They need to distribute incoming HTTP and HTTPS traffic based on the URL path: requests to /api/* go to one VM pool, requests to /images/* go to another pool. They also need to offload SSL/TLS termination. 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 Layer 7 web traffic load balancer that provides advanced application-level features, including URL path-based routing, SSL/TLS termination, cookie-based session affinity, and an optional Web Application Firewall (WAF). It allows traffic to be routed to different backend pools based on URL patterns, which directly meets the stated requirement. This makes it the correct choice for regional Azure VM web applications needing path-based routing and SSL offload.

Why this answer

Azure Application Gateway is a layer-7 load balancer that can route traffic based on URL path (e.g., /api/* vs /images/*) and provides SSL/TLS termination at the gateway, offloading the decryption from the backend VMs. This matches both requirements exactly, whereas other solutions either lack layer-7 path-based routing or are designed for global traffic distribution.

Exam trap

The trap here is that candidates often confuse Azure Application Gateway (regional layer-7 routing) with Azure Front Door (global layer-7 routing) or Azure Load Balancer (layer-4), failing to recognize that only Application Gateway provides both URL path-based routing and SSL termination for a single-region deployment.

How to eliminate wrong answers

Option A is wrong because Azure Load Balancer operates at layer 4 (TCP/UDP) and cannot route based on URL path or perform SSL/TLS termination; it only distributes traffic by IP and port. Option C is wrong because Azure Traffic Manager is a DNS-based global traffic load balancer that routes based on DNS queries, not URL paths, and does not offload SSL/TLS termination. Option D is wrong because Azure Front Door is a global layer-7 service that can route by URL path and offload SSL, but it is designed for global distribution across regions, not for routing within a single region to VM pools; Application Gateway is the correct regional solution for this scenario.

492
MCQhard

You are designing an identity solution for a multinational company that uses Microsoft Entra ID. The company has a requirement that all users must authenticate using biometrics or FIDO2 security keys. Which Entra ID feature should you configure?

A.Passwordless authentication
B.Identity Protection
C.Entra Verified ID
D.Conditional Access policies
AnswerD

Conditional Access policies in Microsoft Entra ID are the correct enforcement mechanism because they can evaluate granular conditions—such as user, location, device compliance, and risk—and then apply grant controls that mandate specific authentication methods. Through the 'Authentication Strengths' feature or the 'Require authentication method' grant control, you can require FIDO2 security keys or Windows Hello for Business, both of which are hardware-backed and inherently phishing-resistant. This aligns with the requirement for rigorous phishing resistance, as these methods use asymmetric cryptography and are not susceptible to phishing attacks, unlike password-based or OTP-based methods.

Why this answer

Conditional Access policies in Microsoft Entra ID allow you to enforce authentication strength requirements, such as requiring biometrics or FIDO2 security keys, by targeting specific user groups or applications. This is achieved by configuring a Conditional Access policy with the 'Require multifactor authentication' control and integrating with authentication methods like Windows Hello for Business or FIDO2 security keys, ensuring that only passwordless authentication methods meeting the company's biometric or FIDO2 requirement are permitted.

Exam trap

The trap here is that candidates confuse the authentication method itself (passwordless authentication) with the policy mechanism (Conditional Access) that enforces its use, leading them to select Option A instead of D.

How to eliminate wrong answers

Option A is wrong because Passwordless authentication is a category of authentication methods (e.g., Windows Hello, FIDO2, Microsoft Authenticator) but not a feature that enforces a requirement; it must be combined with Conditional Access policies to mandate its use. Option B is wrong because Identity Protection is a risk-based detection and remediation service (e.g., detecting leaked credentials or risky sign-ins) and does not enforce specific authentication methods like biometrics or FIDO2. Option C is wrong because Entra Verified ID is a decentralized identity solution for verifiable credentials (e.g., digital IDs for employees or customers) and is unrelated to enforcing authentication method requirements.

493
MCQeasy

Your company needs to store configuration data (key-value pairs) for applications in a highly scalable and low-latency manner. The data is accessed frequently. Which Azure service should you choose?

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

Azure Cache for Redis is a managed in-memory data store that delivers sub-millisecond read latency and native support for key-value pairs, making it ideal for frequently accessed configuration data. Unlike disk-backed services, it holds the working set entirely in RAM, and its automatic scaling and built-in data expiration policies simplify lifecycle management. For simple get/set lookups, this purpose-built caching tier minimizes both latency and operational overhead compared to general-purpose databases.

Why this answer

Azure Cache for Redis is the correct choice because it provides an in-memory data store that delivers extremely low-latency access (typically sub-millisecond) and high throughput for frequently accessed key-value configuration data. It supports common data structures like strings, hashes, and lists, and can be used as a distributed cache or session store, making it ideal for high-frequency read workloads where persistence is not the primary concern.

Exam trap

The trap here is that candidates often confuse Azure Cache for Redis with Azure Cosmos DB or Azure Table Storage, assuming any key-value store is equivalent, but the exam emphasizes the specific requirement for 'highly scalable and low-latency' access, which only an in-memory cache like Redis can deliver for frequently read configuration data.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB is a globally distributed, multi-model NoSQL database designed for complex queries, indexing, and transactional consistency, which introduces higher latency and overhead compared to an in-memory cache for simple key-value lookups. Option C is wrong because Azure SQL Database is a relational database with full ACID compliance and disk-based storage, resulting in higher read latency and cost for simple key-value access patterns that do not require relational features. Option D is wrong because Azure Table Storage is a NoSQL key-value store but operates on disk-based storage with higher latency (typically 10-50 ms) and lacks the sub-millisecond performance and advanced caching features (like TTL, eviction policies) that Azure Cache for Redis provides.

494
MCQhard

You are designing a backup strategy for Azure VMs running critical business applications. The solution must support application-consistent backups and allow for restoration to a different region. Which Azure service and configuration should you use?

A.Azure Backup with application-consistent backup policy and geo-redundant storage
B.Azure Disk Encryption with Azure Backup
C.Azure Snapshot with cross-region copy
D.Azure Site Recovery with replication to secondary region
AnswerA

Azure Backup is the correct choice because it leverages the Volume Shadow Copy Service (VSS) to capture application-consistent recovery points, ensuring that databases and applications are in a consistent state before the backup is taken. Geo-redundant storage (GRS) in the Recovery Services vault replicates backup data to a paired Azure region, enabling geo-restore if the primary region is lost. Azure Backup also offers 99.9% RPO compliance, encrypted backups, and long-term retention policies, making it a comprehensive, managed backup solution for critical VMs.

Why this answer

Azure Backup with an application-consistent backup policy uses the Volume Shadow Copy Service (VSS) on Windows or pre/post-scripts on Linux to ensure that all in-memory data and pending I/O operations are flushed before the snapshot is taken. By configuring the Backup vault with geo-redundant storage (GRS), the backup data is replicated to a paired region, enabling restoration to a different region in the event of a regional disaster.

Exam trap

The trap here is confusing Azure Site Recovery (disaster recovery) with Azure Backup (backup), and assuming that any snapshot or replication mechanism automatically provides application consistency and point-in-time restore capabilities.

How to eliminate wrong answers

Option B is wrong because Azure Disk Encryption provides encryption at rest for managed disks but does not create backups or support application-consistent snapshots, nor does it enable cross-region restoration. Option C is wrong because Azure Snapshot with cross-region copy can copy a snapshot to another region, but snapshots are crash-consistent by default and do not guarantee application consistency without additional scripting or coordination with VSS. Option D is wrong because Azure Site Recovery is designed for disaster recovery and replication of VMs to a secondary region, not for backup; it does not natively support application-consistent backups for point-in-time restoration and is not a backup service.

495
MCQeasy

A company plans to deploy a web application on Azure virtual machines. They want to protect against a datacenter failure within a region. The VMs must be distributed across multiple physically separate locations with independent power, cooling, and networking. Which deployment option should they use?

A.Availability Set
B.Availability Zones
C.Virtual Machine Scale Set
D.Proximity Placement Group
AnswerB

Availability Zones are physically separate locations inside an Azure region, each with its own independent power, cooling, and networking, and each containing at least one datacenter. By placing VMs in different zones, you ensure that no single datacenter failure can bring down all instances, because the zones are designed as isolated failure domains with no shared infrastructure. This is why zone-redundant deployment is the direct answer to protecting against a full datacenter outage.

Why this answer

Availability Zones are physically separate datacenters within an Azure region, each with independent power, cooling, and networking. By deploying VMs across multiple zones, the application is protected against a single datacenter failure, meeting the requirement for fault isolation at the datacenter level.

Exam trap

The trap here is that candidates often confuse Availability Sets (which protect against rack-level failures within a single datacenter) with Availability Zones (which protect against entire datacenter failures), leading them to select the wrong option when the question explicitly requires physically separate locations with independent infrastructure.

How to eliminate wrong answers

Option A is wrong because an Availability Set protects against failures within a single datacenter (rack-level faults) by distributing VMs across update and fault domains, not across physically separate datacenters. Option C is wrong because a Virtual Machine Scale Set is primarily for auto-scaling and managing identical VMs; while it can use Availability Zones, the scale set itself is not a deployment option that guarantees distribution across physically separate locations without explicit zone configuration. Option D is wrong because a Proximity Placement Group is designed to reduce network latency by co-locating VMs close together, which is the opposite of distributing them across physically separate locations.

496
MCQhard

A company runs a critical application on Azure VMs in a single region. They need to implement disaster recovery using Azure Site Recovery (ASR) with a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 2 hours. The database VMs have a very high data change rate, and the company wants to minimize replication costs. They also need to ensure that in the recovery plan, database VMs start before application VMs, and a script updates DNS records after failover. Which combination of ASR configurations should they use?

A.Enable multi-VM consistency groups and use recovery plans with manual ordering.
B.Enable app-consistent replication and use deployment plans with pre- and post-actions.
C.Enable replication with high churn protection and use recovery plans with availability groups.
D.Enable crash-consistent replication and use recovery plans with pre- and post-actions.
AnswerD

Crash-consistent replication in Azure Site Recovery copies all disks without invoking VSS, avoiding application-level snapshot overhead while still generating recovery points at the OS level; for this critical workload, those recovery points meet the stipulated RPO and reduce storage and I/O costs. A recovery plan groups VMs into ordered clauses, and you add pre-actions to enforce startup order — for example, starting the database VM before the web VM — and post-actions to run PowerShell scripts after failover to complete application configuration. This combination provides the required automation with the least expensive replication mode, so it is the correct answer.

Why this answer

Crash-consistent replication is the most cost-effective ASR option for VMs with high data change rates, as it replicates only the data that has changed since the last snapshot without requiring application-level consistency. The RPO of 15 minutes and RTO of 2 hours can be met with crash-consistent replication, and recovery plans with pre- and post-actions allow you to specify that database VMs start before application VMs and run a script to update DNS records after failover.

Exam trap

The trap here is that candidates often assume app-consistent replication is always required for database VMs, but the question explicitly prioritizes minimizing replication costs and only requires a 15-minute RPO, making crash-consistent replication the correct choice despite the high data change rate.

How to eliminate wrong answers

Option A is wrong because multi-VM consistency groups are used to ensure crash-consistent or app-consistent replication across multiple VMs, but they do not address the need to minimize replication costs for high-churn VMs; they also do not provide the ability to run scripts after failover. Option B is wrong because app-consistent replication requires application-level snapshots (e.g., using VSS on Windows), which increases replication overhead and cost, and is not necessary for meeting a 15-minute RPO with high data change rates; deployment plans are not a valid ASR feature. Option C is wrong because 'high churn protection' is not a standard ASR configuration; ASR does not have a specific setting for high churn, and availability groups are a SQL Server feature, not an ASR recovery plan feature.

497
MCQmedium

Your company has an Azure subscription with multiple virtual networks connected via VNet peering. You need to design a solution to allow VMs in different peered VNets to resolve each other's private IP addresses using custom DNS suffixes. The solution must minimize administrative overhead. What should you implement?

A.Deploy custom DNS servers on Azure VMs and configure VNets to use those servers.
B.Configure Azure DNS to use a custom domain name and update each VM's DNS suffix.
C.Use Azure Firewall as a DNS proxy with custom DNS settings.
D.Create an Azure Private DNS Zone linked to each VNet with auto-registration enabled.
AnswerD

Creating an Azure Private DNS Zone and linking it to each VNet with auto-registration enabled provides fully managed, automatic name resolution for VMs across the entire peered network topology. When auto-registration is turned on, Azure automatically creates and maintains A records for every VM as they are generated or deleted, eliminating manual record management. By linking the zone to all VNets involved in peering, nodes in any linked VNet can resolve each other's hostnames using the same private DNS namespace, making this the correct, scalable, and administration-free solution.

Why this answer

Azure Private DNS Zone with auto-registration enables VMs in peered VNets to resolve each other's private IP addresses using custom DNS suffixes without deploying or managing custom DNS servers. When auto-registration is enabled, Azure automatically creates and updates A records for VMs in the linked VNet, and VNet peering propagates DNS resolution across peered VNets. This minimizes administrative overhead because no manual DNS server configuration or VM-level DNS suffix updates are needed.

Exam trap

The trap here is that candidates often assume custom DNS servers or Azure Firewall DNS proxy are needed for custom DNS suffixes, but Azure Private DNS Zone with auto-registration provides a fully managed, zero-maintenance solution for private DNS resolution across peered VNets.

How to eliminate wrong answers

Option A is wrong because deploying custom DNS servers on Azure VMs introduces significant administrative overhead for patching, scaling, and high availability, contradicting the requirement to minimize overhead. Option B is wrong because Azure DNS custom domain names apply to public DNS resolution, not private IP resolution across peered VNets, and updating each VM's DNS suffix manually is not scalable. Option C is wrong because Azure Firewall as a DNS proxy does not provide custom DNS suffix resolution for private IP addresses across peered VNets; it only forwards DNS queries to a specified DNS server and does not create or manage DNS records.

498
MCQeasy

A company is deploying a new application on Azure Kubernetes Service (AKS). The application requires persistent storage that can be dynamically provisioned and accessed by multiple pods simultaneously. Which Azure storage solution should the company use?

A.Azure Blob Storage
B.Azure Files
C.Azure Disk
D.Azure NetApp Files
AnswerB

Azure Files provides fully managed SMB 3.0 file shares that can be mounted by many clients concurrently, giving it native ReadWriteMany (RWX) support. The Azure Files CSI driver dynamically provisions persistent volumes in Kubernetes, and it can integrate with AAD identity for per-share access control. This makes it the ideal choice for a single, shared filesystem that multiple pods across different nodes can access simultaneously.

Why this answer

Azure Files provides SMB and NFS file shares that can be mounted concurrently by multiple pods in Azure Kubernetes Service (AKS), meeting the requirement for persistent storage that is dynamically provisioned and accessible by multiple pods simultaneously. Azure Files supports the ReadWriteMany (RWX) access mode, which is essential for multi-pod access, and can be dynamically provisioned using a StorageClass with the `provisioner: file.csi.azure.com`.

Exam trap

The trap here is that candidates often confuse Azure Disk (RWO) with Azure Files (RWX) because both are block or file storage, but Azure Disk cannot be shared across pods, which is a critical distinction for multi-pod access scenarios.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage is an object storage solution that does not support standard file system semantics like concurrent multi-pod access via POSIX or SMB protocols; it is designed for unstructured data and accessed via REST APIs, not as a shared file system for pods. Option C is wrong because Azure Disk supports only the ReadWriteOnce (RWO) access mode, meaning it can be mounted by only a single pod at a time, which fails the requirement for multiple pods to access storage simultaneously. Option D is wrong because Azure NetApp Files, while supporting ReadWriteMany (RWX), is a premium enterprise file service that is overkill for this scenario and is not the standard or most cost-effective choice for AKS dynamic provisioning; Azure Files is the recommended and simpler solution for general multi-pod shared storage.

499
MCQmedium

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to automate the process of granting users access to a specific application only during business hours and revoking it automatically. The access should be based on a request-approval workflow. Which Microsoft Entra ID feature should they use?

A.Privileged Identity Management (PIM)
B.Conditional Access
C.Access Reviews
D.Entitlement Management
AnswerD

Entitlement Management is the correct tool because it enables administrators to create access packages that bundle resources like groups, apps, and SharePoint sites with request and approval policies. These policies support time-limited assignments, expiration dates, and automatic revocation of access when the entitlement expires. It also integrates with connected organizations and access reviews, providing a complete automated identity governance lifecycle for internal and external users.

Why this answer

Entitlement Management (D) is correct because it provides automated access lifecycle management through access packages, which can include time-bound assignments (e.g., business hours) and require approval workflows. This allows you to define policies that grant access to the application only during specified hours and automatically revoke it when the policy expires or conditions change, without manual intervention.

Exam trap

The trap here is confusing Conditional Access (which controls access at authentication time) with Entitlement Management (which provisions and deprovisions access over time), leading candidates to pick B because they focus on the 'business hours' condition rather than the automated lifecycle workflow.

How to eliminate wrong answers

Option A is wrong because Privileged Identity Management (PIM) is designed for just-in-time privileged role activation (e.g., Global Administrator) and does not support time-bound access to non-privileged applications or request-approval workflows for standard users. Option B is wrong because Conditional Access enforces real-time access policies based on signals (e.g., location, device state) but cannot automate granting or revoking access through a request-approval workflow; it is a gate, not a provisioning mechanism. Option C is wrong because Access Reviews only provide periodic attestation of existing access (e.g., recertification) and do not automate the initial granting or time-bound revocation of access based on a request-approval process.

500
MCQhard

A company deploys Azure VNets in multiple regions and has on-premises data centers. They need to connect all VNets to each other and to on-premises sites using the Microsoft global network for optimal routing. They also want to simplify management by using a single orchestration interface. Which Azure service should they use?

A.Azure Virtual Network peering
B.Azure VPN Gateway with multi-site connections
C.Azure ExpressRoute Gateway
D.Azure Virtual WAN
AnswerD

Azure Virtual WAN is a Microsoft-managed, hub-and-spoke networking service that connects VNets and on-premises branches through a global mesh over the Microsoft backbone. Each regional virtual hub contains a scalable router that automatically computes routes between all attached VNets and remote sites, and hubs in different regions are automatically interconnected to provide any-to-any connectivity. It supports Site-to-Site VPN, Point-to-Site VPN, and ExpressRoute, all managed from a single pane of glass, which dramatically simplifies multi-region and multi-site administration. Because it centralizes routing, security policies (via Virtual WAN Secured Hubs and Azure Firewall Manager), and connectivity, it is the correct choice for a company with VNets in multiple regions plus on-premises locations.

Why this answer

Azure Virtual WAN (D) is correct because it provides a hub-and-spoke architecture that connects VNets across multiple regions and on-premises sites using the Microsoft global network for optimal routing. It offers a single orchestration interface (the Virtual WAN portal/API) to manage all connectivity, including site-to-site VPN, ExpressRoute, and VNet-to-VNet traffic, simplifying management and ensuring traffic traverses Microsoft's backbone rather than the public internet.

Exam trap

The trap here is that candidates often confuse Azure Virtual WAN with a simple VPN gateway or peering solution, overlooking that Virtual WAN is specifically designed for large-scale, multi-region, multi-site connectivity with a single management plane, while the other options are point solutions that require complex manual configuration to achieve the same result.

How to eliminate wrong answers

Option A is wrong because Azure Virtual Network peering only connects two VNets directly and does not provide a single orchestration interface for multiple VNets and on-premises sites; it also does not inherently use the Microsoft global network for routing between peered VNets in different regions (traffic may traverse the internet unless ExpressRoute or VPN is added). Option B is wrong because Azure VPN Gateway with multi-site connections can connect multiple on-premises sites to a single VNet, but it does not connect multiple VNets to each other natively (requires additional VPN gateways or peering) and lacks a unified orchestration interface for all connectivity. Option C is wrong because Azure ExpressRoute Gateway provides dedicated private connectivity to on-premises but only connects a single VNet to on-premises; it does not interconnect multiple VNets across regions or offer a single management interface for multi-site and multi-VNet topologies.

501
Multi-Selectmedium

You are designing a monitoring solution for a multi-region application deployed on Azure Virtual Machines and Azure SQL Database. The solution must provide a unified view of metrics and logs from all resources, detect anomalies using machine learning, and send alerts to the operations team. Which TWO capabilities should you include in the design?

Select 2 answers
A.Azure Service Health
B.Azure Application Insights
C.Azure Security Center
D.Azure Monitor
E.Azure Log Analytics
AnswersB, D

Azure Application Insights is a feature of Azure Monitor and a full-fledged Application Performance Management (APM) service for developers. It automatically collects request rates, response times, dependency calls, exceptions, and custom events, and it uses smart detection to flag anomalies without you having to define thresholds. It also provides distributed tracing and a rich query language, making it the definitive choice for application-specific monitoring.

Why this answer

Azure Monitor is the core platform for collecting, analyzing, and acting on telemetry from Azure resources, including metrics and logs from VMs and SQL Database. Application Insights extends Azure Monitor with application performance management (APM) and built-in machine learning anomaly detection (e.g., Smart Detection) for proactive alerting. Together, they provide a unified monitoring view with ML-driven insights.

Exam trap

The trap here is that candidates often confuse Azure Log Analytics as a separate monitoring service rather than recognizing it as a component of Azure Monitor, leading them to select it as an independent capability instead of Azure Monitor itself.

502
Multi-Selecthard

A company is designing hub-and-spoke networking. Spoke VNets must use a central Azure Firewall for outbound internet traffic. Which two configurations are required?

Select 2 answers
A.Enable public IP addresses on all workload VMs
B.Peer each spoke VNet with the hub VNet
C.Associate a route table to spoke subnets with a default route to the firewall private IP
D.Deploy a NAT gateway in every spoke subnet
AnswersB, C

VNet peering is the required control-plane foundation of the hub-spoke topology: it creates a private, low-latency bidirectional link between each spoke and the hub without traversing the internet, VPN tunnels, or ExpressRoute. Peering is not transitive, so the hub must be peered with every spoke to relay spoke-to-spoke and spoke-to-on-premises traffic through the hub firewall or gateway. When the hub hosts a VPN/ExpressRoute gateway, the spoke peering should also enable "Use remote gateways" so spoke traffic reaches on-premises through the hub without deploying its own gateway.

Why this answer

B is correct because VNet peering is required to establish connectivity between the spoke VNets and the hub VNet, enabling traffic to flow through the central Azure Firewall. Without peering, the spoke VNets would be isolated and unable to route traffic to the hub. C is correct because a route table with a default route (0.0.0.0/0) pointing to the firewall's private IP ensures that all outbound internet traffic from spoke subnets is forced through the firewall for inspection and control.

Exam trap

The trap here is that candidates often assume a NAT gateway or public IPs on VMs are needed for outbound internet, but the correct design forces all traffic through the firewall using UDRs and peering, not direct egress.

503
MCQhard

Your company plans to store sensitive customer data in Azure Blob Storage. The data must be encrypted at rest and in transit. Additionally, access must be audited and restricted based on user identity. Which configuration meets these requirements?

A.Use shared access signatures (SAS) for access control.
B.Use Azure RBAC for access and Azure Monitor logs for auditing.
C.Configure network firewalls and use private endpoints.
D.Enable customer-managed keys (CMK) and use SAS.
AnswerB

Azure RBAC, integrated with Microsoft Entra ID, precisely restricts access to Blob Storage based on user identity by assigning specific roles with defined permissions, directly addressing the requirement for identity-based access control. Concurrently, Azure Monitor logs provide comprehensive auditing by capturing detailed records of all management and data plane operations performed on the storage account, ensuring that access is fully auditable as stipulated.

Why this answer

Azure RBAC provides identity-based access control using Azure Active Directory, which meets the requirement to restrict access based on user identity. Azure Monitor logs (specifically the Azure Activity Log and Storage Analytics logs) capture all read/write operations for auditing. Encryption at rest is automatically provided by Azure Storage Service Encryption (SSE) using Microsoft-managed keys by default, and encryption in transit is enforced via HTTPS when accessing Blob Storage.

Together, these satisfy all stated requirements without additional configuration.

Exam trap

The trap here is that candidates often confuse SAS tokens with identity-based access control, thinking that a signed URI provides user-level restriction, when in fact SAS only delegates permissions to anyone holding the token, not to a specific user identity.

How to eliminate wrong answers

Option A is wrong because shared access signatures (SAS) provide time-limited, delegated access based on a token, not on user identity; SAS tokens do not support Azure AD-based authentication or RBAC, and auditing is limited to the SAS token itself, not the user. Option C is wrong because network firewalls and private endpoints control network-level access and eliminate public internet exposure, but they do not provide identity-based access control or auditing of user actions; they also do not inherently enforce encryption in transit beyond the network boundary. Option D is wrong because customer-managed keys (CMK) only control encryption at rest (via Azure Key Vault) and do not provide access control or auditing based on user identity; SAS tokens again lack identity-based restriction and auditing granularity.

504
MCQeasy

A company needs to connect its on-premises data center to Azure for hybrid workloads. The connection must be private, dedicated, and provide guaranteed bandwidth. Which Azure service should they use?

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

Azure ExpressRoute provides a dedicated, private logical connection between on-premises infrastructure and Azure through a co-location facility or independent cloud exchange, entirely bypassing the public internet. It supports enterprise-grade SLAs, committed bandwidth tiers, and lower, consistent latency, making it the correct choice for workloads requiring guaranteed network performance. ExpressRoute circuits are resilient (active/passive or active/active) and can carry multiple VLANs.

Why this answer

Azure ExpressRoute provides a private, dedicated connection from on-premises to Azure, bypassing the public internet. It offers guaranteed bandwidth, higher reliability, and lower latency compared to VPN-based solutions, making it ideal for hybrid workloads requiring consistent performance.

Exam trap

The trap here is that candidates often confuse Azure VPN Gateway's 'dedicated tunnel' concept with true dedicated bandwidth, overlooking that VPNs still traverse the public internet and cannot guarantee performance, while ExpressRoute provides a physically isolated connection with contractual bandwidth guarantees.

How to eliminate wrong answers

Option A is wrong because Azure VPN Gateway uses encrypted tunnels over the public internet, which cannot provide dedicated bandwidth or guaranteed performance. Option C is wrong because Azure Virtual WAN is a networking orchestration service that can aggregate VPN, ExpressRoute, and SD-WAN connections, but it does not itself provide a dedicated, private connection with guaranteed bandwidth. Option D is wrong because Azure Peering Service is designed to optimize connectivity to Microsoft cloud services over the internet via partner ISPs, not to provide a dedicated private link with guaranteed bandwidth.

505
MCQmedium

A company has two on-premises data centers and an Azure subscription. They need to connect each data center to Azure with a private, high-bandwidth, and reliable connection. They also want a low-cost backup connection for each data center in case the primary connection fails. Which combination of connectivity options should they recommend?

A.A
B.B
C.C
D.D
AnswerA

This is the correct design because each data center establishes its own dedicated ExpressRoute circuit as the primary path, ensuring predictable, high-bandwidth, and low-latency connectivity to Azure with an SLA-backed private link. The site-to-site VPN for each data center acts as an IPsec-based backup over the internet, providing a cost-effective failover path that automatically kicks in if the ExpressRoute circuit fails. This active/passive redundancy model is a best practice for hybrid networking, as it avoids a single point of failure while keeping operational costs reasonable.

Why this answer

Azure ExpressRoute provides a private, high-bandwidth, and reliable connection from on-premises data centers to Azure, bypassing the public internet. To meet the low-cost backup requirement, Azure VPN Gateway (Site-to-Site VPN) offers a secure, encrypted connection over the internet as a failover path, which is significantly cheaper than a second ExpressRoute circuit. This combination ensures primary connectivity via ExpressRoute and cost-effective redundancy via VPN.

Exam trap

The trap here is that candidates often assume two ExpressRoute circuits are needed for redundancy, overlooking the cost-effective VPN backup option that still meets the 'low-cost' requirement while providing private connectivity only for the primary link.

How to eliminate wrong answers

Option B is wrong because using two ExpressRoute circuits for primary and backup is not low-cost; it doubles the recurring expense and is unnecessary for a backup path. Option C is wrong because using two Site-to-Site VPN connections for both primary and backup does not provide the high-bandwidth, reliable, private connection required; VPNs are internet-based and subject to latency and bandwidth limitations. Option D is wrong because using a single ExpressRoute circuit without any backup fails the requirement for a backup connection in case of failure.

506
MCQmedium

A company deploys a web application on Azure virtual machines (VMs) across multiple availability zones. The application needs to automatically distribute incoming HTTPS traffic, offload SSL/TLS termination, and provide session persistence. Additionally, the solution must include a Web Application Firewall (WAF) to protect against common web vulnerabilities. Which Azure load balancing solution should they use?

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

Azure Application Gateway is a regional Layer 7 load balancer that routes HTTP/S traffic intelligently using URL paths, host headers, or other HTTP attributes, and it terminates SSL/TLS connections at the gateway to offload encryption from backend VMs. It provides cookie-based session affinity so a user's session sticks to the same server, and its built-in Web Application Firewall (WAF) blocks common exploits such as SQL injection and cross-site scripting. Autoscaling and availability-zone support make it a robust choice for production web workloads, delivering all the needed features in one regional service.

Why this answer

Azure Application Gateway is the correct choice because it is a Layer 7 load balancer that can route HTTPS traffic, offload SSL/TLS termination, and provide session persistence (cookie-based affinity). It also natively integrates a Web Application Firewall (WAF) to protect against common web vulnerabilities like SQL injection and cross-site scripting.

Exam trap

The trap here is that candidates often confuse Azure Front Door with Application Gateway because both offer WAF and SSL offload, but Front Door is optimized for global multi-region traffic management, not for intra-region zone-resilient load balancing with session persistence, which is the specific requirement in this question.

How to eliminate wrong answers

Option A is wrong because Azure Load Balancer operates at Layer 4 (TCP/UDP) and cannot perform SSL/TLS termination, session persistence based on application cookies, or provide a WAF. Option B is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that routes traffic at the DNS level (Layer 3/4) and does not handle SSL/TLS termination, session persistence, or WAF capabilities. Option D is wrong because Azure Front Door is a global Layer 7 load balancer and CDN that can offload SSL and provide WAF, but it is designed for global HTTP(S) traffic distribution across regions, not for intra-region multi-zone distribution with session persistence; Application Gateway is the appropriate choice for regional, zone-resilient deployments.

507
MCQmedium

Your company operates in a highly regulated industry and must retain all sign-in logs for 7 years. The logs must be immutable and cannot be modified or deleted by administrators. You need to design a monitoring solution that stores sign-in logs in a cost-effective manner while meeting compliance requirements. The solution should also allow for real-time analysis of sign-in activity. What should you include in the design?

A.Stream sign-in logs to Log Analytics for real-time analysis and simultaneously archive them to an Azure Storage account with immutable blob policy (WORM).
B.Stream sign-in logs to Azure Event Hubs and then to cold storage in Azure Blob with lifecycle management.
C.Stream sign-in logs to Log Analytics workspace with 7-year retention and use Azure Policy to restrict deletion.
D.Use Azure Data Explorer to store logs for 7 years and configure a purge policy to prevent deletion.
AnswerA

Streaming sign-in logs to Log Analytics enables near real-time querying and alerting for security operations, satisfying the need for fast analysis. Simultaneously archiving the same logs to an Azure Storage account with immutable blob policy (WORM) ensures that the archived copies are both write-once-read-many and tamper-proof for the mandatory retention period. This dual-destination pattern is explicitly supported by Azure diagnostic settings, making it the correct approach for regulated industries that require both investigative access and compliance-grade immutability.

Why this answer

It meets both compliance and real-time analysis requirements. Streaming sign-in logs to Log Analytics enables real-time monitoring and querying, while simultaneously archiving them to an Azure Storage account with an immutable blob policy (WORM) ensures the logs cannot be modified or deleted for the required 7-year retention period. This combination provides cost-effective long-term storage (Azure Blob is cheaper than Log Analytics for long-term retention) and satisfies regulatory immutability mandates.

Exam trap

The trap here is that candidates often assume Log Analytics retention alone suffices for compliance, but Log Analytics does not provide immutable storage, and Azure Policy cannot prevent data modification within the workspace; the correct approach requires separate immutable archival in Azure Storage.

How to eliminate wrong answers

Option B is wrong because Azure Event Hubs is a real-time ingestion service, but cold storage in Azure Blob with lifecycle management does not provide immutability; lifecycle management can delete blobs based on rules, which violates the requirement that logs cannot be modified or deleted by administrators. Option C is wrong because Log Analytics workspace retention of 7 years does not guarantee immutability; Azure Policy can restrict deletion of the workspace but cannot prevent data modification or deletion within the workspace itself, and Log Analytics does not natively support WORM (Write Once, Read Many) compliance. Option D is wrong because Azure Data Explorer (ADX) is designed for interactive analytics, not long-term immutable archival; a purge policy is used to delete data, not to prevent deletion, and ADX does not provide WORM capabilities required for regulatory compliance.

508
MCQmedium

Your organization is implementing a zero-trust security model. You need to ensure that all access to corporate resources from mobile devices is conditional based on device compliance, user risk, and location. Which Microsoft Entra ID feature should you use?

A.Identity Protection
B.Microsoft Intune
C.Conditional Access policies
D.Microsoft Defender XDR
AnswerC

Conditional Access is Azure AD's policy engine that evaluates real-time signals—including user/group membership, location, application, device compliance, and risk scores—to allow, deny, or require additional verification such as MFA or a compliant device. It natively integrates with Intune compliance status and Identity Protection risk assessments, making it the central enforcement point for zero-trust access control. By combining these signals into granular, context-aware policies, Conditional Access directly enforces the zero-trust principle of never trusting implicit access.

Why this answer

Conditional Access policies in Microsoft Entra ID are the correct choice because they allow you to enforce access controls based on conditions such as device compliance (via integration with Microsoft Intune), user risk (via integration with Identity Protection), and location (via IP ranges or named locations). This directly supports the zero-trust principle of 'never trust, always verify' by evaluating signals before granting access to corporate resources.

Exam trap

The trap here is that candidates often confuse Microsoft Intune (which manages device compliance) with the policy engine that enforces access decisions, failing to realize that Conditional Access is the orchestration layer that consumes compliance, risk, and location signals to enforce zero-trust access.

How to eliminate wrong answers

Option A is wrong because Identity Protection is a feature within Entra ID that detects and responds to identity-based risks (e.g., leaked credentials, anonymous IP addresses), but it does not itself enforce access decisions or combine multiple conditions like device compliance and location—it only provides risk signals that Conditional Access policies can consume. Option B is wrong because Microsoft Intune is a mobile device management (MDM) and mobile application management (MAM) service that manages device compliance policies (e.g., requiring encryption, PIN), but it does not evaluate user risk or location, nor does it enforce conditional access decisions at the authentication gateway—it only reports device compliance status to Entra ID. Option D is wrong because Microsoft Defender XDR is a unified security incident and response platform that correlates alerts across endpoints, email, and identities, but it does not enforce real-time access control policies based on device compliance, user risk, or location at the authentication layer—it focuses on threat detection and response, not conditional access enforcement.

509
MCQeasy

Your company has an Azure subscription with a single virtual network. You need to design a solution to back up Azure VMs to meet a 7-day retention policy. The backup data must be stored in a separate region for compliance. What should you use?

A.Azure Backup with cross-region restore (CRR) enabled
B.Azure Site Recovery with replication to a secondary region
C.Azure File Share snapshots stored in a different region
D.Azure Backup with default geo-redundant storage (GRS) in the same region
AnswerA

Azure Backup with cross-region restore (CRR) enabled is the correct choice because it explicitly copies backup snapshots and vault-tier recovery points to a paired secondary region. With CRR, you can restore a VM from the secondary region's copy even if the entire primary region is inaccessible, providing true geo-resiliency. This feature must be enabled during the Azure Recovery Services vault creation and works alongside GRS, granting independent read access to the replicated backup data in the paired region.

Why this answer

Azure Backup with cross-region restore (CRR) enabled is the correct solution because it allows you to store backup data in a secondary Azure paired region, meeting the compliance requirement for separate region storage. CRR works by replicating the backup data from the default geo-redundant storage (GRS) in the primary region to the paired region, and then enabling you to restore VMs in that secondary region. With a 7-day retention policy, CRR supports restoring from the recovery point within that window, ensuring compliance without additional infrastructure.

Exam trap

The trap here is that candidates often confuse Azure Backup's default GRS with cross-region restore, assuming that GRS alone allows restoring in the secondary region, but without CRR enabled, the secondary region copy is only for durability and cannot be used for restore operations.

How to eliminate wrong answers

Option B is wrong because Azure Site Recovery is a disaster recovery solution designed for replication and failover of VMs to a secondary region, not for backup with retention policies; it does not provide point-in-time restore capabilities for a 7-day retention window. Option C is wrong because Azure File Share snapshots are for file-level backup and are stored within the same region as the file share; they cannot be natively stored in a different region without manual copying, which violates the compliance requirement. Option D is wrong because default geo-redundant storage (GRS) in the same region stores backup data in the same primary region with replication to a secondary region only for durability, but cross-region restore (CRR) is not enabled by default; without CRR, you cannot restore VMs in the secondary region, failing the compliance requirement.

510
MCQmedium

A company uses Microsoft Entra ID. They want to block all access to corporate applications from devices that are not managed by their organization. They require that only devices enrolled in Microsoft Intune and compliant with company policies can access company resources. Which Microsoft Entra ID feature should they use?

A.Conditional Access policy requiring device compliance
B.Identity Protection with user risk policy
C.Privileged Identity Management (PIM)
D.Microsoft Entra ID Join process
AnswerA

Conditional Access is Microsoft Entra ID's policy engine that can evaluate device compliance status from Microsoft Intune at sign-in time. By targeting all users and cloud apps with a 'Require device to be marked as compliant' grant, the policy will block access for any device that is not enrolled and compliant with the organization's compliance policies. This directly satisfies the goal of blocking all access from non-compliant devices, and it can also be combined with session controls to continuously re-evaluate compliance.

Why this answer

Conditional Access policies in Microsoft Entra ID can enforce device compliance as a condition for granting access. By configuring a policy that requires devices to be marked as compliant in Microsoft Intune, only devices enrolled and meeting company policies can access corporate applications, effectively blocking unmanaged devices.

Exam trap

The trap here is that candidates may confuse Identity Protection's user risk policies with device-based controls, or assume that simply joining a device to Entra ID (Option D) is sufficient to enforce compliance, when in fact a Conditional Access policy is required to block non-compliant devices.

How to eliminate wrong answers

Option B is wrong because Identity Protection with user risk policy focuses on detecting and responding to risky user behavior (e.g., leaked credentials, anonymous IP addresses) rather than evaluating device management or compliance status. Option C is wrong because Privileged Identity Management (PIM) provides just-in-time privileged access and role activation controls, not device-level access restrictions. Option D is wrong because Microsoft Entra ID Join is a device identity registration process that enables devices to authenticate with Entra ID, but it does not by itself enforce compliance policies or block non-compliant devices; it must be combined with a Conditional Access policy to achieve the described requirement.

511
MCQmedium

You are designing a solution to store sensitive documents in Azure Blob Storage. The data must be encrypted at rest and access must be audited. You need to ensure that the encryption keys are managed by your organization and that access to the keys is logged. Which combination of Azure services should you use?

A.Azure Storage encryption with customer-managed keys in Azure Key Vault and Azure Monitor
B.Azure Disk Encryption with Azure Key Vault
C.Azure Storage encryption with Microsoft-managed keys and Azure Monitor
D.Azure Information Protection and Azure Sentinel
AnswerA

Azure Storage encryption always encrypts data at rest, but with customer-managed keys (CMK) in Azure Key Vault, you control key rotation, permissions, and lifecycle, which is essential for sensitive documents. Enabling Key Vault diagnostics and routing those logs to Azure Monitor provides auditable access trails, letting you detect unauthorized key usage. This combination meets compliance requirements that demand both cryptographic control and monitoring.

Why this answer

Azure Storage encryption with customer-managed keys in Azure Key Vault meets the requirement for organization-managed encryption keys, while Azure Monitor (specifically the Azure Activity Log or diagnostic settings) captures access logs for both the storage account and Key Vault operations, enabling full auditability of key usage and data access.

Exam trap

The trap here is that candidates often confuse Azure Disk Encryption (which encrypts VM disks) with Azure Storage encryption (which encrypts blob data), leading them to select Option B despite it not addressing blob storage encryption or audit logging requirements.

How to eliminate wrong answers

Option B is wrong because Azure Disk Encryption encrypts VM disks, not Azure Blob Storage data, and does not provide the required storage-level encryption or audit logging for blob access. Option C is wrong because Microsoft-managed keys do not allow your organization to manage the encryption keys, violating the requirement for organization-managed keys. Option D is wrong because Azure Information Protection is a classification and labeling service, not a storage encryption solution, and Azure Sentinel is a SIEM that ingests logs but does not itself provide encryption key management or storage encryption.

512
MCQeasy

A company runs a critical application on Azure virtual machines (VMs) in the West US region. They need a disaster recovery solution that replicates the VMs to East US with a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 2 hours. The application consists of multiple VMs, and the company needs to be able to fail over a single VM without impacting others during an actual disaster. They also want to periodically test the recovery process without affecting the production environment. Which Azure Site Recovery feature should they use to enable non-disruptive testing?

A.Recovery Plans
B.Planned failover
C.Test failover
D.Network mapping
AnswerC

Test failover performs a full validation of replicated VM images by booting them in an isolated virtual network using a selectable recovery point, without disturbing ongoing replication or production traffic. It requires no source VM shutdown and can be run repeatedly for compliance and disaster-recovery drills. This isolated copy allows you to verify application startup and network dependencies exactly as they would behave in a real failover, making it the correct feature for non-disruptive testing.

Why this answer

Test failover (Option C) is the correct feature because it allows you to validate your disaster recovery process by creating an isolated copy of your replicated VMs in a separate test network, without impacting the ongoing replication or the production environment. This directly meets the requirement for periodic, non-disruptive testing while maintaining the RPO of 15 minutes and RTO of 2 hours.

Exam trap

The trap here is that candidates often confuse 'Test failover' with 'Planned failover' or 'Recovery Plans,' mistakenly thinking that any failover action must impact production, when in fact Test failover is specifically designed to be isolated and non-disruptive.

How to eliminate wrong answers

Option A is wrong because Recovery Plans are used to orchestrate the failover sequence of multiple VMs and run custom scripts, but they do not provide a mechanism for non-disruptive testing; they are executed during actual failover or test failover, not as a testing feature themselves. Option B is wrong because Planned failover is designed for zero-data-loss migration or maintenance scenarios where both sites are healthy and no data loss is tolerated, but it requires stopping production VMs and is not a testing mechanism—it disrupts production. Option D is wrong because Network mapping defines how source and target networks correspond for failover, but it is a configuration prerequisite, not a feature for executing a non-disruptive test.

513
MCQhard

You are designing a monitoring solution for a hybrid environment with on-premises servers and Azure VMs. You need to collect performance data from all servers and visualize it in a single dashboard. Which Azure service should you use?

A.Azure Service Health
B.Azure Workbooks
C.Azure Arc
D.Azure Monitor
AnswerD

Azure Monitor is the comprehensive monitoring platform that collects metrics, logs, and dependency data from cloud and hybrid sources. Agents such as the Azure Monitor Agent can be deployed to on-premises VMs via Azure Arc, sending data to a Log Analytics workspace for querying and visualization. It also supports custom dashboards, Workbooks, alert rules, and integration with Service Health, making it the appropriate core service for the hybrid monitoring solution in question.

Why this answer

Azure Monitor is the correct service because it provides a unified platform for collecting, analyzing, and visualizing performance data from both on-premises servers and Azure VMs. By deploying the Azure Monitor agent on all servers, you can send metrics and logs to a single Log Analytics workspace and then use Azure Workbooks or Metrics Explorer to create a consolidated dashboard.

Exam trap

The trap here is that candidates often confuse Azure Workbooks (a visualization tool) with a monitoring solution, forgetting that Workbooks are just a presentation layer and require a data source like Azure Monitor to function.

How to eliminate wrong answers

Option A is wrong because Azure Service Health is a service that provides personalized alerts and guidance for Azure service issues and planned maintenance, not for collecting or visualizing server performance data. Option B is wrong because Azure Workbooks is a visualization tool that can create rich dashboards, but it is not a data collection service; it relies on data already in Azure Monitor (e.g., Log Analytics or Metrics). Option C is wrong because Azure Arc extends Azure management and governance to on-premises and multi-cloud resources, but it does not itself collect performance data or provide a dashboard; it can enable Azure Monitor agents on those servers, but the monitoring and visualization are still done by Azure Monitor.

514
MCQmedium

A company runs a file server on Azure VMs using Windows Server. The server stores business-critical documents. You need to design a backup strategy that meets a recovery point objective (RPO) of 1 hour and recovery time objective (RTO) of 4 hours. The solution must be cost-effective. Which backup solution should you use?

A.Azure Site Recovery
B.Azure Backup for Azure Blobs
C.Azure Backup for Azure VMs
D.Azure File Sync
AnswerC

Azure Backup for Azure VMs is the correct choice because it provides true backup functionality at the VM level, with policy-based scheduling (e.g., once or twice daily) and customizable retention for long-term archival. It leverages the Volume Shadow Copy Service (VSS) for Windows VMs to produce application-consistent snapshots, and also takes crash-consistent snapshots, enabling reliable restore of the entire VM or individual files. This directly covers the file server's data and system state, meeting the requirement for backup with a recovery point objective.

Why this answer

Azure Backup for Azure VMs provides application-consistent backups for Windows Server VMs, supporting RPOs as low as 1 hour with frequent backup policies and RTOs within 4 hours by restoring to a new VM or using instant restore. It is cost-effective because it uses incremental backups and only charges for storage consumed, without the replication overhead of Site Recovery.

Exam trap

The trap here is that candidates confuse Azure Site Recovery (a replication/DR tool) with Azure Backup (a backup tool), leading them to choose Site Recovery for a simple backup requirement, which is cost-prohibitive and not designed for point-in-time recovery with hourly RPOs.

How to eliminate wrong answers

Option A is wrong because Azure Site Recovery is a disaster recovery solution designed for replication and failover with RPOs of seconds to minutes and RTOs of minutes, which is overkill and more expensive for a backup-only requirement. Option B is wrong because Azure Backup for Azure Blobs is designed for protecting blob data (e.g., block blobs, append blobs) and cannot back up a Windows Server VM running a file server. Option D is wrong because Azure File Sync is a synchronization tool that keeps on-premises file servers in sync with Azure file shares, not a backup solution; it does not provide point-in-time recovery or meet RPO/RTO requirements.

515
MCQmedium

A company deploys a web application on Azure VMs. The application stores session state and frequently accessed product data. They need a low-latency, in-memory cache to reduce database load and improve response times. The cache must be managed and support data persistence with replication across availability zones within the region. Which Azure service and tier should they choose?

A.Azure Cache for Redis (Premium tier)
B.Azure Cache for Redis (Basic tier)
C.Azure Cache for Redis (Standard tier)
D.Azure Cache for Redis (Enterprise tier)
AnswerA

Azure Cache for Redis Premium tier is the appropriate choice because it uniquely combines zone-redundant replication—spreading the primary and replica nodes across Azure availability zones—with built-in data persistence options (RDB snapshots and AOF append-only file). This gives you both high availability and durability of cached data, enabling you to survive an entire zone failure without losing data. Being fully managed, it also supports Redis clustering for scaling out beyond the memory limit of a single node, which is why it meets the production requirements.

Why this answer

Azure Cache for Redis Premium tier is the correct choice because it supports data persistence (RDB/AOF), replication across availability zones via zone redundancy, and provides low-latency, in-memory caching for session state and product data. The Basic tier lacks replication and persistence, Standard tier offers replication but not zone redundancy or persistence, and Enterprise tier is overkill for this scenario, adding unnecessary cost and complexity.

Exam trap

The trap here is that candidates often confuse the Standard tier's replication (which is within a single datacenter) with zone redundancy, or assume Enterprise tier is always better for persistence, when Premium tier specifically offers both persistence and zone redundancy at a lower cost.

How to eliminate wrong answers

Option B (Basic tier) is wrong because it provides no replication, no data persistence, and no SLA, making it unsuitable for high-availability or durable caching needs. Option C (Standard tier) is wrong because while it offers replication within a single datacenter, it does not support zone redundancy across availability zones or built-in data persistence (RDB/AOF). Option D (Enterprise tier) is wrong because it is designed for advanced scenarios like active geo-replication and Redis modules (RediSearch, RedisBloom), which are not required here, and it incurs higher cost without providing additional benefit for basic session state and product caching.

516
MCQeasy

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to allow external business partners to request access to a specific application. The access must be time-limited and require approval from the partner's manager. Additionally, access must automatically expire after the defined period. Which Microsoft Entra ID feature should they use?

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

Microsoft Entra ID Entitlement Management is the correct solution because it is a feature of Microsoft Entra ID Identity Governance that lets administrators create access packages, which are bundles of resources such as groups, applications, and SharePoint sites. These access packages can be made available to external users via connected organizations, with customizable request policies that enforce approval workflows and define assignment duration—including automatic expiration and removal of access when the assignment ends. This directly matches the need to grant controlled, time-limited access to applications for external identities, while also supporting recurring access reviews as a complementary control.

Why this answer

Microsoft Entra ID Entitlement Management enables organizations to manage access for external business partners through access packages. These packages can enforce time-limited access, require manager approval, and automatically expire access after a defined period, directly meeting all the stated requirements.

Exam trap

The trap here is that candidates often confuse Entitlement Management with PIM because both involve time-limited access, but PIM is strictly for privileged roles within the organization, not for external partner application access with manager approval.

How to eliminate wrong answers

Option A is wrong because Privileged Identity Management (PIM) is designed for just-in-time privileged role activation and oversight, not for granting time-limited access to applications for external partners. Option C is wrong because Identity Protection focuses on detecting and responding to identity-based risks, such as compromised credentials or suspicious sign-ins, not on managing access requests or approvals. Option D is wrong because Access Reviews are used to periodically audit and confirm existing access assignments, not to handle initial access requests with manager approval and automatic expiration.

517
Multi-Selecthard

You are designing a backup and disaster recovery strategy for a SQL Server database hosted on an Azure virtual machine. The database is critical and has a recovery point objective (RPO) of 15 minutes and a recovery time objective (RTO) of 4 hours. Which TWO services should you include in the solution?

Select 2 answers
A.Azure Backup
B.Azure SQL Database backup
C.Azure Files
D.Azure Site Recovery
E.Azure SQL Database auto-failover groups
AnswersA, D

Azure Backup satisfies the 15-minute RPO by capturing SQL Server transaction log backups every 15 minutes through the workload-aware backup extension, and restores within the 4-hour RTO. It provides the granular, point-in-time recovery the database demands.

Why this answer

Azure Backup (A) is correct because it provides application-consistent, agent-based backups of SQL Server running on an Azure VM, supporting frequent log backups that can meet a 15-minute RPO and enabling restore within the 4-hour RTO. Azure Site Recovery (D) is correct because it replicates the entire VM (including the SQL Server instance and OS) to a secondary region or target, enabling orchestrated failover and recovery of the virtual machine within the RTO window. Azure SQL Database backup (B) does not apply because the database is hosted on an Azure VM (IaaS), not as an Azure SQL Database (PaaS) service.

Azure Files (C) is a managed SMB/NFS file share service and is not a backup or disaster recovery mechanism for a SQL Server VM. Azure SQL Database auto-failover groups (E) are also a PaaS feature for Azure SQL Database/Managed Instance and cannot be used for SQL Server on an Azure VM.

Exam trap

The trap here is confusing PaaS services (Azure SQL Database backup and auto-failover groups) with IaaS solutions for SQL Server on Azure VMs, leading candidates to select options that are incompatible with the stated hosting model.

518
MCQmedium

Your company has a Microsoft Entra ID tenant with 10,000 users. You are designing an identity governance solution to automate user access reviews for critical applications. The compliance team requires that access reviews be conducted quarterly and that any reviewer who does not respond within 7 days have their decisions auto-approved. You need to implement the solution using Microsoft Entra ID Governance. What should you do?

A.Use Microsoft Entra Privileged Identity Management (PIM) to require activation for access to critical applications.
B.Create an access review with 'Auto deny' after 7 days of no response.
C.Create a recurring campaign in Microsoft Purview Compliance Manager.
D.Create an access review with 'Auto approve' after 7 days of no response.
AnswerD

Configuring an access review with the auto-approve fallback directly aligns with the business rule: the review is created in Microsoft Entra ID, managers are assigned as reviewers, and a recurrence schedule is set. When the 7-day response window lapses, the system automatically applies an 'approve' decision for each pending access, preserving user access. This ensures that access is recertified periodically without being disrupted by manager delays, satisfying the requirement precisely.

Why this answer

The compliance team explicitly requires that unreviewed decisions be auto-approved after 7 days. In Microsoft Entra ID Governance, an access review can be configured with 'Auto approve' to automatically approve any reviewer decisions that are not submitted within the specified duration. This directly satisfies the requirement for quarterly reviews with a 7-day auto-approval policy.

Exam trap

The trap here is confusing 'Auto approve' with 'Auto deny' — candidates often assume that non-response should result in denial for security, but the question explicitly states the compliance team requires auto-approval, so the answer must match the stated requirement.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra Privileged Identity Management (PIM) is designed for just-in-time privileged role activation, not for recurring user access reviews of critical applications. Option B is wrong because 'Auto deny' would automatically deny access after 7 days of no response, which contradicts the compliance team's requirement for auto-approval. Option C is wrong because Microsoft Purview Compliance Manager is a compliance management solution for assessments and controls, not for automating user access reviews.

519
MCQhard

An organization is designing a storage solution for Azure VMs running a database that requires low latency and high IOPS. The data is critical and must be durable with automatic replication across multiple datacenters in the same region. Which Azure managed disk type and redundancy option should they choose?

A.Standard SSD with GRS
B.Premium SSD with ZRS
C.Ultra Disk with LRS
D.Premium SSD v2 with LRS
AnswerB

Premium SSDs provide high IOPS (up to 20,000 per disk, depending on size) and low single-digit millisecond latencies, ideal for I/O-intensive workloads. With ZRS, the disk synchronously writes three replicas across three Azure availability zones within the same region, so the VM can survive an entire datacenter or zone failure while retaining the performance characteristics needed. This combination is directly supported for managed disks and precisely satisfies the stated requirement for high performance and replication across multiple datacenters.

Why this answer

Premium SSD with ZRS is correct because the database requires low latency and high IOPS, which Premium SSD provides, and ZRS (Zone-Redundant Storage) automatically replicates data synchronously across three Azure availability zones within the same region, ensuring durability and high availability without the cross-region latency of GRS.

Exam trap

The trap here is that candidates often confuse ZRS with GRS, assuming that 'redundancy across multiple datacenters' requires geo-replication, but ZRS provides intra-region zone redundancy without the latency penalty of asynchronous geo-replication.

How to eliminate wrong answers

Option A is wrong because Standard SSD does not deliver the low latency and high IOPS required for a database workload, and GRS (Geo-Redundant Storage) replicates data asynchronously to a paired region, not within the same region, adding latency and complexity. Option C is wrong because Ultra Disk offers extreme performance but only supports LRS (Locally Redundant Storage), which replicates data within a single datacenter and does not provide automatic replication across multiple datacenters in the same region. Option D is wrong because Premium SSD v2, while offering high performance, also only supports LRS, lacking the cross-zone replication needed for durability across multiple datacenters within the same region.

520
MCQeasy

A company needs to store and analyze petabytes of IoT telemetry data. The data is append-only and rarely updated. They require SQL-based querying and columnar storage for fast analytics. Which Azure storage solution should you choose?

A.Azure Cosmos DB with analytical store
B.Azure SQL Database with columnstore indexes
C.Azure Blob Storage with Azure Cognitive Search
D.Azure Data Lake Storage Gen2 with Azure Synapse SQL pool
AnswerD

Azure Data Lake Storage Gen2 is the correct storage foundation because it blends the object storage scalability of Blob Storage with a hierarchical namespace, POSIX permissions, and built-in support for storing data in open formats like Parquet—making it ideal for petabyte- and exabyte-scale IoT telemetry ingestion. Azure Synapse SQL pool (dedicated or serverless) provides a distributed, massively parallel processing (MPP) engine that executes T-SQL directly over the files in ADLS Gen2, enabling schema-on-read analytics without moving and re-loading data. This architecture natively handles append-only telemetry streams, accelerates queries via partition elimination and columnar storage, and separates storage from compute to independently scale ingestion throughput and query concurrency.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) provides hierarchical namespace and petabyte-scale storage optimized for big data analytics. When combined with Azure Synapse SQL pool (formerly SQL DW), it enables SQL-based querying over columnar storage (using PolyBase or CETAS) for fast analytics on append-only IoT telemetry data. This combination supports massive data volumes, append-only workloads, and columnar storage for high-performance analytical queries.

Exam trap

The trap here is that candidates often choose Azure SQL Database with columnstore indexes (Option B) because they focus on the 'SQL-based querying and columnar storage' requirement without considering the petabyte-scale constraint, which exceeds Azure SQL Database's maximum storage capacity.

How to eliminate wrong answers

Option A is wrong because Azure Cosmos DB with analytical store is designed for globally distributed, multi-model NoSQL data with automatic indexing, not for petabyte-scale append-only IoT telemetry requiring SQL-based columnar analytics; its analytical store uses Azure Synapse Link but is optimized for operational data, not bulk append-only streams. Option B is wrong because Azure SQL Database with columnstore indexes is a relational OLTP database with a maximum size of 4 TB (or 128 TB with Hyperscale), which cannot handle petabytes of data, and columnstore indexes are best for read-mostly workloads but the service lacks the distributed scale-out architecture needed for petabyte-scale analytics. Option C is wrong because Azure Blob Storage with Azure Cognitive Search provides object storage and full-text search capabilities, not SQL-based querying or columnar storage; Cognitive Search is for indexing and searching unstructured text, not for analytical queries on structured IoT data.

521
MCQmedium

A company wants 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 require multi-factor authentication (MFA) or block the sign-in in real time. Additionally, they need a dashboard that shows risk events and allows generating weekly risk reports. 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
D.Microsoft Entra ID Identity Governance
AnswerA

Microsoft Entra ID Identity Protection is the dedicated detection engine that evaluates each sign-in against a set of risk signals, including the anonymous IP address signal, which flags sign-ins originating from Tor, virtual private networks (VPNs), and other IP-anonymizing services. It applies machine-learning models and heuristics to produce a risk score (Low/Medium/High) and generates a risky sign-in report, which can then trigger automated remediation such as requiring multifactor authentication (MFA) or blocking the sign-in. This is the component responsible for the underlying detection, not Conditional Access.

Why this answer

Microsoft Entra ID Identity Protection is the correct feature because it specifically detects sign-in risks such as anonymous IP addresses and unfamiliar locations, and it can automatically enforce conditional access policies like requiring MFA or blocking sign-ins in real time. It also provides a dashboard for risk events and supports generating weekly risk reports, directly matching all stated requirements.

Exam trap

The trap here is that candidates often confuse Conditional Access as the detection mechanism, but it is only the enforcement layer; Identity Protection is the service that actually detects the risks and provides the risk signals that Conditional Access uses.

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) manages just-in-time privileged role assignments and access reviews, not risk detection or sign-in anomaly monitoring. Option D is wrong because Identity Governance focuses on access lifecycle management, entitlement reviews, and compliance, not real-time risk detection or MFA enforcement during sign-in.

522
MCQmedium

You are designing a backup and disaster recovery strategy for an Azure SQL Database instance that runs a critical business application. The database is 500 GB and experiences high transaction rates. The recovery point objective (RPO) is 1 minute and recovery time objective (RTO) is 1 hour. What should you recommend?

A.Enable geo-redundant backup storage and use geo-restore in the secondary region.
B.Configure automated backups with locally-redundant storage (LRS) and enable point-in-time restore.
C.Configure active geo-replication to a secondary region in the same Azure geography.
D.Export the database to a bacpac file daily and store it in Azure Blob Storage.
AnswerC

Active geo-replication continuously replicates transactions from a primary database to one or more readable secondary databases in a paired or chosen secondary region, achieving an RPO of typically 5 seconds and an RTO of under 1 minute when paired with automatic failover groups. Because the secondary is always online and kept nearly synchronized, a failover merely changes the role and does not require copying or restoring data. This is the only option that satisfies both the aggressive 1-minute RPO and the minutes-level RTO while also providing cross-region redundancy.

Why this answer

Active geo-replication for Azure SQL Database provides a continuously synchronized readable secondary replica in a different Azure region, enabling failover with an RPO of 1 minute (due to synchronous replication) and an RTO of 1 hour (since failover is manual or can be automated). This meets the critical business application's requirements for high transaction rates and low data loss.

Exam trap

The trap here is that candidates often confuse geo-redundant backup storage (which provides backup redundancy but not real-time replication) with active geo-replication (which provides near-real-time data synchronization for DR), leading them to choose Option A despite its insufficient RPO.

How to eliminate wrong answers

Option A is wrong because geo-redundant backup storage (RA-GRS) only protects against regional disasters by restoring from the last full/differential/log backup, which can have an RPO of up to 12 hours for log backups, far exceeding the 1-minute requirement. Option B is wrong because locally-redundant storage (LRS) for automated backups does not provide any cross-region disaster recovery, so a regional outage would result in complete data loss. Option D is wrong because exporting to a bacpac file daily provides an RPO of up to 24 hours, which is far too high, and the export process can be slow and disruptive for a 500 GB database with high transaction rates.

523
MCQhard

A company runs a large-scale write-intensive application that requires a horizontally scalable relational database. They need to distribute data across multiple nodes to handle high write throughput while supporting SQL queries, including joins and transactions. The solution must be fully managed and provide elastic scaling. Which Azure database service should they choose?

A.Azure SQL Database Hyperscale
B.Azure Cosmos DB
C.Azure Database for PostgreSQL Hyperscale (Citus)
D.Azure SQL Managed Instance
AnswerC

Azure Database for PostgreSQL Hyperscale (Citus) is a managed relational database that horizontally shards tables across worker nodes by choosing a distribution column. Writes are distributed to multiple workers in parallel, so write throughput can scale out as worker nodes are added. It preserves full PostgreSQL SQL semantics, including distributed joins, foreign keys, and ACID transactions, making it the only option that combines relational integrity with horizontal write scaling.

Why this answer

Azure Database for PostgreSQL Hyperscale (Citus) is the correct choice because it provides horizontal scaling (sharding) across multiple worker nodes using the Citus extension, which distributes data and parallelizes SQL queries. It supports full SQL, including joins and transactions, while offering elastic scaling for write-intensive workloads. This makes it ideal for large-scale relational databases that need high write throughput and horizontal scalability.

Exam trap

The trap here is that candidates often confuse 'horizontal scaling' with 'hyperscale' or 'managed instance' options, assuming any 'scalable' database service supports distributed writes, but only Citus provides true horizontal sharding for relational workloads with full SQL and transaction support.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database Hyperscale is designed for read-intensive workloads with fast scaling of compute and storage, but it does not distribute data across multiple nodes for horizontal write scaling; it uses a single primary node with page servers for storage. Option B is wrong because Azure Cosmos DB is a NoSQL database that does not support full relational SQL features like joins and transactions across multiple documents in the same way a relational database does; it is schema-agnostic and not a relational database. Option D is wrong because Azure SQL Managed Instance is a fully managed instance of SQL Server that provides vertical scaling but not horizontal scaling across multiple nodes; it is limited to a single instance and does not distribute data across nodes for high write throughput.

524
MCQmedium

You are reviewing a PowerShell script for Azure SQL Database. The exhibit shows the script that sets backup retention. What is the effect of running this script?

A.It sets the short-term backup retention to 7 days, enabling point-in-time restore within that period.
B.It enables geo-redundant backups for the database.
C.It sets the long-term retention (LTR) backup policy to 7 days.
D.It increases the backup retention from 7 to 35 days.
AnswerA

This is the correct interpretation: the cmdlet being reviewed is Set-AzSqlDatabaseBackupShortTermRetentionPolicy (or equivalent), which explicitly configures the short-term backup retention policy for an Azure SQL database. Setting the property to 7 days means automated backups (full, differential, and transactional log backups) are retained for 7 days, and point-in-time restore (PITR) can be performed to any point within that window. The default is 7 days, so this is a direct, deliberate setting of the PITR window. The parameter range for short-term retention is 1–35 days, and 7 is within that range.

Why this answer

The script uses the `Set-AzSqlDatabaseBackupShortTermRetentionPolicy` cmdlet with `-RetentionDays 7`, which configures the short-term backup retention period for point-in-time restore (PITR) to 7 days. This allows restoring the database to any point within the last 7 days, as automated backups are retained for that duration.

Exam trap

The trap here is confusing short-term retention (PITR) with long-term retention (LTR) or geo-redundancy, as candidates may misread the cmdlet name or assume any retention setting applies to all backup types.

How to eliminate wrong answers

Option B is wrong because geo-redundant backups are enabled via the `-BackupStorageRedundancy` parameter (e.g., `Geo`) in the database creation or update cmdlet, not through the short-term retention policy cmdlet. Option C is wrong because long-term retention (LTR) backup policy is configured using the `Set-AzSqlDatabaseBackupLongTermRetentionPolicy` cmdlet, not the short-term retention cmdlet shown. Option D is wrong because the script sets retention to 7 days, not increases it from 7 to 35 days; the value 7 is the target retention, not a delta.

525
MCQmedium

A company has multiple Azure virtual networks (VNets) in different regions connected via VNet peering. They also have an on-premises data center connected to Azure via ExpressRoute. They need to provide internet-bound traffic from all Azure VNets through a single, centralized network virtual appliance (NVA) in the hub VNet for security inspection. They also need to ensure that traffic between VNets and on-premises is routed optimally without going through the internet. Which Azure solution should they implement?

A.Implement VNet peering with user-defined routes (UDRs) to force traffic through the NVA
B.Use Azure Firewall in each VNet to inspect traffic locally
C.Deploy an Azure Virtual WAN with a secured hub (Azure Firewall) and route traffic through it
D.Use Azure Route Server to propagate routes to all VNets
AnswerC

Azure Virtual WAN with a secured hub (Azure Firewall) is the correct choice because it provides automatic transitive routing between all connected VNets across regions, so you don't need to manage UDRs or individual peerings. The Azure Firewall in the secured hub centrally inspects all traffic—both VNet-to-VNet and branch-to-VNet—and routing intent can be configured to ensure that traffic is always forced through the firewall for inspection. This architecture scales naturally to many VNets and regions, integrates with ExpressRoute for hybrid connectivity, and centralizes security policy management, satisfying every stated requirement.

Why this answer

Azure Virtual WAN with a secured hub (Azure Firewall) provides a centralized, managed routing architecture that meets all requirements. It automatically routes internet-bound traffic from all VNets through the Azure Firewall in the hub for security inspection, while also ensuring optimal routing between VNets and on-premises via ExpressRoute without traversing the internet. This solution eliminates the need for manual UDRs and complex NVA management, as Virtual WAN handles routing and security centrally.

Exam trap

The trap here is that candidates often confuse Azure Virtual WAN with simple VNet peering or assume that Azure Route Server alone can provide centralized security inspection, but Virtual WAN is the only solution that combines centralized routing, security, and automatic propagation across multiple regions.

How to eliminate wrong answers

Option A is wrong because VNet peering with UDRs to force traffic through an NVA requires complex manual route management and does not scale well across multiple regions; it also does not inherently optimize on-premises routing without additional configuration. Option B is wrong because deploying Azure Firewall in each VNet inspects traffic locally, not centrally, which violates the requirement for a single, centralized inspection point and increases operational overhead. Option D is wrong because Azure Route Server propagates routes between NVAs and VNets but does not provide centralized internet-bound traffic inspection or force traffic through a single NVA; it is designed for dynamic route exchange, not security inspection.

Page 6

Page 7 of 11

Page 8

All pages