Courseiva

Microsoft Azure Solutions Architect Expert AZ-305 (AZ-305) — Questions 301–375

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

Page 4

Page 5 of 11

Page 6
301
MCQmedium

Your organization uses Microsoft Entra ID. You need to allow external users to sign in using their own identity providers (e.g., Google, Facebook) to access a custom application. What should you configure?

A.Microsoft Entra Connect
B.Microsoft Entra External ID
C.Microsoft Entra B2B collaboration
D.Microsoft Entra ID (tenant)
AnswerB

Microsoft Entra External ID, formerly Azure AD B2C, is a customer identity and access management (CIAM) service specifically built to handle external user authentication. It natively integrates with social identity providers like Google, Facebook, Apple, and Microsoft accounts via OIDC/OAuth2 protocols, and offers configurable user flows for registration, sign-in, and profile management. This makes it the correct solution when the requirement is to allow external identities to authenticate through social IdPs.

Why this answer

Microsoft Entra External ID (formerly Azure AD External Identities) is the correct solution because it is specifically designed to allow external users to authenticate using their own social identity providers (e.g., Google, Facebook) via OAuth 2.0 and OpenID Connect protocols. This configuration enables a custom application to accept sign-ins from these external identities without requiring them to have a Microsoft Entra ID account, using a dedicated external tenant or identity experience.

Exam trap

The trap here is that candidates often confuse Microsoft Entra B2B collaboration (which is for business-to-business guest access using work/school accounts) with Microsoft Entra External ID (which is for consumer-facing social identity providers), leading them to incorrectly select B2B collaboration.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra Connect is used for hybrid identity synchronization between on-premises Active Directory and Microsoft Entra ID, not for enabling external social identity providers. Option C is wrong because Microsoft Entra B2B collaboration allows external users to access your organization's resources using their own work or school accounts (e.g., another Microsoft Entra tenant), but it does not natively support social identity providers like Google or Facebook for custom applications. Option D is wrong because a standard Microsoft Entra ID (tenant) alone does not provide the built-in identity provider federation for social logins; it requires the External ID configuration to add those social identity providers.

302
Multi-Selecthard

A multinational corporation is designing a hybrid identity solution using Microsoft Entra ID. The company has multiple on-premises Active Directory forests with complex trust relationships. They require that users can authenticate to both cloud and on-premises resources using the same credentials, and they want to minimize changes to the existing infrastructure. Which THREE components should be part of the solution? (Choose three.)

Select 3 answers
A.Microsoft Entra Connect Sync
B.Password hash synchronization
C.Microsoft Entra Connect Health
D.Active Directory Federation Services (AD FS)
E.Microsoft Entra Domain Services
AnswersA, B, D

Microsoft Entra Connect Sync is the foundational synchronization engine that replicates object metadata and credential hashes from on-premises Active Directory forests into Microsoft Entra ID, creating a unified identity for each user across both environments. It uses a rule-based sync engine to handle multiple on-premises forests, merging them into a single Entra tenant and resolving conflicts with a deterministic source anchor. Without this component, neither Password Hash Synchronization nor federation (AD FS) can function, because the user objects must first be provisioned in Entra ID. It is the core service that makes hybrid identity possible.

Why this answer

Microsoft Entra Connect Sync is correct because it synchronizes user identities from multiple on-premises Active Directory forests to Microsoft Entra ID, enabling single sign-on and unified credential usage across cloud and on-premises resources. It supports complex forest trust relationships by using the source anchor and UPN mapping to ensure each user has a unique identity in the cloud without requiring changes to the existing on-premises infrastructure.

Exam trap

The trap here is that candidates often select Microsoft Entra Domain Services (option E) thinking it provides hybrid identity synchronization, but it actually creates a standalone managed domain in Azure that does not sync credentials from on-premises AD forests and cannot handle complex trust relationships.

303
Multi-Selecthard

Which THREE of the following are valid methods to securely transfer data to Azure Blob Storage? (Select three.)

Select 3 answers
A.Azure Data Box
B.Azure File Sync
C.AzCopy
D.Azure Migrate
E.Azure Import/Export service
AnswersA, C, E

Azure Data Box is a physical, ruggedized storage appliance supplied by Microsoft to accelerate offline transfers of large volumes of data to Azure Blob Storage. You order the device through the portal, copy data to its local SMB/NFS shares, ship it back, and Microsoft uploads the contents to blob storage. The device encrypts data at rest with BitLocker and is irreversibly erased after upload, making it ideal when network transfer would take days or weeks.

Why this answer

Azure Data Box is a physical data transfer solution that allows you to securely transfer large volumes of data to Azure Blob Storage when network transfer is impractical. It uses AES-256 encryption for data at rest and TLS for data in transit, and after the device is shipped back, data is automatically uploaded to your designated storage account.

Exam trap

The trap here is that candidates often confuse Azure File Sync with a general-purpose data transfer tool, but it is strictly for file shares (SMB) and cannot target Blob Storage, while Azure Migrate is mistaken for a data transfer service when it is actually a migration orchestration tool for servers and applications.

304
Multi-Selectmedium

Which TWO Azure networking services provide DDoS protection at the application layer (Layer 7)?

Select 2 answers
A.Azure Front Door Premium with WAF
B.Azure Firewall
C.Azure DDoS Protection Standard
D.Azure Web Application Firewall on Azure Application Gateway
E.Azure Bastion
AnswersA, D

Azure Front Door Premium includes an integrated web application firewall (WAF) that provides Layer 7 DDoS protection by inspecting HTTP/S traffic at Microsoft's global edge. Its distributed anycast architecture absorbs and mitigates application floods close to the source, preventing malicious requests from overwhelming backend origins, which is why this is a correct choice.

Why this answer

Azure Front Door Premium includes a web application firewall (WAF) that operates at Layer 7, inspecting HTTP/HTTPS traffic for application-layer attacks such as SQL injection and cross-site scripting. This integration provides both global load balancing and application-layer DDoS protection, making it a correct answer for Layer 7 DDoS defense.

Exam trap

The trap here is that candidates often confuse Azure DDoS Protection Standard (Layer 3/4) with application-layer protection, or assume Azure Firewall provides Layer 7 inspection, when in fact only WAF-enabled services like Front Door Premium and Application Gateway offer Layer 7 DDoS defense.

305
Multi-Selectmedium

Your organization needs to ensure that all Azure resources are compliant with corporate security policies. You need to design a solution that can enforce policies at scale, audit compliance, and automatically remediate non-compliant resources. Which THREE Azure services should you include?

Select 2 answers
A.Azure Policy
B.Azure Monitor
C.Azure Automation
D.Azure RBAC
E.Azure Blueprints
AnswersA, C

Azure Policy enforces corporate security standards at scale by evaluating resource properties against built-in or custom definitions, denying non-compliant deployments and auditing existing estate state. Its remediation tasks deploy correction via managed identities, satisfying the automatic remediation requirement. Policy assignments scoped to management groups apply governance consistently across all subscriptions.

Why this answer

Azure Policy (A) is the core governance service that defines, assigns, and evaluates policy definitions and initiatives at management-group, subscription, and resource-group scopes, providing the enforce and audit-at-scale capabilities required. Azure Automation (C) supplies runbooks and, via its integration with Azure Policy's deployIfNotExists and modify effects (or remediation tasks), performs the automatic remediation of non-compliant resources. Azure Blueprints is deprecated/retired and should not be used for new designs, so it is not a valid AZ-305 answer.

Azure Monitor (B) is for telemetry, metrics, and alerts rather than policy enforcement or remediation, and Azure RBAC (D) governs who can perform actions on resources through role assignments, not whether resource configurations comply with security policies.

Exam trap

AZ-305 often tests the confusion between Azure Policy (enforcement/audit) and Azure Blueprints (packaging and deployment). Note that Azure Blueprints is deprecated/retired, so it should not be selected as the answer; the enforcement, audit, and remediation capabilities are provided by Azure Policy and Azure Automation.

306
MCQmedium

Your company uses Microsoft Sentinel for security monitoring. You need to design a solution to detect when a user account is created in Microsoft Entra ID with Global Administrator privileges. When detected, an incident must be created in Sentinel and the account should be disabled temporarily until reviewed. You want to use built-in capabilities where possible. What should you do?

A.Use Microsoft Entra Privileged Identity Management to require approval for role activation, and audit logs to detect permanent assignments.
B.Use Microsoft Defender for Cloud Apps to monitor for privileged role assignments and send an alert to Sentinel.
C.Use a Microsoft Sentinel analytics rule template for 'Suspicious Entra ID role assignment' and configure a playbook to disable the account via Microsoft Graph API.
D.Create a custom KQL query in Log Analytics and schedule it as a Sentinel analytics rule, then use an Azure Function to disable the account.
AnswerC

The Sentinel analytics rule template 'Suspicious Entra ID role assignment' is purpose-built to detect privileged role assignments that match known attack patterns, such as a new administrator added to a highly privileged role outside normal activation times. Because it natively surfaces the event as an incident, you can attach an automated playbook that invokes Microsoft Graph API to disable the compromised account immediately. This combination provides detection, correlation, and automated response exactly as required.

Why this answer

It uses a built-in Sentinel analytics rule template specifically designed to detect suspicious Entra ID role assignments, which meets the requirement for built-in capabilities. The playbook, triggered by the rule, can use the Microsoft Graph API to disable the account temporarily, providing automated remediation without custom code or external services.

Exam trap

The trap here is that candidates may overcomplicate the solution by choosing custom KQL queries or external services (like Defender for Cloud Apps) when a built-in analytics rule template and playbook are available and sufficient for the detection and automated response.

How to eliminate wrong answers

Option A is wrong because Privileged Identity Management (PIM) requires approval for role activation but does not detect permanent assignments or create Sentinel incidents; it focuses on just-in-time access, not post-creation detection. Option B is wrong because Microsoft Defender for Cloud Apps can monitor for privileged role assignments but is not a built-in Sentinel capability for creating incidents directly; it would require additional configuration to forward alerts to Sentinel, and it does not natively disable accounts. Option D is wrong because creating a custom KQL query and using an Azure Function introduces unnecessary custom development and complexity, whereas built-in analytics rule templates and playbooks are available and preferred for this scenario.

307
MCQhard

A company runs a critical application on Azure VMs in a single region. They need to improve availability to meet an SLA of 99.99% while minimizing costs. The application is stateless and can run on multiple VMs. Which solution should you recommend?

A.Deploy a virtual machine scale set across multiple availability zones in a single region.
B.Deploy two VMs in the same availability set in a single region.
C.Deploy a single VM with Azure Site Recovery to another region.
D.Deploy two VMs in two different Azure regions with Azure Traffic Manager.
AnswerA

A virtual machine scale set deployed across multiple availability zones distributes VM instances among distinct fault domains and update domains in separate Azure datacenters within the same region. This architecture meets the 99.99% availability SLA for virtual machines while also enabling elastic scaling and automatic rebalancing of instances, making it a cost-effective and resilient single-region solution. Because all instances reside in the same region, latency remains low and the setup avoids the expense of replicating data across geo-disparate regions.

Why this answer

A virtual machine scale set deployed across multiple availability zones in a single region provides zone-level redundancy, protecting against datacenter failures while keeping traffic within a single region for low latency. This configuration can achieve up to 99.99% availability (when using two or more zones) without the cost and complexity of multi-region replication, making it the most cost-effective solution for a stateless application.

Exam trap

The trap here is that candidates often over-engineer by choosing multi-region solutions (Option D) or under-engineer with availability sets (Option B), failing to recognize that a single-region, multi-zone scale set is the optimal balance of cost and availability for a stateless app targeting 99.99%.

How to eliminate wrong answers

Option B is wrong because an availability set protects against rack-level failures within a single datacenter, not against full datacenter or zone outages, so it cannot meet a 99.99% SLA (which requires zone or region redundancy). Option C is wrong because a single VM with Azure Site Recovery provides disaster recovery but does not offer high availability within the primary region; failover time and potential data loss prevent achieving 99.99% uptime for the application. Option D is wrong because deploying across two regions with Traffic Manager adds significant cost (cross-region data transfer, duplicate resources) and complexity, which is unnecessary for a stateless app that can achieve 99.99% with a multi-zone scale set in a single region.

308
Multi-Selectmedium

Your company is planning to use Azure Monitor Workbooks to create custom dashboards for IT operations. You need to select the data sources that can be used in a workbook. Which TWO data sources are supported? (Choose two.)

Select 2 answers
A.Azure Resource Graph
B.Azure SQL Database
C.Microsoft Sentinel
D.Log Analytics workspace
E.Azure Blob Storage
AnswersA, D

Azure Resource Graph is a fully supported data source in Azure Monitor workbooks. Workbooks include a dedicated query control that natively targets Azure Resource Graph (ARG), enabling you to run KQL-based resource exploration queries across subscriptions, management groups, and resource types. Because ARG provides a live, inventory-level view of Azure resources rather than logs or metrics, it is the correct choice when the workbook’s goal is to visualize resource properties, tags, or compliance-related metadata. This direct integration differentiates ARG from stores like SQL Database or Blob Storage, which require an intermediate log-ingestion step.

Why this answer

Azure Monitor Workbooks support Azure Resource Graph as a data source, allowing you to query Azure resources and their properties across subscriptions. This enables rich, resource-centric visualizations in custom dashboards without needing to export data to a separate store.

Exam trap

The trap here is that candidates often confuse Microsoft Sentinel as a separate data source, when in reality it relies on Log Analytics workspaces, and they may incorrectly assume Azure SQL Database or Blob Storage are directly queryable by workbooks.

309
MCQmedium

A company runs a critical application on an Azure virtual machine in the West US region. They want to enable disaster recovery to East US with the ability to perform non-disruptive DR drills. They need an RPO of a few minutes. Which Azure service should they use?

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

Azure Site Recovery is the correct disaster recovery solution because it continuously replicates Azure VM disks asynchronously to the paired region, enabling a low recovery point objective (RPO) that can be as low as 30 seconds for supported workloads. It also provides orchestrated failover and test failover capabilities, allowing you to validate recovery plans in an isolated test network without affecting the production environment. Recovery plans can automate the startup order of multi-tier applications, making ASR a true DR orchestration tool rather than just a data protection service.

Why this answer

Azure Site Recovery (ASR) is the correct service because it provides continuous replication of Azure VMs from a primary region (West US) to a secondary region (East US) with a Recovery Point Objective (RPO) of a few minutes. It also supports non-disruptive disaster recovery drills by allowing you to perform test failovers in an isolated network without impacting the production workload.

Exam trap

The trap here is that candidates often confuse Azure Backup (which is for long-term retention) with Azure Site Recovery (which is for replication and failover), leading them to choose Backup for DR scenarios that require low RPO and non-disruptive testing.

How to eliminate wrong answers

Option B (Azure Backup) is wrong because it is designed for long-term backup and retention, not for low-RPO replication or non-disruptive DR drills; its RPO is typically hours or days, not a few minutes. Option C (Azure Traffic Manager) is wrong because it is a DNS-based traffic load balancer for distributing incoming traffic across endpoints, not a replication or failover service for disaster recovery with a specific RPO. Option D (Azure Blueprints) is wrong because it is a governance and compliance tool for defining repeatable Azure resource templates, not a disaster recovery or replication service.

310
MCQmedium

Your company is planning to migrate a large number of on-premises servers to Azure. The migration must be completed within 3 months. You need to assess the current on-premises environment and recommend the most appropriate Azure VM sizes and costs. What should you do?

A.Create a manual inventory of all servers and use Azure Pricing Calculator to estimate costs.
B.Use Azure Migrate to discover and assess the on-premises environment, and generate sizing and cost recommendations.
C.Use Azure Advisor to analyze on-premises server usage and recommend Azure VM sizes.
D.Use Azure Cost Management to estimate costs based on manual input of server specifications.
AnswerB

Azure Migrate is the correct service for migration planning because it performs agentless discovery of on-premises servers, collects performance history, and maps application dependencies. Its assessment engine can right-size Azure VM SKUs based on actual utilization rather than nominal hardware, and it generates cost recommendations that account for Azure Hybrid Benefit and Reserved Instances. This gives you a data-driven, repeatable basis for migration decisions.

Why this answer

Azure Migrate is the correct tool because it provides automated discovery and assessment of on-premises servers, including performance data, dependencies, and configuration details. It then generates right-sized Azure VM recommendations and cost estimates based on actual usage, which is essential for a large-scale migration with a tight 3-month deadline.

Exam trap

The trap here is that candidates may confuse Azure Advisor (which optimizes existing Azure resources) with Azure Migrate (which assesses on-premises environments for migration), or assume that manual inventory and pricing calculators are sufficient for large-scale migrations despite the lack of performance-based sizing.

How to eliminate wrong answers

Option A is wrong because a manual inventory of all servers is time-consuming, error-prone, and impractical for a large number of servers within a 3-month timeframe; it also lacks performance-based sizing. Option C is wrong because Azure Advisor is designed to optimize existing Azure resources, not to discover or assess on-premises environments. Option D is wrong because Azure Cost Management is a cost monitoring and analysis tool for existing Azure resources, not a discovery or assessment tool for on-premises servers.

