Courseiva

Microsoft Azure Security Engineer Associate AZ-500 (AZ-500) — Questions 301–375

617 questions total · 9 pages · All types, answers revealed

Page 4

Page 5 of 9

Page 6
301
MCQhard

Your company has Microsoft Sentinel deployed in multiple workspaces across several Azure regions. The security operations team wants to query data from all workspaces centrally using a single KQL query. What feature should you implement?

A.Configure Log Analytics workspaces as linked to a central workspace.
B.Use cross-workspace queries with the workspace() expression in KQL.
C.Export all data to Azure Data Explorer and query there.
D.Use the Microsoft Sentinel SIEM connector to aggregate data.
AnswerB

The workspace() expression in KQL—e.g., union workspace('Contoso-Sentinel').SecurityEvent, workspace('Fabrikam-Sentinel').SecurityEvent—lets you query tables across multiple Log Analytics workspaces in a single query. This is the Azure-native mechanism designed for Microsoft Sentinel multi-workspace scenarios and works without duplicating data or adding an extra ETL layer. It also supports resource-id based references, so you can query Sentinel workspaces that data is retained in while preserving the full context of the original table schema.

Why this answer

The workspace() expression in KQL allows you to include tables from multiple Log Analytics workspaces in a single query, enabling centralized querying across all Microsoft Sentinel workspaces without moving or aggregating data. This is the native and recommended approach for cross-workspace queries in Azure Sentinel.

Exam trap

The trap here is that candidates confuse the workspace() expression with the legacy linked workspace feature (Option A) or assume that a central aggregation mechanism (like a SIEM connector or data export) is required, when in fact KQL's native cross-workspace querying is the simplest and most cost-effective solution.

How to eliminate wrong answers

Option A is wrong because linked workspaces (via the legacy 'linked server' feature) are used for cross-region querying in Log Analytics but do not support the workspace() expression and are not designed for Microsoft Sentinel's multi-workspace architecture; they also require manual configuration and have limitations on the number of linked workspaces. Option C is wrong because exporting all data to Azure Data Explorer is unnecessary overhead—it introduces additional cost, latency, and complexity, and is not the standard method for querying Sentinel data across workspaces; the workspace() expression is simpler and more efficient. Option D is wrong because the Microsoft Sentinel SIEM connector is used to ingest data from external SIEMs (e.g., Splunk, ArcSight) into Sentinel, not to aggregate queries across multiple Sentinel workspaces.

302
MCQeasy

You are a security engineer for a company that uses Microsoft Entra ID. You need to ensure that all users accessing the company's Salesforce application from unmanaged devices are prompted for multi-factor authentication (MFA) every time. What should you configure?

A.Enable per-user MFA for all users in the Salesforce application.
B.Create a Conditional Access policy that targets the Salesforce application, apply to all users, include 'All device platforms' with 'Device state' filter for 'Unmanaged', and grant access requiring MFA with session control 'Sign-in frequency - Every time'.
C.Configure device compliance policy to require MFA on non-compliant devices.
D.Configure MFA registration policy to require all users to register MFA.
AnswerB

This Conditional Access policy is correct because it precisely targets the Salesforce app and all users, then uses the 'Device state' filter to include only 'Unmanaged' devices, excluding managed, compliant, and hybrid-joined devices. The grant control 'Require MFA' forces an MFA challenge on those unmanaged devices, while the session control 'Sign-in frequency - Every time' ensures that even within an existing session, every sign-in to Salesforce is reauthenticated with MFA, closing the gap for stolen tokens or stale sessions. This delivers exactly the required behavior: MFA every time on unmanaged devices, without affecting managed ones.

Why this answer

A Conditional Access policy with a 'Device state' filter for 'Unmanaged' and 'Sign-in frequency - Every time' session control forces MFA prompts on every access attempt from unmanaged devices. This meets the requirement to prompt MFA every time for users accessing Salesforce from unmanaged devices, without affecting managed devices or requiring per-user MFA.

Exam trap

The trap here is that candidates often confuse per-user MFA (Option A) with Conditional Access MFA, not realizing that per-user MFA cannot target specific applications or device states, and that 'Sign-in frequency' is a session control, not a grant control.

How to eliminate wrong answers

Option A is wrong because per-user MFA applies MFA to all sign-ins for the user, regardless of device state or application, and does not provide the granularity to target only unmanaged devices or enforce 'every time' frequency. Option C is wrong because device compliance policies evaluate device health (e.g., encryption, OS version) but do not directly trigger MFA prompts; they can block or grant access but cannot enforce 'Sign-in frequency - Every time' as a session control. Option D is wrong because the MFA registration policy only ensures users have registered MFA methods; it does not enforce MFA prompts during sign-in, nor does it target specific applications or device states.

303
MCQhard

You are deploying a three-tier application on Azure VMs. The web tier must be accessible from the internet, but the application and database tiers must only accept traffic from the web tier. You need to implement network segmentation using Azure networking components. What is the most secure and manageable solution?

A.Use a single subnet and configure NSGs on VM NICs to restrict traffic.
B.Use VNet peering to connect separate VNets for each tier and use NSGs.
C.Use a single VNet with one subnet and use Azure Firewall to filter traffic between tiers.
D.Use separate subnets for each tier in the same VNet and configure NSGs to allow traffic only from the previous tier.
AnswerD

Segmenting the VNet into separate subnets for each tier is the core of Azure network security for app workloads, because it lets you attach an NSG at the subnet boundary and enforce least-privilege traffic flow. For example, you can create a rule that allows only the application subnet to access the database subnet on TCP 1433, and only the web subnet to access the application subnet on TCP 443, while the default deny-all rule blocks everything else. Because NSGs are stateful, rules apply to both directions and new VMs added to a subnet automatically inherit the same security posture, providing a scalable, manageable tier-isolation pattern.

Why this answer

Placing each tier in its own subnet within the same VNet allows you to apply Network Security Groups (NSGs) at the subnet level with inbound rules that restrict traffic to only the previous tier's subnet IP range. This follows the principle of least privilege and provides a clear, manageable boundary between tiers without introducing unnecessary complexity or performance overhead.

Exam trap

The trap here is that candidates often overcomplicate the solution by choosing Azure Firewall or VNet peering, not realizing that NSGs on separate subnets within the same VNet are the simplest, most cost-effective, and most secure way to enforce east-west traffic restrictions between application tiers.

How to eliminate wrong answers

Option A is wrong because using a single subnet with NSGs on individual VM NICs does not provide network-level segmentation; it relies on host-level filtering, which is harder to manage at scale and does not prevent lateral movement between VMs in the same subnet. Option B is wrong because VNet peering between separate VNets introduces unnecessary latency, complexity, and cost; it is overkill for a simple three-tier application that can be contained within a single VNet. Option C is wrong because Azure Firewall is a stateful, centralized service designed for perimeter and hub-spoke scenarios, not for internal subnet-to-subnet filtering within a single VNet; using it here would add unnecessary cost and latency compared to NSG rules.

304
MCQhard

A company uses Azure SQL Database to store personally identifiable information (PII). They need to encrypt specific columns containing social security numbers so that even database administrators with the 'db_owner' role cannot view the plaintext. The application must be able to perform equality searches on the encrypted columns. Which encryption technology should they implement?

A.Transparent Data Encryption (TDE)
B.Always Encrypted with deterministic encryption
C.Dynamic Data Masking
D.Row-Level Security
AnswerB

Always Encrypted encrypts sensitive columns in the client driver using a column encryption key, which is protected by a column master key held outside SQL Server in Azure Key Vault or Windows Certificate Store. The SQL Server Database Engine receives only ciphertext and never sees the plaintext, so DBAs cannot read the data. With deterministic encryption, the same plaintext always produces the same ciphertext, allowing the server to perform equality comparisons (e.g., WHERE clause lookups) without exposing the values.

Why this answer

Always Encrypted with deterministic encryption is the correct choice because it encrypts specific columns at the client-side, ensuring that even database administrators with db_owner cannot view plaintext data. Deterministic encryption generates the same ciphertext for a given plaintext value, enabling equality searches (e.g., WHERE SSN = '123-45-6789') directly on the encrypted column without decrypting the data on the server.

Exam trap

The trap here is that candidates often confuse encryption at rest (TDE) with client-side column encryption, mistakenly believing TDE protects against privileged users, but TDE only protects against physical theft of the database files, not against authorized database access.

How to eliminate wrong answers

Option A is wrong because Transparent Data Encryption (TDE) encrypts the entire database at rest (pages written to disk) but does not protect data from users or DBAs who have access to the database; plaintext is visible to anyone with query permissions. Option C is wrong because Dynamic Data Masking obfuscates data in query results for non-privileged users but does not encrypt the underlying data; DBAs with db_owner can still view the unmasked values by altering the masking rule or querying directly. Option D is wrong because Row-Level Security restricts access to rows based on a predicate function but does not encrypt column values; DBAs with db_owner can bypass or modify the security policy to see all data.

305
MCQeasy

You are a security administrator for a financial institution. You need to implement a solution that allows users to authenticate using biometrics and prevents password-based attacks. Which Microsoft Entra ID feature should you enable?

A.Microsoft Entra ID Protection
B.Passwordless authentication (FIDO2 or Windows Hello for Business)
C.Password hash synchronization
D.Azure Multi-Factor Authentication
AnswerB

Passwordless authentication using FIDO2 security keys or Windows Hello for Business replaces the password entirely with public/private key cryptography. The private key never leaves the device and is unlocked by a biometric gesture (fingerprint or face) or a PIN, while the public key is registered with Microsoft Entra ID. Because no shared secret is transmitted over the network, these methods are phishing-resistant and eliminate the most common attack vectors like password spraying and credential theft, making this the only option that truly removes passwords.

Why this answer

Passwordless authentication methods like FIDO2 and Windows Hello for Business eliminate the use of passwords entirely, thereby preventing password-based attacks such as brute force, phishing, and credential stuffing. Biometric verification (e.g., fingerprint or facial recognition) is a core component of these methods, meeting the requirement for biometric authentication. This aligns with the Zero Trust principle of reducing the attack surface by removing shared secrets.

Exam trap

The trap here is that candidates often confuse Azure MFA (which still requires a password) with passwordless methods, mistakenly thinking MFA alone eliminates password-based attacks, when in fact it only adds a second layer after the password is entered.

How to eliminate wrong answers

Option A is wrong because Microsoft Entra ID Protection is a risk-based conditional access tool that detects and responds to identity risks (e.g., leaked credentials, anomalous sign-ins) but does not itself enable biometric authentication or eliminate passwords. Option C is wrong because Password Hash Synchronization (PHS) is a synchronization mechanism that hashes and syncs on-premises AD passwords to Azure AD for hybrid identity scenarios; it does not provide biometric authentication or prevent password attacks. Option D is wrong because Azure Multi-Factor Authentication (MFA) adds a second factor (e.g., phone call, OTP) but still relies on a password as the first factor, so it does not prevent password-based attacks—it only mitigates them after a password is compromised.

306
MCQmedium

You have an Azure subscription with multiple virtual networks. You need to centrally manage and enforce security policies for all outbound traffic from virtual machines to the internet. The solution must be able to inspect traffic and log all connections. What should you deploy?

A.Azure Firewall in a hub virtual network.
B.Network security groups (NSGs) on all subnets.
C.Azure Application Gateway with WAF.
D.Azure VPN Gateway with forced tunneling.
AnswerA

Azure Firewall is a managed, cloud-native firewall service with built-in availability and autoscaling. Deployed as a hub in a hub-and-spoke topology, it can inspect outbound traffic from peered spoke VNets through user-defined routes, and provide stateful network and FQDN-based application rules. It also centralizes logging and integrates with Azure Monitor, satisfying the requirement for outbound inspection and centralized logging.

Why this answer

Azure Firewall is a managed, cloud-native network security service that provides centralized outbound traffic inspection and logging. It can be deployed in a hub virtual network to enforce security policies across all spoke VMs, inspecting all outbound connections using application (FQDN) and network (IP/port) rules, and logging all traffic to Azure Monitor or Storage. This meets the requirements for central management, traffic inspection, and full connection logging.

Exam trap

The trap here is that candidates often confuse Azure Firewall with NSGs, assuming NSGs can centrally manage outbound traffic across VNets, but NSGs are decentralized and cannot inspect or log traffic at the application layer or across peered networks.

How to eliminate wrong answers

Option B is wrong because Network Security Groups (NSGs) operate at the subnet or NIC level, provide only stateful packet filtering (no deep packet inspection), and do not log individual connections with full details like source/destination IPs and ports by default; they also cannot centrally enforce policies across multiple virtual networks. Option C is wrong because Azure Application Gateway with WAF is a Layer 7 load balancer designed for inbound HTTP/HTTPS traffic protection, not for outbound traffic inspection or logging of all connections. Option D is wrong because Azure VPN Gateway with forced tunneling only redirects outbound traffic to an on-premises network for inspection, but it does not inspect traffic itself, nor does it log connections natively; it requires additional on-premises firewall infrastructure.

307
Drag & Dropmedium

Drag and drop the steps to configure Azure Disk Encryption for a Windows VM using Azure Key Vault 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 configuring Azure Disk Encryption for a Windows VM using Azure Key Vault is to first create or configure the Key Vault with soft-delete and purge protection, then set the Key Vault access policy to grant the Azure Disk Encryption service the required permissions, and finally enable disk encryption on the VM specifying the Key Vault and key. This order ensures that all prerequisites are met, preventing errors during the encryption process.

308
MCQeasy

A company has Azure virtual machines that need to download updates from specific external websites (e.g., *.microsoft.com and *.windowsupdate.com). The security team wants to centrally manage and allow outbound HTTPS traffic only to these FQDNs, while blocking all other outbound internet access. Which Azure networking service should they deploy to achieve this?

A.Azure Firewall
B.Azure Application Gateway
C.Azure Front Door
D.Azure VPN Gateway
AnswerA

Azure Firewall is the only option that can control outbound traffic based on FQDN. You deploy it in a dedicated AzureFirewallSubnet and configure application rules with FQDN targets such as *.windowsupdate.com to allow or deny VM-initiated downloads. Unlike NSGs, which filter by IP/port, Azure Firewall inspects Layer 7 DNS and HTTP/S headers to enforce FQDN-based outbound filtering, making it the correct service for this requirement.

Why this answer

Azure Firewall is a managed, cloud-native network security service that can centrally enforce outbound FQDN-based rules. It allows you to create application rules that permit HTTPS traffic to specific FQDNs (e.g., *.microsoft.com) while blocking all other outbound internet access, meeting the security team's requirement for granular, centralized control.

Exam trap

The trap here is that candidates often confuse Azure Firewall with Azure Application Gateway, mistakenly thinking the latter can filter outbound traffic, but Application Gateway is strictly an inbound reverse proxy and cannot enforce outbound FQDN rules.

How to eliminate wrong answers

Option B (Azure Application Gateway) is wrong because it is a Layer 7 load balancer designed for inbound HTTP/HTTPS traffic routing and Web Application Firewall (WAF) protection, not for centrally controlling outbound traffic to specific FQDNs. Option C (Azure Front Door) is wrong because it is a global load balancer and application delivery controller for inbound traffic, optimizing performance and providing WAF, but it does not manage outbound traffic from virtual networks. Option D (Azure VPN Gateway) is wrong because it establishes encrypted tunnels between on-premises networks and Azure, or between VNets, and does not provide FQDN-based filtering or internet traffic control.

309
MCQhard

A company has a hub-spoke network topology in Azure. They need to inspect and filter all traffic flowing between spoke virtual networks for malicious content and require that the inspection is stateful. Which Azure-native service should they deploy in the hub virtual network to meet this requirement?

A.Azure Firewall
B.Network Security Groups (NSG) on the peering connections
C.Azure Application Gateway with WAF
D.Azure DDoS Protection Standard
AnswerA

Azure Firewall provides stateful inspection and can filter traffic between spoke VNets when configured as a hub. It supports network and application rules, including threat intelligence-based filtering.

Why this answer

Azure Firewall is the correct choice because it is a fully stateful, managed firewall service that can inspect and filter traffic at Layers 3–7. In a hub-spoke topology, deploying Azure Firewall in the hub virtual network allows it to centrally inspect all traffic flowing between spoke virtual networks via forced tunneling (user-defined routes) or through the hub's network virtual appliance, meeting the requirement for stateful inspection of inter-spoke traffic.

Exam trap

A common pitfall is assuming that NSGs applied to subnets within the hub or spokes can centrally inspect all inter-spoke traffic. While NSGs are stateful, they operate per subnet or NIC and cannot inspect traffic flowing through the hub without explicit routing. Azure Firewall provides the centralized stateful inspection required in a hub-spoke topology.

How to eliminate wrong answers

Option B is wrong because Network Security Groups (NSGs) are stateless (they do not track connection state) and cannot be applied directly to peering connections; they are applied to subnets or NICs and lack advanced inspection capabilities like intrusion detection. Option C is wrong because Azure Application Gateway with WAF is a Layer 7 load balancer focused on HTTP/HTTPS traffic and does not provide stateful inspection of all network traffic (e.g., non-web protocols) between spoke VNets. Option D is wrong because Azure DDoS Protection Standard is a mitigation service for volumetric DDoS attacks, not a stateful firewall for inspecting and filtering inter-spoke traffic.

310
MCQmedium