311
MCQmedium

Your organization is deploying a critical application on Azure virtual machines. You need to ensure that the VMs are distributed across multiple fault domains and update domains within an availability set. You create an availability set with 3 fault domains and 5 update domains. How many VMs can you add to this availability set to maximize fault tolerance?

A.5 VMs
B.Unlimited
C.15 VMs
D.3 VMs
AnswerB

The correct answer is that an availability set has no prescribed maximum number of VMs; instead, you can place as many VMs as your Azure subscription and regional capacity support. Availability sets are primarily a placement construct that separates VMs across fault and update domains to maximize availability, and they do not impose a numeric ceiling on the number of instances you can add. This means your critical application can scale to hundreds of VMs within a single availability set, constrained only by Azure quota limits and not by the availability set design.

Why this answer

B is correct because Azure availability sets do not limit the number of VMs you can place into them; you can add an unlimited number of VMs. The fault domains (3) and update domains (5) define the maximum distribution groups, but Azure will place VMs across these domains as evenly as possible. Adding more VMs beyond the number of fault or update domains does not reduce fault tolerance—it simply means multiple VMs will share the same fault or update domain, but the set still provides the best possible distribution given the defined domain counts.

Exam trap

The trap here is that candidates often multiply fault domains by update domains (3 × 5 = 15) and assume that is the maximum number of VMs, but Azure does not enforce such a product limit—the domains are logical groups, not slots that can hold only one VM each.

How to eliminate wrong answers

Option A is wrong because 5 VMs is not a limit; it confuses the number of update domains (5) with a maximum VM count, but update domains only control how many groups of VMs are updated sequentially during planned maintenance, not the total number of VMs. Option C is wrong because 15 VMs (3 fault domains × 5 update domains) is a common misconception that each fault domain can hold only one VM per update domain, but Azure allows multiple VMs per fault domain and update domain, so the product of these numbers is not a cap. Option D is wrong because 3 VMs incorrectly assumes the limit equals the number of fault domains, ignoring that each fault domain can host multiple VMs and that update domains also allow multiple VMs.

312
MCQhard

You are reviewing a custom RBAC role in Azure. The exhibit shows the role definition. A user with this role reports they cannot read diagnostic settings for a storage account in the Production resource group. What is the most likely cause?

A.The role does not include 'Microsoft.Storage/storageAccounts/read'
B.Custom roles cannot be assigned to users
C.The role lacks the 'Microsoft.Storage/storageAccounts/listKeys/action' permission
D.The role is assigned at the wrong scope
AnswerA

Although the custom role grants Microsoft.Storage/storageAccounts/listKeys/action and possibly other storage permissions, it omits the control-plane action Microsoft.Storage/storageAccounts/read. Azure Resource Manager relies on that read action to list and enumerate storage accounts, and the portal uses it to populate the Storage accounts view. Without it, a user cannot discover storage accounts or navigate to them, because even a known resource ID only works if the caller has the read action on that resource; the role is therefore functionally incomplete.

Why this answer

The user cannot read diagnostic settings because the custom role lacks the 'Microsoft.Storage/storageAccounts/read' permission. This permission is required to read the storage account resource itself, which is a prerequisite for accessing its diagnostic settings. Without it, the role cannot perform any read operations on the storage account, including reading diagnostic logs or metrics configuration.

Exam trap

The trap here is that candidates may confuse data plane permissions (like listKeys) with control plane permissions (like read), or assume that diagnostic settings can be read independently of the parent resource's read permission.

How to eliminate wrong answers

Option B is wrong because custom roles can be assigned to users, groups, or service principals just like built-in roles; the limitation is that custom roles must be defined in the same tenant. Option C is wrong because 'listKeys/action' is used to retrieve storage account access keys for data plane operations, not for reading diagnostic settings, which is a control plane operation. Option D is wrong because even if the role is assigned at the wrong scope, the core issue is the missing 'read' permission; assigning at the correct scope would still fail without the required permission.

313
MCQhard

A large enterprise has a management group hierarchy with 50 subscriptions. They need to enforce that every resource group must have a 'CostCenter' tag and that any new resource group without that tag is automatically denied creation. Additionally, they need to ensure that only the Finance team can modify tags on any resource. They also want to generate monthly compliance reports showing which resources are non-compliant. Which combination of Azure services should they use?

A.Azure Policy for tag enforcement, Azure RBAC for scoping tag modification to Finance, and Azure Policy for compliance reporting
B.Azure Blueprints with tag policy and Azure RBAC, and Azure Security Center for compliance
C.Azure Policy for tag enforcement, Azure Management Groups for governance, and Azure Monitor for compliance reports
D.Azure Policy for tag enforcement, Azure RBAC for tag modification, and Azure Security Center for compliance
AnswerA

The correct combination uses Azure Policy to assign a tag requirement at the root or intermediate management group, so the Deny or Modify effects apply consistently across every subscription and the Policy compliance dashboard gives finance stakeholders a continuously updated report of noncompliant resources. Azure RBAC then grants the Finance team the Tag Contributor built-in role at the necessary scope, letting them edit tag keys and values without broader write access. Because compliance reporting is generated from the same Azure Policy assignments, no separate monitoring or security tool is needed. This is the only option that both enforces the policy and correctly identifies the reporting service.

Why this answer

Azure Policy can enforce the 'CostCenter' tag on resource groups via a 'deny' effect policy, Azure RBAC can restrict tag modification to the Finance team by assigning the 'Tag Contributor' role at the appropriate scope, and Azure Policy's compliance reporting (via the Azure Policy Compliance dashboard or export to Log Analytics) provides monthly reports on non-compliant resources without needing additional services.

Exam trap

The trap here is that candidates confuse Azure Security Center (for security compliance) with Azure Policy (for governance compliance), or assume Azure Monitor can generate compliance reports when it is designed for metrics and logs, not policy evaluation.

How to eliminate wrong answers

Option B is wrong because Azure Blueprints are for deploying consistent environments (including policies), but they do not provide ongoing compliance reporting; Azure Security Center (now Microsoft Defender for Cloud) focuses on security posture, not tag compliance. Option C is wrong because Azure Management Groups are for organizing subscriptions and applying policies, not for governance enforcement itself, and Azure Monitor is for telemetry and alerts, not for generating compliance reports on tags. Option D is wrong because Azure Security Center is not designed for tag compliance reporting; it handles security recommendations and vulnerabilities, not resource metadata compliance.

314
Multi-Selecteasy

Which TWO of the following are valid options to achieve high availability for Azure SQL Database? (Choose two.)

Select 2 answers
A.Deploy a single database with locally redundant storage (LRS)
B.Deploy a zone-redundant Azure SQL Database
C.Configure manual failover to a secondary replica in the same region
D.Configure SQL Server Always On availability groups
E.Configure active geo-replication to a secondary database in a different region
AnswersB, E

A zone-redundant Azure SQL Database automatically replicates both compute and storage across multiple availability zones within the same region. This configuration provides an availability SLA of 99.995% and enables transparent failover to another zone without any application changes. It is a valid, supported option for achieving high availability within a single Azure region.

Why this answer

Azure SQL Database offers zone-redundant configuration that automatically replicates databases across multiple Azure Availability Zones within the same region, providing an SLA of 99.995% uptime. This built-in high availability feature uses quorum-based commit and automatic failover without any manual intervention, ensuring data durability and business continuity during zone-level failures.

Exam trap

The trap here is that candidates often confuse the high availability features of Azure SQL Database (PaaS) with those of SQL Server on Azure VMs (IaaS), mistakenly selecting Always On availability groups or manual failover options that are not applicable to the managed service.

315
MCQhard

You are designing a storage solution for a global e-commerce platform that must serve users from multiple regions with low latency. The data includes product catalog (read-heavy, rarely updated) and user session state (write-heavy, short-lived). Which combination of Azure services meets the requirements?

A.Azure Cosmos DB for session state and Azure Front Door with Azure CDN for catalog.
B.Azure Cache for Redis for session state and Azure Front Door for catalog.
C.Azure Table Storage for session state and Azure Front Door for catalog.
D.Azure SQL Database with geo-replication for both.
AnswerA

Azure Cosmos DB is the correct choice for session state because it provides multi-region writes with automatic failover, ensuring globally distributed users can write and read session data with low latency and no single point of failure. Its tunable consistency levels allow you to balance performance against data freshness, while Azure Front Door with Azure CDN delivers the global catalog by routing dynamic traffic intelligently and caching static/mixed content at the edge, offloading origin servers and improving read-heavy catalog performance.

Why this answer

Azure Cosmos DB is ideal for session state because it offers multi-region writes with single-digit-millisecond latency and automatic failover, meeting the write-heavy, short-lived requirements. Azure Front Door with Azure CDN provides global load balancing and caching for the read-heavy, rarely updated product catalog, ensuring low-latency content delivery from the nearest point of presence.

Exam trap

The trap here is that candidates often confuse Azure Cache for Redis as a durable session store, but it is a volatile cache that requires a persistence strategy (e.g., Redis persistence or Azure Cache for Redis with data persistence) to avoid data loss, which is not suitable for session state that must survive restarts.

How to eliminate wrong answers

Option B is wrong because Azure Cache for Redis is an in-memory cache, not a durable storage solution; it would lose session state on restart or scaling events, making it unsuitable for persistent session state in a global e-commerce platform. Option C is wrong because Azure Table Storage is a NoSQL key-value store with higher latency and no native multi-region write support, failing to meet the low-latency write requirements for session state. Option D is wrong because Azure SQL Database with geo-replication is optimized for structured relational data and ACID transactions, not for the high-throughput, schema-flexible session state or the read-heavy catalog caching; it also introduces unnecessary cost and complexity for this workload.

316
Matchingmedium

Match each Azure compute service to its characteristic.

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

Concepts
Matches

IaaS with full control over OS and apps

PaaS for web apps, APIs, and mobile backends

Managed Kubernetes for container orchestration

Serverless compute for event-driven code

Simple, fast container deployment without orchestration

Why these pairings

Azure compute services range from IaaS (Virtual Machines) to PaaS (App Service) to serverless (Azure Functions) and container orchestration (AKS). Distractors confuse definitions of serverless and container orchestration, or PaaS and managed Kubernetes.

317
MCQeasy

Your organization is moving to a cloud-only identity model using Microsoft Entra ID. You need to ensure that users can reset their own passwords without help desk intervention. The solution must support multi-factor authentication and notify administrators of password resets. What should you implement?

A.Microsoft Entra Connect Password Writeback
B.Conditional Access policies for password change
C.Microsoft Entra Self-Service Password Reset (SSPR)
D.Microsoft Entra ID Protection
AnswerC

Microsoft Entra Self-Service Password Reset (SSPR) lets users reset or unlock their own passwords through the Microsoft Entra portal using pre-registered authentication methods, satisfying the self-service requirement. It supports multi-factor authentication by requiring verification via methods such as mobile app or SMS before allowing a reset, and administrators can configure email notifications whenever a reset occurs. SSPR works natively in a cloud-only identity model and aligns with all constraints in the scenario.

Why this answer

Microsoft Entra Self-Service Password Reset (SSPR) allows users to reset their own passwords without help desk intervention. It supports multi-factor authentication (MFA) as a verification step before resetting, and can be configured to send notifications to administrators when a password reset occurs. This directly meets all stated requirements.

Exam trap

The trap here is that candidates often confuse password writeback (a prerequisite for hybrid environments) with the actual self-service reset feature, or they mistake Conditional Access policies (which enforce MFA during sign-in) for the self-service reset process itself.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra Connect Password Writeback is a feature that enables password changes from the cloud to be written back to an on-premises Active Directory; it is not a self-service reset solution and does not by itself provide MFA or admin notifications. Option B is wrong because Conditional Access policies for password change control the conditions under which a password change is allowed (e.g., requiring MFA during sign-in), but they do not provide a self-service reset portal or admin notification for password resets. Option D is wrong because Microsoft Entra ID Protection is a risk-based security service that detects and responds to identity risks (e.g., leaked credentials, anomalous sign-ins); it does not provide a self-service password reset capability.

318
MCQhard

A company uses Azure NetApp Files for high-performance file shares accessed by Linux VMs. They need to reduce latency for read-heavy workloads. Which configuration should you implement?

A.Migrate to Azure Files with Azure File Sync
B.Enable read-only cache on the volume
C.Disable the export policy to allow all clients
D.Mount the volume using SMB protocol
AnswerB

Enabling a read-only cache on the volume configures Azure NetApp Files to use local NVMe or SSD storage on the compute cluster as a cache for repeated reads, dramatically reducing latency for read-heavy workloads. This feature is transparent to clients and requires no client-side changes, as cached data is served without hitting the underlying storage tier. It is a targeted, low-friction optimization that directly addresses read performance, unlike cross-service migrations or protocol changes.

Why this answer

Azure NetApp Files supports a read-only cache option on volumes, which stores frequently accessed data in a high-speed cache (SSD-based) local to the compute resources. This reduces read latency for read-heavy workloads by serving data from the cache instead of the underlying storage tier. The cache is transparent to the Linux VMs and requires no application changes.

Exam trap

The trap here is that candidates may confuse Azure NetApp Files with Azure Files, assuming that Azure File Sync or SMB mounting can provide similar performance benefits, when in fact Azure NetApp Files uses NFS and its read-only cache is the specific feature designed for reducing read latency.

How to eliminate wrong answers

Option A is wrong because migrating to Azure Files with Azure File Sync does not provide the same low-latency, high-performance characteristics as Azure NetApp Files, and Azure File Sync is designed for hybrid caching, not for reducing latency within Azure. Option C is wrong because disabling the export policy to allow all clients removes all access controls and security, which is a security risk and does not reduce latency. Option D is wrong because mounting the volume using SMB protocol is not supported for Azure NetApp Files with Linux VMs (it uses NFS), and SMB would introduce additional protocol overhead and compatibility issues, increasing latency rather than reducing it.

319
Drag & Dropmedium

Drag and drop the steps to implement Azure Traffic Manager for geographic routing into the correct order.

Drag or tap steps into the slots.

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

Why this order

The correct sequence for implementing Azure Traffic Manager for geographic routing is: first create the Traffic Manager profile, then add the endpoints (e.g., Azure regions), then configure the geographic routing mapping to assign regions to endpoints, then update DNS records to point to the Traffic Manager domain name, and finally test the routing. Skipping or reordering these steps can lead to misconfiguration or routing failures.

320
MCQhard

Your company is designing a new cloud-native application on Azure that consists of multiple microservices running on Azure Kubernetes Service (AKS). The application must be accessible from the internet via a custom domain name (app.contoso.com) and must support SSL/TLS termination. You need to design a secure ingress solution that provides Web Application Firewall (WAF) capabilities, SSL offloading, and automatic scaling. The solution should also support path-based routing to different microservices (e.g., /api, /web). You have the following options: Option A: Deploy an Azure Application Gateway v2 with WAF in front of the AKS cluster. Configure Application Gateway Ingress Controller (AGIC) to route traffic to the services. Option B: Deploy an Azure Load Balancer with a public IP and install an NGINX ingress controller on AKS. Configure SSL termination on NGINX and use a third-party WAF. Option C: Deploy an Azure Front Door with WAF policy in front of the AKS cluster. Use Azure Private Link to connect Front Door to the internal load balancer of AKS. Option D: Deploy an Azure API Management instance with WAF and expose the microservices through API endpoints. Use Azure Application Gateway as a reverse proxy. Which option best meets the requirements for a high-performance, integrated, and managed solution with minimal operational overhead?

A.Deploy an Azure Front Door with WAF policy in front of the AKS cluster. Use Azure Private Link to connect Front Door to the internal load balancer of AKS.
B.Deploy an Azure Application Gateway v2 with WAF in front of the AKS cluster. Configure Application Gateway Ingress Controller (AGIC) to route traffic to the services.
C.Deploy an Azure Load Balancer with a public IP and install an NGINX ingress controller on AKS. Configure SSL termination on NGINX and use a third-party WAF.
D.Deploy an Azure API Management instance with WAF and expose the microservices through API endpoints. Use Azure Application Gateway as a reverse proxy.
AnswerB

Application Gateway v2 is a regional, autoscaling, Layer 7 load balancer with a managed WAF that includes OWASP rule sets, making it a strong fit for exposing AKS-based microservices. By deploying AGIC, the Kubernetes Ingress resources are automatically translated into Application Gateway routing rules, so no separate ingress controller pod is required. It provides SSL termination, path-based routing, and zone redundancy, all while being fully managed by Azure, which reduces operational burden compared to self-managed ingress.

Why this answer

Azure Application Gateway v2 with WAF provides a fully managed, integrated ingress solution that natively supports SSL/TLS offloading, path-based routing, and Web Application Firewall capabilities. By using the Application Gateway Ingress Controller (AGIC), traffic is automatically routed to the appropriate AKS microservices based on URL paths (e.g., /api, /web), and the gateway can scale automatically based on load. This minimizes operational overhead while meeting all stated requirements.

Exam trap

The trap here is that candidates often confuse Azure Front Door's global load balancing capabilities with the need for a regional, AKS-integrated ingress controller that supports path-based routing and WAF, leading them to choose Option A despite its lack of native AKS ingress controller support.

How to eliminate wrong answers

Option A is wrong because Azure Front Door is a global load balancer and application delivery controller that does not natively integrate with AKS for path-based routing to microservices; using Private Link adds complexity and latency, and Front Door lacks the direct ingress controller integration that AGIC provides. Option C is wrong because deploying an Azure Load Balancer with a public IP and a third-party WAF on NGINX introduces significant operational overhead for managing SSL certificates, WAF rules, and scaling, and does not provide a managed, integrated solution. Option D is wrong because Azure API Management is designed for API management and governance, not as a primary ingress controller; adding Application Gateway as a reverse proxy creates unnecessary complexity and does not directly support path-based routing to AKS microservices with minimal overhead.

321
MCQeasy

Refer to the exhibit. You are deploying an ARM template that assigns a policy to audit virtual machines not using managed disks. After deployment, you need to verify that the policy assignment is working. Which Azure CLI command should you run?

A.az policy assignment list --subscription 12345678-1234-1234-1234-123456789abc
B.az policy state list --resource-group myResourceGroup
C.az policy definition list --subscription 12345678-1234-1234-1234-123456789abc
D.az policy event list --subscription 12345678-1234-1234-1234-123456789abc
AnswerA

The az policy assignment list command enumerates policy assignments at the specified subscription scope, and because the ARM template was deployed at that scope, the newly created assignment object appears as an entry in the output. It returns each assignment’s name, ID, scope, associated definition, and parameters, allowing you to verify that the deployment actually registered the assignment. This is the only option that directly queries the assignment resource rather than definitions or derived evaluation records.

Why this answer

The `az policy assignment list` command retrieves all policy assignments in the specified subscription, including the one deployed via the ARM template. This allows you to confirm that the policy assignment exists and is properly configured. To verify that the policy is actually evaluating resources and producing compliance states, you would then use `az policy state list` to see the compliance results, but the question specifically asks to verify that the assignment itself is working, which is done by listing assignments.

Exam trap

The trap here is that candidates confuse the command for listing policy assignments with the command for viewing compliance states, leading them to choose `az policy state list` (Option B) instead of `az policy assignment list` (Option A) when the question asks to verify that the assignment itself is working.

How to eliminate wrong answers

Option B is wrong because `az policy state list` shows the current compliance states of resources against a policy, not the existence or configuration of the policy assignment itself. Option C is wrong because `az policy definition list` retrieves the built-in or custom policy definitions, not the assignments of those definitions to a scope. Option D is wrong because `az policy event list` is not a valid Azure CLI command; the correct command for viewing policy events is `az policy state list` with the `--filter` parameter, and events are not used for verifying assignment existence.

322
MCQeasy

A company uses Microsoft Entra ID. They want to automatically detect sign-ins from anonymous IP addresses, sign-ins from unfamiliar locations, and other risky activities. When such a risk is detected, they want to block the sign-in or require multi-factor authentication. They also need a dashboard to review risk events. Which Microsoft Entra ID feature should they use?

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

Identity Protection detects anonymous IP sign-ins, unfamiliar locations and other risky activities, then applies risk-based policies to block sign-ins or require multi-factor authentication. Its dashboard surfaces detected risk events, satisfying every stated requirement within Microsoft Entra ID.

Why this answer

Microsoft Entra ID Identity Protection is the correct feature because it is specifically designed to detect and respond to identity-based risks such as sign-ins from anonymous IP addresses, unfamiliar locations, and other risky activities. It provides a risk-based conditional access policy that can automatically block sign-ins or require multi-factor authentication (MFA) when a risk is detected, and it includes a dashboard for reviewing risk events and reports.

Exam trap

The trap here is that candidates often confuse Conditional Access (which enforces policies) with Identity Protection (which provides the risk detection signals), leading them to select Conditional Access as the answer when the question explicitly asks for the feature that detects risks and provides a dashboard.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra ID Conditional Access is a policy engine that enforces access controls based on conditions (e.g., location, device state), but it does not itself detect risky sign-ins or provide a risk dashboard; it relies on Identity Protection to supply risk signals. Option C is wrong because Privileged Identity Management (PIM) focuses on just-in-time privileged role activation, approval workflows, and access reviews for administrative roles, not on detecting anonymous IP addresses or unfamiliar location sign-ins. Option D is wrong because Access Reviews are used for periodic recertification of group memberships or application access, not for real-time risk detection or automated blocking of risky sign-ins.

323
Matchingmedium

Match each Azure migration tool to its use case.

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

Concepts
Matches

Centralized hub for discovery, assessment, and migration

Migrate databases to Azure with minimal downtime

Physical device for offline data transfer

Replicate and migrate on-premises VMs to Azure

Ship hard drives to transfer large data volumes

Why these pairings

Azure Migrate is for server assessment/migration, Azure Site Recovery for disaster recovery, and Azure Database Migration Service for database migrations. Common confusions involve swapping these use cases.

324
MCQeasy

You are designing a high-availability solution for a stateless web application running on Azure VMs. The solution must provide automatic failover to another region in the event of a regional outage. Which Azure service should you use to distribute traffic across regions?

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

Azure Front Door is a global, layer 7 service that uses anycast to route HTTP(S) traffic to the nearest healthy origin, with automatic failover if a backend region becomes unhealthy. It supports SSL termination, path-based routing, session affinity, and a built-in WAF, making it well-suited for stateless web applications that require both low-latency global access and resiliency. Front Door continuously probes health endpoints in each region and instantly shifts traffic to the next-capable origin without relying on DNS caching clients.

Why this answer

Azure Front Door is the correct choice because it is a global, scalable entry point that uses HTTP/HTTPS traffic to provide cross-region load balancing and automatic failover. It supports path-based routing, SSL offload, and health probes that can detect a regional outage and instantly reroute traffic to a healthy region, meeting the requirement for stateless web applications.

Exam trap

The trap here is that candidates often confuse Azure Traffic Manager (DNS-based, slower failover) with Azure Front Door (application-layer, faster failover), but the question's emphasis on 'automatic failover' and 'regional outage' points to Front Door's superior health probe and anycast capabilities over Traffic Manager's DNS-dependent routing.

How to eliminate wrong answers

Option A is wrong because Azure Application Gateway is a regional load balancer that operates at Layer 7 (HTTP/HTTPS) but cannot distribute traffic across multiple Azure regions; it is confined to a single region. Option B is wrong because Azure Load Balancer is a Layer 4 (TCP/UDP) load balancer that is also regional and does not support cross-region failover or global traffic distribution. Option D is wrong because Azure Traffic Manager is a DNS-based traffic router that can distribute traffic across regions, but it relies on DNS resolution and does not provide automatic failover at the application layer with health probes that react as quickly as Front Door's anycast network; it also lacks native HTTP/HTTPS features like SSL offload and path-based routing.

325
MCQhard

A company deploys a multi-tier web application on Azure VMs across availability zones. The web tier must have SSL termination, session persistence, and health probe monitoring. Additionally, all traffic must be inspected by a central firewall for compliance. The solution must be highly available. Which combination of Azure services should they implement?

A.Azure Application Gateway (WAF) in front of web VMs, with Azure Firewall in a hub VNet for central inspection
B.Azure Load Balancer (Standard) in front of web VMs, with a third-party Network Virtual Appliance (NVA) for inspection
C.Azure Front Door in front of web VMs, with Azure Firewall for inspection
D.Azure Traffic Manager + Azure Application Gateway
AnswerA

Application Gateway (WAF) is an L7 load balancer that terminates TLS, provides web application firewall rules (SQL injection, XSS), and supports cookie-based session affinity at the HTTP layer. By placing it in front of the web VMs, you get protocol-aware routing and protection. Azure Firewall in a hub VNet then serves as the centralized inspection point for all east-west and outbound traffic via UDR or forced tunneling, enabling consistent security policy enforcement without separate L4/L7 devices. This hub-spoke design is the industry-standard pattern for multi-tier web workloads.

Why this answer

Azure Application Gateway provides SSL termination, session persistence (via cookie-based affinity), and health probes at Layer 7, which are required for a web tier. Placing Azure Firewall in a hub VNet for central inspection ensures all traffic is inspected for compliance, and deploying the web VMs across availability zones meets the high-availability requirement.

Exam trap

The trap here is that candidates often confuse Azure Load Balancer (Layer 4) with Application Gateway (Layer 7), assuming the Load Balancer can handle SSL termination and session persistence, or they overlook that Azure Front Door lacks session persistence and central inspection capabilities.

How to eliminate wrong answers

Option B is wrong because Azure Load Balancer operates at Layer 4 and cannot perform SSL termination or session persistence at the application layer; it also lacks native WAF capabilities, and using a third-party NVA introduces a single point of failure unless also deployed in a highly available manner. Option C is wrong because Azure Front Door is a global load balancer and CDN that does not support session persistence (sticky sessions) natively, and it cannot enforce central firewall inspection for all traffic as it terminates SSL at the edge, bypassing the central firewall. Option D is wrong because Azure Traffic Manager is a DNS-level load balancer that does not provide SSL termination, session persistence, or health probes at the application layer; combining it with Application Gateway adds unnecessary complexity without addressing the central firewall inspection requirement.

326
MCQmedium

A company is designing a serverless architecture for a real-time data processing pipeline. The pipeline ingests data from IoT devices, processes the data using Azure Functions, and stores the results in Azure Cosmos DB. The solution must scale automatically and minimize cold starts. Which Azure service should the company use to trigger the Azure Functions?

A.Azure Event Grid
B.Azure Queue Storage
C.Azure Event Hubs
D.Azure Service Bus
AnswerA

Event Grid is a fully managed event routing service that delivers events to subscribers via push-based HTTP calls, enabling Azure Functions to execute with near-zero latency and minimal cold starts. It can ingest device telemetry events directly from IoT Hub and route them to a function trigger without any polling layer. This push model is purpose-built for real-time serverless processing, making it the correct choice for this architecture.

Why this answer

Azure Event Grid is the correct choice because it provides a fully managed event routing service that can trigger Azure Functions in near real-time with sub-second latency, minimizing cold starts through its push-based model and support for serverless event handlers. It is ideal for IoT data ingestion scenarios where each device event needs to trigger a function independently, and it scales automatically to handle high throughput without requiring polling or batching.

Exam trap

The trap here is that candidates often confuse Azure Event Hubs (a streaming ingestion service) with Azure Event Grid (an event routing service), mistakenly choosing Event Hubs for real-time triggers when it is actually designed for high-throughput data capture and requires additional processing layers, not direct function invocation.

How to eliminate wrong answers

Option B (Azure Queue Storage) is wrong because it uses a pull-based model where the function must poll the queue for messages, introducing latency and potential cold starts due to idle polling intervals, and it is not designed for real-time event-driven triggers. Option C (Azure Event Hubs) is wrong because it is optimized for high-throughput data streaming and big data ingestion, not for triggering individual functions per event; it typically requires a separate consumer or stream processing job to process events, and it does not natively support direct function triggers without additional configuration. Option D (Azure Service Bus) is wrong because it is a message broker designed for enterprise messaging with features like sessions and transactions, but it uses a pull-based model for functions (via the Service Bus trigger) that can incur cold starts and is not optimized for the high-frequency, low-latency event pattern required by IoT device data.

327
MCQmedium

A media company needs to store large volumes of video files that are processed by an application. The files are accessed via REST APIs and are rarely accessed after the first few days. The company wants to minimize storage costs by automatically moving older files to a cheaper storage tier without any manual intervention. Which Azure storage solution should they use, and which feature should they configure?

A.Azure Blob Storage with lifecycle management policies
B.Azure Files with tiering
C.Azure NetApp Files with capacity pools
D.Azure Disk Storage with managed disks
AnswerA

Azure Blob Storage is the correct choice because it provides REST API access for direct HTTP/HTTPS retrieval of video files, and its lifecycle management policies can automatically move blobs through hot, cool, and archive tiers based on age. This allows a media company to store large volumes of video files cost-effectively, with older content automatically transitioned to cheaper archive storage while still being retrievable on demand. Unlike file or disk storage, Blob Storage scales horizontally for massive unstructured data and integrates with CDNs for streaming.

Why this answer

Azure Blob Storage with lifecycle management policies is the correct solution because it allows you to define rules that automatically move blobs to cooler tiers (e.g., from Hot to Cool to Archive) based on age or last modification time, minimizing storage costs without manual intervention. The REST API access requirement is natively supported by Blob Storage via HTTPS, and the large video file workload fits well within its object storage capabilities.

Exam trap

The trap here is that candidates may confuse Azure Files tiering (which is for hybrid caching with Azure File Sync) with Blob Storage lifecycle management, or assume that any storage service with 'tiering' in its name provides automated cost-optimized tiering for REST-accessible data.

How to eliminate wrong answers

Option B is wrong because Azure Files uses the SMB protocol and does not support REST API access for video file processing; its tiering feature (Azure File Sync cloud tiering) is designed for on-premises caching, not automated cost-optimized tiering of rarely accessed files. Option C is wrong because Azure NetApp Files provides NFS/SMB volumes with capacity pools for high-performance workloads, but it lacks built-in automated lifecycle tiering to cheaper storage and is overkill for rarely accessed video files. Option D is wrong because Azure Disk Storage provides block-level managed disks for VMs, not REST API-accessible object storage, and has no lifecycle management feature to automatically move data to cheaper tiers.

328
MCQhard

A company is building a petabyte-scale data lake for analytics. They need a storage solution that supports a hierarchical namespace, POSIX-like permissions (ACLs), and is optimized for big data analytics workloads using Apache Spark and Hive. The data must be accessible over the Azure Blob Storage API. Which Azure data service should they use?

A.Azure Blob Storage (with flat namespace)
B.Azure Data Lake Storage Gen2
C.Azure NetApp Files
D.Azure HPC Cache
AnswerB

Azure Data Lake Storage Gen2 is the correct choice because it provides a hierarchical namespace atop Blob Storage, enabling POSIX-like ACLs and directory-level operations that Apache Spark and Hive require for efficient metadata-heavy workloads. It offers Hadoop-compatible access (ABFS driver) natively, supports petabyte-scale analytics, and retains Blob Storage API compatibility for existing applications. Unlike a flat namespace, the hierarchical namespace allows atomic, rename-based directory operations and fine-grained security, which are critical for high-throughput analytics pipelines exploring partition pruning and O(1) directory scans.

Why this answer

Azure Data Lake Storage Gen2 (ADLS Gen2) is the correct choice because it combines a hierarchical namespace with POSIX-like ACLs and is natively optimized for big data analytics workloads like Apache Spark and Hive. It exposes data through the Azure Blob Storage API, meeting all stated requirements for petabyte-scale analytics.

Exam trap

The trap here is that candidates often confuse Azure Blob Storage (which is object storage with a flat namespace) with ADLS Gen2, not realizing that the hierarchical namespace and POSIX ACLs are exclusive to ADLS Gen2 and critical for big data analytics engines like Spark and Hive.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage with a flat namespace lacks a hierarchical namespace and POSIX-like ACLs, making it unsuitable for Hive and Spark workloads that rely on directory structures and fine-grained permissions. Option C is wrong because Azure NetApp Files provides NFS/SMB access with POSIX permissions but does not support the Azure Blob Storage API, which is a stated requirement. Option D is wrong because Azure HPC Cache is a caching layer for high-performance computing, not a persistent data lake storage service, and it does not provide a hierarchical namespace or native Blob API access.

329
MCQeasy

A company is deploying a web application that must scale out automatically based on CPU usage. The application runs on Azure App Service. Which Azure feature should they configure?

A.Autoscale rules
B.Azure Front Door
C.Azure Load Balancer
D.Azure Traffic Manager
AnswerA

Autoscale rules are the only option that directly modifies the compute capacity of the App Service plan. They let you configure scale conditions based on runtime metrics such as CPU percentage, request queue length, or a custom Application Insights metric, and you can set minimum and maximum instance counts. When a metric threshold is breached, the service adds or removes instances to keep the app responsive, and you can even schedule scale actions for known load patterns.

Why this answer

Autoscale rules in Azure App Service allow the application to automatically increase or decrease the number of instances based on CPU usage metrics. This is the correct feature for scaling out a web application horizontally in response to load, as it directly adjusts the instance count of the App Service Plan.

Exam trap

The trap here is that candidates often confuse load-balancing services (Front Door, Load Balancer, Traffic Manager) with autoscaling, but only Autoscale rules directly adjust the number of compute instances based on a metric like CPU usage.

How to eliminate wrong answers