You need to secure outbound traffic from an Azure virtual network to the internet. All outbound traffic must be inspected by a firewall and logged. You also need to ensure that traffic to known malicious IP addresses is blocked. Which solution should you implement?

A.Use Network Security Groups (NSGs) with default outbound deny rules.
B.Deploy Azure Front Door with WAF policy.
C.Enable Azure DDoS Protection on the virtual network.
D.Configure Azure Firewall with threat intelligence-based filtering and route all outbound traffic through it.
AnswerD

Azure Firewall is a managed, stateful cloud-native firewall that supports threat intelligence-based filtering to alert or deny traffic to/from known malicious IPs and domains, and it can be integrated with Azure Monitor for centralized logging. By forcing all outbound traffic from the virtual network through the firewall via a user-defined route (UDR) to the firewall's private IP address, you gain full egress inspection, FQDN/network rule control, and real-time threat-intel blocking. This is the only option that directly secures and logs outbound traffic with threat intelligence in a supported, centralized manner.

Why this answer

Azure Firewall with threat intelligence-based filtering can inspect and log all outbound traffic, and it uses Microsoft's threat intelligence feeds to block traffic to known malicious IP addresses and domains. By routing all outbound traffic through the firewall (e.g., via a forced tunneling route), you meet the requirements for inspection, logging, and malicious IP blocking.

Exam trap

The trap here is that candidates often confuse Azure Firewall with NSGs or DDoS Protection, thinking that NSGs can block malicious IPs (they cannot without custom rules and lack threat intelligence) or that DDoS Protection provides outbound traffic inspection (it only protects inbound traffic against volumetric attacks).

How to eliminate wrong answers

Option A is wrong because Network Security Groups (NSGs) do not provide logging of traffic flows (they only log rules that are applied) and cannot block traffic based on threat intelligence feeds; they also lack centralized inspection capabilities. Option B is wrong because Azure Front Door is a global load balancer and application delivery controller for inbound HTTP/S traffic, not designed to inspect or control outbound traffic from a virtual network. Option C is wrong because Azure DDoS Protection only mitigates volumetric DDoS attacks against public IP addresses; it does not inspect outbound traffic, log it, or block traffic to known malicious IP addresses.

311
MCQhard

A company uses Azure Key Vault to store secrets for their applications. They want to ensure that an application hosted on an Azure virtual machine can access secrets from only a specific Key Vault, and that all traffic between the VM and Key Vault remains within the Azure network and does not traverse the public internet. Which configuration should they implement?

A.Create a private endpoint for Key Vault in the same VNet as the VM and disable public network access on the Key Vault.
B.Enable the Key Vault firewall and add the VM's public IP address to the allowed list.
C.Use a service endpoint for Key Vault on the VM's subnet, and assign a managed identity to the VM.
D.Assign a system-assigned managed identity to the VM and grant it access to the Key Vault.
AnswerA

A private endpoint attaches a network interface with a private IP from your VNet directly to Key Vault, so all requests from the VM resolve to that IP and traverse the Azure backbone rather than the public internet. Disabling public network access on the vault, which means setting the firewall's default action to deny and allowing only private endpoint connections, ensures that no traffic can reach the vault through its public DNS name or IP. This combination gives the required private connectivity and eliminates any accidental public exposure, which is why it is the correct choice.

Why this answer

It combines a private endpoint for Azure Key Vault with disabling public network access. A private endpoint assigns a private IP address from the VM's VNet to the Key Vault, ensuring all traffic stays within the Microsoft Azure backbone network and never traverses the public internet. Disabling public network access on the Key Vault firewall then blocks any attempts to access the vault via its public endpoint, enforcing that only traffic through the private endpoint is allowed.

Exam trap

The trap here is that candidates often confuse service endpoints with private endpoints, not realizing that service endpoints still use the public endpoint of the resource and do not provide true private IP-based isolation, while private endpoints assign a private IP and can fully disable public access.

How to eliminate wrong answers

Option B is wrong because adding the VM's public IP address to the Key Vault firewall allows traffic that still traverses the public internet; it does not keep traffic within the Azure network. Option C is wrong because a service endpoint for Key Vault on the VM's subnet only routes traffic to the Key Vault's public endpoint via the Azure backbone, but it does not prevent the Key Vault from being accessible over the public internet, and it does not use a private IP address; a managed identity alone does not enforce network isolation. Option D is wrong because assigning a system-assigned managed identity and granting it access to Key Vault only handles authentication and authorization; it does not address network-level isolation or prevent traffic from leaving the Azure network.

312
MCQmedium

A company uses Azure AD B2B collaboration to invite external partner users to collaborate on a project. The security team wants to ensure that when a partner user's account is disabled in their home Azure AD tenant, the user should immediately lose access to the company's resources, even if the user had a valid session token. Which configuration should they implement in cross-tenant access settings?

A.Configure cross-tenant access settings to trust the user's account status from the home tenant.
B.Configure external collaboration settings to restrict B2B users to specific apps.
C.Assign a conditional access policy that requires device compliance for B2B users.
D.Enable Azure AD Identity Protection for B2B users.
AnswerA

Enabling 'Trust user's account' in Azure AD cross-tenant access inbound settings causes Azure AD to call the user's home tenant directory during each interactive token acquisition to verify the accountEnabled attribute. If the account is disabled or deleted in the home tenant, the sign-in is blocked immediately, regardless of any previously issued tokens. This is the only option that directly and continuously checks the external account's status, not just policies or device state.

Why this answer

Configuring cross-tenant access settings to trust the user's account status from the home tenant enables Azure AD to evaluate the external user's account state (enabled/disabled) in their home tenant at each authentication. When the partner user's account is disabled in their home tenant, Azure AD will deny access even if a valid session token exists, because the token's validity is rechecked against the home tenant's account status via the cross-tenant trust policy.

Exam trap

The trap here is that candidates often confuse session token revocation with conditional access policies or app restrictions, failing to realize that only the cross-tenant trust setting directly ties the external user's access to their home tenant's account status, enabling immediate revocation without waiting for token expiry.

How to eliminate wrong answers

Option B is wrong because restricting B2B users to specific apps controls which applications they can access, not whether their account status is honored from the home tenant; it does not enforce immediate revocation when the account is disabled. Option C is wrong because a conditional access policy requiring device compliance checks the device state, not the user account status in the home tenant; it cannot detect or react to a disabled account in the external tenant. Option D is wrong because enabling Azure AD Identity Protection for B2B users provides risk-based conditional access (e.g., risky sign-ins), but it does not directly trust the home tenant's account disabled state; it relies on Microsoft's risk signals, not the partner tenant's directory status.

313
MCQmedium

You are an Azure security engineer. Your team has assigned the Azure Policy shown in the exhibit. A developer creates a new virtual network with a subnet that does not have a Network Security Group (NSG) associated. What will happen when the policy is evaluated?

A.A default NSG is automatically associated with the subnet.
B.The virtual network creation fails because a subnet lacks an NSG.
C.The virtual network is created, but the subnet is denied.
D.The virtual network is created, and a non-compliant alert is generated.
AnswerB

A policy with the 'deny' effect prevents the entire virtual network resource from being deployed when any of its subnets lacks a network security group. During deployment, Azure Resource Manager evaluates the policy against the full resource definition; because the subnet does not reference an NSG, the whole virtual network creation fails atomically. This is the correct outcome because the deny effect stops non-compliant resources from ever being provisioned.

Why this answer

The Azure Policy in the exhibit is configured with a 'Deny' effect for virtual networks that have subnets without an associated Network Security Group (NSG). When the developer attempts to create a virtual network with a subnet lacking an NSG, the policy evaluation triggers a denial of the entire virtual network creation operation. This is because the policy's condition checks each subnet for the presence of an NSG, and if any subnet is non-compliant, the 'Deny' effect prevents the resource from being created.

Exam trap

The trap here is that candidates often confuse the 'Deny' effect with 'Audit' or 'Append' effects, mistakenly thinking the virtual network will be created with a warning or that Azure will automatically remediate the missing NSG.

How to eliminate wrong answers

Option A is wrong because Azure does not automatically associate a default NSG with a subnet; NSGs must be explicitly created and associated by the user or through automation like policies. Option C is wrong because the 'Deny' effect in Azure Policy blocks the entire deployment of the virtual network, not just the subnet; partial creation is not allowed. Option D is wrong because a 'Deny' effect prevents resource creation entirely, whereas a non-compliant alert would only occur with an 'Audit' or 'Disabled' effect, not with 'Deny'.

314
MCQeasy

A security analyst uses Microsoft Sentinel. They want to create a scheduled analytics rule that runs every hour and queries Azure Activity logs to detect deployment of VMs in non-approved regions. They want to generate an incident automatically when suspicious activity is found. Which configuration is required to automatically create an incident?

A.Enable 'Create incident from alerts triggered by this rule' in the Incident settings
B.Configure the 'Alert details' section with the appropriate severity and description
C.Define entity mapping in the 'Entity mapping' tab
D.Connect Azure Activity log to Sentinel via Event Hub
AnswerA

The 'Create incident from alerts triggered by this rule' toggle resides in the Incident settings tab of the analytics rule wizard in Microsoft Sentinel. When enabled, every alert generated by the rule is automatically fed into the incident creation pipeline, where alert grouping rules determine whether alerts are merged into a single incident or create separate ones. This is the definitive switch that controls whether the rule produces incidents at all; without it, alerts are stored in the Sentinel alerts table but no incident is created.

Why this answer

The 'Create incident from alerts triggered by this rule' setting in the Incident settings tab is the specific toggle that instructs Microsoft Sentinel to automatically generate a security incident whenever the scheduled analytics rule fires an alert. Without this setting enabled, the rule will only produce raw alerts that must be manually triaged or routed through a separate automation rule to become incidents. This is the direct configuration required for automatic incident creation from a scheduled query rule.

Exam trap

The trap here is that candidates often confuse the 'Alert details' configuration (which only sets alert metadata) with the incident creation toggle, assuming that defining severity and description automatically generates an incident, when in fact a separate explicit setting is required.

How to eliminate wrong answers

Option B is wrong because configuring the 'Alert details' section (severity and description) only defines the metadata of the alert itself, not the automatic creation of an incident from that alert. Option C is wrong because entity mapping enriches alerts with entity types (e.g., IP, host) for correlation and investigation, but does not control whether an incident is automatically generated. Option D is wrong because connecting Azure Activity log to Sentinel via Event Hub is a data ingestion method, not a configuration for incident creation; the log source must already be connected for the rule to query it, but that step is separate from the incident creation setting.

315
MCQhard

Your company is migrating from on-premises Active Directory to Microsoft Entra ID. You need to synchronize user accounts and enable self-service password reset (SSPR) for cloud users. You have set up Microsoft Entra Connect Sync. Which additional configuration is required to allow password writeback for SSPR?

A.Enable password writeback in Microsoft Entra Connect and assign Azure AD Premium licenses
B.Configure pass-through authentication
C.Enable password hash synchronization
D.Install the Azure AD Password Protection proxy
AnswerA

Password writeback is an optional feature in Microsoft Entra Connect that must be explicitly enabled in the configuration wizard, and it requires Azure AD Premium P1 or P2 licenses to be assigned to users. When enabled, password changes performed in Azure AD (for example, via self-service password reset) are written back to on-premises Active Directory, making the hybrid password bidirectional. This is the only mechanism that fulfills the requirement of writing back passwords from the cloud to on-premises.

Why this answer

Password writeback requires both the feature to be enabled in Microsoft Entra Connect (via the synchronization settings) and Azure AD Premium licenses (P1 or P2) assigned to users. Without the license, the SSPR writeback functionality is not available, even if the feature is enabled in the sync tool. This combination allows password changes from the cloud to be written back to on-premises Active Directory.

Exam trap

The trap here is that candidates often assume password hash synchronization (PHS) alone enables writeback, but PHS only handles one-way hash flow to the cloud, while writeback is a separate bidirectional feature requiring explicit enablement and licensing.

How to eliminate wrong answers

Option B is wrong because pass-through authentication validates passwords against on-premises AD but does not enable password writeback for SSPR; it is an authentication method, not a writeback mechanism. Option C is wrong because password hash synchronization (PHS) is required for cloud authentication and SSPR, but it alone does not provide writeback capability; writeback is a separate feature that must be explicitly enabled. Option D is wrong because the Azure AD Password Protection proxy is used to enforce custom banned password lists for on-premises environments, not to enable password writeback for SSPR.

316
MCQmedium

Your company uses Microsoft Entra ID and has Microsoft Defender for Cloud Apps. You need to monitor and control access to cloud apps based on user behavior. Which feature should you use?

A.Conditional Access for Cloud Apps (session control)
B.Information Protection (DLP)
C.Cloud Discovery
D.Application Proxy
AnswerA

Microsoft Entra Conditional Access for Cloud Apps (session control) is an identity-driven, real-time enforcement point that uses a reverse proxy to monitor and restrict user actions inside sanctioned cloud apps. It applies policies at the session layer, allowing you to block download, upload, cut/copy/paste, or print based on user, device, or risk signals—beyond mere sign-in conditions. This is the correct answer because it directly satisfies the requirement to monitor and control behavior in real time within a cloud app session, not just gate initial access.

Why this answer

Conditional Access for Cloud Apps with session control is the correct feature because it allows you to monitor and control access to cloud apps in real time based on user behavior. It uses Microsoft Entra ID Conditional Access policies combined with Microsoft Defender for Cloud Apps to enforce session policies, such as blocking downloads or requiring multi-factor authentication, when anomalous behavior is detected.

Exam trap

The trap here is that candidates often confuse Cloud Discovery (which identifies app usage) with session control (which monitors and controls behavior in real time), leading them to select Option C incorrectly.

How to eliminate wrong answers

Option B is wrong because Information Protection (DLP) focuses on preventing data loss by inspecting and protecting sensitive data at rest or in transit, not on monitoring or controlling access based on user behavior. Option C is wrong because Cloud Discovery is used to identify shadow IT by analyzing traffic logs to discover which cloud apps are being used in your organization, not to monitor or control access based on user behavior. Option D is wrong because Application Proxy provides secure remote access to on-premises web applications through Microsoft Entra ID, but it does not include behavior-based monitoring or control of cloud app access.

317
MCQmedium

Refer to the exhibit. You are reviewing an NSG rule configuration for a subnet. The source subnet is 10.0.0.0/24 and the destination subnet is 10.0.1.0/24. What is the effect of this rule?

A.Allows outbound SSH traffic from 10.0.1.0/24 to 10.0.0.0/24.
B.Blocks inbound SSH traffic from 10.0.0.0/24 to 10.0.1.0/24.
C.Allows all inbound traffic from 10.0.0.0/24 to 10.0.1.0/24.
D.Allows inbound SSH traffic from 10.0.0.0/24 to 10.0.1.0/24.
AnswerD

This rule is configured with Direction=Inbound, Source=10.0.0.0/24, Destination=10.0.1.0/24, Protocol=TCP, Destination Port=22, and Action=Allow. Those attributes match an inbound SSH connection from a host in the source subnet to any host in the destination subnet on port 22. Because the rule's priority places it ahead of the default deny rules and the traffic matches every condition, the rule allows that SSH traffic.

Why this answer

The rule shown in the exhibit is an inbound security rule with source 10.0.0.0/24, destination 10.0.1.0/24, protocol TCP, destination port 22 (SSH), and action Allow. This explicitly permits inbound SSH traffic from the source subnet to the destination subnet. Therefore, option D is correct.

Exam trap

The trap here is that candidates often confuse the direction of the rule (inbound vs. outbound) or misinterpret the source and destination, leading them to think the rule blocks traffic or applies to the opposite direction.

How to eliminate wrong answers

Option A is wrong because the rule is inbound (traffic entering the subnet), not outbound, and SSH traffic from 10.0.1.0/24 to 10.0.0.0/24 would be outbound from the perspective of the destination subnet. Option B is wrong because the rule allows SSH traffic, not blocks it; a deny rule would have action Deny. Option C is wrong because the rule only allows SSH (port 22), not all traffic; allowing all inbound traffic would require a rule with destination port ranges * or any protocol.

318
MCQeasy

Your company uses Microsoft Entra ID. You need to block sign-ins from countries where your company does not operate. Which approach should you use?

A.Configure MFA for all users
B.Create a Conditional Access policy to block access from those countries
C.Use Identity Protection user risk policy
D.Add those countries as Named locations
AnswerB

Create a Conditional Access policy that targets the 'Locations' condition and specifies the relevant countries as Named Locations. When you set the access control to 'Block access', Entra ID checks the sign-in IP address at runtime and denies authentication if it maps to a blocked country. This policy must be assigned to the appropriate users and apps, and should exclude emergency access accounts to avoid tenant lockout.

Why this answer

The correct option is B: create a Conditional Access policy to block access from those countries. Conditional Access is the Microsoft Entra ID feature designed to enforce sign-in decisions based on conditions such as location, and a policy can be scoped to all users and cloud apps with a Block grant control, using a Named location that defines the countries to exclude or block. Option D is only a building block—Named locations merely define geographic IP ranges and do not by themselves block anything.

Option A (MFA for all users) adds an authentication requirement but does not prevent sign-ins from specific countries, and Option C (Identity Protection user risk policy) responds to risky user behavior, not geographic origin.

319
MCQhard