Option B is wrong because Azure Front Door is a global load balancer and application delivery controller that provides SSL offloading, path-based routing, and acceleration, but it does not scale the underlying App Service instances based on CPU usage. Option C is wrong because Azure Load Balancer distributes incoming traffic at the transport layer (TCP/UDP) to virtual machines in a backend pool, but it does not provide automatic scaling based on CPU metrics for App Service. Option D is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that routes users to different endpoints based on geographic location or endpoint health, but it does not scale out the application instances based on CPU usage.

330
MCQeasy

A small business is migrating its on-premises file server to Azure. The file server contains 2 TB of data that is accessed infrequently. The business wants to minimize costs and only pay for storage used. The solution must support SMB protocol and allow for on-premises caching to reduce latency. Which Azure storage solution should the business recommend?

A.Azure Files Standard tier with Azure File Sync
B.Azure Disk Storage Standard HDD with shared disks
C.Azure NetApp Files Standard tier with cross-region replication
D.Azure Blob Storage Cool tier with Azure Storage Explorer
AnswerA

Azure Files Standard tier with Azure File Sync is the correct replacement for an on-premises file server because it provides fully managed SMB 3.0 file shares that support NTFS ACLs, Active Directory identity-based authentication, and Windows-native access semantics. Azure File Sync goes further by keeping a local cache of the most frequently used files on the existing server, providing low-latency access for on-premises clients while transparently tiering older data to Azure. This delivers the exact file-sharing behavior and caching benefits a small business needs without requiring custom infrastructure or expensive enterprise storage.

Why this answer

Azure Files Standard tier with Azure File Sync is correct because it provides fully managed SMB file shares in the cloud, supports the required SMB protocol, and Azure File Sync enables on-premises caching to reduce latency. The Standard tier is cost-effective for infrequently accessed data, and the pay-as-you-go model minimizes costs by charging only for actual storage used.

Exam trap

The trap here is that candidates often confuse Azure Blob Storage with file storage, overlooking that Blob Storage does not support SMB protocol natively, and they may incorrectly choose it for cost savings without considering protocol requirements.

How to eliminate wrong answers

Option B is wrong because Azure Disk Storage Standard HDD with shared disks does not natively support the SMB protocol; it provides block-level storage that requires a VM to host a file server, adding management overhead and cost. Option C is wrong because Azure NetApp Files Standard tier is a premium, high-performance solution that is significantly more expensive than Azure Files, and cross-region replication is unnecessary for a small business with infrequently accessed data. Option D is wrong because Azure Blob Storage Cool tier does not support the SMB protocol natively; it is object storage accessed via REST APIs or tools like Azure Storage Explorer, not a file share solution.

331
MCQmedium

Your company has a critical application running on Azure Virtual Machines that processes financial transactions. You need to ensure that the application remains available during an Azure region failure. The application is stateless and can scale horizontally. What is the most cost-effective design to meet the availability requirement?

A.Deploy VMs in an active-active configuration across two Azure regions using Traffic Manager and Azure Front Door.
B.Deploy VMs in an availability zone in the primary region and use Azure Site Recovery to replicate to a secondary region.
C.Deploy VMs in an availability set in the primary region and use Azure Site Recovery to failover to a secondary region.
D.Deploy VMs in a single region using Virtual Machine Scale Sets with automatic scaling.
AnswerB

This design places VMs in an availability zone in the primary region to guard against datacenter-level failures, while Azure Site Recovery (ASR) continuously replicates the VMs to a secondary region using asynchronous disk replication. ASR enables an orchestrated, controlled failover to the secondary region when the entire primary region becomes unavailable, and because the secondary resources are only started during failover (or remain deallocated), you avoid paying for idle compute capacity in the passive region. This active-passive approach provides both zone-level and region-level resilience, making it the optimal cost-availability balance for a critical stateless application.

Why this answer

Deploying VMs across availability zones within a region protects against datacenter-level failures, but for region-level failures, Azure Site Recovery (ASR) provides cost-effective disaster recovery by replicating VMs to a secondary region. Since the application is stateless and horizontally scalable, you can run a minimal footprint in the primary region and use ASR for orchestrated failover, avoiding the cost of always-on active-active infrastructure.

Exam trap

The trap here is that candidates often assume active-active across regions is always the best for high availability, but the question specifically asks for the most cost-effective design, and Azure Site Recovery with a single-region primary and DR replication is cheaper than maintaining dual-region active-active compute.

How to eliminate wrong answers

Option A is wrong because deploying active-active across two regions with Traffic Manager and Azure Front Door is over-engineered and costly for a stateless application that can scale horizontally; it incurs continuous egress and compute costs in both regions without necessity. Option C is wrong because an availability set only protects against rack-level failures within a single datacenter, not an Azure region failure, and ASR failover to a secondary region is still needed but the primary region design is insufficient. Option D is wrong because deploying VMs in a single region with Virtual Machine Scale Sets provides no protection against a full region outage, regardless of auto-scaling capabilities.

332
MCQeasy

A company wants to store log data from multiple applications for up to 30 days for analysis. The data is append-only, and queries are infrequent but need to be fast when run. Which Azure data storage solution should you recommend?

A.Azure Log Analytics Workspace
B.Azure Table Storage
C.Azure Data Lake Storage Gen2
D.Azure Blob Storage (archive tier)
AnswerA

Log Analytics Workspace ingests append-only log data and retains it for a configurable period, here 30 days. Its Kusto query engine returns fast results on infrequent ad hoc queries, unlike blob storage, which suits archival rather than interactive analysis.

Why this answer

Azure Log Analytics Workspace is the correct choice because it is purpose-built for ingesting, storing, and querying log data from multiple sources. It supports append-only log ingestion, retains data for up to 30 days in its interactive retention tier (configurable), and provides fast Kusto Query Language (KQL) queries for infrequent analysis. The workspace integrates natively with Azure Monitor and other services, making it ideal for centralized log analysis.

Exam trap

The trap here is that candidates often choose Azure Blob Storage (archive tier) for cost savings, overlooking the explicit requirement for fast query performance, which the archive tier cannot provide due to its multi-hour rehydration latency.

How to eliminate wrong answers

Option B is wrong because Azure Table Storage is a NoSQL key-value store designed for structured, transactional data, not for log analytics; it lacks native query capabilities for time-series log data and does not support fast, ad-hoc queries across multiple log sources. Option C is wrong because Azure Data Lake Storage Gen2 is optimized for big data analytics on large volumes of unstructured or semi-structured data, not for low-latency, infrequent queries on append-only logs; it is better suited for batch processing and data lakes. Option D is wrong because Azure Blob Storage (archive tier) is designed for long-term, cold storage with high retrieval latency (hours), not for fast queries on recent log data; it is cost-effective for archival but violates the requirement for fast query performance.

333
MCQhard

Refer to the exhibit. A user reports they cannot access a secret in the vault 'vault-prod'. The user has a Contributor role at the subscription scope and a Key Vault Secrets User role at the specific vault scope. What is the most likely reason for the failure?

A.The user does not have write permissions on the vault.
B.The vault uses access policies instead of RBAC for authorization.
C.The Key Vault Secrets User role does not allow reading secrets.
D.The scope of the Key Vault Secrets User role is incorrect.
AnswerB

Key Vault can authorize data-plane access either through the older vault access policy model or through Azure RBAC, and the two are mutually exclusive for a given vault. When the vault is set to use access policies, Azure RBAC role assignments such as Key Vault Secrets User are not evaluated at all by the data plane, so the user will be denied even though the role appears correct. The fix is to switch the vault's access configuration to Azure RBAC, or more directly, add the user to the vault's access policy with Get and List permissions on secrets.

Why this answer

The user has the Key Vault Secrets User role at the vault scope, which grants read permissions to secrets via Azure RBAC. However, if the vault is configured to use access policies instead of RBAC for authorization, the RBAC role assignment is ignored. In that case, the user must be granted explicit permissions through the vault's access policy to read secrets.

The Contributor role at subscription scope does not include data plane permissions for Key Vault secrets.

Exam trap

The trap here is that candidates assume RBAC roles always apply to Key Vault data plane operations, forgetting that the vault's authorization model must be set to RBAC for those roles to take effect; otherwise, access policies override them.

How to eliminate wrong answers

Option A is wrong because the issue is about reading a secret, not writing; the user has the Key Vault Secrets User role which includes read permissions, so write permissions are irrelevant. Option C is wrong because the Key Vault Secrets User role specifically allows reading secrets (Microsoft.KeyVault/vaults/secrets/read). Option D is wrong because the role is assigned at the specific vault scope, which is correct for granting permissions to that vault.

334
MCQhard

Your company has multiple Azure subscriptions managed by different teams. You need to design a governance solution that ensures: 1) All subscriptions must have a consistent set of policies (e.g., allowed locations, allowed VM SKUs). 2) Compliance reports must be generated daily for each subscription. 3) Non-compliant resources must be automatically remediated where possible (e.g., add tags). 4) The solution must use a single management group hierarchy. What should you include in the design?

A.Create a management group hierarchy, assign Azure Policy at the root management group level with both 'audit' and 'deployIfNotExists' effects, and use a daily Logic App to query compliance via Azure Resource Graph and send reports.
B.Create a management group hierarchy and use Azure Blueprints to assign policies and role assignments per subscription.
C.Use Azure DevOps to deploy a pipeline that runs PowerShell scripts to enforce policies and generate reports.
D.Create a custom Azure Policy initiative with all required policies and assign it to each subscription individually.
AnswerA

Assigning Azure Policy at the root management group scopes the policy to all nested subscriptions, ensuring uniform governance across the entire tenant. Using both audit and deployIfNotExists effects allows you to first assess non-compliant resources and then automatically trigger remediation tasks to fix them without manual intervention. A daily Logic App calling Azure Resource Graph to query compliance aggregates results across subscriptions and can automatically email a report, providing a scalable, native reporting mechanism.

Why this answer

Assigning Azure Policy at the root management group level ensures consistent policy enforcement across all subscriptions in the hierarchy. The 'deployIfNotExists' effect enables automatic remediation (e.g., adding missing tags), while a daily Logic App querying Azure Resource Graph can generate compliance reports without manual intervention. This design satisfies all requirements with a single management group hierarchy.

Exam trap

The trap here is that candidates may assume Azure Blueprints (Option B) are required for consistent governance, but Blueprints are for initial environment setup, not ongoing policy enforcement and automatic remediation, which is the core of this question.

How to eliminate wrong answers

Option B is wrong because Azure Blueprints assign policies per subscription or management group, but they do not provide built-in automatic remediation or daily compliance reporting; they are primarily for environment composition, not ongoing governance. Option C is wrong because using Azure DevOps with PowerShell scripts is a custom, non-native approach that lacks the automatic remediation capabilities of Azure Policy's 'deployIfNotExists' effect and requires manual pipeline maintenance. Option D is wrong because assigning a custom initiative to each subscription individually violates the requirement to use a single management group hierarchy and creates administrative overhead, failing to enforce consistency at the root level.

335
MCQmedium

A company is deploying a web application on Azure App Service. They need to guarantee that all traffic from the internet goes through a Web Application Firewall (WAF) before reaching the app. The solution must be cost-effective for a single application. Which Azure service should they place in front of the App Service?

A.Azure Application Gateway with WAF.
B.Azure Front Door with WAF policy.
C.Azure Firewall with application rules.
D.Azure Traffic Manager.
AnswerA

Application Gateway is a regional Layer 7 load balancer that integrates WAF. It can be placed directly in front of App Service to inspect all incoming traffic. This is a cost-effective solution for a single-region application.

Why this answer

Azure Application Gateway with WAF is the correct choice because it provides a regional, layer-7 load balancer with built-in Web Application Firewall capabilities, designed to protect web applications from common exploits and vulnerabilities. For a single application, it is more cost-effective than Azure Front Door, which is a global service with higher minimum costs and additional features not required here. Application Gateway can be deployed directly in front of App Service to inspect and filter all internet traffic before it reaches the app.

Exam trap

The trap here is that candidates often confuse Azure Front Door with Application Gateway, assuming Front Door is always the better choice for WAF, but the question's emphasis on cost-effectiveness for a single application points to the regional, lower-cost Application Gateway instead.

How to eliminate wrong answers

Option B is wrong because Azure Front Door is a global, multi-region load balancer and application delivery network; while it supports WAF policies, it is designed for multi-region deployments and incurs higher costs, making it less cost-effective for a single application. Option C is wrong because Azure Firewall is a network-layer firewall that filters traffic based on IP addresses, ports, and protocols, not at the application layer (HTTP/HTTPS), so it cannot provide Web Application Firewall capabilities to inspect and block web application attacks like SQL injection or cross-site scripting. Option D is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that routes traffic based on routing methods (e.g., performance, priority) but does not include any WAF or application-layer inspection capabilities.

336
MCQmedium

Your company is migrating a legacy on-premises application to Azure. The application requires persistent storage for configuration files that must be accessible from multiple virtual machines in a virtual network. The storage must be accessible only from within the virtual network and should not be exposed to the internet. Which Azure storage solution should you use?

A.Azure Disk Storage with shared disks
B.Azure NetApp Files with network security groups
C.Azure Blob Storage with a service endpoint
D.Azure Files with a private endpoint
AnswerD

Azure Files provides fully managed SMB file shares (also supports NFS for premium tiers) that can be mounted concurrently by multiple VMs, making it the most direct migration target for a legacy on-premises file-based application. By configuring a private endpoint, the file share is assigned a private IP address within your Azure virtual network, eliminating exposure to the public internet and ensuring traffic stays on the Microsoft backbone. Private endpoints also integrate with NSGs, private DNS zones, and Azure Active Directory authentication, giving you fine-grained access control and meeting security requirements without sacrificing the native file-protocol compatibility that legacy applications rely on.

Why this answer

Azure Files with a private endpoint is the correct choice because it provides fully managed file shares accessible via SMB or NFS protocols, supports persistent storage for configuration files, and ensures the storage is accessible only from within the virtual network by assigning a private IP address from the VNet, eliminating internet exposure. This meets the requirement for multi-VM access with network isolation.

Exam trap

The trap here is that candidates often confuse service endpoints (which still expose the storage to the internet at the endpoint level) with private endpoints (which fully isolate the resource within the VNet), and they may overlook that Azure Files supports SMB for shared file access while Blob Storage does not.

How to eliminate wrong answers

Option A is wrong because Azure Disk Storage with shared disks is a block-level storage solution designed for clustered applications (e.g., SQL Server FCI) and does not natively support file-level access or SMB/NFS protocols required for configuration files; it also cannot be easily accessed from multiple VMs without complex clustering. Option B is wrong because Azure NetApp Files is a high-performance file service that can use network security groups, but it is overkill for simple configuration files and incurs higher cost and complexity; more critically, NSGs alone do not guarantee complete internet isolation—a private endpoint is the proper method for VNet-only access. Option C is wrong because Azure Blob Storage with a service endpoint still exposes the storage account to the public internet (though restricted to the VNet), and Blob Storage is object storage not designed for file-sharing protocols like SMB, making it unsuitable for configuration files that need to be mounted as a drive.

337
MCQhard

You are designing a business continuity solution for a globally distributed SaaS application that uses Azure Cosmos DB for its operational store. The application must survive a complete regional outage with zero data loss and automatic failover. What should you use?

A.Configure a single write region in Cosmos DB with eventual consistency and manual failover.
B.Configure Cosmos DB with a single write region, strong consistency, and enable automatic failover to a secondary region.
C.Enable multi-region writes in Cosmos DB with eventual consistency and automatic failover.
D.Use Azure SQL Database with active geo-replication and automatic failover.
AnswerB

Strong consistency in Azure Cosmos DB ensures that all reads return the most recently committed write, and with a single write region, writes are synchronously replicated to the secondary region before acknowledgment. This guarantees an RPO of zero because no acknowledged data is lost during a regional outage. Enabling automatic failover allows Cosmos DB to detect a region failure and redirect traffic without manual intervention, thereby satisfying the required RTO target.

Why this answer

It combines a single write region with strong consistency and automatic failover, which guarantees zero data loss during a regional outage. Strong consistency ensures that all reads reflect the latest write, and automatic failover allows Azure to promote a secondary read region to the primary write region without manual intervention, meeting the requirement for zero data loss and automatic failover.

Exam trap

The trap here is that candidates often assume multi-region writes (Option C) are necessary for zero data loss, but they overlook that multi-region writes require eventual consistency and conflict resolution, which can lead to data loss or conflicts, whereas a single write region with strong consistency and automatic failover provides the strictest guarantee of zero data loss.

How to eliminate wrong answers

Option A is wrong because eventual consistency does not guarantee zero data loss—writes acknowledged in the primary region may not be replicated to the secondary before a failover, leading to potential data loss. Option C is wrong because multi-region writes with eventual consistency can cause write conflicts and does not guarantee zero data loss; conflict resolution may drop or merge writes, violating the zero data loss requirement. Option D is wrong because Azure SQL Database with active geo-replication is not the correct service for a globally distributed SaaS application that uses Azure Cosmos DB as its operational store; the question specifically requires a Cosmos DB solution, and SQL Database does not provide the same global distribution and multi-model capabilities.

338
MCQeasy

A company uses Microsoft Entra ID and wants to allow users to sign in using their existing personal Microsoft accounts, Google, and Facebook identities. They also need custom sign-up and sign-in flows with collection of specific user attributes. Which Microsoft Entra ID feature should they use?

A.Microsoft Entra ID B2B
B.Microsoft Entra ID B2C
C.Microsoft Entra ID Identity Protection
D.Microsoft Entra ID Conditional Access
AnswerB

Microsoft Entra ID B2C is the correct solution because it is a Customer Identity and Access Management (CIAM) service built specifically to handle consumer identities at scale. It natively supports multiple identity providers, including Microsoft, Google, and Facebook, and provides self-service sign-up/sign-in user flows. With the Identity Experience Framework, you can define custom policies that collect custom attributes, perform API-based validation, and create fully branded, tailored registration journeys for customers, which is exactly what this company needs.

Why this answer

Microsoft Entra ID B2C (Business-to-Consumer) is the correct choice because it is specifically designed to support external identity providers like personal Microsoft accounts, Google, and Facebook, and it provides a customizable policy framework (user flows) for sign-up and sign-in that can collect custom user attributes. Unlike B2B, which focuses on business partner collaboration, B2C allows you to define attribute collection during registration via built-in or custom policies.

Exam trap

The trap here is that candidates often confuse Entra ID B2B with B2C, assuming B2B can handle consumer identities and custom sign-up flows, but B2B is strictly for business partner collaboration and lacks the user flow customization and social identity provider support that B2C provides.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra ID B2B is intended for business-to-business collaboration, allowing external users from partner organizations to access your apps using their work or school accounts, not personal Microsoft accounts, Google, or Facebook identities, and it does not support custom sign-up flows with attribute collection. Option C is wrong because Microsoft Entra ID Identity Protection is a security feature that detects and responds to identity-based risks (e.g., leaked credentials, sign-in anomalies) and does not provide federation with external identity providers or custom sign-up flows. Option D is wrong because Microsoft Entra ID Conditional Access is a policy engine that enforces access controls (e.g., MFA, device compliance) based on conditions like user, location, or risk, but it cannot configure external identity providers or custom sign-up/attribute collection.

339
MCQeasy

A company is using Azure SQL Database for a critical application. They need to ensure that the database is automatically backed up and that backups are retained for 35 days. What should they configure?

A.Enable long-term retention (LTR) for backups
B.Configure the point-in-time restore (PITR) retention to 35 days
C.Configure active geo-replication
D.Use Azure Backup to back up the SQL Database
AnswerB

Azure SQL Database automatically takes full, differential, and transaction log backups, and PITR retention is configurable up to 35 days for most service tiers. This enables restoring to any point in time within that window, directly meeting the requirement. By configuring the PITR retention to 35 days, the organization ensures that automated backups are retained long enough to recover to any second within the past 35 days, which is the standard mechanism for backup retention in Azure SQL Database.

Why this answer

Azure SQL Database has a default point-in-time restore (PITR) retention period of 7 days, which can be configured up to 35 days. By setting the PITR retention to 35 days, the company ensures that automated backups are retained for the required duration, allowing restoration to any point within that window. This meets the requirement without additional services or configurations.

Exam trap

The trap here is that candidates may confuse long-term retention (LTR) with the standard automated backup retention, thinking LTR is required for any retention beyond the default 7 days, when in fact PITR can be extended to 35 days without enabling LTR.

How to eliminate wrong answers

Option A is wrong because long-term retention (LTR) is used for retaining backups beyond 35 days (up to 10 years), not for meeting a 35-day retention requirement. Option C is wrong because active geo-replication provides disaster recovery by maintaining a readable secondary database in a different region, but it does not control backup retention periods. Option D is wrong because Azure Backup is not used for Azure SQL Database; automated backups are built-in and managed by the platform, and Azure Backup is intended for on-premises SQL Server or Azure VMs running SQL Server.

340
Multi-Selectmedium

Which THREE Azure services can be used to monitor the performance of a web application? (Choose three.)

Select 3 answers
A.Azure Policy
B.Application Insights
C.Azure Monitor Metrics
D.Microsoft Defender for Cloud
E.Azure Monitor Logs
AnswersB, C, E

Application Insights collects request rates, response times, dependency calls and failures through the SDK or auto-instrumentation, providing end-to-end telemetry for a web application. It satisfies the monitoring requirement by surfacing performance and availability data at the application layer.

Why this answer

Application Insights (B) is correct because it is the APM feature of Azure Monitor that automatically collects request rates, response times, failure rates, dependency calls, and server/client performance telemetry for web applications. Azure Monitor Metrics (C) is correct because it stores numeric time-series performance data such as CPU percentage, memory usage, request counts, and response times that can be charted and alerted on. Azure Monitor Logs (E) is correct because Log Analytics workspaces collect and query detailed telemetry (e.g., via KQL over AppRequests, Perf, and AppTraces tables) to analyze web app performance and trends.

Azure Policy (A) is incorrect because it enforces governance and compliance rules on resources rather than monitoring runtime performance. Microsoft Defender for Cloud (D) is incorrect because it provides security posture management and threat protection, not application performance monitoring.

Exam trap

The trap here is that candidates often confuse governance tools like Azure Policy or security tools like Defender for Cloud with performance monitoring, but the exam specifically tests the distinction between monitoring (Application Insights, Metrics, Logs) and management/security services.

341
MCQmedium

Your company uses Microsoft Entra ID and has a custom application that requires users to have specific roles assigned. You need to ensure that role assignments are reviewed quarterly and automatically remove assignments that are not approved. Which feature should you use?

A.Microsoft Entra Privileged Identity Management
B.Microsoft Entra Identity Protection
C.Microsoft Entra ID Governance access reviews
D.Microsoft Entra Conditional Access
AnswerC

Microsoft Entra ID Governance access reviews is the correct answer because it is specifically designed for periodic, auditable re-certification of access. Administrators can create a review campaign targeting a single role or multiple role assignments, delegate reviewers (such as department managers or resource owners), and configure scheduled recurrence for the review. Reviewers approve or deny an assignment, and the system can enforce the decision by automatically removing a denied user's role at the end of the review period. This directly supports the requirement to periodically review role assignments and automatically remove users who no longer need access, which is the hallmark of identity governance and least-privilege management.

Why this answer

Microsoft Entra ID Governance access reviews enable you to create recurring reviews of role assignments, with automatic removal of assignments that reviewers do not approve. This directly meets the requirement for quarterly reviews and automatic removal of unapproved assignments, making it the correct choice.

Exam trap

The trap here is that candidates often confuse Privileged Identity Management (PIM) with access reviews, but PIM handles just-in-time activation and approval, not recurring reviews with automatic removal of unapproved assignments.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra Privileged Identity Management (PIM) provides just-in-time role activation and approval workflows for privileged roles, but it does not natively support recurring access reviews with automatic removal of unapproved assignments. Option B is wrong because Microsoft Entra Identity Protection focuses on detecting and remediating identity-based risks (e.g., compromised credentials, sign-in anomalies) and does not manage role assignment reviews or removals. Option D is wrong because Microsoft Entra Conditional Access enforces access policies based on conditions like location or device state, but it does not provide periodic review or automatic removal of role assignments.

342
Drag & Dropmedium

Drag and drop the steps to deploy a web app using Azure App Service with a custom domain and SSL certificate into the correct order.

Drag or tap steps into the slots.

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

Why this order

The correct order for deploying a web app using Azure App Service with a custom domain and SSL certificate is: create the App Service app, map the custom domain, upload the SSL certificate, bind the certificate to the domain, and finally enforce HTTPS. This sequence ensures that each step has the necessary prerequisites: the app exists before domain mapping, the domain is mapped before certificate upload and binding, and the certificate is bound before enforcing HTTPS.

343
MCQeasy

Your company has a web application deployed on Azure App Service that experiences periodic traffic spikes. You need to ensure the application scales out quickly without manual intervention. The solution must minimize cost during low-traffic periods. What should you configure?

A.Enable pre-warming in the App Service plan
B.Configure Autoscale rules based on CPU or memory metrics
C.Deploy the app to a Virtual Machine Scale Set
D.Manually increase the instance count before expected spikes
AnswerB

Configuring autoscale rules is the proper PaaS-native mechanism for Azure App Service to automatically adjust the instance count of your App Service plan. You define scale conditions based on metrics such as CPU percentage, memory consumption, or request queue length, and Autoscale adds or removes instances in response to those thresholds. This is a fully automated, reactive approach that continuously monitors load and eliminates the need for manual intervention.

Why this answer

Autoscale rules based on CPU or memory metrics allow the App Service to automatically increase or decrease the number of instances in response to traffic spikes, meeting the requirement for quick scaling without manual intervention. By scaling down during low-traffic periods, it minimizes cost, as you only pay for the instances you use. This is the native Azure App Service scaling feature that directly addresses the need for elastic, cost-effective scaling.

Exam trap

The trap here is that candidates often confuse pre-warming (Option A) with autoscaling, thinking it handles scaling automatically, but pre-warming only prepares instances for a planned scale event and does not react to real-time metrics.

How to eliminate wrong answers

Option A is wrong because pre-warming is a feature for reducing cold-start latency on new instances, not for triggering scale-out events; it does not automate scaling based on load. Option C is wrong because Virtual Machine Scale Sets are designed for IaaS workloads, not for PaaS web apps on App Service, and would require additional management overhead and cost for the same functionality. Option D is wrong because manually increasing the instance count violates the requirement for 'quickly without manual intervention' and cannot react to unexpected spikes in real time.

344
MCQmedium

You are designing a governance strategy for Azure resources. The company has multiple departments, each requiring separate cost tracking and policy enforcement. You need to organize resources to align with the departments while minimizing management overhead. What should you use?

A.Management groups
B.Azure Blueprints
C.Resource tags
D.Resource groups
AnswerA

Management groups provide a hierarchical governance structure above subscriptions, allowing you to apply Azure Policy and RBAC assignments at scale, and aggregate cost data across multiple subscriptions for consolidated billing and compliance. They enable enterprise-level organization of your Azure estate, with policies and governance inherited down through child management groups and subscriptions.

Why this answer

Management groups are the correct choice because they allow you to organize Azure subscriptions into a hierarchy that aligns with your organizational structure, enabling you to apply Azure Policy and cost management controls at scale across multiple departments. By placing each department's subscriptions into separate management groups, you can enforce department-specific policies and track costs without managing each subscription individually, minimizing administrative overhead.

Exam trap

The trap here is that candidates often confuse resource tags with a governance mechanism for policy enforcement and cost tracking, but tags are only metadata and cannot enforce policies or aggregate costs across subscriptions like management groups can.

How to eliminate wrong answers

Option B (Azure Blueprints) is wrong because Blueprints are used to define a repeatable set of Azure resources and policies for deploying compliant environments, not for organizing existing resources or subscriptions for cost tracking and policy enforcement across departments. Option C (Resource tags) is wrong because tags are metadata key-value pairs applied to resources for filtering and reporting, but they do not provide hierarchical policy enforcement or cost aggregation at the subscription or management group level. Option D (Resource groups) is wrong because resource groups are logical containers for resources within a single subscription, and they cannot span subscriptions or provide the cross-subscription policy and cost management needed for multiple departments.

345
MCQeasy

A company needs to store immutable audit logs for regulatory compliance. The logs must be stored in a write-once, read-many (WORM) state for 7 years. Which Azure storage feature should be used?

A.Azure Blob Storage immutable storage with time-based retention
B.Azure SQL Database temporal tables
C.Azure Blob Storage change feed
D.Azure Blob Storage soft delete
AnswerA

Azure Blob Storage immutable storage with time-based retention enforces a Write-Once-Read-Many (WORM) policy at the container level, preventing any blob from being modified or deleted during a user-defined retention interval. This satisfies regulatory audit-log requirements such as SEC 17a-4(f) because even the storage account owner cannot alter or purge the data until the period expires, and it can optionally be combined with legal holds for indefinite preservation.

Why this answer

Azure Blob Storage immutable storage with time-based retention enforces a WORM (Write Once, Read Many) state, preventing logs from being modified or deleted for a specified retention period. This directly meets the regulatory requirement to store audit logs immutably for 7 years, as the policy locks the data at the container or blob level and cannot be removed until the retention interval expires.

Exam trap

The trap here is that candidates confuse soft delete or change feed with immutable storage, not realizing that only immutable storage enforces a true WORM state that prevents both deletion and overwriting, which is required for regulatory compliance.

How to eliminate wrong answers

Option B is wrong because Azure SQL Database temporal tables track historical changes to data but do not enforce WORM immutability; data can still be physically deleted or altered by privileged users. Option C is wrong because Azure Blob Storage change feed provides a transaction log of blob changes for processing, not a mechanism to prevent modifications or deletions. Option D is wrong because Azure Blob Storage soft delete only offers recovery from accidental deletion within a retention window, but does not prevent overwrites or enforce a write-once state.

346
MCQhard

Your company, Contoso Ltd., operates a global e-commerce platform hosted on Azure. The architecture consists of: (1) A web front-end running on Azure App Service in multiple regions (East US, West Europe, Southeast Asia). (2) A microservices backend running on Azure Kubernetes Service (AKS) in East US. (3) A SQL Database in East US with geo-replication to West Europe and Southeast Asia for read scaling. (4) Azure Redis Cache for session state. (5) Azure Front Door for global load balancing. The platform experiences periodic traffic spikes, and during a recent spike, users reported slow page loads and intermittent errors. The operations team observed that the SQL Database in East US reached 100% DTU consumption, causing timeouts. The geo-replicated databases in other regions were underutilized. The application logic is read-heavy but also writes to a separate write-only table. You need to design a solution to improve scalability and reduce database load. The solution must: minimize latency for users, ensure write consistency, and handle traffic spikes without over-provisioning. What should you do?

A.Upgrade the SQL Database in East US to a higher DTU tier and enable auto-scaling.
B.Configure read-only routing in the application connection string to use the geo-replicated databases for read queries, and keep writes directed to the primary.
C.Implement a second-level cache using Azure Cache for Redis with a local cache pattern in the web front-end.
D.Shard the database by customer region and deploy shards in each region.
AnswerB

For an Azure SQL Database with active geo-replication, you can set the application connection string to include ApplicationIntent=ReadOnly; the gateway then automatically routes incoming read-only queries to the nearest readable secondary, while the login remains pointed at the primary for any write transactions. This offloads the bulk of the SELECT traffic from the primary DTU pool, effectively increasing total system throughput without changing the database tier and saving the primary for writes. Because the geo-replicas already exist, the only change is a connection string property, making this the lowest-complexity, highest-leverage fix for a global read-heavy workload and the reason it is the correct answer.

Why this answer

It leverages the existing geo-replicated SQL Databases for read scaling without additional cost. By configuring read-only routing in the application connection string, read queries are automatically directed to the readable secondary replicas in West Europe and Southeast Asia, offloading the primary East US database. This reduces DTU consumption on the primary while maintaining write consistency, as all writes still go to the primary.

Azure SQL Database's active geo-replication supports this pattern, and Azure Front Door can route users to the nearest region for low latency.

Exam trap

The trap here is that candidates often choose Option A (upgrade DTU) because it seems like a direct fix for high DTU consumption, but they overlook the underutilized geo-replicated databases and the requirement to minimize latency globally without over-provisioning.

How to eliminate wrong answers

Option A is wrong because upgrading to a higher DTU tier and enabling auto-scaling only addresses the symptom (high DTU consumption) but does not utilize the underutilized geo-replicated databases, leading to over-provisioning and higher costs without improving global read latency. Option C is wrong because implementing a second-level cache with Azure Cache for Redis and a local cache pattern reduces database load for cached data but does not address the write-only table or the need to offload read traffic from the primary database; it also introduces cache invalidation complexity for write-heavy scenarios. Option D is wrong because sharding by customer region requires significant application redesign, complicates cross-region queries, and does not leverage the existing geo-replication; it also risks write consistency issues if shards are not properly synchronized.

347
MCQmedium

A company deploys a containerized application on Azure Kubernetes Service (AKS). They need to expose the application to the internet and provide TLS termination. The solution must also include a Web Application Firewall (WAF) to protect against common attacks. Which Azure service should they use as the ingress controller?

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

Azure Application Gateway, when integrated as the Application Gateway Ingress Controller (AGIC), is the native Azure L7 load balancer that serves as an ingress gateway for AKS clusters. It terminates TLS connections at the gateway, decrypts HTTP traffic, and enforces Web Application Firewall policies (such as OWASP CRS rules) before forwarding requests to AKS pods. This makes it the correct solution for the requirement of TLS termination and WAF in an AKS environment.

Why this answer

Azure Application Gateway is the correct choice because it is a layer-7 load balancer that can act as an ingress controller for AKS, providing TLS termination and a built-in Web Application Firewall (WAF) to protect against common attacks like SQL injection and cross-site scripting. It integrates directly with AKS via the Application Gateway Ingress Controller (AGIC) add-on, allowing it to route external HTTP/HTTPS traffic to containerized applications while offloading SSL/TLS processing and enforcing WAF policies at the edge.