You are the security engineer for a multinational company that uses Azure to host critical workloads. The company has deployed Microsoft Defender for Cloud with the enhanced security features enabled on all subscriptions. Recently, a security audit revealed that several virtual machines (VMs) in the production environment are missing critical security updates. The audit report indicates that the VMs are not being assessed for missing updates by Defender for Cloud. You need to ensure that all VMs are automatically assessed for missing OS updates using Defender for Cloud's vulnerability assessment capabilities. The solution must minimize administrative overhead and should not require manual installation of agents on existing VMs. What should you do?

A.Enable the 'SQL servers on machines' plan in Defender for Cloud.
B.Enable the 'Servers' plan in Defender for Cloud and ensure that the 'Vulnerability assessment for machines' setting is turned on.
C.Configure a vulnerability assessment solution from the Azure Marketplace and assign it to the VMs.
D.Deploy the Log Analytics agent to all VMs using Azure Policy.
AnswerB

Enabling the 'Servers' plan (Microsoft Defender for Servers) and turning on the 'Vulnerability assessment for machines' setting activates the built-in Microsoft Defender Vulnerability Management (MDVM) scanning capability. This integration automatically discovers installed software, missing OS patches, and configuration vulnerabilities across Azure and hybrid VMs without requiring you to manually deploy a separate VA scanner on each machine. The resulting recommendations are surfaced in Defender for Cloud, directly satisfying the requirement to assess VMs for missing updates with minimal administrative overhead.

320
MCQhard

Your organization has a hybrid identity environment with Microsoft Entra ID (formerly Azure AD) and on-premises Active Directory. You are using Microsoft Defender for Cloud to monitor security posture. You notice that the recommendation 'MFA should be enabled on accounts with owner permissions on your subscription' shows a status of 'Unhealthy' for some accounts, but those accounts already have Microsoft Entra Conditional Access policies requiring MFA. What is the most likely reason for the discrepancy?

A.The Conditional Access policies are not applied to all users; some users bypass MFA.
B.The accounts are guest users from another tenant; MFA cannot be enforced.
C.Defender for Cloud evaluates the 'per-user' MFA state, which is separate from Conditional Access.
D.The recommendation requires MFA to be configured in the subscription's access control (IAM) blade.
AnswerC

Defender for Cloud's identity recommendations rely on the per-user MFA state in Microsoft Entra ID, which is a distinct flag set at the user level independent of any Conditional Access policies. Even when an organization has robust Conditional Access requiring MFA for all users, the per-user MFA property may still be 'Disabled', causing the recommendation to flag accounts as non-compliant. This is why the recommendation persists even when there is no actual MFA bypass, making this the correct explanation.

Why this answer

The correct answer is C: Defender for Cloud evaluates the 'per-user' MFA state, which is separate from Conditional Access. Microsoft Defender for Cloud's MFA recommendation checks whether each account has MFA enabled at the per-user level in Microsoft Entra ID (the legacy per-user MFA setting), not whether Conditional Access policies enforce MFA at sign-in. Therefore, accounts protected only by Conditional Access can still appear 'Unhealthy' because their per-user MFA status remains disabled.

Option A is wrong because the scenario states the Conditional Access policies require MFA, so the discrepancy is not caused by policy scope. Option B is wrong because guest users can be protected by MFA through Conditional Access. Option D is wrong because Azure subscription IAM does not configure MFA; MFA is an identity-level control in Microsoft Entra ID.

321
MCQmedium

Your company has an Azure subscription with several VNets. You deploy Azure Firewall in a hub VNet. You need to ensure that all traffic from spoke VNets to the internet goes through the firewall. What should you configure?

A.Configure forced tunneling on the spoke VNet gateways.
B.Enable VNet peering to the hub VNet.
C.Apply an Azure Firewall policy that denies internet access for spoke VNets.
D.Create a route table with a default route (0.0.0.0/0) to the Azure Firewall private IP and associate it with the spoke subnets.
AnswerD

This is the correct approach: create a route table containing a default route 0.0.0.0/0 with the next hop type set to VirtualAppliance and the next hop address set to the Azure Firewall's private IP. Associate that route table with all spoke subnets, which overrides Azure's system route for 0.0.0.0/0 and forces every outbound packet to be forwarded to the firewall first. The firewall then inspects the traffic using network and application rules, providing the intended centralized filtering for internet-bound and cross-premises traffic.

Why this answer

To force all internet-bound traffic from spoke VNets through Azure Firewall, you must create a user-defined route (UDR) with a default route (0.0.0.0/0) pointing to the Azure Firewall's private IP address as the next hop. This route table must be associated with the subnets in the spoke VNets, ensuring that any traffic destined for the internet is redirected to the firewall for inspection and policy enforcement.

Exam trap

The trap here is that candidates often confuse Azure Firewall policy (which controls allowed traffic) with routing (which directs traffic to the firewall), leading them to select Option C, but without a UDR, traffic never reaches the firewall for policy to be applied.

How to eliminate wrong answers

Option A is wrong because forced tunneling on a VPN gateway redirects traffic from the gateway itself to an on-premises network, not from spoke VNet subnets to Azure Firewall; it does not apply to VNet peering scenarios. Option B is wrong because VNet peering alone only enables connectivity between VNets; it does not automatically route internet traffic through the firewall—explicit UDRs are required. Option C is wrong because an Azure Firewall policy denies or allows traffic at the firewall level, but it does not force traffic to reach the firewall; without a UDR, spoke VNet traffic will use Azure's default internet path and bypass the firewall entirely.

322
MCQmedium

A company wants to identify excessive permissions across Azure, AWS, and GCP identities. Which Microsoft security capability is designed for cloud infrastructure entitlement management?

A.Azure Monitor metrics
B.Microsoft Purview eDiscovery
C.Azure Front Door WAF
D.Microsoft Entra Permissions Management
AnswerD

Microsoft Entra Permissions Management is the correct CIEM (Cloud Infrastructure Entitlement Management) tool because it continuously discovers every identity, role assignment, and permission in Azure, AWS, and GCP, then applies analytics to separate used permissions from unused ones. It calculates a 'permission creep index,' surfaces over-privileged or dormant accounts, and supports remediation actions such as permission right-sizing, on-demand access, and just-in-time elevation. That is exactly the capability needed to identify excessive permissions across all three clouds.

Why this answer

Microsoft Entra Permissions Management is a Cloud Infrastructure Entitlement Management (CIEM) solution that provides visibility into permissions assigned to identities across multi-cloud environments (Azure, AWS, GCP). It helps detect and remediate excessive, unused, or risky permissions by analyzing identity activity and entitlement data, enabling least-privilege access control.

Exam trap

The trap here is that candidates may confuse Azure Monitor (a monitoring tool) with a security management tool, or assume a WAF or eDiscovery solution can handle identity permissions, when only a dedicated CIEM like Entra Permissions Management is designed for multi-cloud entitlement visibility.

How to eliminate wrong answers

Option A is wrong because Azure Monitor metrics collect and analyze telemetry data (e.g., CPU usage, request rates) from Azure resources, not identity permissions across clouds. Option B is wrong because Microsoft Purview eDiscovery focuses on legal discovery and compliance searches for content in Microsoft 365, not on managing cloud infrastructure entitlements. Option C is wrong because Azure Front Door WAF is a web application firewall that protects HTTP/HTTPS traffic from common web exploits, not a tool for identity permission analysis.

323
MCQmedium

Refer to the exhibit. You are reviewing the Microsoft Defender for Cloud settings for a subscription. The JSON shows that 'autoProvision' is set to true. What does this mean?

A.All Microsoft Defender plans are automatically enabled for new resources
B.The Log Analytics agent is automatically installed on new Azure VMs
C.Security policies are automatically assigned to new resource groups
D.Continuous export of security alerts is enabled
AnswerB

When auto-provisioning is enabled in Microsoft Defender for Cloud, the Log Analytics agent is automatically installed on existing and newly created Azure VMs. For new VMs, the agent extension is deployed as part of the VM provisioning process, ensuring that security data like event logs, performance counters, and audit records are collected without manual intervention. This agent installation is the core behavior of auto-provisioning and is the correct interpretation of the setting in the exhibit. The agent forwards data to the configured Log Analytics workspace for analysis by Defender for Cloud.

Why this answer

When 'autoProvision' is set to true in Microsoft Defender for Cloud, it means the Log Analytics agent (formerly Microsoft Monitoring Agent) is automatically installed on all existing and new Azure VMs in the subscription. This agent collects security-related telemetry and sends it to the Log Analytics workspace associated with Defender for Cloud, enabling threat detection and security monitoring. The setting does not enable any Defender plans or policies—it only controls agent deployment.

Exam trap

The trap here is that candidates confuse 'autoProvision' (agent installation) with 'auto enablement of Defender plans' (pricing tier), leading them to incorrectly select Option A, even though enabling plans requires explicit configuration under 'Environment settings' > 'Defender plans'.

How to eliminate wrong answers

Option A is wrong because 'autoProvision' controls agent installation, not the enabling of Defender plans; Defender plans (e.g., Defender for Servers, Defender for SQL) are enabled separately via the 'pricing' tier settings. Option C is wrong because security policies are assigned at the management group or subscription level, not automatically to new resource groups, and 'autoProvision' has no effect on policy assignment. Option D is wrong because continuous export of security alerts is a separate feature configured under 'Continuous export' settings in Defender for Cloud, unrelated to the 'autoProvision' property.

324
MCQmedium

You are designing a network security solution for a multi-tier application in Azure. The web tier must be accessible from the internet, the application tier only from the web tier, and the database tier only from the application tier. All tiers are in different subnets of the same VNet. What is the minimum configuration?

A.Use service endpoints for each tier.
B.Create separate VNets for each tier and use VNet peering.
C.Deploy Azure Firewall in the VNet and route all traffic through it.
D.Configure NSGs on each subnet with appropriate allow rules.
AnswerD

Network Security Groups are the native Azure mechanism for filtering traffic between subnets, as they contain stateful rules that allow or deny traffic based on source and destination IP, port, and protocol. By assigning a distinct NSG to the web, app, and data subnets, you can explicitly permit only the necessary flows—for instance, web tier to app tier on port 443, and app tier to data tier on port 1433—while blocking all other traffic by default. NSGs are applied directly to subnets or NICs, incur no additional cost, and require no custom routing, making them the most efficient and cost-effective solution for east-west traffic isolation within a VNet. This aligns with Azure's defense-in-depth guidance of securing every subnet with an NSG.

Why this answer

Network Security Groups (NSGs) applied to each subnet can enforce least-privilege network access: allow inbound from Internet to the web tier subnet, allow inbound only from the web tier subnet to the application tier subnet, and allow inbound only from the application tier subnet to the database tier subnet. This is the minimum configuration as it uses built-in, no-cost Azure constructs without additional services or complex routing.

Exam trap

The trap here is that candidates often overcomplicate the solution by choosing Azure Firewall or separate VNets, forgetting that NSGs on subnets within a single VNet provide the simplest and most cost-effective way to enforce tier-to-tier access control.

How to eliminate wrong answers

Option A is wrong because service endpoints secure traffic to Azure PaaS services (e.g., Azure SQL, Storage) by restricting access to a specific subnet, but they do not filter traffic between subnets within the same VNet—they are not a substitute for subnet-level access control. Option B is wrong because creating separate VNets for each tier and using VNet peering is unnecessarily complex and costly; peering adds latency and management overhead, and it is not the minimum configuration when a single VNet with NSGs can achieve the same isolation. Option C is wrong because deploying Azure Firewall is an over-engineered solution for this scenario; while it can provide centralized inspection, it incurs additional cost and complexity, and NSGs alone are sufficient to enforce the required east-west traffic rules between subnets.

325
MCQmedium

Your company uses Azure Blob Storage to store sensitive documents. You need to prevent data exfiltration by ensuring that all access to the storage account is through Microsoft's private network. What should you configure?

A.Apply a network security group (NSG) to the subnet with a deny rule for internet traffic.
B.Create a private endpoint for the storage account and disable public network access.
C.Set the firewall to deny all and add a rule to allow only your VNet's public IP.
D.Enable service endpoints and configure a service endpoint policy.
AnswerB

A private endpoint places the storage account on a private IP inside your VNet, and all requests to that IP are forwarded over Microsoft's backbone through Private Link, never the public internet. Disabling public network access then closes the storage account's externally visible endpoint, so only connections through the private endpoint are successful. This combination gives both private connectivity and exfiltration protection because the resource is no longer routable from any public source.

Why this answer

Creating a private endpoint for the storage account assigns it a private IP from your virtual network, and disabling public network access ensures that all traffic to the storage account is routed through Microsoft's backbone network, preventing data exfiltration over the public internet. This configuration effectively isolates the storage account to your private network, meeting the requirement to block all public access.

Exam trap

The trap here is that candidates often confuse service endpoints (which still leave the public endpoint active) with private endpoints (which fully remove public access), leading them to choose option D or C, thinking they have achieved private network access when they have not.

How to eliminate wrong answers

Option A is wrong because an NSG deny rule for internet traffic on the subnet does not prevent direct access to the storage account's public endpoint from other sources (e.g., on-premises or other VNets) and does not force traffic through Microsoft's private network. Option C is wrong because setting the firewall to deny all and allowing only your VNet's public IP still exposes the storage account to the public internet via its public endpoint, and a public IP is not private; this does not ensure access is through Microsoft's private network. Option D is wrong because service endpoints provide direct connectivity from a VNet to Azure services over the Microsoft backbone but still leave the storage account's public endpoint enabled, allowing potential data exfiltration if the firewall is misconfigured or bypassed.

326
MCQmedium

A company stores sensitive documents in an Azure Blob Storage account. They have enabled infrastructure encryption and configured the storage account to use a customer-managed key stored in Azure Key Vault for encryption at rest. Despite this, newly uploaded blobs are still encrypted with Microsoft-managed keys. What is the most likely cause?

A.The Key Vault is in a different Azure region than the storage account.
B.The storage account does not have a system-assigned managed identity enabled.
C.A default encryption scope is configured on the blob container that uses a Microsoft-managed key.
D.The customer-managed key in Key Vault is disabled or expired.
AnswerC

Encryption scopes can be set at the container level. A default encryption scope overrides the storage account-level encryption. If the scope uses Microsoft-managed keys, new blobs in that container will not use the customer-managed key.

Why this answer

When a default encryption scope is set on a blob container, it overrides the storage account's encryption settings for all blobs uploaded to that container. Even if the storage account is configured with a customer-managed key (CMK), the container-level encryption scope with a Microsoft-managed key takes precedence, causing new blobs to be encrypted with Microsoft-managed keys instead.

Exam trap

The trap here is that candidates assume the storage account-level CMK setting applies uniformly to all blobs, but they overlook that encryption scopes at the container level can override that setting, causing a silent fallback to Microsoft-managed keys.

How to eliminate wrong answers

Option A is wrong because Azure Key Vault and the storage account can be in different regions; cross-region CMK is supported as long as the Key Vault is in the same Azure Active Directory tenant. Option B is wrong because a system-assigned managed identity is not required for CMK; a user-assigned managed identity can be used, or the storage account can use its own identity implicitly when granted access to Key Vault via access policies or RBAC. Option D is wrong because if the customer-managed key were disabled or expired, the storage account would fail to encrypt or decrypt blobs, resulting in errors (e.g., 403 Forbidden) rather than silently falling back to Microsoft-managed keys.

327
Multi-Selecteasy

Which TWO database-level security features are available in Azure SQL Database to protect sensitive data?

Select 2 answers
A.Azure Information Protection
B.Always Encrypted
C.Dynamic Data Masking
D.Azure AD authentication
E.Azure Disk Encryption
AnswersB, C

Always Encrypted is a client-side encryption technology that protects sensitive data at the column level within Azure SQL Database. The database engine stores and processes ciphertext, while the encryption keys are held by the client application, so plaintext is never exposed to the database service. This makes it a true database-level data protection feature, purpose-built to prevent even database administrators from seeing raw sensitive values.

Why this answer

Always Encrypted (B) is correct because it is a database-level feature in Azure SQL Database that encrypts sensitive columns at the client side, keeping data encrypted at rest, in transit, and in memory, with the encryption keys never revealed to the database engine. Dynamic Data Masking (C) is also correct because it is a database-level feature that limits exposure of sensitive data by masking it in query results for non-privileged users without altering the underlying data. Azure Information Protection (A) is a classification and labeling service for documents and emails, not a database-level SQL security feature.

Azure AD authentication (D) is an identity/authentication mechanism for connecting to Azure SQL Database, not a data-protection feature for sensitive columns. Azure Disk Encryption (E) encrypts the underlying OS and data disks of VMs, so it does not apply to Azure SQL Database's database-level security.

Exam trap

The trap here is that candidates often confuse Azure Information Protection (a document-level classification tool) with database-level column encryption, or they mistakenly think Azure AD authentication or Disk Encryption directly protect sensitive data within the database tables.

328
MCQmedium

Refer to the exhibit. You are creating a custom Azure RBAC role for a security analyst. The role as shown allows read access to storage accounts. The analyst reports that they cannot read the contents of a blob container in a storage account. Why is this?

A.The role is not assigned to the analyst's user account.
B.The role does not include dataActions to read blob data.
C.The assignable scope is incorrect; it should be at the resource group level.
D.The storage account does not exist in the specified subscription.
AnswerB