Exam trap

The trap here is that candidates often confuse Azure Front Door with Application Gateway because both provide WAF and TLS termination, but Front Door is a global service for multi-region traffic distribution, not a direct AKS ingress controller that can route to pods within a single cluster.

How to eliminate wrong answers

Option B (Azure Front Door) is wrong because it is a global, multi-region load balancer and application delivery network that operates at layer 7, but it is not designed as an AKS ingress controller; it sits in front of the cluster and cannot directly route traffic to AKS pods without an additional ingress controller like Application Gateway or NGINX. Option C (Azure Load Balancer) is wrong because it operates at layer 4 (TCP/UDP) and cannot perform TLS termination or WAF inspection; it only distributes traffic at the network level without understanding HTTP/HTTPS protocols. Option D (Azure Traffic Manager) is wrong because it is a DNS-based traffic router that operates at layer 3/4 and does not provide TLS termination or WAF capabilities; it only directs traffic based on DNS resolution and health probes, not application-layer routing.

348
MCQmedium

Your organization has a hybrid identity infrastructure with Microsoft Entra ID Connect Sync. You plan to enable Microsoft Entra ID Seamless Single Sign-On (Seamless SSO) for domain-joined Windows devices. What is the minimum requirement for the on-premises Active Directory forest functional level?

A.Windows Server 2016
B.Windows Server 2012
C.Windows Server 2008
D.Windows Server 2003
AnswerC

Windows Server 2008 is the exact minimum forest functional level required to enable Azure AD Seamless SSO. Microsoft's prerequisite documentation specifies that an on-premises forest must be at this level or higher, because the feature relies on Kerberos-based authentication and the creation of an AzureADKerberos computer account that is only supported on 2008 FFL and above. Thus, it is the only correct answer when identifying the minimum.

Why this answer

Microsoft Entra ID Seamless SSO works by having the client computer attempt Kerberos authentication against a local Active Directory domain controller using a special service principal name (AZUREADSSOACC). This process requires the on-premises Active Directory forest functional level to be at least Windows Server 2008, because the Kerberos service ticket used for Seamless SSO relies on the AES encryption type, which is only supported in domains with a Windows Server 2008 or higher functional level. Lower functional levels (2003 or earlier) do not support AES encryption, causing the authentication to fail.

Exam trap

The trap here is that candidates often assume the minimum requirement is based on the operating system version of the domain controllers (e.g., Windows Server 2012 or 2016) rather than the forest/domain functional level, which is a separate configuration that controls available Kerberos encryption types and features.

How to eliminate wrong answers

Option A is wrong because Windows Server 2016 is not the minimum requirement; the feature works with any functional level from Windows Server 2008 onward, so requiring 2016 would be unnecessarily restrictive. Option B is wrong because Windows Server 2012 is also above the minimum; while it supports Seamless SSO, it is not the lowest possible functional level. Option D is wrong because Windows Server 2003 functional level does not support AES encryption for Kerberos, which is required for the Seamless SSO authentication flow, and thus cannot be used.

349
MCQmedium

Refer to the exhibit. You are deploying NSG flow logs. After deployment, you notice that no logs are being written to the storage account. What is the most likely cause?

A.Network Watcher is not enabled in the region.
B.Retention policy is set to 0 days.
C.The storage account is in a different subscription.
D.The format version is incorrect.
AnswerA

NSG flow logs are implemented as a child resource of Network Watcher, so the Network Watcher provider must be registered and the regional Network Watcher instance must exist in the exact Azure region where the NSG resides. Without an active Network Watcher in that region, any attempt to enable flow logs fails with a provisioning error. This is the definitive root cause in this scenario.

Why this answer

NSG flow logs require Network Watcher to be enabled in the region where the NSG resides. If Network Watcher is not enabled, the flow logs cannot be written to the storage account because the logging pipeline depends on the Network Watcher agent to capture and forward flow data. Enabling Network Watcher in the region resolves this issue.

Exam trap

The trap here is that candidates often assume the retention policy (0 days) or storage account subscription mismatch is the root cause, but the actual issue is the missing regional Network Watcher dependency, which is a prerequisite for NSG flow logs to function.

How to eliminate wrong answers

Option B is wrong because a retention policy of 0 days means logs are deleted immediately after being written, but logs would still be written to the storage account initially. Option C is wrong because NSG flow logs support writing to a storage account in a different subscription as long as the appropriate RBAC permissions are configured. Option D is wrong because the format version (e.g., version 1 or 2) affects the schema of the logs but does not prevent logs from being written to the storage account.

350
Multi-Selecthard

Which THREE of the following are valid methods to secure access to Azure Storage accounts? (Choose three.)

Select 3 answers
A.Generate Shared Access Signatures (SAS) with limited permissions and expiry
B.Configure firewall rules and virtual network service endpoints
C.Enable Azure Front Door to authenticate requests
D.Use Azure AD RBAC to assign roles to users and applications
E.Use storage account access keys for authentication
AnswersA, B, D

SAS tokens provide scoped, time-bound delegated access to specific Azure Storage resources, such as a single blob, container, or queue, with granular permissions (read, write, delete, list) and an explicit expiry. A service SAS or user delegation SAS can be issued to clients without exposing the account key, and a stored access policy allows revocation by changing the policy. However, a poorly configured SAS with broad permissions or no expiry reduces its security value.

Why this answer

Shared Access Signatures (SAS) allow you to grant time-limited, delegated access to specific storage resources (e.g., blobs, queues) with granular permissions (read, write, delete) and an expiry time, without exposing the account key. This is a key security method for controlling access at the resource level.

Exam trap

The trap here is that candidates often confuse Azure Front Door (a traffic routing and CDN service) with an authentication gateway, or mistakenly think storage account access keys are a secure method for user access, when in fact they are equivalent to a root password and should be rotated and protected.

351
Multi-Selectmedium

A company is designing a backup and disaster recovery solution for an on-premises SQL Server database that will be migrated to Azure. The solution must meet the following requirements: 1) Point-in-time restore up to 30 days. 2) Cross-region restore in case of a regional disaster. 3) Long-term retention of backups for 7 years for compliance. Which THREE Azure services or features should the company use? (Choose three.)

Select 3 answers
A.Azure Backup Server
B.Azure Site Recovery
C.Azure Blob Storage
D.Azure Backup
E.Azure Recovery Services vault
AnswersB, D, E

Azure Site Recovery (ASR) is the Azure-native disaster recovery service that replicates Azure VMs from a primary region to a secondary region using continuous, asynchronous disk replication. It delivers a measurable RPO and RTO by enabling you to failover to replicated copies of the VMs, with options for planned, unplanned, and test failovers, all orchestrated through recovery plans. Because the company needs a disaster recovery solution, ASR is the exact service that meets that need, working alongside Azure Backup for point-in-time restore.

Why this answer

Azure Site Recovery (B) is correct because it provides cross-region replication and orchestrated failover for SQL Server, enabling disaster recovery with the ability to restore in a secondary Azure region. This directly meets the requirement for cross-region restore in case of a regional disaster.

Exam trap

The trap here is that candidates often confuse Azure Backup Server (a legacy on-premises tool) with Azure Backup (a cloud-native service), or assume Azure Blob Storage alone can fulfill backup and DR requirements without the orchestration and retention capabilities of Azure Backup and Site Recovery.

352
MCQeasy

A company is migrating on-premises applications to Azure. They require that all traffic between Azure resources and on-premises resources traverse a private connection. They also want to reduce the attack surface by eliminating exposure of management endpoints over the internet. Which solution should they implement?

A.Azure Firewall
B.Azure Front Door
C.Azure ExpressRoute with Private Link for Azure services
D.Azure VPN Gateway
AnswerC

Azure ExpressRoute creates a dedicated private circuit from your on-premises network into Azure through an MPLS or other network provider, completely bypassing the public internet to reduce latency and improve security. Pairing it with Azure Private Link extends your virtual network's private IP space to Azure PaaS services via private endpoints, so traffic between your datacenter and those services never traverses a public endpoint. This combination offers both a private transit network and private access to individual services, meeting strict compliance and isolation requirements.

Why this answer

Azure ExpressRoute provides a private, dedicated connection from on-premises to Azure, bypassing the public internet. By combining ExpressRoute with Private Link for Azure services, you ensure that traffic to Azure PaaS services (e.g., Azure SQL, Storage) traverses only the private connection and that the service endpoints are not exposed over the internet, reducing the attack surface. This directly meets the requirement for private connectivity and elimination of public management endpoints.

Exam trap

The trap here is that candidates often confuse Azure VPN Gateway with ExpressRoute, thinking that an encrypted tunnel provides equivalent privacy and security, but VPN Gateway still uses the public internet for transit, whereas ExpressRoute is a dedicated private connection that completely bypasses the internet.

How to eliminate wrong answers

Option A is wrong because Azure Firewall is a managed network security service that filters traffic, but it does not provide a private connection between on-premises and Azure; traffic still flows over the internet or through a VPN/ExpressRoute, and it does not eliminate exposure of management endpoints. Option B is wrong because Azure Front Door is a global load balancer and application delivery controller that operates over the public internet; it does not provide a private connection and does not remove internet exposure of endpoints. Option D is wrong because Azure VPN Gateway creates an encrypted tunnel over the public internet, which still exposes traffic to internet transit and does not provide the dedicated private connection required; it also does not eliminate exposure of management endpoints.

353
MCQhard

A company is designing a hub-spoke network topology across multiple Azure regions. They plan to deploy a third-party network virtual appliance (NVA) in the hub for traffic inspection. They require that all traffic between spokes in different regions must be routed through the hub NVA, and they want to minimize the number of peered connections. Which solution should they implement?

A.VNet peering with user-defined routes (UDRs) in each spoke pointing to the NVA IP in the hub
B.Azure Virtual WAN with a secured hub using Azure Firewall
C.Azure VNet-to-VNet VPN gateways between all spokes
D.Azure ExpressRoute with private peering
AnswerA

VNet peering with UDRs is the correct approach because Azure VNet peering is non-transitive, so spokes cannot reach each other through the hub unless traffic is explicitly directed to the NVA. You associate a route table with each spoke subnet, adding a UDR with next hop type 'Virtual Appliance' and the NVA's private IP, and you must enable IP forwarding on the NVA's NIC. This enforces all inter-spoke traffic through the NVA while maintaining only one peering connection per spoke, which is the minimal, cost-effective hub-and-spoke design for a third-party firewall or router.

Why this answer

VNet peering combined with user-defined routes (UDRs) allows traffic between spokes in different regions to be forced through the NVA in the hub for inspection. By configuring UDRs in each spoke with the next hop set to the NVA's private IP, you ensure inter-spoke traffic traverses the hub without requiring a full mesh of peering connections. This minimizes the number of peered connections (only hub-to-spoke peering is needed) while meeting the routing requirement.

Exam trap

The trap here is that candidates often assume Virtual WAN (Option B) is the only way to simplify hub-spoke routing, but it does not support custom third-party NVAs for traffic inspection without complex workarounds, making VNet peering with UDRs the correct choice for this specific requirement.

How to eliminate wrong answers

Option B is wrong because Azure Virtual WAN with a secured hub using Azure Firewall introduces a managed service that may not support a third-party NVA for traffic inspection; it is designed for Azure Firewall or third-party security providers via integrated partners, not a custom NVA. Option C is wrong because Azure VNet-to-VNet VPN gateways between all spokes would create a full mesh of VPN connections, increasing complexity and cost, and it does not force traffic through the hub NVA unless additional routing is configured, which still requires more connections than hub-spoke peering. Option D is wrong because Azure ExpressRoute with private peering provides a dedicated private connection to on-premises networks, not routing between spokes in different regions; it does not address inter-spoke traffic inspection or minimize peered connections.

354
MCQhard

You are reviewing a recovery plan for Azure Site Recovery. The exhibit shows a snippet of the recovery plan configuration. What is the purpose of the script action defined in the exhibit?

A.To run a custom script on the recovered VMs after they boot up during test and unplanned failover.
B.To run a script before the VMs shut down during failover.
C.To update the Azure DNS records after failover.
D.To run a script only during planned failover from the primary to the recovery region.
AnswerA

This correctly describes the purpose. In Azure Site Recovery recovery plans, script actions are grouped into Boot and Shutdown groups, with the Boot group running after the virtual machines have started. The recovery plan is triggered for both Test Failover and Unplanned Failover, as indicated by the failoverTypes settings, so the custom script executes post-boot in those scenarios. This is a common way to perform configuration, application startup, or health checking on the recovered instances.

Why this answer

The script action in an Azure Site Recovery recovery plan is configured to run after the VMs have booted up, allowing custom tasks such as installing software, modifying configurations, or verifying connectivity. This is supported during both test failover and unplanned failover, as the script executes post-boot on the recovered VMs.

Exam trap

The trap here is that candidates confuse the script action's timing (post-boot) with pre-shutdown actions or assume it only applies to planned failover, overlooking the test and unplanned failover checkboxes in the exhibit.

How to eliminate wrong answers

Option B is wrong because a script action defined in the recovery plan runs after VMs boot, not before they shut down; pre-shutdown scripts are configured separately in the plan's pre-group actions. Option C is wrong because Azure Site Recovery does not natively update Azure DNS records; DNS updates require custom scripting or Azure Automation runbooks, but the exhibit shows a script action, not a DNS-specific action. Option D is wrong because the script action in the exhibit is not limited to planned failover; it applies to test and unplanned failover as well, as indicated by the 'Failover' and 'Test Failover' checkboxes.

355
MCQeasy

A company has an Azure subscription with a Log Analytics workspace. They need to ensure that all administrative operations performed on Azure resources are logged and retained for 90 days. The logs must be queryable using Kusto Query Language (KQL). What should you configure?

A.Azure Activity Log with a diagnostic setting to send logs to the Log Analytics workspace.
B.Azure Monitor Logs with a data collection rule to collect Windows event logs from all VMs.
C.Microsoft Defender for Cloud with continuous export to the Log Analytics workspace.
D.Azure Monitor metrics with a diagnostic setting to send metrics to the Log Analytics workspace.
AnswerA

Azure Activity Log records administrative operations on resources. By creating a diagnostic setting to forward the Activity Log to a Log Analytics workspace, the logs become queryable using KQL and can be retained for 90 days (or more). This meets the requirement for logging administrative operations and querying them.

Why this answer

The Azure Activity Log captures administrative operations at the subscription level. To retain and query these logs with KQL, you create a diagnostic setting that sends the Activity Log to a Log Analytics workspace. This provides long-term retention and powerful querying capabilities.

Metrics, Defender for Cloud, and VM data collection rules do not capture administrative operations.

Exam trap

The trap here is assuming that Azure Monitor metrics or Defender for Cloud can provide administrative operation logs; they serve different purposes and do not capture control-plane operations.

356
Multi-Selecthard

Your organization has multiple Azure subscriptions and uses Azure Blueprints to enforce governance. You need to design a blueprint that includes role assignments, policy assignments, and resource groups. Which THREE components can be included in an Azure Blueprint? (Choose three.)

Select 3 answers
A.Management group
B.Role assignments
C.Policy assignment
D.Subscription
E.ARM template
AnswersB, C, E

Role assignments in Azure Blueprints are artifacts that specify which Azure RBAC role (e.g., Contributor, Reader, Owner) is granted to a named user, group, or service principal at the blueprint's assigned scope. When the blueprint is assigned, these assignments are created automatically, enabling consistent identity-based access control across multiple subscriptions. For example, a blueprint can assign the 'Security Reader' role to a central security team in every subscription, ensuring uniform visibility without manual configuration.

Why this answer

Azure Blueprints allow you to define a repeatable set of Azure resources that adhere to your organization's standards, patterns, and requirements. Role assignments (B) are a core artifact that can be included to grant specific Azure RBAC roles at the blueprint scope, ensuring consistent access control. Policy assignments (C) are also a native blueprint artifact, enabling you to enforce compliance rules across the environment.

ARM templates (E) can be included as an artifact to deploy infrastructure as code, making them a valid component of a blueprint definition.

Exam trap

The trap here is that candidates often confuse the target scope (management group or subscription) with the artifacts that can be included in the blueprint definition, leading them to incorrectly select management group or subscription as valid blueprint components.

357
MCQhard

A company is designing a data storage solution for an IoT pipeline that ingests time-series data from millions of devices. The data is append-only and queried by time range. The solution must support low-latency queries and automated retention policies. Which Azure data store should they choose?

A.Azure SQL Database
B.Azure Cosmos DB
C.Azure Data Explorer (ADX)
D.Azure Blob Storage with Azure Data Lake Storage Gen2
AnswerC

Azure Data Explorer (ADX) is a columnar analytics engine purpose-built for time-series and IoT data, ingesting high-velocity telemetry from Event Hubs and IoT Hub at gigabytes per second with low latency. It automatically compresses and indexes columns, uses Kusto Query Language (KQL) for time-based aggregates, filters, and pattern detection, and stores data in immutable, sharded extents that enable fast scans and retention policies. This is the correct choice for interactive, near-real-time diagnostics and analytics over append-only sensor streams.