The custom role's 'Actions' list includes only control-plane operations such as Microsoft.Storage/storageAccounts/read, which govern resource management actions but not blob reads. Reading blob data is a data-plane operation and must be granted via the 'dataActions' property, for example Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read. Because no dataActions exist in the role definition, the analyst is denied blob read access despite having a valid role assignment.

Why this answer

The custom RBAC role only includes read permissions for the storage account's control plane (e.g., listing keys, reading properties) but lacks the necessary dataActions to read blob data. To read blob container contents, the role must include 'Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read' under dataActions, which governs access to the data plane. Without this, the analyst can see the storage account but cannot access the blobs within it.

Exam trap

The trap here is that candidates often assume that 'read' access to a storage account automatically grants read access to its data, but Azure RBAC requires explicit dataActions for data plane operations, a distinction that is frequently tested on the AZ-500 exam.

How to eliminate wrong answers

Option A is wrong because the question states the role is created and assigned, so the issue is not a missing assignment but a missing permission. Option C is wrong because the assignable scope (subscription) is broader than the resource group level and does not prevent reading blob data; the problem is the lack of dataActions, not the scope. Option D is wrong because the storage account exists in the specified subscription (the analyst can see it), and the error is about reading blob contents, not account existence.

329
MCQhard

A company uses Azure Front Door (AFD) with WAF policy in front of a web application. The security team notices that some requests from a specific IP range are being blocked incorrectly. The WAF policy uses custom rules. The team wants to allow a specific IP range while still having the WAF inspect other traffic. What is the most efficient way to configure this?

A.Add a custom rule with priority 100, action 'Block', and match condition for the IP range.
B.Create a custom rule with priority 1, action 'Allow', and match condition for the source IP range.
C.Add a rate limit rule that allows traffic from the IP range.
D.Disable the managed rule sets for the specific IP range using a geo-match condition.
AnswerB

This works because WAF custom rules are processed in ascending priority order, where priority 1 is the highest precedence. An Allow action stops further evaluation of the policy, so any request that matches the source IP range will be permitted to reach the backend without being checked against managed rule sets. This is the standard whitelisting technique for trusted IPs that trigger false positives.

Why this answer

The correct option is B: create a custom rule with priority 1, action 'Allow', and a match condition for the source IP range. In Azure Front Door WAF, custom rules are evaluated in priority order (lower numbers first), and an Allow rule matched early short-circuits the remaining WAF evaluation, so the trusted IP range bypasses blocking while all other traffic continues to be inspected by the managed and custom rules. Option A is wrong because a Block rule for that IP range would continue blocking the traffic the team wants to permit.

Option C is wrong because a rate-limit rule controls request volume, not allow-listing, and would not reliably exempt the range from other WAF blocks. Option D is wrong because managed rule sets cannot be selectively disabled per IP range via a geo-match condition; exclusions apply to specific rule/request attributes, not source IP ranges in that manner.

330
MCQmedium

A Defender for Cloud recommendation requires enabling private endpoints for a storage account. Which security risk is primarily reduced?

A.VM disk fragmentation
B.Public internet exposure of the storage service endpoint
C.Unauthorized changes to Azure AD users
D.Excessive Log Analytics ingestion
AnswerB

Correct. Private endpoints eliminate public internet access to the storage account, directly reducing the risk of unauthorized network-based attacks via the public endpoint.

Why this answer

Enabling private endpoints for a storage account connects it to an Azure Virtual Network over a private IP address, eliminating access from the public internet. This directly reduces the risk of public internet exposure of the storage service endpoint (Option B). The primary risk addressed is network-level exposure, not identity-related risks like unauthorized changes to Azure AD users (Option C).

While private endpoints can contribute to a defense-in-depth strategy, the most immediate and primary risk reduction is the removal of public network accessibility.

Exam trap

The trap is that candidates may incorrectly associate private endpoints with identity protection (Option C) because private endpoints limit network access, which could indirectly reduce identity attacks. However, the question asks for the primary risk reduced, which is specifically public internet exposure (Option B). Private endpoints are a network security control, not an identity control.

How to eliminate wrong answers

Option A is wrong because VM disk fragmentation is a performance issue related to virtual hard disk (VHD) storage and I/O operations, not a security risk that private endpoints address. Option B is wrong because while private endpoints do reduce public internet exposure, the question asks which risk is primarily reduced, and the correct answer is unauthorized changes to Azure AD users, which is not directly related to private endpoints for storage accounts. Option D is wrong because excessive Log Analytics ingestion is a cost and data volume management concern, not a security risk that private endpoints mitigate.

331
Multi-Selecthard

Which THREE components are part of Microsoft Entra Conditional Access? (Choose three.)

Select 3 answers
A.Multi-factor authentication service settings
B.Conditions (sign-in risk, device state, location)
C.Access controls (grant, block, session controls)
D.Role assignments
E.Assignments (users, groups, workload identities)
AnswersB, C, E

Conditions define the specific circumstances under which the policy is evaluated, including sign-in risk (from Identity Protection), device state (compliant or hybrid joined), and location (named locations or countries). These conditions act as the 'when' of the policy, allowing the same user assignment to trigger different access requirements based on context. This is one of the three core components of a Conditional Access policy, distinct from Assignments and Access controls.

Why this answer

Conditional Access in Microsoft Entra is built on an if-then policy model, and option B correctly identifies the 'if' side: Conditions such as sign-in risk, user risk, device state/platform, location, and client app that determine when a policy applies. Option C correctly identifies the 'then' side: Access controls, which include grant controls (for example require MFA or compliant device), block controls, and session controls (such as app-enforced restrictions or sign-in frequency). Option E correctly identifies Assignments, which scope the policy to specific users, groups, directory roles, or workload identities (service principals) as the target of the policy.

Option A is not a component of Conditional Access; MFA is one possible grant control configured within a policy, not a standalone Conditional Access component. Option D is not a Conditional Access component either; role assignments belong to Entra RBAC and govern administrative permissions, not policy evaluation.

Exam trap

The trap here is that candidates often confuse the 'Assignments' component (users/groups/workload identities) with Azure RBAC role assignments, but Conditional Access Assignments define who the policy applies to, not what permissions they have.

332
MCQeasy

You are a security engineer for a healthcare company that stores patient records in an Azure Storage account. A compliance requirement mandates that all data in the storage account be encrypted at rest using a key that the company controls and can revoke at any time. The storage account is currently configured with Microsoft-managed keys for encryption. You need to change the encryption key management to meet the compliance requirement. What should you do first?

A.Create an Azure Key Vault and generate a customer-managed key, then configure the storage account to use that key for encryption.
B.Enable Azure Disk Encryption on the storage account to use customer-managed keys.
C.Enable Secure transfer required on the storage account to enforce encryption in transit.
D.Configure the storage account to use infrastructure encryption with Microsoft-managed keys.
AnswerA

Azure Storage supports server-side encryption with customer-managed keys stored in Azure Key Vault. To meet the requirement of using a company-controlled key that can be revoked, you must create a Key Vault, generate a key, and then update the storage account's encryption settings to use that key. This gives the organization full control over the encryption key lifecycle, including rotation and revocation, satisfying the compliance mandate.

Why this answer

To meet the requirement of encrypting data at rest with a customer-managed key, you must create an Azure Key Vault, generate a key, and configure the storage account to use that key for encryption. This ensures the organization controls the key lifecycle, including revocation. Other options either address different encryption aspects (in-transit) or use Microsoft-managed keys, which do not provide the required control.

Exam trap

The trap here is confusing encryption in transit (Secure transfer required) or infrastructure encryption with customer-managed encryption at rest.

333
MCQhard

Refer to the exhibit. You are analyzing the Always Encrypted configuration for an Azure SQL Database. The SSN column uses randomized encryption, and the CreditCard column uses deterministic encryption. Which statement is true regarding querying these columns?

A.Both columns support equality searches.
B.Only the CreditCard column supports equality searches.
C.Both columns support pattern matching with LIKE.
D.Only the SSN column supports point lookups.
AnswerB

Correct. The CreditCard column uses deterministic encryption, which with the same plaintext and column encryption key always yields the same ciphertext, enabling SQL Server to perform equality comparisons and exact-match point lookups directly on the encrypted column. SSN, by contrast, uses randomized encryption, so the same value encrypts differently each time and cannot be compared for equality without client-side decryption. Therefore only CreditCard supports equality searches.

Why this answer

Deterministic encryption always generates the same ciphertext for a given plaintext, enabling equality comparisons and point lookups. Randomized encryption produces different ciphertexts each time, preventing any equality or pattern-matching operations. Therefore, only the CreditCard column (deterministic) supports equality searches.

Exam trap

The trap here is that candidates assume randomized encryption still supports equality searches because it is still 'encryption,' but the key distinction is that deterministic encryption is the only mode that allows server-side equality comparisons.

How to eliminate wrong answers

Option A is wrong because randomized encryption (SSN) does not support equality searches; only deterministic encryption does. Option C is wrong because neither randomized nor deterministic encryption supports pattern matching with LIKE, as encryption operates on the entire value and does not allow substring operations. Option D is wrong because the SSN column uses randomized encryption, which does not support point lookups (equality searches); only the CreditCard column (deterministic) supports them.

334
MCQmedium

Your security team receives a high-priority alert from Microsoft Sentinel indicating a potential brute-force attack against an Azure SQL Database. The alert was generated by an analytics rule using the following KQL query: 'SigninLogs | where ResultType == "50057" | summarize Count = count() by UserPrincipalName, IPAddress | where Count > 10'. What is the most likely cause of the alert?

A.Multiple failed MFA attempts by a user.
B.A user successfully signed in after many attempts.
C.Multiple sign-in attempts using a disabled account from the same IP address.
D.Multiple sign-in attempts from a non-existent user account.
AnswerC

Sign-in attempts against a disabled account return error code 50057 (user account disabled), which means the directory explicitly prohibits authentication. When multiple such attempts come from the same IP address, it signals a coordinated credential-stuffing or brute-force effort targeting a specific disabled account. Because a disabled account has no legitimate use, every attempt is unequivocally anomalous and represents a high-priority threat, especially if the IP shows other malicious activity.

Why this answer

The KQL query filters for ResultType == '50057', which specifically indicates 'User Account is Disabled'. The query then counts sign-in attempts by UserPrincipalName and IPAddress, triggering the alert when the count exceeds 10. This means the alert fires when there are more than 10 sign-in attempts from the same user and IP address against a disabled account, which matches the description of a brute-force attack targeting a disabled account.

Exam trap

The trap here is that candidates may confuse ResultType '50057' with generic sign-in failures or MFA errors, but Microsoft specifically uses unique error codes for each failure type, and this question tests your ability to map the code to the exact condition.

How to eliminate wrong answers

Option A is wrong because ResultType '50057' does not correspond to failed MFA attempts; failed MFA attempts return ResultType '50074' or '50076'. Option B is wrong because the query filters on ResultType '50057', which is a failure code, not a success code; successful sign-ins return ResultType '0'. Option D is wrong because non-existent user accounts generate ResultType '50034' (user does not exist), not '50057'.

335
Multi-Selectmedium

Which TWO are capabilities of Microsoft Sentinel UEBA? (Choose two.)

Select 2 answers
A.Integration with external threat intelligence feeds
B.Entity pages with timelines and related events
C.Automatic incident creation for all detected anomalies
D.Peer group analysis to detect anomalies
E.Automated response actions like blocking IPs
AnswersB, D

Entity pages in Microsoft Sentinel are a UEBA feature that aggregates an entity's activity into a timeline, showing behavior over time, related alerts, and anomalies. This allows analysts to quickly assess an entity's risk and contextualize investigations. UEBA specifically contributes anomaly-prone behavior insights and peer-group comparisons to these pages.

Why this answer

Option B is correct because Microsoft Sentinel UEBA provides entity pages that show a timeline of activities and related events for entities such as users, hosts, and IP addresses, helping analysts investigate anomalous behavior in context. Option D is correct because UEBA includes peer group analysis, which baselines an entity's behavior against similar peers to surface deviations that may indicate compromise or insider threat. Option A is not a UEBA capability per se; threat intelligence integration is a separate Sentinel feature (threat intelligence connectors and analytics rules), not part of UEBA's behavioral analytics.

Option C is incorrect because UEBA does not automatically create incidents for every detected anomaly; anomalies are surfaced as insights/entities and can be used by analytics rules to generate incidents selectively. Option E is incorrect because automated response actions such as blocking IPs are handled by Sentinel automation rules and playbooks (Logic Apps), not by the UEBA feature itself.

Exam trap

The trap here is that candidates confuse UEBA's behavioral alerting with automated incident creation or response, assuming that any anomaly detection must automatically trigger an incident or action, when in fact UEBA focuses on providing investigative context and anomaly scoring.

336
MCQmedium

A security team uses Microsoft Defender for Cloud to monitor Azure virtual machines. They want to automatically install a specific endpoint protection solution on all Windows VMs that are currently missing it, without manual intervention. The solution is not integrated natively with Defender for Cloud. Which feature should they use?

A.Enable the 'Endpoint protection' recommendation and use the 'Fix' option
B.Create an Azure Policy 'DeployIfNotExists' assignment that installs the endpoint protection extension on VMs missing it
C.Configure adaptive application controls to allow the endpoint protection software
D.Enable just-in-time VM access for the VMs
AnswerB

Create an Azure Policy definition using the DeployIfNotExists effect that targets VMs (or VM extensions) where the specific endpoint protection extension is absent. When the policy evaluates a VM and the condition is true, it deploys a linked ARM template, which installs the vendor's protection extension using the assignment's managed identity. This approach works for non-native, third-party solutions because you provide the extension template, and it can be used both for automatic evaluation of new VMs and for a remediation task to cover already-running VMs. The policy assignment must have a managed identity with Contributor (or equivalent) permissions on the target scope.

Why this answer

Azure Policy's 'DeployIfNotExists' effect can automatically deploy a custom endpoint protection extension to Windows VMs that are missing it, even if the solution is not natively integrated with Defender for Cloud. This allows the security team to enforce compliance by installing the specific third-party endpoint protection agent via a policy assignment, without manual intervention.

Exam trap

The trap here is that candidates often assume Defender for Cloud's 'Fix' option can deploy any endpoint protection solution, but it only supports solutions that are natively integrated and listed in the Defender for Cloud dashboard.

How to eliminate wrong answers

Option A is wrong because the 'Endpoint protection' recommendation in Defender for Cloud and its 'Fix' option only work with endpoint protection solutions that are natively integrated (e.g., Microsoft Defender Antivirus, Trend Micro, Symantec); it cannot deploy a non-integrated, custom solution. Option C is wrong because adaptive application controls are a whitelisting feature that controls which applications can run on a VM, not a mechanism to install or deploy software. Option D is wrong because just-in-time VM access manages network access to management ports (e.g., RDP, SSH) to reduce attack surface, not the installation of endpoint protection agents.

337
MCQmedium

You are investigating a security incident in Microsoft Sentinel. The incident involves multiple alerts from different data sources. You need to correlate the alerts to determine the full attack chain. Which Microsoft Sentinel feature should you use?

A.Incident investigation
B.Analytics rules
C.Playbooks
D.Workbooks
AnswerA

The Incident investigation view in Microsoft Sentinel opens an interactive graphical map that presents the incident's related alerts, entities, and activities as linked nodes. This tool enables you to trace relationships between hosts, IP addresses, accounts, and security events, revealing the attack path through entity timeline and expansion queries. It is precisely the correlation capability that helps analysts explore how individual alerts combine into an attacker's sequence of actions.

Why this answer

Incident investigation in Microsoft Sentinel is designed specifically for visualizing and correlating alerts within an incident to reconstruct the full attack chain. It provides a graphical map that links entities (e.g., IP addresses, user accounts, hosts) across alerts from different data sources, enabling you to trace the attacker's path step by step.

Exam trap

The trap here is that candidates confuse 'incident investigation' with 'analytics rules' or 'workbooks,' thinking that correlation happens at the rule or dashboard level, rather than understanding that investigation is a dedicated post-detection feature for exploring relationships within an incident.

How to eliminate wrong answers

Option B is wrong because analytics rules are used to generate alerts from raw data based on predefined queries, not to correlate already-generated alerts within an incident. Option C is wrong because playbooks automate response actions (e.g., blocking an IP) but do not provide visual correlation or mapping of alerts. Option D is wrong because workbooks are interactive dashboards for reporting and monitoring, not a tool for investigating a specific incident's alert correlation.

338
MCQhard

A financial services company uses Microsoft Sentinel to detect ransomware activity. They want to correlate alerts from multiple sources to reduce false positives. They have enabled Microsoft Defender for Cloud, Microsoft Defender XDR, and Azure Firewall logs. Which Sentinel feature should they use to create a single alert from multiple signals?

A.Near-real-time (NRT) rules
B.Fusion (machine learning) rules
C.Anomaly detection rules
D.Scheduled query rules
AnswerB

Fusion (machine learning) rules are specifically built for detecting multi-stage attacks by correlating alerts from multiple products, such as Microsoft Defender for Endpoint, Defender for Identity, Defender for Office 365, and Defender for Cloud. The engine uses scalable machine learning algorithms to analyze incoming alerts, identify patterns that match known kill-chain sequences, and automatically fuse them into a single actionable incident with a story of the attack. This goes beyond simple alert aggregation: Fusion evaluates the timing, context, and relationships between alerts to produce high-fidelity incidents with low false-positive rates. Because the scenario requires detecting a multi-stage attack that spans various alert sources, Fusion is the correct choice.

Why this answer

Fusion (machine learning) rules in Microsoft Sentinel are specifically designed to correlate alerts from multiple sources—such as Microsoft Defender for Cloud, Microsoft Defender XDR, and Azure Firewall logs—by using machine learning models to identify multi-stage attack patterns and reduce false positives. This makes Fusion the correct choice for creating a single alert from multiple signals, as it automatically combines related alerts into a single, high-fidelity incident.

Exam trap

The trap here is that candidates often confuse Fusion rules with Scheduled query rules, thinking they can manually write KQL to correlate alerts, but Fusion's machine learning correlation is automatic and purpose-built for multi-source alert fusion, which is exactly what the scenario requires.

How to eliminate wrong answers

Option A is wrong because Near-real-time (NRT) rules are used for querying data with low latency (up to 5 minutes) but do not correlate alerts from multiple sources; they simply run a query on a single table. Option C is wrong because Anomaly detection rules identify deviations from baseline behavior using machine learning on a single data source, not correlation across multiple sources. Option D is wrong because Scheduled query rules run periodic queries on log data but require manual correlation logic and do not automatically fuse alerts from different sources like Fusion does.

339
MCQmedium

A company deploys Azure Firewall in a hub VNet to inspect all outbound traffic from a spoke VNet. They enable VNet peering between the hub and spoke. They create a route table with a default route (0.0.0.0/0) pointing to the firewall's private IP as the next hop, and associate it with the spoke subnets. However, outbound traffic from the spoke subnets is still going directly to the internet, bypassing the firewall. What is the most likely cause?

A.The route table's next hop type is not set to 'Virtual appliance'
B.The route table is not associated with the subnet
C.The hub-spoke peering is not configured correctly
D.Azure Firewall is in a different resource group
AnswerA

For an Azure Firewall to inspect traffic via a user-defined route, the route's next hop type must be set to 'Virtual appliance' and the next hop address must be the firewall's private IP. If the next hop type is instead set to 'Internet', Azure treats the destination as directly reachable through the default route, so traffic egresses without ever hitting the firewall, even if the IP address field still contains the firewall's IP. This configuration error produces exactly the symptom described: traffic continues to flow, but none of it is actually inspected by the firewall.

Why this answer

The most likely cause is that the route table's next hop type is not set to 'Virtual appliance'. When creating a custom route in Azure, the next hop type must be explicitly set to 'Virtual appliance' and the next hop address must be the firewall's private IP. If the next hop type is left as 'Internet' or another value, Azure will ignore the custom route and use the default system route for 0.0.0.0/0, which sends traffic directly to the internet without inspection.

Exam trap

The trap here is that candidates assume any custom route with a firewall IP will work, but Azure requires the next hop type to be explicitly set to 'Virtual appliance' to override the default system route for 0.0.0.0/0.

How to eliminate wrong answers

Option B is wrong because if the route table were not associated with the subnet, the custom route would not apply at all, and traffic would use the default system route—but the question states the route table is associated with the spoke subnets, so this is not the issue. Option C is wrong because VNet peering is correctly enabled between hub and spoke; peering configuration does not affect the next hop type of a route table, and traffic can still flow through the firewall if the route is correct. Option D is wrong because Azure Firewall can be in a different resource group without impacting routing; resource group placement has no effect on network traffic flow or route table functionality.

340
MCQeasy

You need to ensure that all data at rest in an Azure Storage account is encrypted using a customer-managed key. Which feature should you enable?

A.Azure Disk Encryption
B.Azure Storage Service Encryption (SSE) with platform-managed key
C.Azure Storage Service Encryption with customer-managed key
D.Azure Information Protection
AnswerC

Customer-managed keys wrap the storage account's data encryption key in Azure Key Vault, giving you control over rotation and revocation. This satisfies the requirement for encryption at rest governed by your own key rather than a Microsoft-managed one.

Why this answer

Azure Storage Service Encryption (SSE) automatically encrypts data at rest in Azure Storage accounts. By default, it uses Microsoft-managed keys, but you can configure it to use customer-managed keys (CMK) stored in Azure Key Vault. This ensures that you control the encryption keys and can manage their lifecycle, rotation, and access policies, meeting the requirement for customer-managed key encryption.

Exam trap