Why this answer

Azure Data Explorer (ADX) is purpose-built for interactive analytics on large volumes of streaming, time-series data. It supports append-only ingestion, low-latency queries over time ranges via its Kusto Query Language (KQL), and native automated retention policies (e.g., soft-delete and hard-delete periods) without manual management.

Exam trap

The trap here is that candidates often confuse Cosmos DB's low-latency individual item access with the need for time-series range queries, overlooking that Cosmos DB lacks native time-series indexing and automated retention policies, while ADX is the only Azure service explicitly designed for high-throughput append-only time-series analytics with built-in lifecycle management.

How to eliminate wrong answers

Option A is wrong because Azure SQL Database is a relational OLTP store optimized for transactional workloads with frequent updates, not for high-throughput append-only time-series ingestion or time-range queries at scale. Option B is wrong because Azure Cosmos DB is a multi-model NoSQL database designed for globally distributed, low-latency reads/writes on individual items, but it lacks native time-series optimization, efficient range scans over massive append-only streams, and built-in automated retention policies for time-series data. Option D is wrong because Azure Blob Storage with Azure Data Lake Storage Gen2 provides cheap, scalable object storage for raw data but does not offer low-latency interactive querying or native time-series analytics; it requires additional compute engines (e.g., Azure Synapse) to query, adding latency and complexity.

358
MCQmedium

Your organization plans to migrate a legacy on-premises application that uses a proprietary authentication mechanism to Azure. The application must run as a virtual machine and must not require any code changes. You need to design an identity solution that integrates with the application without modifying it. What should you use?

A.Azure VPN Gateway
B.Microsoft Entra Application Proxy with Kerberos Constrained Delegation
C.Microsoft Entra Domain Services
D.Azure Bastion
AnswerB

Microsoft Entra Application Proxy with Kerberos Constrained Delegation is the correct approach because it publishes the legacy on-premises web app as an enterprise application in Entra ID, allowing pre-authentication via Entra ID (including MFA and conditional access). The Application Proxy connector, running on-premises, then uses KCD to obtain a Kerberos ticket for the user and forwards it to the backend app, enabling Windows-integrated authentication without any code changes. This gives a seamless SSO experience while protecting the app from direct exposure.

Why this answer

Microsoft Entra Application Proxy with Kerberos Constrained Delegation (KCD) allows you to publish on-premises applications that use Kerberos authentication without modifying the application code. The Application Proxy pre-authenticates users via Entra ID, then uses KCD to obtain a Kerberos ticket on behalf of the user and pass it to the legacy application running on a VM. This meets the requirement of no code changes while integrating the proprietary authentication mechanism with Azure identity.

Exam trap

The trap here is that candidates often confuse network-level solutions (VPN, Bastion) or domain services (Entra DS) with identity proxy solutions, failing to recognize that Application Proxy with KCD is the only option that provides seamless authentication integration without code changes.

How to eliminate wrong answers

Option A is wrong because Azure VPN Gateway provides network-level connectivity between on-premises and Azure, not an identity integration solution for application authentication. Option C is wrong because Microsoft Entra Domain Services provides managed domain services (LDAP, Kerberos, NTLM) but does not itself proxy or translate authentication for a legacy application that uses a proprietary mechanism; it would require the application to be domain-joined and use Kerberos directly, which may still need code changes. Option D is wrong because Azure Bastion is a secure RDP/SSH gateway for VM management, not an identity or application authentication solution.

359
MCQeasy

Your company uses Microsoft Entra ID for identity management. You need to ensure that users can access corporate resources without passwords while maintaining a high level of security. Which feature should you implement?

A.Azure AD B2C
B.Conditional Access policies
C.Passwordless authentication
D.Multifactor authentication (MFA)
AnswerC

Passwordless authentication in Microsoft Entra ID lets users sign in without entering a password by using methods like Windows Hello for Business, FIDO2/WebAuthn security keys, or the Microsoft Authenticator app. These methods rely on asymmetric cryptography: the user's device or key securely stores a private key, and the server verifies a signed challenge using the corresponding public key. This eliminates common password attack vectors like phishing, credential stuffing, and password reuse. By replacing the password entirely with biometrics or a hardware-bound credential, it directly achieves the goal of password-free sign-in for internal users.

Why this answer

Passwordless authentication (Option C) is correct because it allows users to access corporate resources without entering a password, using methods like Windows Hello for Business, FIDO2 security keys, or the Microsoft Authenticator app. This eliminates password-related risks (e.g., phishing, credential theft) while maintaining strong security through cryptographic key pairs or biometric verification, aligning with the requirement for both password-free access and high security.

Exam trap

The trap here is that candidates confuse 'passwordless' with 'multifactor authentication' (MFA), assuming MFA alone removes the password requirement, but MFA still requires a password as the first factor unless explicitly combined with a passwordless method.

How to eliminate wrong answers

Option A is wrong because Azure AD B2C is a customer-facing identity service for external users (e.g., social logins), not for internal corporate resource access without passwords. Option B is wrong because Conditional Access policies enforce access controls (e.g., requiring MFA or location checks) but do not eliminate passwords; they still rely on a password as the primary authentication factor unless combined with passwordless methods. Option D is wrong because Multifactor Authentication (MFA) adds a second factor (e.g., SMS, app notification) but still requires a password as the first factor, so it does not achieve passwordless access.

360
MCQhard

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to implement a solution that automatically detects identity-related risks such as leaked credentials, impossible travel, and sign-ins from anonymous IP addresses. They want to generate reports summarizing risk events and integrate the risk data with their existing Security Information and Event Management (SIEM) system via API. Which Microsoft Entra ID feature should they use?

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

Microsoft Entra ID Identity Protection is the correct service because it continuously detects a broad range of identity risks—including leaked credentials, impossible travel, unfamiliar sign-in properties, and anomalous user activity—and stores each detection as a rich risk event. It provides detailed risk reports in the portal and, importantly, exposes these risk events through Microsoft Graph API endpoints (e.g., riskDetection and riskyUser), enabling direct integration with a SIEM. This combination of detection, reporting, and API access makes it the only option that meets the stated requirement.

Why this answer

Microsoft Entra ID Identity Protection is the correct feature because it is specifically designed to automatically detect identity-related risks such as leaked credentials, impossible travel, and sign-ins from anonymous IP addresses. It provides risk event reports and integrates with SIEM systems via the Microsoft Graph API, enabling automated risk data export for centralized monitoring.

Exam trap

The trap here is that candidates often confuse Conditional Access (which enforces policies) with Identity Protection (which detects risks), but Conditional Access relies on Identity Protection's risk signals and cannot generate risk events on its own.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra ID Conditional Access is a policy engine that enforces access controls based on signals (e.g., risk level from Identity Protection), but it does not detect or generate risk events itself. Option C is wrong because Privileged Identity Management (PIM) focuses on just-in-time privileged role activation and access reviews, not on detecting identity risks like leaked credentials or impossible travel. Option D is wrong because Entitlement Management handles access packages and lifecycle management for external users and groups, not risk detection or SIEM integration.

361
MCQmedium

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to grant specific IT administrators just-in-time (JIT) access to Azure virtual machines for troubleshooting. The access must be time-bound, require approval from a senior manager, and be automatically revoked after the granted time period. The company also needs an audit log of all access requests and assignments. Which Azure service or feature should they use?

A.Azure Bastion
B.Microsoft Entra ID Privileged Identity Management (PIM) for Azure resources
C.Just-in-Time VM access (Microsoft Defender for Cloud)
D.Microsoft Entra ID Application Proxy
AnswerB

Microsoft Entra ID Privileged Identity Management (PIM) for Azure resources is the correct choice because it activates RBAC roles, such as Virtual Machine Administrator Login or Contributor, just-in-time with a configurable maximum duration (typically 1–8 hours). Activation can require justification, multi-factor authentication, and an explicit approval from a designated manager or approver, and the role is automatically deactivated when the time window expires. Every activation and action is logged in the Microsoft Entra audit log, providing a complete and auditable record of who accessed what, when, and for how long.

Why this answer

Microsoft Entra ID Privileged Identity Management (PIM) for Azure resources provides just-in-time (JIT) access with time-bound activation, approval workflows, and automatic revocation. It also includes full audit logging of all requests and assignments, meeting all the specified requirements for granting temporary access to Azure VMs.

Exam trap

The trap here is that candidates confuse Just-in-Time VM access in Microsoft Defender for Cloud (which is network-level JIT) with PIM for Azure resources (which is role-level JIT), but only PIM supports the required approval workflow and audit logging for role assignments.

How to eliminate wrong answers

Option A is wrong because Azure Bastion provides secure RDP/SSH connectivity to VMs over TLS without public IPs, but it does not offer time-bound JIT access, approval workflows, or automatic revocation. Option C is wrong because Just-in-Time VM access in Microsoft Defender for Cloud provides time-bound network-level access (NSG rules) to VMs, but it lacks the built-in approval workflow from a senior manager and does not integrate with Entra ID PIM for role-based access control. Option D is wrong because Microsoft Entra ID Application Proxy enables secure remote access to on-premises web applications via pre-authentication, not to Azure VMs, and it does not provide JIT access, approval workflows, or automatic revocation.

362
MCQmedium

A database workload has an RPO of 15 minutes and an RTO of 4 hours. Cost is more important than near-zero data loss. Which design is usually more appropriate than synchronous multi-region replication?

A.Use scheduled backups or asynchronous replication aligned to the RPO/RTO.
B.Use synchronous replication across every Azure region.
C.Run the database on a single VM with no backups.
D.Use a public DNS CNAME only.
AnswerA

Scheduled backups taken every 15 minutes, or asynchronous replication with a similar lag, can restore the database to within 15 minutes of a failure, and a 4-hour RTO gives ample time to recover from those backups. This approach balances the stated RPO and RTO with cost efficiency, since the requirement does not justify the expense and added latency of synchronous multi-region replication. Azure SQL Database automated backups or Azure Site Recovery with log shipping are examples of such aligned solutions.

Why this answer

The workload's RPO of 15 minutes and RTO of 4 hours, combined with a cost-sensitive requirement that deprioritizes near-zero data loss, makes synchronous multi-region replication overkill. Scheduled backups (e.g., every 15 minutes using Azure SQL Database automated backups with point-in-time restore) or asynchronous replication (e.g., Azure SQL Database active geo-replication with a recovery point objective of up to 5 seconds, but here we can tune it to meet 15 minutes) provide sufficient protection at a lower cost, avoiding the latency and expense of synchronous replication across regions.

Exam trap

The trap here is that candidates often assume synchronous replication is always the best choice for business continuity, but the question explicitly prioritizes cost over near-zero data loss, making asynchronous replication or scheduled backups the more appropriate and cost-effective design.

How to eliminate wrong answers

Option B is wrong because synchronous replication across every Azure region would incur high latency, significant cost, and unnecessary complexity for a workload that tolerates up to 15 minutes of data loss and 4 hours of downtime; it is designed for near-zero RPO scenarios, which the question explicitly de-emphasizes. Option C is wrong because running the database on a single VM with no backups provides no recovery point or recovery time guarantee, violating the stated RPO of 15 minutes and RTO of 4 hours entirely. Option D is wrong because a public DNS CNAME only provides DNS-level redirection, not any database replication, backup, or failover capability, so it cannot meet the RPO or RTO requirements.

363
MCQeasy

You are designing a web application that will be hosted on Azure App Service. The application must authenticate users from your company's Microsoft Entra ID tenant. You need to implement authentication without writing any authentication code. What should you use?

A.Azure API Management with OAuth 2.0 policy
B.Microsoft Authentication Library (MSAL) integrated into the application code
C.App Service Authentication (EasyAuth)
D.Azure Front Door with authentication rules
AnswerC

App Service Authentication, also known as EasyAuth, runs natively in the App Service platform overlay and automatically handles the full OAuth 2.0 and OpenID Connect flow against Microsoft Entra ID. When a request arrives, EasyAuth validates the identity, establishes an encrypted session cookie, and injects security claims into HTTP headers such as X-MS-CLIENT-PRINCIPAL and X-MS-TOKEN-AAD-ID-TOKEN for the app to read. Since this all occurs at the platform level, the application requires zero authentication code; the developer simply enables the feature and configures the identity provider in the Azure portal. For multitenant apps, it also manages tenant restrictions without changes to the app.

Why this answer

App Service Authentication (also known as EasyAuth) is the correct choice because it provides built-in authentication for Azure App Service without requiring any custom code. It integrates directly with Microsoft Entra ID (formerly Azure AD) and automatically handles token validation, session management, and redirects by intercepting HTTP requests before they reach your application code.

Exam trap

The trap here is that candidates often confuse Azure API Management's OAuth 2.0 policy with end-user authentication, but API Management secures APIs at the gateway level and does not provide the login UI or session management needed for a web application without custom code.

How to eliminate wrong answers

Option A is wrong because Azure API Management with OAuth 2.0 policy is designed to secure APIs and validate tokens at the gateway layer, not to authenticate end users of a web application without writing authentication code. Option B is wrong because the Microsoft Authentication Library (MSAL) requires explicit integration into the application code to handle login flows, token acquisition, and caching, which contradicts the requirement of 'without writing any authentication code.' Option D is wrong because Azure Front Door with authentication rules can enforce access policies at the edge but does not provide built-in authentication flows (like login pages or token exchange) for a web application; it relies on backend services or custom rules for actual authentication.

364
MCQhard

A company is designing a data lake for analytics. The data includes personally identifiable information (PII) that must be anonymized before analysts access it. Which Azure service should they use to automate the anonymization process?

A.Azure Policy
B.Azure SQL Database dynamic data masking
C.Azure Key Vault
D.Microsoft Purview data policies
AnswerD

Microsoft Purview data policies, which include data owner policies and Microsoft Purview access policies, can automatically classify sensitive data across sources like Azure Data Lake Storage and then enforce policies such as masking (column-level or file-level) or access control based on that classification. For a data lake, Purview's scanning engines discover sensitive data using built-in or custom classifiers, and data policies can apply masking to read operations or restrict access to certain users. This makes it the correct choice for a unified, policy-driven approach to protecting sensitive data in a data lake analytics scenario.

Why this answer

Microsoft Purview data policies allow you to define and enforce data access policies that can automatically anonymize or mask sensitive data, such as PII, when accessed by analysts. This service integrates with Azure data lake storage and provides a centralized way to manage data governance and compliance, making it the correct choice for automating anonymization in a data lake scenario.

Exam trap

The trap here is that candidates often confuse Azure SQL Database dynamic data masking (Option B) with a general-purpose anonymization solution, but it only works for relational databases, not for data lakes, and does not automate the process across heterogeneous file formats.

How to eliminate wrong answers

Option A is wrong because Azure Policy is used to enforce organizational standards and assess compliance across Azure resources, not to automate data-level anonymization or masking within a data lake. Option B is wrong because Azure SQL Database dynamic data masking applies masking at the database query level for SQL databases, but it is not designed for data lake storage (e.g., Azure Data Lake Storage Gen2) and does not automate anonymization for file-based analytics. Option C is wrong because Azure Key Vault is a service for securely storing and managing secrets, keys, and certificates, not for applying data anonymization or masking transformations.

365
MCQmedium

An on-premises datacenter must connect privately to Azure with predictable bandwidth and avoid traversal of the public internet. Which connectivity option should be recommended?

A.Azure Bastion
B.Point-to-site VPN
C.Site-to-site VPN only
D.ExpressRoute
AnswerD

ExpressRoute provides a private, dedicated Layer 3 connection between your on-premises datacenter and Azure through a connectivity provider, using redundant Microsoft Enterprise Edge routers and BGP peering. Traffic never traverses the public internet, enabling consistent latency, higher bandwidth, and an availability SLA. With private peering, virtual networks can be reached directly over this backbone, making it the correct service for private datacenter-to-Azure connectivity.

Why this answer

ExpressRoute provides a dedicated private connection from on-premises to Azure, bypassing the public internet entirely. It offers predictable bandwidth, low latency, and high reliability through a Layer 3 MPLS or direct fiber link from a connectivity provider. This meets the requirement for a private, consistent network path without internet traversal.

Exam trap

The trap here is that candidates may confuse Site-to-site VPN (which also provides a private IP tunnel) as meeting the 'private' requirement, but it still traverses the public internet and cannot guarantee predictable bandwidth like ExpressRoute.

How to eliminate wrong answers

Option A is wrong because Azure Bastion is a managed PaaS service for secure RDP/SSH access to Azure VMs over TLS, not a connectivity option for on-premises datacenters. Option B is wrong because Point-to-site VPN uses SSTP or IKEv2 over the public internet, which cannot guarantee predictable bandwidth and does traverse the internet. Option C is wrong because Site-to-site VPN only uses IPsec tunnels over the public internet, which introduces variable latency and bandwidth due to internet routing, failing the requirement for predictable bandwidth and no public internet traversal.

366
MCQhard