The trap here is that candidates often confuse Azure Disk Encryption (which encrypts VM disks) with Storage Service Encryption (which encrypts the storage account's blob, file, queue, and table data), leading them to select Option A instead of the correct SSE with CMK.

How to eliminate wrong answers

Option A is wrong because Azure Disk Encryption (ADE) uses BitLocker (Windows) or DM-Crypt (Linux) to encrypt OS and data disks of virtual machines, not the data at rest in an Azure Storage account. Option B is wrong because SSE with platform-managed key uses Microsoft-managed keys, not customer-managed keys, so it does not satisfy the requirement for customer-managed key control. Option D is wrong because Azure Information Protection (AIP) is a classification and labeling service for documents and emails, not an encryption mechanism for data at rest in Azure Storage.

341
Multi-Selectmedium

You are designing a secure network for an e-commerce application in Azure. The application consists of web servers, application servers, and database servers. You need to ensure that inbound traffic is filtered at multiple layers. Which THREE Azure services should you use to implement defense in depth for network security?

Select 3 answers
A.Azure Application Gateway with WAF policy
B.Azure Front Door with WAF policy
C.Network Security Groups (NSGs)
D.Azure Bastion
E.Azure DNS
AnswersA, B, C

Azure Application Gateway with WAF policy operates at Layer 7, terminating TLS and inspecting incoming HTTP/HTTPS traffic before it reaches web servers. Its managed OWASP Core Rule Set blocks common attacks such as SQL injection, XSS, and command injection, and it can also enforce URL-path-based routing and listen-level rules. Unlike network-layer controls, it decodes application payloads and can make allow/deny decisions based on request content, making it the most direct web-application protection service within a regional VNet.

Why this answer

Azure Application Gateway with WAF policy (A) is correct because it provides layer 7 (HTTP/HTTPS) filtering at the regional level, inspecting inbound web traffic for OWASP Top 10 threats such as SQL injection and cross-site scripting before it reaches the web servers. Azure Front Door with WAF policy (B) is correct because it adds a global layer 7 entry point with anycast routing, TLS termination, and WAF inspection at the network edge, filtering malicious inbound traffic before it enters the Azure region. Network Security Groups (C) are correct because they enforce layer 3/layer 4 stateful packet filtering on subnets and NICs, allowing you to segment web, application, and database tiers with rules based on source/destination IP, port, and protocol.

Azure Bastion (D) is not correct here because it provides secure RDP/SSH access to VMs over TLS from the Azure portal and does not filter inbound application traffic. Azure DNS (E) is not correct because it is a name resolution service for hosting and resolving DNS zones, not a traffic-filtering or security control.

Exam trap

The trap here is that candidates often confuse Azure Bastion as a network security filtering service because it secures management access, but it does not filter inbound application traffic and is not part of a defense in depth strategy for application-layer protection.

342
MCQmedium

Your organization uses Azure Virtual WAN. You need to secure traffic between a spoke VNet and an on-premises site that connects via a Virtual WAN VPN gateway. What is the best way to inspect traffic?

A.Deploy Azure Firewall in the spoke VNet.
B.Deploy a third-party NVA in the spoke VNet.
C.Apply NSG rules on the spoke subnet.
D.Use Azure Firewall Manager to deploy a secured virtual hub.
AnswerD

Azure Firewall Manager integrates natively with Virtual WAN to deploy a secured virtual hub, meaning Azure Firewall is placed directly in the hub's transit path where all inter-spoke, branch-to-spoke, and branch-to-branch traffic converges. The firewall's routing is automatically managed by the hub's route tables, and Firewall Manager provides a single control plane to apply and audit security policies across all hubs and regions. This is the correct way to secure Virtual WAN because it centralizes inspection without requiring per-spoke configuration or custom user-defined routes.

Why this answer

Azure Firewall Manager enables you to deploy a secured virtual hub, which centrally manages and routes traffic between Virtual WAN spokes and on-premises sites through Azure Firewall for inspection. This is the best approach because it provides a scalable, hub-and-spoke architecture with forced tunneling and routing policies that ensure all traffic between the spoke VNet and the on-premises site is inspected without requiring additional NVAs or complex user-defined routes.

Exam trap

The trap here is that candidates often assume deploying a firewall directly in the spoke VNet (Option A) is sufficient, but they overlook that Virtual WAN's automatic routing bypasses spoke-based firewalls unless complex and unsupported UDRs are configured, making the secured virtual hub the only native and supported solution.

How to eliminate wrong answers

Option A is wrong because deploying Azure Firewall in the spoke VNet does not automatically route traffic from the Virtual WAN VPN gateway through it; you would need complex user-defined routes and it breaks the Virtual WAN routing model. Option B is wrong because a third-party NVA in the spoke VNet also requires manual routing configuration and does not integrate natively with Virtual WAN's automatic routing, leading to asymmetric routing or traffic bypass. Option C is wrong because NSGs are stateful packet filters that operate at the subnet level and cannot perform deep packet inspection or application-level filtering; they are also not designed to inspect traffic that is routed through a Virtual WAN hub.

343
MCQmedium

You are a security administrator for a company that stores sensitive data in Azure Blob Storage. The data must be encrypted at rest with a customer-managed key (CMK) stored in Azure Key Vault, and the key must be automatically rotated every 90 days. You need to configure the storage account to meet these requirements. What should you do?

A.Use a customer-provided key (CPK) on each blob upload and configure an Azure Automation runbook to rotate the key every 90 days.
B.Enable infrastructure encryption on the storage account and set the key rotation policy in Key Vault to 90 days.
C.Configure the storage account to use a customer-managed key from Key Vault and set the key rotation policy in Key Vault to 90 days.
D.Create a new customer-managed key in Key Vault every 90 days and manually update the storage account to use the new key.
AnswerC

Configuring the storage account to use a customer-managed key from Key Vault ensures that the data encryption key is wrapped by the CMK. Setting a rotation policy in Key Vault automatically rotates the key every 90 days. Because the storage account references the Key Vault key, it will use the new key version after rotation, meeting both encryption and rotation requirements.

Why this answer

To use a customer-managed key for Azure Storage encryption, you must configure the storage account to reference a key in Key Vault. Key Vault's rotation policy can automatically rotate the key on a schedule, and the storage account will use the latest version if configured to do so. This provides automatic key rotation without manual intervention, satisfying the 90-day requirement.

Exam trap

The trap here is confusing infrastructure encryption or customer-provided keys with customer-managed keys stored in Key Vault, which are distinct features with different configuration steps.

344
MCQhard

A security operations team uses Microsoft Sentinel. They have a scheduled analytics rule that generates an incident when a user signs in from an unusual location. They want to automatically assign the incident to the 'Security Engineering' team and set its severity to 'High' when it is created. Which feature should they use?

A.Automation rules
B.Playbooks
C.Incident settings in analytics rule
D.Workbooks
AnswerA

Automation rules in Microsoft Sentinel run immediately on incident creation, letting you assign the owner to 'Security Engineering' and set severity to 'High' without playbook latency. Unlike analytics rule configuration, they act post-creation, satisfying the requirement to modify incidents automatically at creation time.

Why this answer

Automation rules in Microsoft Sentinel allow you to centrally manage the automated handling of incidents, including assigning them to a specific team and setting their severity. When a scheduled analytics rule generates an incident, an automation rule can trigger on incident creation to perform these actions without requiring a playbook or manual intervention.

Exam trap

The trap here is that candidates often confuse playbooks with automation rules, thinking that playbooks are required for any automated action, when in fact automation rules are the native, simpler mechanism for assignment and severity changes without needing Logic Apps.

How to eliminate wrong answers

Option B is wrong because playbooks are collections of actions based on Azure Logic Apps that run in response to alerts or incidents, but they are typically used for more complex, multi-step orchestration and require additional configuration; automation rules are the simpler, built-in feature for direct assignment and severity changes. Option C is wrong because incident settings within an analytics rule only allow you to configure group-related settings (e.g., alert grouping) and entity mapping, not post-creation actions like assignment or severity override. Option D is wrong because workbooks are interactive dashboards for visualizing data and reports, not for automating incident response actions.

345
MCQhard

A healthcare organization stores sensitive patient data in Azure SQL Database. They need to encrypt specific columns containing medical history so that even database administrators with the 'sysadmin' role cannot view the plaintext data. Additionally, they need to support equality comparisons (WHERE clauses) on the encrypted columns. Which encryption technology should they implement?

A.Transparent Data Encryption (TDE)
B.Always Encrypted with randomized encryption
C.Always Encrypted with deterministic encryption
D.Dynamic Data Masking
AnswerC

Always Encrypted with deterministic encryption derives a fixed initialization vector from the plaintext value, so identical plaintexts always yield identical ciphertexts, enabling the server to perform equality comparisons, joins, and exact-match lookups without ever seeing the plaintext. The column encryption key is stored and used only on the client side (for example, in Windows Certificate Store or Azure Key Vault), meaning SQL Server and DBAs see only opaque ciphertext and cannot decrypt the data. This achieves the dual goal of secure patient data protection while retaining the ability to query by known identifiers.

Why this answer

Always Encrypted with deterministic encryption is correct because it encrypts specific columns at the client side, ensuring that even database administrators with 'sysadmin' role cannot view plaintext data. Deterministic encryption generates the same ciphertext for identical plaintext values, which allows equality comparisons (WHERE clauses) on encrypted columns, meeting both requirements.

Exam trap

The trap here is that candidates confuse Dynamic Data Masking with encryption, thinking it prevents privileged users from seeing data, when in fact it only masks output and does not protect data at rest or from direct queries by sysadmins.

How to eliminate wrong answers

Option A is wrong because Transparent Data Encryption (TDE) encrypts the entire database at rest but does not protect data from database administrators who have access to the database engine; they can still query plaintext data. Option B is wrong because Always Encrypted with randomized encryption does not support equality comparisons (WHERE clauses) on encrypted columns, as it produces different ciphertext for the same plaintext each time. Option D is wrong because Dynamic Data Masking only obfuscates data at query result time but does not encrypt the underlying data, so administrators with 'sysadmin' role can still access plaintext by running queries without masking.

346
MCQmedium

Your company deploys a new Azure application gateway with WAF policy in prevention mode. After deployment, users report that legitimate traffic is being blocked. You need to identify which WAF rules are causing the blocks without affecting the security posture. What should you do?

A.Disable the WAF policy temporarily.
B.Create a custom rule to allow all traffic.
C.Set the WAF policy to custom rules only.
D.Change the WAF policy mode to detection.
AnswerD

Changing the WAF policy mode to detection makes the gateway evaluate every managed and custom rule and log all matches to the WAF diagnostic logs, but it stops enforcing blocking actions. You can then correlate the rejected requests with the exact rule ID and request details in Log Analytics, confirming whether this is a false positive. Once you've identified the offending rule, you can add exclusions or tune rule actions and switch the policy back to prevention mode.

Why this answer

Switching the WAF policy mode from prevention to detection allows the application gateway to log WAF rule matches without blocking legitimate traffic. This enables you to review the logs and identify which specific rules are causing false positives, while still maintaining visibility into threats. Once identified, you can fine-tune the rules or create exceptions without disrupting the security posture.

Exam trap

The trap here is that candidates may think disabling the WAF or creating an allow-all rule is a quick fix, but the correct approach is to use detection mode to diagnose false positives without compromising security.

How to eliminate wrong answers

Option A is wrong because disabling the WAF policy entirely removes all protection, leaving the application vulnerable to attacks during troubleshooting. Option B is wrong because creating a custom rule to allow all traffic effectively bypasses the WAF, negating its security benefits and defeating the purpose of having a WAF in place. Option C is wrong because setting the WAF policy to custom rules only disables the managed rule sets, which are the primary source of false positives in this scenario, and still does not provide a diagnostic view of which rules are blocking traffic.

347
MCQeasy

Your company has a hybrid environment with Azure resources and on-premises servers. You have deployed Microsoft Sentinel and connected it to Azure AD, Azure Activity Logs, and Windows Security Events from on-premises servers via the Log Analytics gateway. You need to create a workbook that shows the number of sign-ins from each country over the last 24 hours. The data source is the SigninLogs table. However, the workbook does not display any data. You verify that the Log Analytics workspace is receiving sign-in logs from Azure AD. Which of the following is the most likely reason the workbook shows no data?

A.The workbook uses a different visualization type that requires KQL.
B.The Log Analytics gateway is blocking the sign-in logs.
C.The workbook's time range filter is set to 'Last 7 days' but the query uses a 24-hour filter incorrectly.
D.The Log Analytics workspace is not receiving sign-in logs from Azure AD.
AnswerC

This is correct. The workbook's time range filter might be set to a broader range (e.g., last 7 days) while the query uses a 24-hour filter. If the query does not correctly use the time parameter, it may return no results when the dashboard filter is applied.

Why this answer

The workbook likely has a time range filter set to 'Last 7 days', but the underlying KQL query uses a hardcoded 24-hour filter. This mismatch causes the query to return data only for the last 24 hours, but the dashboard filter may interfere or the query may be incorrectly referencing the time parameter. As a result, no data is displayed.

Option A is incorrect because workbooks rely on KQL queries regardless of visualization type. Option B is incorrect because the Log Analytics gateway is used for on-premises data, not for Azure AD sign-in logs which stream directly to the workspace. Option D is incorrect because the problem statement confirms sign-in logs are being received.

Exam trap

The most common trap is assuming that if logs are flowing into the Log Analytics workspace, the workbook will automatically show data. However, workbook queries often have their own time filters that must align with the dashboard's time range. Misconfigured time parameters are a frequent hidden issue.

348
MCQmedium

A company stores sensitive data in Azure Blob Storage. They want to encrypt the data at rest using customer-managed keys (CMK) stored in Azure Key Vault. Additionally, they want the key to be automatically rotated every 90 days without manual intervention. Which configuration should they implement?

A.Enable Azure Storage encryption with a CMK and configure a rotation policy on the storage account.
B.Enable Azure Storage encryption with a CMK and enable automatic key rotation in Azure Key Vault by creating a rotation policy.
C.Enable Azure Storage encryption with a CMK and manually rotate the key every 90 days.
D.Use Azure Storage service-side encryption with platform-managed keys and enforce rotation via Azure Policy.
AnswerB

This is correct because with a customer-managed key (CMK) in Azure Key Vault, you can define a key rotation policy that automatically generates new key versions on a schedule. The storage account must reference the key URI without a specific version so it automatically uses the latest key version. This provides the required automatic rotation of the encryption key, fully managed through Azure Key Vault, without manual intervention.

Why this answer

Azure Key Vault supports automatic key rotation through a rotation policy, which can be configured to rotate a customer-managed key (CMK) every 90 days without manual intervention. When Azure Storage encryption uses a CMK stored in Key Vault, the storage account references the key version, and enabling a rotation policy in Key Vault automatically creates new key versions, which Azure Storage then uses for encryption. This satisfies the requirement for automated 90-day rotation without manual steps.

Exam trap

The trap here is that candidates confuse where the rotation policy is configured—thinking it is on the storage account (Option A) rather than in Azure Key Vault, or they assume platform-managed keys can be scheduled for rotation (Option D), which is not supported.

How to eliminate wrong answers

Option A is wrong because a rotation policy cannot be configured on the storage account itself; key rotation is managed in Azure Key Vault, not on the storage account resource. Option C is wrong because it requires manual rotation every 90 days, which contradicts the requirement for automatic rotation without manual intervention. Option D is wrong because platform-managed keys (PMK) cannot be rotated on a custom schedule; they are managed entirely by Microsoft, and Azure Policy cannot enforce a specific rotation interval for PMKs.

349
MCQmedium

Your organization uses Microsoft Defender for Cloud to monitor Azure SQL databases. You receive an alert indicating a potential SQL injection attack. What is the most effective immediate action to validate and respond?

A.Enable Transparent Data Encryption (TDE) on the database
B.Run a vulnerability assessment on the database
C.Review the SQL database auditing logs to identify the source queries
D.Immediately block all IP addresses from the alert in the SQL firewall
AnswerC

SQL database auditing tracks database events and writes them to an audit log in Azure Storage, Log Analytics, or Event Hub. Reviewing these logs lets you see the exact queries, the principal/user, the source IP address, and the timestamp of the suspicious activity, confirming whether the Defender alert is a genuine attack and revealing its origin. This is the direct and immediate way to validate an alert from Microsoft Defender for Cloud.

Why this answer

SQL database auditing logs capture detailed information about database events, including the exact SQL queries executed against the database. Reviewing these logs allows you to identify the source queries, the originating IP addresses, and the user accounts involved in the suspected SQL injection attack, enabling you to validate the alert and take targeted remediation actions. This is the most effective immediate step to confirm the attack and understand its scope before implementing broader security controls.

Exam trap

The trap here is that candidates often confuse reactive forensic actions (like reviewing audit logs) with proactive security controls (like TDE or vulnerability assessments), or they assume that blocking IPs is the immediate best practice without first validating the attack through logs, which is a common mistake in incident response scenarios.

How to eliminate wrong answers

Option A is wrong because Transparent Data Encryption (TDE) encrypts data at rest, which protects against physical theft of storage media but does not prevent or detect SQL injection attacks, which exploit application-layer vulnerabilities. Option B is wrong because running a vulnerability assessment identifies misconfigurations and missing patches but does not provide real-time forensic data about an ongoing or recent attack; it is a proactive security measure, not a reactive validation step. Option D is wrong because immediately blocking all IP addresses from the alert in the SQL firewall could disrupt legitimate traffic and may not address the root cause if the attack originated from a compromised application or a spoofed IP; it is a reactive measure that should be taken only after confirming the malicious queries through auditing logs.

350
MCQhard

A company has an Azure SQL Database with a private endpoint connection. The database is accessed from on-premises via ExpressRoute and from other Azure virtual networks (VNets) via VNet peering. The security team wants to ensure that all queries from both on-premises and peered VNets go through the private endpoint and NEVER use the public endpoint, even as a fallback. Which additional configuration is required to enforce this?

A.Configure a Network Security Group (NSG) on the subnet hosting the private endpoint to deny outbound traffic to the public endpoint's IP addresses.
B.Enable Azure SQL Auditing and configure a log analytics workspace to monitor for public endpoint calls, then manually block them.
C.Disable public network access on the Azure SQL server.
D.Configure a service endpoint for Azure SQL on the VNet and associate a firewall rule allowing only the VNet traffic.
AnswerC

Correct. Disabling public network access on the SQL server blocks all traffic from the public internet, leaving only the private endpoint as the entry point. This ensures all traffic from on-premises and peered VNets must use the private endpoint.

Why this answer

Disabling public network access on the Azure SQL server explicitly blocks all traffic that does not originate from a private endpoint. This setting ensures that even if a client attempts to connect using the public endpoint (e.g., via a misconfigured connection string or DNS resolution fallback), the server will reject the connection. This is the only configuration that enforces the requirement that all queries—from on-premises via ExpressRoute or from peered VNets—must go through the private endpoint and never use the public endpoint.

Exam trap

The trap here is that candidates often confuse 'private endpoint' with 'service endpoint' or think that NSGs or monitoring can enforce private-only access, when in fact the only way to guarantee that no traffic uses the public endpoint is to disable public network access at the server level.

How to eliminate wrong answers

Option A is wrong because NSGs are not supported on subnets hosting private endpoints; Azure blocks NSG association on private endpoint subnets, and even if applied, an NSG cannot block outbound traffic from the private endpoint to the public endpoint because the private endpoint itself does not route traffic to the public IP—the issue is client-side DNS resolution. Option B is wrong because auditing and monitoring only detect public endpoint usage after the fact; they do not prevent the connection from using the public endpoint as a fallback, which violates the 'never use' requirement. Option D is wrong because service endpoints allow traffic from the VNet to the Azure SQL public endpoint, which is exactly what the security team wants to avoid; service endpoints do not enforce private endpoint usage and would permit public endpoint access from peered VNets.

351
MCQhard

You are designing a Microsoft Sentinel solution for a multinational company. The company requires that security incidents be correlated across regions, but data residency mandates require logs to remain in their original region. What should you implement?

A.Deploy one Microsoft Sentinel workspace per region and use cross-workspace querying for correlation
B.Deploy a separate Log Analytics workspace per region, but only one Sentinel workspace
C.Deploy a single Microsoft Sentinel workspace in a central region and use Azure Lighthouse
D.Deploy a single Microsoft Sentinel workspace and use data collection rules to filter logs
AnswerA

Deploying one Microsoft Sentinel workspace per region satisfies data residency because each workspace is a Log Analytics workspace that ingests and stores logs within its own geographic boundary. Cross-workspace querying with the 'workspace()' expression or Azure Resource Graph lets security analysts run a single KQL query that references multiple workspaces, correlating threats without moving data out of its resident region. Sentinel's built-in UEBA and analytics rules work on each workspace, while cross-workspace views preserve centralized hunting.

Why this answer

Deploying one Microsoft Sentinel workspace per region satisfies data residency mandates by keeping logs in their original region, while cross-workspace querying allows security incidents to be correlated across regions using KQL queries that span multiple workspaces. This approach ensures compliance with regional data sovereignty laws without sacrificing the ability to perform centralized threat detection and investigation.

Exam trap

The trap here is that candidates often assume a single Sentinel workspace is required for centralized correlation, overlooking that cross-workspace querying can achieve the same goal while respecting data residency mandates.

How to eliminate wrong answers

Option B is wrong because deploying a separate Log Analytics workspace per region but only one Sentinel workspace violates data residency mandates, as Sentinel ingests and stores logs in the workspace's region, forcing all logs into a single region. Option C is wrong because a single Sentinel workspace in a central region would store all logs in that region, directly conflicting with data residency requirements. Option D is wrong because data collection rules (DCRs) control ingestion and transformation of logs but do not alter the storage location; logs still reside in the single workspace's region, failing the residency mandate.

352
MCQmedium

Your company uses Azure Storage to store sensitive customer data. You need to ensure that only authorized applications running on Azure VMs can access the storage account without using shared keys or SAS tokens. What should you configure?

A.Use Azure AD authentication with storage account access keys.
B.Enable Azure Storage firewall, deny access from all networks, and add a private endpoint. Then assign a managed identity to the VMs and grant it the necessary RBAC role.
C.Configure a storage account key and distribute it to the applications.
D.Generate a SAS token with IP restrictions and embed it in the application code.
AnswerB

This is the correct keyless design. Enabling the storage firewall to deny all public network traffic ensures the account is unreachable from the internet, while adding a private endpoint places the storage account on a private IP within your VNet, so traffic never traverses the public endpoint. Assigning a managed identity to the VMs and granting the appropriate RBAC role (e.g., Storage Blob Data Reader) provides identity-based, least-privilege access without any account key or SAS token, and access is further verified against the virtual network rules.

Why this answer

Azure Storage firewall with service endpoints or private endpoints, combined with managed identity, allows secure access without shared keys or SAS tokens. Option A (storage account key) is a shared key. Option C (SAS token) is a shared access signature.

Option D (access keys) are shared keys.

353
Multi-Selectmedium

Which THREE of the following are features of Microsoft Defender for Cloud's Cloud Security Posture Management (CSPM)?

Select 3 answers
A.Vulnerability scanning of containers
B.Security recommendations for resources
C.Secure Score
D.Threat detection for VMs
E.Regulatory compliance assessments
AnswersB, C, E

CSPM generates recommendations to improve security.

Why this answer

CSPM in Microsoft Defender for Cloud continuously assesses Azure resources against built-in security policies and industry best practices, generating actionable security recommendations to harden the environment. These recommendations are derived from the Azure Security Benchmark and are displayed in the Recommendations blade, directly influencing the Secure Score.

Exam trap

The trap here is that candidates confuse CSPM's configuration-based recommendations and Secure Score with the threat detection and vulnerability scanning features that belong to separate Defender for Cloud workload protection plans, leading them to select options A or D as CSPM features.

354
Multi-Selecthard

Which THREE are valid ways to trigger a playbook in Microsoft Sentinel? (Choose three.)

Select 3 answers
A.Manually from an incident by selecting 'Run playbook'.
B.From an automation rule when an incident is created.
C.From a watchlist item update.
D.From an entity page by clicking 'Investigate'.
E.From an automation rule when an alert is created.
AnswersA, B, E

From an incident, clicking 'Run playbook' opens a side panel where you can select an enabled playbook, which then executes with the Incident trigger. This manual trigger is essential for ad-hoc response, testing, or remediation tasks that require human judgment, and it passes the full incident context—including alerts, entities, and metadata—to the playbook. It is a valid, documented way to launch a playbook on demand.

Why this answer

Option A is correct because Microsoft Sentinel allows analysts to manually trigger a playbook directly from an incident's page by selecting 'Run playbook', which executes the associated Logic App workflow on demand. Option B is correct because automation rules in Microsoft Sentinel can be configured with a trigger of 'When incident is created' and an action of 'Run playbook', automatically invoking the playbook as soon as the incident is generated. Option E is correct because automation rules also support the trigger 'When alert is created', allowing a playbook to be run automatically at alert creation time, before or independently of incident creation.

Option C is not a valid trigger because watchlists are reference data sources and do not have automation-rule triggers for playbook execution. Option D is not a valid trigger because the 'Investigate' action on an entity page opens the investigation experience and does not itself run a playbook.

Exam trap

A common mistake is confusing automation rule triggers: remember that automation rules can trigger on both alert creation and incident creation, but not on watchlist updates or entity page actions.

355
MCQeasy

You need to ensure that all new blobs uploaded to an Azure Storage account are automatically encrypted at rest. What is the simplest way to achieve this?

A.Use Azure Disk Encryption on any VMs writing to storage.
B.Implement client-side encryption in the application.
C.Enable Azure Storage Service Encryption (SSE) on the storage account.
D.Configure a customer-managed key in Azure Key Vault.
AnswerC

Azure Storage Service Encryption (SSE), now formally called Azure Storage encryption, is automatically enabled at the storage account level and transparently encrypts all data at rest—including blobs, files, queues, and tables—using AES-256 before it is written to disk. No extra configuration is needed for new blobs because encryption is applied by the platform on every write and decrypted on every read without any code changes. Ensuring that this setting is enabled (or simply confirming it is already on by default) directly guarantees that all new blob uploads are encrypted at rest.

Why this answer

Azure Storage Service Encryption (SSE) automatically encrypts data at rest for all storage accounts using 256-bit AES encryption, and it is enabled by default for new storage accounts. This ensures that any new blobs uploaded are encrypted without requiring any application changes or additional configuration, making it the simplest solution.

Exam trap

The trap here is that candidates often confuse Azure Disk Encryption (which encrypts VM disks) with Storage Service Encryption (which encrypts data at rest in Azure Storage), leading them to select option A incorrectly.

How to eliminate wrong answers

Option A is wrong because Azure Disk Encryption encrypts the OS and data disks of VMs, not the blobs stored in Azure Storage; it protects data at the VM level, not the storage service level. Option B is wrong because client-side encryption requires modifying the application code to encrypt data before uploading, which adds complexity and is not the simplest approach. Option D is wrong because configuring a customer-managed key in Azure Key Vault is an additional step that can be used with SSE for more control, but SSE with Microsoft-managed keys already provides automatic encryption at rest without extra configuration.

356
MCQmedium

You are deploying a new application on Azure VMs. The application must be encrypted at rest and during transmission. Which combination of features should you implement?

A.Azure Firewall and Azure Disk Encryption
B.Azure Disk Encryption and HTTPS
C.Azure Storage Service Encryption and SSL
D.Azure Disk Encryption and SSL
AnswerB

This combination fully satisfies both stated requirements. Azure Disk Encryption encrypts the VM's managed OS and data disks at rest using BitLocker for Windows and DM-Crypt for Linux, integrating with Azure Key Vault to protect the disk encryption keys. HTTPS, which relies on TLS, encrypts the application traffic in transit between the VM and its clients, preventing eavesdropping and tampering along the network path. Together, they provide the required at-rest and in-transit confidentiality for an Azure VM-hosted application.

Why this answer

Azure Disk Encryption (ADE) provides at-rest encryption for Azure VM disks using BitLocker (Windows) or DM-Crypt (Linux), while HTTPS ensures encryption in transit between the client and the application. Together, they satisfy the requirement for encryption both at rest and during transmission.

Exam trap

The trap here is that candidates often confuse Azure Storage Service Encryption (which applies to Azure Blob/File storage) with Azure Disk Encryption (which applies to VM disks), or they assume SSL/TLS alone covers all encryption needs, forgetting that at-rest encryption requires a separate mechanism like ADE.

How to eliminate wrong answers

Option A is wrong because Azure Firewall is a network security service that filters traffic, not an encryption mechanism; it does not encrypt data at rest or in transit. Option C is wrong because Azure Storage Service Encryption (SSE) encrypts data at rest in Azure Storage accounts, but it does not apply to VM disks, and SSL (the predecessor to TLS) is a transport encryption protocol, but the combination does not cover VM disk encryption. Option D is wrong because SSL (or TLS) provides in-transit encryption, but Azure Disk Encryption is needed for at-rest encryption; however, the question asks for the correct combination, and Option B explicitly pairs ADE with HTTPS (which is HTTP over TLS), making it the precise answer.

357
MCQeasy

A company has established a site-to-site VPN connection between its on-premises network and an Azure virtual network using an Azure VPN gateway. The security team wants to confirm that all traffic crossing the VPN tunnel is encrypted. Which protocol does the Azure VPN gateway use to encrypt the data?

A.IPSec (Internet Protocol Security)
B.SSL (Secure Sockets Layer) / TLS (Transport Layer Security)
C.SSH (Secure Shell)
D.PGP (Pretty Good Privacy)
AnswerA

Azure site-to-site VPN tunnels rely on IPSec in tunnel mode to encrypt and authenticate every packet crossing the connection. IPSec uses the Internet Key Exchange (IKE) protocol to negotiate security associations, then applies Encapsulating Security Payload (ESP) for confidentiality and integrity. Because IPSec operates at the network layer (Layer 3), it transparently protects all IP payloads between the on-premises gateway and the Azure VPN gateway. This makes IPSec the mandatory protocol for Azure VPN site-to-site configurations, not SSL/TLS or other application-layer protocols.

Why this answer

Azure VPN gateways use IPsec (Internet Protocol Security) in tunnel mode to encrypt all data traversing the site-to-site VPN tunnel. IPsec provides confidentiality, integrity, and authentication at the IP layer, ensuring that all traffic between the on-premises network and Azure virtual network is encrypted and secure.

Exam trap

The trap here is that candidates may confuse SSL/TLS-based VPNs (like OpenVPN) with IPsec-based site-to-site VPNs, but Azure VPN gateways exclusively use IPsec for site-to-site connections, not SSL/TLS.

How to eliminate wrong answers

Option B is wrong because SSL/TLS operates at the transport layer (Layer 4) and is used for securing web traffic (HTTPS), not for site-to-site VPN tunnels which require IP-layer encryption. Option C is wrong because SSH is a protocol for secure remote administration and file transfer, not for encrypting bulk network traffic across a VPN tunnel. Option D is wrong because PGP is an encryption program used for securing emails and files, not for network-layer VPN encryption.

358
MCQeasy

You are configuring security for an Azure App Service web app that connects to an Azure SQL Database. You need to ensure that the database connection string does not contain credentials in plaintext. What should you use?

A.Store the connection string in the web.config file with encryption.
B.Store the connection string in Azure Key Vault and use a Key Vault reference in the App Service application settings.
C.Store the connection string in Azure App Configuration with encryption.
D.Store the connection string in an App Service application setting without encryption.
AnswerB

Using an Azure Key Vault reference in an App Service application setting, written as `@Microsoft.KeyVault(SecretUri=https://myvault.vault.azure.net/secrets/...)`, removes the connection string from the App Service configuration entirely. App Service authenticates to Key Vault with the app's managed identity, retrieves the secret at runtime, and injects it as an environment variable, so the secret is never stored in plaintext on the platform. This enables central secret governance, granular access policies, full audit logging, and rotation without redeploying the application, making it the most secure and operationally efficient option.

Why this answer

Azure Key Vault provides a secure, centralized store for secrets like database connection strings. By using a Key Vault reference in the App Service application settings (e.g., @Microsoft.KeyVault(SecretUri=https://myvault.vault.azure.net/secrets/mysecret/)), the connection string is never exposed in plaintext in configuration files or environment variables, and access is controlled via managed identities or service principals.

Exam trap

The trap here is that candidates often confuse Azure App Configuration (which is for feature flags and configuration management, not secret storage) with Azure Key Vault, or they assume that encrypting a configuration file (web.config) is sufficient, not realizing that the decryption key is co-located and the plaintext is still exposed at runtime.

How to eliminate wrong answers

Option A is wrong because encrypting the web.config file (e.g., using aspnet_regiis.exe) only protects the file at rest on the server, but the decryption key is stored on the same machine, making it vulnerable to compromise; Azure App Service does not support this encryption natively, and the plaintext is still exposed during runtime. Option C is wrong because Azure App Configuration with encryption still stores the secret in a configuration store that requires additional access management, but it does not provide the same level of secret rotation, auditing, and access control as Key Vault; the connection string would still be retrievable in plaintext by anyone with access to the App Configuration store. Option D is wrong because storing the connection string in an App Service application setting without encryption leaves it as plaintext in the Azure portal and in the runtime environment, which can be exposed through logs, debugging, or compromised access.

359
MCQhard

A compliance team wants evidence that Azure resources are evaluated against the Microsoft Cloud Security Benchmark. Which Defender for Cloud area should they use?

A.Regulatory compliance and security policy assignments
B.Microsoft Entra app consent settings
C.Azure Firewall DNAT rules
D.Log Analytics saved searches only
AnswerA

Regulatory compliance and security policy assignments are the primary mechanism in Azure for evidence that resources comply with standards. Azure Policy initiative definitions (e.g., CIS Microsoft Azure Foundations Benchmark, NIST SP 800-53, HIPAA) continuously evaluate resource configuration against required controls and report compliance states per resource. Defender for Cloud's regulatory compliance blade aggregates these policy assignments into a dashboard showing pass/fail status, making them the direct evidence source for a compliance team.

Why this answer

The Regulatory compliance dashboard in Microsoft Defender for Cloud provides continuous monitoring of Azure resources against the Microsoft Cloud Security Benchmark (MCSB). It maps built-in policy assignments to compliance controls, generates a compliance score, and offers remediation steps. This is the designated area for evidence of MCSB evaluation.

Exam trap

The trap here is that candidates may confuse the Regulatory compliance dashboard with general log querying or network security controls, overlooking that the MCSB is specifically enforced through Azure Policy initiatives within Defender for Cloud's compliance monitoring.

How to eliminate wrong answers

Option B is wrong because Microsoft Entra app consent settings manage user consent for application permissions, not compliance evaluation against security benchmarks. Option C is wrong because Azure Firewall DNAT rules configure inbound network address translation for traffic, unrelated to compliance assessment. Option D is wrong because Log Analytics saved searches are used for querying log data, not for providing a structured compliance dashboard against the MCSB.

360
MCQhard

You have an Azure Kubernetes Service (AKS) cluster that needs to restrict egress traffic to specific Azure services (e.g., Azure Container Registry, Azure Monitor). You want a managed solution that allows you to define FQDN-based rules. Which Azure service should you use?

A.Azure Application Gateway
B.Azure Front Door
C.Network Security Groups (NSGs)
D.Azure Firewall
AnswerD

Azure Firewall is a managed, cloud-native firewall service that provides application rules specifically designed for outbound FQDN filtering. It can inspect and allow/deny traffic based on fully qualified domain names, including wildcard FQDNs and FQDN tags, by examining the HTTP Host header or TLS SNI. For an AKS cluster, you can route all egress traffic through the firewall using user-defined routes or a secured virtual hub, enabling centralized, DNS-aware policy enforcement.

Why this answer

Azure Firewall is the correct choice because it is a managed, cloud-native network security service that provides FQDN-based rules to control outbound (egress) traffic. It allows you to define application rules using fully qualified domain names (FQDNs) to restrict egress traffic to specific Azure services like Azure Container Registry and Azure Monitor, without needing to manage underlying infrastructure.

Exam trap

The trap here is that candidates often confuse Network Security Groups (NSGs) as a solution for FQDN-based filtering, but NSGs only support IP-based rules and cannot resolve domain names, making Azure Firewall the only managed service that provides FQDN-based egress control.

How to eliminate wrong answers

Option A is wrong because Azure Application Gateway is a Layer 7 load balancer and web application firewall (WAF) that handles inbound HTTP/HTTPS traffic, not egress traffic filtering with FQDN rules. Option B is wrong because Azure Front Door is a global, scalable entry point for web applications that provides load balancing and WAF for inbound traffic, not egress traffic control. Option C is wrong because Network Security Groups (NSGs) filter traffic based on IP addresses, ports, and protocols at Layers 3 and 4, and do not support FQDN-based rules for egress traffic; they cannot resolve domain names to IP addresses dynamically.

361
Multi-Selectmedium

Which TWO methods can be used to protect privileged accounts in Microsoft Entra ID? (Choose two.)

Select 2 answers
A.Enable external identities for guest users
B.Enable self-service password reset for all users
C.Register all devices with Azure AD
D.Create a Conditional Access policy that requires MFA for privileged roles
E.Configure Privileged Identity Management for just-in-time access
AnswersD, E

Creating a Conditional Access policy that targets privileged roles and requires MFA forces administrators to prove possession of a second authentication factor before signing in to Azure AD, the Azure portal, or Microsoft 365 admin centers. This neutralizes the risk of credential theft and password reuse because even a stolen password is insufficient alone to access high-impact administrative actions. Microsoft recommends this as a baseline control for every privileged account.

Why this answer

Option D is correct because a Conditional Access policy that requires multifactor authentication for privileged roles enforces an additional authentication factor specifically when members of highly privileged directory roles (such as Global Administrator) sign in, directly reducing the risk of credential compromise for those accounts. Option E is correct because Microsoft Entra Privileged Identity Management (PIM) provides just-in-time role activation, so privileged roles are not permanently assigned; users must activate eligibility with justification, approval, and MFA, and access expires after a set duration, which minimizes standing administrative access. Option A is not correct because enabling external identities for guest users governs B2B collaboration and does not protect privileged administrative accounts.

Option B is not correct because self-service password reset for all users is a general account-recovery feature and does not specifically secure privileged roles. Option C is not correct because registering devices with Azure AD (now Microsoft Entra ID) supports device-based Conditional Access but by itself does not protect privileged accounts.

Exam trap

The trap here is that candidates often confuse general security best practices (like SSPR or device registration) with specific privileged account protection mechanisms, overlooking that only MFA enforcement for privileged roles and JIT access via PIM directly reduce the standing privileges and credential exposure of high-value accounts.

362
MCQmedium

A security team uses Microsoft Sentinel. They want to automatically block a user's account in Azure AD when a high-severity incident is created in Sentinel indicating the user's credentials are compromised. Which automation feature should they use?

A.Create a playbook that uses the Azure AD connector to block the user, and associate it with an automation rule for high-severity incidents.
B.Configure the analytic rule for credential compromise to include a script that blocks the user as part of the rule.
C.Use a workbook to monitor incidents and manually block users.
D.Enable the 'User blocking' feature directly in the Microsoft Sentinel settings for all high-severity incidents.
AnswerA

Microsoft Sentinel playbooks are Logic Apps-based workflows that execute response actions. By using the Azure AD (Entra ID) connector, a playbook can call a user-blocking action such as disabling the user account via the 'Update user' or the dedicated 'Block user' action. Automation rules evaluate incident properties (e.g., severity, entity) and can automatically trigger the playbook when a high-severity incident is created, providing a fully automated containment response.

Why this answer

Microsoft Sentinel automation rules can trigger a playbook (an Azure Logic Apps workflow) when a high-severity incident is created. The playbook can use the Azure AD connector to call the Microsoft Graph API and block the user account, providing automated response to credential compromise without manual intervention.

Exam trap

The trap here is that candidates may think analytic rules can include scripts or that Sentinel has a native user-blocking toggle, but in reality, automated response requires a separate playbook triggered by an automation rule.

How to eliminate wrong answers

Option B is wrong because analytic rules in Sentinel define detection logic (KQL queries) and cannot contain scripts to perform actions like blocking users; actions are handled separately by automation rules and playbooks. Option C is wrong because workbooks are for visualization and reporting, not for automated response; they require manual monitoring and action, which does not meet the requirement for automatic blocking. Option D is wrong because Microsoft Sentinel does not have a built-in 'User blocking' feature in its settings; blocking users requires integration with Azure AD via a playbook or other external automation.

363
MCQeasy

You need to encrypt an Azure Storage account at rest using a customer-managed key stored in Azure Key Vault. Which feature should you enable?

A.Azure Information Protection
B.Azure Confidential Computing
C.Azure Disk Encryption
D.Azure Storage Service Encryption with customer-managed keys
AnswerD

Azure Storage Service Encryption (SSE) automatically encrypts all data at rest in an Azure storage account using AES-256 before it is persisted to disk. When configured with customer-managed keys, you supply a key from your Azure Key Vault or Managed HSM, giving you control over rotation, revocation, and audit logging of the encryption key. This is the correct service-level mechanism to encrypt a storage account at rest with a key you manage.

Why this answer

Azure Storage Service Encryption (SSE) encrypts data at rest automatically. By enabling customer-managed keys (CMK) in Azure Key Vault, you can control the encryption key used for SSE, meeting the requirement to encrypt the storage account with a key you manage.

Exam trap

The trap here is confusing Azure Disk Encryption (which encrypts VM disks) with Azure Storage Service Encryption (which encrypts the storage account's data at rest), leading candidates to pick Option C when the question explicitly targets storage account encryption.

How to eliminate wrong answers

Option A is wrong because Azure Information Protection is a data classification and labeling service, not an encryption mechanism for storage accounts. Option B is wrong because Azure Confidential Computing protects data in use via trusted execution environments (TEEs), not data at rest in storage. Option C is wrong because Azure Disk Encryption uses BitLocker or DM-Crypt to encrypt OS/data disks on VMs, not Azure Storage account blobs, files, or queues.

364
MCQmedium

Refer to the exhibit. You are configuring network access for an Azure Storage account. After applying this configuration, users report that they cannot access the storage account from their on-premises network (public IP: 198.51.100.50). What is the most likely reason?

A.The storage account is configured with a private endpoint
B.The bypass for AzureServices is not configured correctly
C.The virtual network rules are missing
D.The user's public IP address is not in the allowed IP rules
AnswerD

The storage account's firewall has an IP allow rule only for 203.0.113.0/24. The user's public IP address is 198.51.100.50, which falls outside that CIDR range. Because the default action for the firewall is to deny all traffic that does not match an allow rule, the request is blocked. The IP must be added to the allowed range, or the user must use a permitted network path.

Why this answer

The correct answer is D: the user's public IP address is not in the allowed IP rules. When an Azure Storage account firewall is configured with selected networks, only traffic from explicitly listed public IP addresses (or ranges) and permitted virtual networks is allowed; since the on-premises public IP 198.51.100.50 is not included in the allowed IP rules, requests are denied. Option A is not the likely cause because a private endpoint would affect access over the private link rather than simply blocking an on-premises public IP, and the scenario points to firewall IP filtering.

Option B is incorrect because the AzureServices bypass applies to trusted Microsoft services, not to on-premises clients. Option C is incorrect because missing virtual network rules would not matter for an on-premises client connecting over the public internet.

365
MCQhard

You are the security architect for a large enterprise that uses Microsoft Entra ID with 50,000 users. The company recently adopted a cloud-first strategy and is migrating on-premises applications to Azure. You need to design a secure identity and access solution that meets the following requirements: - All access to cloud applications must be authenticated using modern authentication protocols. - Legacy authentication protocols (such as POP3, IMAP4, SMTP, and basic authentication) must be blocked. - Users must be required to use multi-factor authentication (MFA) when accessing any application from outside the corporate network. - Administrative access to Azure resources must be time-bound and require approval. - The solution must minimize user friction for internal users on the corporate network. - All sign-in risks must be detected and automatically remediated. You have deployed Microsoft Entra ID P2 licensing and configured Microsoft Defender for Cloud Apps. Which of the following is the most appropriate combination of actions to meet all requirements?

A.Enable Security defaults for all users and configure risk-based Conditional Access policies for admin roles. Use PIM for time-bound access.
B.Configure device compliance policies in Intune and require compliant devices for access. Use PIM with time-bound roles but without approval. Enable Identity Protection for risk detection.
C.Create a Conditional Access policy to require MFA for all cloud apps and allow legacy authentication for non-interactive service accounts. Use PIM without approval for admin roles.
D.Create a Conditional Access policy to block legacy authentication and require MFA for all users when accessing from outside the corporate network. Exclude trusted locations from MFA. Use PIM with approval for admin roles. Enable Identity Protection for risk detection and automatic remediation.
AnswerD

This solution correctly blocks legacy authentication as a client-app condition in Conditional Access, ensuring that protocols like POP, IMAP, and SMTP cannot bypass modern security controls. MFA is required only for non-corporate-network access by excluding trusted named locations, which minimizes user friction for internal employees. PIM with approval grants time-bound admin roles and enforces an approval workflow, while Identity Protection with automatic remediation (e.g., requiring a password change for risky users) closes the gap for identity-based threats, fully satisfying all requirements.

Why this answer

Option D is correct because it directly satisfies every stated requirement: a Conditional Access policy blocking legacy authentication eliminates POP3, IMAP4, SMTP, and basic authentication; requiring MFA for all users outside the corporate network with trusted locations excluded minimizes friction for internal users; PIM with approval provides time-bound, approved administrative access to Azure resources; and Microsoft Entra ID Protection (included with Entra ID P2) detects sign-in risk and enables automatic remediation via risk-based Conditional Access. Option A is wrong because Security defaults cannot enforce the granular legacy-auth blocking, trusted-location MFA exclusions, or risk-based remediation required here, and it does not scope MFA by network location. Option B is wrong because it omits blocking legacy authentication and omits approval for PIM activation, and device compliance alone does not meet the MFA-from-outside requirement.

Option C is wrong because it explicitly allows legacy authentication for service accounts and uses PIM without approval, violating two requirements.

366
Multi-Selecteasy

Which TWO of the following are authentication methods supported by Microsoft Entra ID?

Select 2 answers
A.Certificate-based authentication (CBA)
B.Security questions
C.Smart card with PIN
D.OAuth 2.0 authorization code flow
E.SMS-based one-time passcode
AnswersA, E

Certificate-based authentication (CBA) leverages X.509 digital certificates issued by a trusted certification authority to verify a user's identity. In Microsoft Entra ID, this method is supported for federated domains, where the certificate is used to authenticate against the identity provider instead of a password. It offers strong, phishing-resistant protection and is distinct from the physical smart card interaction, which is not natively supported.

Why this answer

Microsoft Entra ID natively supports certificate-based authentication (CBA), where a user presents an X.509 certificate and Entra ID validates it against configured trusted certificate authorities to satisfy authentication, making option A correct. Entra ID also supports SMS-based one-time passcode as a built-in authentication method, sending a code to a registered phone number that the user enters to complete sign-in, making option E correct. Security questions (B) are not an Entra ID authentication method; they are used in self-service password reset (SSPR) for identity verification, not as a primary or MFA authentication method.

Smart card with PIN (C) is not a distinct Entra ID authentication method — smart cards are typically surfaced through certificate-based authentication, so C is not separately supported. OAuth 2.0 authorization code flow (D) is an authorization protocol used by applications to obtain tokens, not an authentication method offered by Entra ID.

Exam trap

The trap here is that candidates often confuse authentication methods with authorization protocols (like OAuth 2.0) or confuse legacy on-premises methods (like security questions) with cloud-supported methods in Entra ID, leading them to select options that are not actual authentication methods in the Microsoft Entra ID context.

367
Multi-Selectmedium

A security engineer needs to collect custom application logs from Azure VMs using Azure Monitor Agent for Sentinel analysis. Which two components are required?

Select 2 answers
A.A Data Collection Rule that defines the custom log collection
B.A storage account configured for static website hosting
C.Association of the Data Collection Rule with the target machines
D.A Conditional Access policy requiring MFA
AnswersA, C

A Data Collection Rule defines which custom logs Azure Monitor Agent gathers, including the destination workspace and parsing logic. Without a DCR, the agent has no collection specification, making it an essential component for Sentinel ingestion.

Why this answer

Option A is correct because a Data Collection Rule (DCR) is the Azure Monitor Agent mechanism that defines what data to collect, including custom logs via a custom text or JSON log definition, and where to send it (e.g., a Log Analytics workspace used by Microsoft Sentinel). Option C is correct because a DCR must be associated with the target machines (through a DCR association on the VM or via Azure Policy/monitoring insights) for the Azure Monitor Agent to actually apply that collection configuration to those VMs. Option B is incorrect because a storage account configured for static website hosting is unrelated to log ingestion by Azure Monitor Agent; custom logs are sent to a Log Analytics workspace, not served as web content.

Option D is incorrect because Conditional Access policies govern user/identity sign-in access to resources and play no role in agent-based log collection from VMs.

Exam trap

The trap here is that candidates may confuse storage accounts (used for Azure Diagnostics extension or legacy agents) with the modern Azure Monitor Agent requirement, or mistakenly think Conditional Access policies are relevant to log ingestion.

368
Multi-Selecthard

You need to monitor network traffic to detect anomalies and potential security threats. Which THREE Azure services can you use to achieve this? (Choose three.)

Select 3 answers
A.Microsoft Sentinel
B.Azure Monitor Metrics
C.Azure Firewall logs
D.Azure Policy
E.Azure Network Watcher
AnswersA, C, E

Microsoft Sentinel is the correct answer because it is a cloud-native SIEM/SOAR service that ingests network telemetry from sources such as Azure Firewall logs, NSG flow logs, and Microsoft 365 Defender. It applies built-in analytics, machine learning, and UEBA to correlate that traffic data and surface anomalies, while also enabling automated response via playbooks. Sentinel is the monitoring and analysis layer where raw network logs become actionable threat intelligence.

Why this answer

Microsoft Sentinel (A) is correct because it is a cloud-native SIEM/SOAR platform that ingests network telemetry and logs, applies analytics rules and machine learning to detect anomalies and security threats, and supports investigation and automated response. Azure Firewall logs (C) are correct because the firewall's network, application, and threat-intelligence logs capture allowed/denied traffic and malicious activity that can be analyzed for anomalies and threats. Azure Network Watcher (E) is correct because it provides network monitoring and diagnostic tools such as NSG flow logs, Traffic Analytics, packet capture, and connection monitor that reveal traffic patterns and anomalies.

Azure Monitor Metrics (B) is not correct here because it stores numeric time-series metrics rather than detailed traffic/log data needed for threat detection. Azure Policy (D) is not correct because it is a governance service that enforces and audits resource configurations, not a network traffic monitoring or threat detection tool.

Exam trap

The trap here is that candidates often confuse Azure Monitor Metrics (a performance monitoring tool) with Azure Monitor Logs (which can ingest security logs), leading them to incorrectly select Metrics as a security monitoring service, while Azure Policy is mistakenly thought to monitor traffic when it only enforces configuration rules.

369
Multi-Selectmedium

You need to protect Azure SQL Database from SQL injection attacks. Which TWO measures should you implement? (Choose TWO.)

Select 2 answers
A.Use Always Encrypted for sensitive columns.
B.Deploy Azure Web Application Firewall (WAF) in front of the application.
C.Enable Transparent Data Encryption (TDE).
D.Enable SQL Server auditing.
E.Use parameterized queries in application code.
AnswersB, E

Azure Web Application Firewall, when attached to Application Gateway or Front Door, evaluates incoming HTTP requests against managed rule sets that specifically detect SQL injection patterns, allowing you to block malicious payloads at the network edge before they reach your application. It filters on query strings, request bodies, and header parameters using signature analysis and can scale to absorb attack traffic. This is a strong compensating control, but it operates outside the database engine and may require false-positive tuning.

Why this answer

Option B is correct because Azure Web Application Firewall (WAF), typically via Application Gateway or Front Door, inspects HTTP/HTTPS traffic and applies OWASP Core Rule Set rules that detect and block common SQL injection payloads before they reach the application or database. Option E is correct because parameterized queries (prepared statements) cause the database engine to treat user input strictly as data rather than executable SQL, which is the fundamental application-level defense against SQL injection. Option A is not correct here because Always Encrypted protects data confidentiality at rest and in memory by encrypting sensitive columns, but it does not detect or prevent SQL injection.

Option C is not correct because Transparent Data Encryption (TDE) only encrypts data and log files at rest and has no bearing on injection attacks. Option D is not correct because SQL Server auditing records activity for compliance and forensic review after the fact; it is a detective control, not a preventive measure against SQL injection.

Exam trap

The trap here is that candidates often confuse data-at-rest encryption (TDE or Always Encrypted) with input validation or application-layer defenses, mistakenly thinking encryption alone can prevent SQL injection attacks.

370
MCQhard

A company uses Azure SQL Database with Transparent Data Encryption (TDE) protected by a customer-managed key (CMK) stored in Azure Key Vault. The Key Vault has a firewall enabled that denies all public network access. The SQL server is in the same region and has a system-assigned managed identity with the 'Key Vault Crypto Service Encryption User' role assigned at the key scope. However, TDE operations fail because the SQL server cannot access the Key Vault. What additional configuration is required to allow the SQL server to access the Key Vault for TDE operations?

A.Configure a private endpoint for the SQL server to the Key Vault.
B.Enable the 'Allow trusted Microsoft services to bypass the firewall' setting on the Key Vault.
C.Change the Key Vault firewall to allow all Azure services.
D.Create a VNet service endpoint for Microsoft.KeyVault on the SQL server's subnet.
AnswerB

This setting allows trusted Azure services, including Azure SQL Database, to access the Key Vault even when the firewall is enabled. Since the SQL server's managed identity already has the cryptographic role, this is the missing piece to allow TDE operations.

Why this answer

When Azure Key Vault has a firewall that denies all public network access, the 'Allow trusted Microsoft services to bypass this firewall' setting is required for Azure SQL Database (a trusted Microsoft service) to authenticate using its system-assigned managed identity and access the customer-managed key for TDE. This setting allows the SQL server to reach the Key Vault over the Microsoft backbone network without requiring a private endpoint or VNet integration, as the service is explicitly trusted by Azure.

Exam trap

The trap here is that candidates often assume a private endpoint or VNet service endpoint is always required for Key Vault access when firewalls are enabled, but they overlook the 'Allow trusted Microsoft services' bypass which is specifically designed for Azure PaaS services like SQL Database to access Key Vault without additional network configuration.

How to eliminate wrong answers

Option A is wrong because configuring a private endpoint for the SQL server to the Key Vault would require the SQL server to be in a VNet with a private endpoint connection, but the SQL server is not VNet-injected by default and the question does not indicate VNet integration; additionally, the system-assigned managed identity and role assignment are already in place, so the issue is firewall bypass, not network connectivity. Option C is wrong because 'Allow all Azure services' is a legacy setting that is overly permissive and deprecated in favor of the more specific 'Allow trusted Microsoft services' option; it would also allow all Azure services, not just trusted ones, which violates least-privilege principles. Option D is wrong because a VNet service endpoint for Microsoft.KeyVault on the SQL server's subnet would only help if the SQL server were deployed in a VNet (which it is not by default for Azure SQL Database), and service endpoints do not bypass the Key Vault firewall's deny-all rule unless the firewall explicitly allows the specific VNet/subnet, which is not mentioned.

371
Multi-Selecteasy

You are configuring Azure DDoS Network Protection for your VNet. Which TWO benefits does enabling DDoS Protection Standard provide?

Select 2 answers
A.Integration with Azure Firewall for packet inspection.
B.Adaptive tuning to baseline traffic patterns.
C.Application-layer (Layer 7) protection via integrated WAF.
D.Vulnerability scanning for web applications.
E.Cost protection for scaled resources during an attack.
AnswersB, E

Adaptive tuning is a core feature of Azure DDoS Protection Standard. It uses machine learning algorithms to analyze each protected resource's typical traffic patterns over time, then automatically adjusts detection thresholds to match that baseline. This reduces false positives and ensures that legitimate traffic is not blocked during normal spikes, while still flagging anomalies that indicate a DDoS attack. It requires no manual configuration, as the thresholds self-tune continuously.

Why this answer

Option B is correct because Azure DDoS Protection Standard continuously monitors traffic and uses adaptive tuning to learn your application's normal traffic patterns, then automatically adjusts mitigation thresholds to match that baseline, enabling accurate detection of anomalies. Option E is correct because DDoS Protection Standard includes cost protection, which provides service credits for resource costs (such as scaled-out VM instances) incurred as a result of a documented DDoS attack. Option A is incorrect because DDoS Protection Standard does not perform packet inspection through Azure Firewall integration; it operates at Layers 3/4 within the Azure network fabric.

Option C is incorrect because Layer 7 application protection is provided by Azure Web Application Firewall (WAF) on Application Gateway or Front Door, not by DDoS Protection Standard itself. Option D is incorrect because vulnerability scanning is not a DDoS Protection Standard feature; it is offered through separate services such as Microsoft Defender for Cloud.

Exam trap

The trap here is that candidates often confuse Azure DDoS Protection Standard with a full web application firewall (WAF) or assume it provides Layer 7 protection, when in fact it is strictly a network-layer (L3/L4) defense with adaptive tuning and cost protection as its key differentiators.

372
MCQmedium

You are investigating a security incident in Microsoft Sentinel. A KQL query returns results indicating that a user logged in from an IP address that is not in the organization's approved list. The user's account has been compromised. You need to automatically disable the user account in Microsoft Entra ID when such an alert is triggered. What should you configure?

A.Configure an Azure Policy that disables the user account.
B.Use Microsoft Defender for Cloud to automatically disable the account.
C.Create a Power Automate flow triggered by the Sentinel alert.
D.Create a playbook in Microsoft Sentinel with a Logic Apps connector to Microsoft Entra ID.
AnswerD

A Sentinel playbook is an Azure Logic Apps workflow that is designed explicitly to run automated responses in conjunction with Sentinel incidents and alerts. When you create a playbook, you can add a Microsoft Entra ID connector that uses the Microsoft Graph API to perform actions such as disabling a user or updating the accountEnabled property of the target identity. The playbook can be attached to an automation rule that fires on an incident, making it the correct, supported way to automatically disable a compromised account.

Why this answer

Microsoft Sentinel can use playbooks, which are automated workflows built on Azure Logic Apps, to respond to security alerts. By creating a playbook triggered by a Sentinel alert, you can use the Microsoft Entra ID connector to automatically disable a compromised user account, providing a direct and integrated remediation action.

Exam trap

The trap here is that candidates might confuse Microsoft Defender for Cloud's workload protection capabilities with identity-based remediation, or think that Azure Policy can manage Entra ID objects, when in fact only a Logic Apps-based playbook provides the necessary automation and API access to disable a user account.

How to eliminate wrong answers

Option A is wrong because Azure Policy is used to enforce compliance rules on Azure resources (e.g., VMs, storage accounts) and cannot directly disable user accounts in Microsoft Entra ID. Option B is wrong because Microsoft Defender for Cloud focuses on securing cloud workloads and infrastructure, not on managing user identities or automating account disablement in response to Sentinel alerts. Option C is wrong because while Power Automate can be triggered by Sentinel alerts, it lacks the native, deep integration with Microsoft Entra ID that a Logic Apps playbook provides; playbooks are the recommended and more robust method for automated remediation in Sentinel.

373
MCQmedium

A company uses Microsoft Defender for Cloud to protect its hybrid workloads. Security administrators report that critical alerts for SQL servers are not appearing in the Defender for Cloud dashboard. The SQL servers are on-premises and have Azure Arc enabled. Which configuration step should be verified first?

A.Deploy the Log Analytics agent to the SQL servers
B.Configure Azure Firewall logs for SQL traffic
C.Assign the 'Configure Azure Defender for SQL agents on virtual machines' policy
D.Enable the 'SQL servers on machines' plan in Microsoft Defender for Cloud
AnswerD

Enabling the 'SQL servers on machines' plan in Microsoft Defender for Cloud is the prerequisite that activates threat detection for Azure Arc-enabled SQL Server instances. This plan, part of Defender for Cloud's enhanced security features, turns on SQL-specific alerts, vulnerability assessments, and advanced threat protection for on-premises and multi-cloud SQL servers. Without this plan enabled, no SQL server security alerts will be generated regardless of other configurations, so this is the required first step.

Why this answer

For on-premises SQL servers with Azure Arc, the 'SQL servers on machines' plan must be enabled in Microsoft Defender for Cloud to surface alerts. Without enabling this plan, alerts for SQL servers will not appear. Options A and C are related to agent deployment and policy assignment, but the first step is to ensure the plan is enabled.

Option B is unrelated as Azure Firewall logs are not required for SQL-specific alerts.

374
MCQeasy

You are configuring Microsoft Defender for Cloud to protect your Azure virtual machines. You need to enable just-in-time (JIT) VM access to reduce the attack surface. What prerequisite must be met?

A.Configure Microsoft Defender for Cloud Apps with the VMs as connected.
B.Enable the Defender for Cloud 'JIT' plan.
C.Deploy Azure Bastion in the same virtual network.
D.Enable Microsoft Defender for Servers Plan 2.
AnswerD

This is the correct action because JIT VM access is a feature specifically included in Microsoft Defender for Servers Plan 2. When you enable Defender for Servers Plan 2, Defender for Cloud automatically activates JIT and allows you to create just-in-time policies on supported VMs. The JIT feature locks down VM management ports (e.g., SSH 22 and RDP 3389) via NSG rules and opens them temporarily only after approval, with a configurable maximum access duration. Without this plan—or with only Defender for Servers Plan 1—JIT is not available, so enabling Plan 2 is the required step.

Why this answer

Just-in-time (JIT) VM access in Microsoft Defender for Cloud requires Microsoft Defender for Servers Plan 2 to be enabled. This plan provides the advanced security capabilities, including JIT, vulnerability assessment, and file integrity monitoring. Without Plan 2, the JIT blade and policy options are not available, as Plan 1 only covers basic log collection and threat detection.

Exam trap

The trap here is that candidates often confuse the 'JIT' feature as a standalone plan or assume it works with any Defender for Cloud tier, but it specifically requires Defender for Servers Plan 2 (the full server protection plan) to be enabled.

How to eliminate wrong answers

Option A is wrong because Microsoft Defender for Cloud Apps is a separate SaaS security broker (CASB) that does not control VM network access or JIT functionality; it focuses on cloud application usage and shadow IT. Option B is wrong because there is no standalone 'JIT plan' in Defender for Cloud; JIT is a feature bundled within Defender for Servers Plan 2, not a separate purchasable plan. Option C is wrong because Azure Bastion provides secure RDP/SSH connectivity via a browser without exposing public IPs, but it is not a prerequisite for JIT; JIT works independently of Bastion and can be used with or without it.

375
MCQhard

You are a security engineer at Fabrikam. The company has an Azure virtual network that contains a subnet named WebSubnet with a network security group (NSG) named NSG1. You need to ensure that inbound HTTP traffic from the internet is allowed to the web servers in WebSubnet, but only when the traffic originates from a specific set of public IP addresses used by a partner company. The partner's IP addresses are 203.0.113.0/24 and 198.51.100.10. What should you configure in NSG1?

A.Create an outbound security rule with source set to the two partner IP addresses, destination port 80, and action Allow, and apply it to WebSubnet.
B.Create an inbound security rule with source set to the two partner IP addresses, destination port 80, protocol TCP, and action Deny, and then create a lower-priority Allow rule for all other traffic.
C.Create an inbound security rule with source set to the two partner IP addresses, destination port 80, protocol TCP, and action Allow. Set a lower priority number than any deny rule.
D.Configure a service tag named Internet as the source and use an application security group (ASG) as the destination, with an Allow rule for port 80.
AnswerC

NSG rules are processed in priority order, lowest number first. To allow specific partner IPs, you create an inbound rule with those source addresses, destination port 80, and action Allow, and ensure its priority is lower than any broader deny rule. This permits only the partner traffic while other traffic can be denied by a subsequent rule.

Why this answer

Network security groups evaluate rules by priority, with lower numbers processed first. To allow inbound HTTP only from specific partner IP addresses, you create an Allow rule with those source addresses and a priority lower than any Deny rule that might block other traffic. This ensures the partner traffic is permitted while other internet traffic can be denied by a later, higher-numbered rule.

Exam trap

The trap here is confusing inbound and outbound rules or reversing the allow/deny action, when the requirement is specifically to permit inbound HTTP from a defined set of external IP addresses.

Page 4

Page 5 of 9

Page 6

All pages