Refer to the exhibit. The JSON snippet shows the properties of a replication-protected item in Azure Site Recovery. What is the MOST LIKELY reason for the replication health being 'Critical'?

A.The replication storage account is misconfigured
B.There is a network connectivity issue between the on-premises site and Azure
C.A planned failover was completed, stopping replication
D.A test failover was initiated but not cleaned up
AnswerC

Azure Site Recovery intentionally stops the continuous replication stream during a planned failover to guarantee that no data written after the cutover is replicated; once this completes, the protection state is set to 'PlannedFailoverCompleted'. The replication health automatically becomes 'Critical' because the active replication link is no longer transferring data—this is an expected result of the failover lifecycle, not a sign of misconfiguration or infrastructure failure. To restore a healthy state, you must commit or reverse the failover and then re-protect the workload, which establishes a fresh replication relationship; until then, the critical health flag correctly indicates that replication is stopped.

Why this answer

When a planned failover is completed in Azure Site Recovery, replication is automatically stopped and the replication health status changes to 'Critical' because the protected item is no longer actively replicating to the recovery region. This is expected behavior after a planned failover, as the source and target are now synchronized and replication is disabled to prevent data overwrites. The 'Critical' health indicator in this context reflects the intentional cessation of replication, not a fault.

Exam trap

The trap here is that candidates often assume 'Critical' replication health always indicates a technical failure (e.g., network or storage issues), but in Azure Site Recovery, a planned failover intentionally stops replication, causing the health to become 'Critical' as a normal post-failover state.

How to eliminate wrong answers

Option A is wrong because a misconfigured replication storage account would typically cause replication errors or failures, not a clean 'Critical' health status after a planned failover; the JSON snippet shows no storage account misconfiguration details. Option B is wrong because a network connectivity issue would manifest as replication errors, missed recovery points, or a 'Warning' status, not a definitive 'Critical' status with replication stopped; the JSON shows replication is disabled, not failing. Option D is wrong because a test failover that is not cleaned up would leave the test virtual machine running in Azure but would not stop ongoing replication; the replication health would remain healthy or show a warning, not become 'Critical' with replication disabled.

367
MCQeasy

Your company requires that all administrative actions in Azure subscriptions be logged and retained for seven years. Which service should you use to collect and store these logs?

A.Azure Monitor Metrics
B.Azure Resource Health
C.Azure Activity Log
D.Microsoft Entra ID audit logs
AnswerC

The Azure Activity Log is a subscription-level audit log that records every control-plane operation (create, update, delete, and write) on Azure resources, including the actor (who initiated the action), the timestamp, the operation name, and the status. It captures administrative actions such as starting or stopping a virtual machine, modifying a network security group, or assigning a policy, and can be retained for up to 7 years when exported to a storage account or Log Analytics workspace. This makes it the correct source for answering who did what, when, and where in your Azure environment.

Why this answer

The Azure Activity Log (now part of Azure Monitor) records all control-plane operations (create, update, delete) on Azure resources and can be retained for up to seven years by configuring a diagnostic setting to stream the logs to a Log Analytics workspace or Azure Storage. This meets the requirement for logging and long-term retention of administrative actions.

Exam trap

The trap here is that candidates confuse the Azure Activity Log (control-plane) with Microsoft Entra ID audit logs (identity-plane), or mistakenly think Azure Monitor Metrics can store long-term administrative logs instead of numerical performance data.

How to eliminate wrong answers

Option A is wrong because Azure Monitor Metrics stores numerical time-series data (e.g., CPU usage, request counts) with a default retention of 93 days, not administrative action logs for seven years. Option B is wrong because Azure Resource Health provides real-time status of resource availability and service issues, not a historical log of administrative actions. Option D is wrong because Microsoft Entra ID audit logs capture user sign-ins and directory changes, not Azure resource-level administrative actions (control-plane operations).

368
Multi-Selectmedium

Which THREE Azure services can be used to implement a disaster recovery plan for Azure Virtual Desktop (AVD) that meets an RTO of 2 hours and an RPO of 30 minutes? (Select THREE.)

Select 3 answers
A.Azure Database for MySQL
B.Azure Migrate
C.Azure Site Recovery
D.Azure Backup
E.Azure Files with geo-redundant storage
AnswersC, D, E

Azure Site Recovery (ASR) is the core DR orchestration service for AVD session host VMs, because it continuously replicates Azure VMs to a secondary region and enables one-click failover with defined RPO/RTO. By protecting the session host VMs in a Recovery Services vault, ASR ensures compute infrastructure is promptly recreated after a regional outage. However, it does not replicate FSLogix user profiles, which is why it must be combined with geo-redundant Azure Files.

Why this answer

Azure Site Recovery (ASR) orchestrates replication and failover of Azure Virtual Desktop (AVD) session hosts and their workloads to a secondary Azure region, enabling RTO of 2 hours and RPO of 30 minutes when configured with replication policies set to 30-minute frequency. It supports multi-VM consistency groups to ensure application-consistent recovery points for AVD infrastructure components.

Exam trap

The trap here is that candidates often confuse Azure Migrate (a migration tool) with Azure Site Recovery (a DR orchestration service), or assume that Azure Backup alone can meet the RTO/RPO for AVD without considering the need for full infrastructure replication and failover.

369
MCQhard

Refer to the exhibit. You are deploying a Log Analytics workspace using an ARM template with the parameters shown. Your compliance team requires that all log data be retained for at least 2 years. Which parameter value should you modify?

A.retentionInDays
B.workspaceName
C.sku
D.dailyQuotaGb
AnswerA

In Azure Log Analytics, retentionInDays is the workspace-level property that determines exactly how many days log data is retained before being purged from the storage layer. The current setting of 365 fails the 2-year requirement, so this value must be set to 730 or higher. This is the only property that directly controls the retention period; no other workspace setting can extend it.

Why this answer

The `retentionInDays` parameter controls how long log data is retained in a Log Analytics workspace. To meet the compliance requirement of at least 2 years (730 days), you must set this value to 730 or higher. The default retention is 30 days for free tiers and up to 730 days for paid tiers, but the parameter must be explicitly modified to enforce the 2-year retention.

Exam trap

The trap here is that candidates often confuse `sku` with retention capabilities, assuming that upgrading the SKU automatically extends retention, when in fact `retentionInDays` is an independent parameter that must be explicitly set to meet compliance requirements.

How to eliminate wrong answers

Option B is wrong because `workspaceName` only defines the name of the Log Analytics workspace and has no impact on data retention policies. Option C is wrong because `sku` determines the pricing tier (e.g., PerGB2018, Standalone) and affects features like ingestion costs and retention limits, but does not directly set the retention period; retention is configured separately via `retentionInDays`. Option D is wrong because `dailyQuotaGb` sets a cap on daily data ingestion to control costs, not the retention duration of stored logs.

370
MCQeasy

A company plans to store operational logs from Azure App Services in a scalable and cost-effective way. The logs must be retained for 90 days and then automatically deleted. Which Azure data storage solution should you recommend?

A.Azure Blob Storage with lifecycle management
B.Azure SQL Database with retention policy
C.Azure Log Analytics Workspace
D.Azure Cosmos DB with TTL
AnswerC

Azure Log Analytics Workspace is the correct choice because it is purpose-built for ingesting, storing, and querying operational logs from Azure resources via diagnostic settings. It provides native Kusto Query Language (KQL) for fast, interactive analysis, an integrated retention and archive policy for balancing cost and compliance, and direct integration with Azure Monitor alerts, workbooks, and dashboards. This makes it the optimal, low-friction service for operational logs that must be searched, correlated, and visualized without additional tooling.

Why this answer

Azure Log Analytics Workspace is the correct choice because it natively ingests operational logs from Azure App Services via diagnostic settings, provides a scalable and cost-effective storage tier with a 90-day retention policy that can be configured to automatically delete data after the retention period expires. It also supports Kusto Query Language (KQL) for analysis and integrates with Azure Monitor for alerting, making it purpose-built for log storage and management.

Exam trap

The trap here is that candidates may choose Azure Blob Storage with lifecycle management because they associate 'scalable and cost-effective' with blob storage, overlooking that operational logs require querying and analysis, which Log Analytics Workspace provides natively, while blob storage would require additional services like Azure Data Explorer or custom indexing to make the logs searchable.

How to eliminate wrong answers

Option A is wrong because Azure Blob Storage with lifecycle management is designed for storing unstructured data like files or backups, not for operational logs that require querying and analysis; while it can retain and delete blobs after 90 days, it lacks native log ingestion, indexing, and query capabilities. Option B is wrong because Azure SQL Database is a relational database for transactional workloads, not a log storage solution; its retention policy applies to point-in-time restore backups, not to operational log data, and it is significantly more expensive for high-volume log ingestion. Option D is wrong because Azure Cosmos DB with TTL is a NoSQL database for globally distributed, low-latency applications; its time-to-live feature automatically deletes documents after a specified period, but it is not designed for log storage, lacks native integration with Azure App Services diagnostic settings, and incurs high costs for write-heavy log ingestion.

371
Multi-Selectmedium

Which TWO Azure services can be used to host a MongoDB-compatible database with global distribution? (Select two.)

Select 2 answers
A.Azure SQL Database
B.Azure Cosmos DB API for MongoDB
C.Azure Database for PostgreSQL
D.Azure Database for MongoDB (MongoDB Atlas on Azure)
E.Azure Cache for Redis
AnswersB, D

Azure Cosmos DB API for MongoDB is a first-party Azure service that implements the MongoDB wire protocol, allowing existing MongoDB SDKs, drivers, and tools to connect directly. It provides MongoDB-compatible CRUD operations, indexing, aggregation pipelines, and sharding semantics while adding Azure-native capabilities such as global distribution, multi-region writes, automatic failover, and flexible consistency levels. Because it is natively integrated with Azure Portal, ARM templates, and Azure CLI, it is a correct and widely recommended choice for hosting MongoDB-compatible workloads on Azure.

Why this answer

Azure Cosmos DB API for MongoDB is correct because it provides a MongoDB-compatible API layer over Cosmos DB's globally distributed, multi-model database engine. This allows you to use standard MongoDB drivers and tools while benefiting from Cosmos DB's turnkey global distribution, multi-region writes, and 99.999% availability SLA.

Exam trap

The trap here is that candidates may assume only one service can host a MongoDB-compatible database, overlooking that both a native MongoDB service (Atlas) and a protocol-compatible alternative (Cosmos DB API for MongoDB) are valid, and that Azure SQL Database or PostgreSQL are relational databases that cannot serve MongoDB workloads.

372
Multi-Selectmedium

A hub-and-spoke Azure network must centralize outbound inspection and still allow spokes to resolve private endpoint DNS names. Which two components are commonly required? (Choose 2.)

Select 2 answers
A.User-defined routes from spoke subnets to the firewall or NVA.
B.Private DNS zones linked to the VNets or resolved through a central DNS design.
C.A public IP address on every private endpoint.
D.Basic SKU load balancers in each spoke.
AnswersA, B

User-defined routes (UDRs) are essential in a hub-and-spoke topology because they force all outbound traffic from spoke subnets to traverse the central firewall or NVA by specifying the inspection appliance as the next hop. Without a UDR, spoke traffic follows Azure's default system routes and reaches the internet directly, bypassing the hub's security controls. Associating a route table with each spoke subnet—and setting the next hop type to Virtual Appliance—is the mechanism that makes centralized outbound inspection and egress traffic deterministic.

Why this answer

User-defined routes (UDRs) on spoke subnets force all outbound traffic (including internet-bound traffic) to the central firewall or network virtual appliance (NVA) in the hub, enabling centralized inspection. Without UDRs, spoke VMs would bypass the firewall and use default outbound internet access, breaking the inspection requirement.

Exam trap

The trap here is that candidates often assume private endpoints require public IPs for DNS resolution, but Azure Private DNS zones resolve FQDNs to private IPs, and UDRs handle traffic routing without needing public exposure.

373
MCQhard

A company uses Microsoft Entra ID (Microsoft Entra ID). They need to enforce that all users accessing the company's internal application from mobile devices must be compliant with device management policies (e.g., require a PIN and encryption). The application does not support modern authentication. Which Microsoft Entra ID feature should they use?

A.Microsoft Entra ID Conditional Access
B.Microsoft Entra ID Application Proxy
C.Microsoft Entra ID Identity Protection
D.Microsoft Entra ID Privileged Identity Management
AnswerB

Application Proxy is the correct choice because it publishes the legacy on-premises application as an enterprise application in Microsoft Entra ID, adding a modern OAuth/OIDC authentication layer in front of it. Once published, the app becomes visible to Conditional Access, so device compliance requirements can be enforced during pre-authentication. The connector then forwards the authenticated request to the legacy backend using Kerberos or NTLM, preserving the original app's behavior without changing its code.

Why this answer

Microsoft Entra ID Application Proxy is the correct choice because it enables secure remote access to on-premises web applications that do not support modern authentication. By publishing the internal application through Application Proxy, you can enforce device compliance policies (e.g., requiring a PIN and encryption) via Conditional Access policies applied to the Application Proxy service, even though the application itself uses legacy authentication.

Exam trap

The trap here is that candidates often assume Conditional Access alone can enforce device compliance on any application, but they miss the critical requirement that the application must support modern authentication; Application Proxy is the bridge that enables Conditional Access to work with legacy apps.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra ID Conditional Access is a policy engine that enforces access controls, but it cannot directly enforce device compliance on an application that does not support modern authentication; it requires the application to support modern authentication protocols (e.g., OAuth 2.0, OpenID Connect) to evaluate device state. Option C is wrong because Microsoft Entra ID Identity Protection is focused on detecting and responding to identity-based risks (e.g., leaked credentials, anomalous sign-ins), not on enforcing device management policies or enabling legacy app access. Option D is wrong because Microsoft Entra ID Privileged Identity Management is designed for managing, controlling, and monitoring privileged roles and just-in-time access, not for enforcing device compliance or proxying legacy applications.

374
Multi-Selecteasy

Which TWO Microsoft Entra ID editions include Conditional Access? (Choose two.)

Select 2 answers
A.Microsoft Entra ID P1
B.Microsoft Entra ID P2
C.Azure AD Basic (legacy)
D.Microsoft 365 Business Basic
E.Microsoft Entra ID Free
AnswersA, B

Microsoft Entra ID P1 is the entry-level premium edition that licenses the Conditional Access policy engine. It evaluates a rich set of signals—including user identity, group membership, device status, and geographic location—to grant, block, or require multifactor authentication on every authentication request. P1 is available as a standalone SKU or via Microsoft 365 E3/E5 and Enterprise Mobility+Security E3, and it covers most policy-driven conditional access scenarios such as 'require MFA for all users' or 'block legacy authentication protocols.'

Why this answer

Microsoft Entra ID P1 includes Conditional Access, which allows organizations to enforce access policies based on signals like user, location, device, and application. This edition provides the core Conditional Access capabilities needed for most enterprise scenarios, such as requiring multi-factor authentication or blocking access from untrusted locations.

Exam trap

The trap here is that candidates often confuse Microsoft 365 Business Basic (which includes only Azure AD Free) with a higher-tier license that includes Conditional Access, or mistakenly think legacy Azure AD Basic still supports Conditional Access.

375
MCQmedium

Refer to the exhibit. You are reviewing an ARM template that deploys a virtual network with two subnets. Subnet-b includes a delegation to Microsoft.Web/serverFarms. What is the purpose of this delegation?

A.It allows subnet-b to use a different address space
B.It configures a firewall policy for subnet-b
C.It creates a peering connection to another virtual network
D.It enables Azure App Service instances to be deployed into subnet-b
AnswerD

With 'serviceName': 'Microsoft.Web/serverFarms', the delegation tells Azure that the subnet is reserved for App Service infrastructure, enabling an App Service plan or App Service Environment to deploy worker instances directly into subnet-b. The service then creates and manages the required network interfaces and permissions within that delegated subnet. This is the intended meaning of the delegation in the ARM template and the only option consistent with how subnet delegation works.

Why this answer

Delegating a subnet to Microsoft.Web/serverFarms explicitly authorizes Azure App Service (specifically, the App Service Plan's infrastructure) to inject network interfaces into that subnet. This is required for features like regional VNet Integration, where an App Service instance needs direct access to resources in the virtual network without going through a public endpoint. Without this delegation, the App Service cannot use the subnet for its internal networking.

Exam trap

The trap here is that candidates confuse subnet delegation with general VNet integration or peering, but delegation is specifically a resource provider permission model that allows a PaaS service (like App Service) to own and manage the subnet's network interfaces.

How to eliminate wrong answers

Option A is wrong because a subnet's address space is defined by its address prefix in the virtual network configuration, not by a delegation; delegation does not change IP addressing. Option B is wrong because firewall policies (e.g., Azure Firewall or NSG rules) are applied separately via network security groups or Azure Firewall policies, not through a subnet delegation. Option C is wrong because VNet peering is configured at the virtual network level using peering connections, not by delegating a subnet to a resource provider.

Page 4

Page 5 of 11

Page 6

All pages