Courseiva

Microsoft Azure Security Engineer Associate AZ-500 (AZ-500) — Questions 526–600

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

Page 7

Page 8 of 9

Page 9
526
Multi-Selectmedium

Which TWO of the following are valid data sources for Microsoft Sentinel's UEBA (User and Entity Behavior Analytics)? (Select two.)

Select 2 answers
A.Microsoft Entra ID sign-in logs.
B.Microsoft Entra ID audit logs.
C.Azure SQL Database audit logs.
D.Azure Activity Logs.
E.Azure Firewall logs.
AnswersA, B

Microsoft Entra ID sign-in logs are a core UEBA data source in Microsoft Sentinel because UEBA profiles entities based on authentication behavior, such as successful/failed logons, anomalous locations, impossible travel, and device attributes. These logs feed the UEBA engine to establish baselines and detect risky sign-in patterns. Without them, UEBA would lack the primary signal for user identity and access activity.

Why this answer

Microsoft Sentinel UEBA is designed to ingest identity-centric telemetry, and Microsoft Entra ID sign-in logs (option A) are a core data source because they provide the authentication events (user, application, IP, location, device, risk level) that UEBA uses to build behavioral baselines and detect anomalous sign-in activity. Microsoft Entra ID audit logs (option B) are also a valid UEBA source, since they record directory-level changes such as user, group, role, and application modifications that feed entity behavior profiling and help correlate administrative actions with other activity. Options C, D, and E are not among the documented UEBA data sources: Azure SQL Database audit logs, Azure Activity Logs, and Azure Firewall logs are resource/network telemetry that can be collected into Sentinel for analytics, but they are not identity behavior sources used by the UEBA engine.

527
MCQmedium

A company uses Azure SQL Database for a critical application. Security policy requires that all client connections use at least TLS 1.2 encryption and that connections not meeting this requirement are rejected. Which configuration should they implement on the Azure SQL Server?

A.Configure firewall rules to allow only trusted IP addresses
B.Enable Transparent Data Encryption (TDE)
C.Set the 'Minimum TLS version' on the SQL server
D.Enable Advanced Threat Protection (ATP)
AnswerC

Setting the 'Minimum TLS version' on the Azure SQL Server enforces that every inbound client connection must negotiate at least TLS 1.2 at handshake time; if a client attempts to connect using TLS 1.0 or 1.1, the server rejects the connection entirely. This server-side enforcement is applied by the Azure SQL Gateway before any authentication or data exchange occurs, making it the correct control to ensure all traffic between the application and database is encrypted with a modern protocol version. The setting can be configured as 1.2 (or higher if supported) and is a hard policy, unlike client-side connection string options which a user could omit.

Why this answer

Azure SQL Server allows you to enforce a minimum TLS version for all client connections. By setting the 'Minimum TLS version' to 1.2, the server will reject any connection attempt using TLS 1.0 or 1.1, ensuring compliance with the security policy that requires at least TLS 1.2 encryption.

Exam trap

The trap here is that candidates often confuse encryption in transit (TLS) with encryption at rest (TDE) or network access controls (firewall rules), leading them to select options that address different security layers rather than the specific requirement to enforce a minimum TLS version.

How to eliminate wrong answers

Option A is wrong because firewall rules control network access based on IP addresses, not encryption protocol version; they cannot enforce TLS 1.2. Option B is wrong because Transparent Data Encryption (TDE) encrypts data at rest, not data in transit; it does not affect the TLS version used for client connections. Option D is wrong because Advanced Threat Protection (ATP) provides security monitoring and alerts for suspicious activities, but it does not enforce encryption protocols or reject connections based on TLS version.

528
MCQhard

A security team uses Microsoft Sentinel. They create a scheduled analytics rule that queries Azure Activity Logs to detect virtual machines deployed in non-approved regions. The rule generates an incident. The team wants the incident to be automatically assigned to the 'Infrastructure' team and its severity set to 'High' when it is created. Which automation feature should they use?

A.Create an automation rule with trigger 'When incident is created' and actions to assign the incident to an owner and set severity
B.Create a playbook triggered by alert creation that performs the assignment and severity change
C.Use an automation rule with trigger 'When incident is updated' and condition on alert type
D.Configure the analytics rule directly to set severity and owner
AnswerA

Automation rules in Microsoft Sentinel are the native, low-latency mechanism for incident lifecycle operations, and the 'When incident is created' trigger fires within seconds of an incident being generated by an analytics rule. By specifying actions that assign an owner and set severity, the rule applies these changes deterministically and immediately, without requiring a playbook to be invoked. This is the recommended and simplest way to ensure the incident appears in the SOC queue with the correct owner and severity from the very first moment.

Why this answer

Automation rules in Microsoft Sentinel allow you to define triggers such as 'When incident is created' and then perform actions like assigning the incident to an owner and setting its severity. This is the native, no-code way to automate incident management without requiring a playbook or modifying the analytics rule itself.

Exam trap

The trap here is that candidates often confuse playbooks (which are triggered by alerts and require Logic Apps) with automation rules (which are triggered by incident lifecycle events and are simpler to configure), leading them to select Option B instead of the correct automation rule approach.

How to eliminate wrong answers

Option B is wrong because playbooks are triggered by alerts, not by incident creation, and they require additional configuration and logic apps, making them more complex than necessary for simple assignment and severity changes. Option C is wrong because the trigger 'When incident is updated' would not fire at incident creation time, so the assignment and severity would not be applied automatically when the incident is first generated. Option D is wrong because analytics rules do not have native settings to directly assign an owner or set severity; those properties are managed at the incident level, not within the rule definition.

529
MCQmedium

You are designing network security for a multi-tier application deployed in Azure. The application consists of a front-end web tier, a middle-tier API, and a back-end database. All tiers must be isolated from the internet except the front-end, which must accept HTTPS traffic from the internet. You need to ensure that no traffic can bypass the network security controls. What should you implement?

A.Place all tiers in the same virtual network and use Azure Front Door with WAF for the web tier, and rely on NSGs for internal traffic.
B.Deploy Network Security Groups (NSGs) on each subnet and allow only necessary traffic between tiers.
C.Deploy Azure Firewall in a hub virtual network and route all traffic between tiers through the firewall for inspection.
D.Use Azure Application Gateway with Web Application Firewall (WAF) in front of the web tier, and use NSGs for the other tiers.
AnswerC

This is the correct approach because Azure Firewall is a managed, stateful firewall service designed for centralized inspection and control of all traffic, including east-west traffic between tiers. By placing Azure Firewall in a hub virtual network and configuring user-defined routes to force all inter-tier traffic through it, you create a security choke point that enforces consistent policies, provides FQDN filtering, and generates comprehensive logs for auditing. This gives you a single, centrally managed security boundary across the entire application.

Why this answer

Deploying Azure Firewall in a hub virtual network and routing all traffic between tiers through the firewall for inspection ensures that no traffic can bypass network security controls. This design enforces a forced tunneling architecture where all inter-tier traffic (e.g., from front-end to API to database) must traverse the firewall, allowing centralized inspection, logging, and filtering. This meets the requirement for complete isolation and control, as NSGs alone cannot prevent traffic from bypassing inspection if routes are not explicitly forced.

Exam trap

The trap here is that candidates often assume NSGs alone are sufficient for full traffic control, but they fail to recognize that NSGs cannot enforce mandatory inspection or prevent traffic from bypassing controls when routes are not explicitly forced through a central firewall.

How to eliminate wrong answers

Option A is wrong because placing all tiers in the same virtual network and relying solely on NSGs for internal traffic does not prevent traffic from bypassing network security controls; NSGs are stateless or stateful at the subnet/NIC level but do not provide centralized inspection or logging, and Azure Front Door with WAF only protects the web tier from internet traffic, not internal traffic between tiers. Option B is wrong because deploying NSGs on each subnet and allowing only necessary traffic between tiers is insufficient to ensure no traffic bypasses controls; NSGs cannot inspect or log traffic at the application layer, and they do not prevent a compromised tier from sending unauthorized traffic directly to another tier without inspection. Option D is wrong because using Azure Application Gateway with WAF in front of the web tier and NSGs for the other tiers does not enforce mandatory inspection of traffic between the middle-tier API and back-end database; NSGs alone cannot provide the centralized, forced routing required to ensure all inter-tier traffic is inspected, and the Application Gateway only handles inbound internet traffic to the web tier.

530
MCQmedium

A security team uses Microsoft Sentinel. They have created a playbook that isolates a virtual machine by modifying a network security group rule. They want this playbook to execute automatically whenever a new incident of type 'Suspicious VM activity' is created. Which Microsoft Sentinel feature should they use to trigger the playbook?

A.Analytics rule
B.Automation rule
C.Playbook
D.Hunt
AnswerB

Automation rules are a built-in incident orchestration feature in Sentinel that activate when defined conditions are met—for example, when an incident is created. They can perform a variety of actions, including running a playbook as an automated response. Since they directly associate incident triggers with playbook execution, automation rules are the correct component to automatically start a playbook when a security incident is raised.

Why this answer

Automation rules in Microsoft Sentinel allow you to define triggers that automatically run playbooks when incidents are created or updated. In this scenario, the automation rule can be configured to trigger on incident creation with the condition 'Suspicious VM activity' and then execute the playbook that modifies the NSG rule to isolate the VM. This is the correct mechanism because automation rules are designed specifically for incident-based triggers, unlike analytics rules which generate alerts or incidents.

Exam trap

The trap here is confusing the playbook (the action) with the trigger (automation rule), leading candidates to select 'Playbook' as the trigger instead of recognizing that automation rules are the mechanism to invoke playbooks automatically on incident creation.

How to eliminate wrong answers

Option A is wrong because analytics rules are used to generate alerts or incidents from data sources, not to trigger playbooks in response to existing incidents. Option C is wrong because a playbook is the set of actions (like modifying an NSG rule) that runs, not the trigger mechanism itself; playbooks must be invoked by an automation rule or manually. Option D is wrong because Hunts are manual, ad-hoc investigations to find threats, not automated triggers for incident response.

531
Multi-Selecteasy

Your organization wants to use Microsoft Sentinel to detect and respond to threats. You need to ensure that Sentinel can ingest data from Azure Firewall logs. Which three components are required? (Choose three.)

Select 3 answers
A.Enable diagnostic logs on Azure Firewall.
B.A Log Analytics workspace.
C.Assign an Azure Policy to enforce diagnostic logs on all firewalls.
D.Install the Log Analytics agent on the Azure Firewall.
E.The Azure Firewall data connector in Sentinel.
AnswersA, B, E

Azure Firewall does not emit its logs to Sentinel by default. Instead, you must enable diagnostic settings on the firewall resource itself, selecting the relevant log categories (e.g., AzureFirewallNetworkRule, AzureFirewallApplicationRule, AzureFirewallDnsProxy) and streaming them to a Log Analytics workspace. This is the foundational ingestion step that makes firewall data available to Sentinel; without it, no traffic analysis or detection can occur.

Why this answer

Azure Firewall logs must be enabled via diagnostic settings to send data to a Log Analytics workspace. Without diagnostic logs, the firewall does not produce the necessary log data for Sentinel to ingest. This is the foundational step for log collection.

Exam trap

The trap here is that candidates often assume the Log Analytics agent is required for all Azure resources, but Azure Firewall (and other PaaS services) use diagnostic settings instead, making Option D a common distractor.

532
MCQmedium

Your company uses Microsoft Entra ID and Microsoft Intune for mobile device management. You need to ensure that only devices that are compliant with your security policies can access Exchange Online. The solution must require users to reauthenticate every 12 hours. What should you configure?

A.Create a Conditional Access policy that requires MFA for Exchange Online and set sign-in frequency to 12 hours.
B.Create a Conditional Access policy that grants access to Exchange Online only if the device is compliant, and set session sign-in frequency to 12 hours.
C.Create an app protection policy for Exchange Online that requires device compliance and sets sign-in frequency.
D.Configure a device compliance policy for all devices and enable 'Reauthenticate every 12 hours' in the compliance policy.
AnswerB

Conditional Access enforces the compliance gate by requiring Intune-marked compliant devices before granting Exchange Online access. Sign-in frequency set to 12 hours forces reauthentication at that interval, satisfying both the device-compliance and periodic-reauthentication constraints in one policy.

Why this answer

A Conditional Access policy can enforce device compliance as a grant control for Exchange Online, ensuring only compliant devices can access the service. Setting the session sign-in frequency to 12 hours forces users to reauthenticate at that interval, meeting the requirement without requiring MFA. This combines device compliance enforcement with session lifetime control in a single policy.

Exam trap

The trap here is that candidates confuse device compliance policies with Conditional Access session controls, assuming sign-in frequency can be set directly in a compliance policy, when it is actually a separate Conditional Access setting.

How to eliminate wrong answers

Option A is wrong because requiring MFA does not enforce device compliance; it only adds an authentication factor, so non-compliant devices could still access Exchange Online. Option C is wrong because app protection policies (MAM) manage data protection within apps, not device-level compliance, and they do not support a sign-in frequency setting. Option D is wrong because a device compliance policy itself does not include a 'Reauthenticate every 12 hours' setting; sign-in frequency is a Conditional Access session control, not a compliance policy setting.

533
MCQhard

A company stores business records in Azure Blob Storage. Due to a legal investigation, they must prevent any modification or deletion of the blobs for an indefinite period until the legal hold is released. They also need to ensure that even storage account owners cannot alter the data during the hold. Which blob storage feature should they enable?

A.Time-based retention policy
B.Legal hold
C.Soft delete
D.Blob versioning
AnswerB

Legal hold is the correct choice because it applies an indefinite, immutable lock on blob storage, preventing any modification or deletion until the hold is explicitly released by an authorized user. This hold is designed for legal and compliance scenarios where records must be preserved for an unknown or open-ended duration, such as active litigation or an ongoing investigation. Unlike time-based retention, legal hold does not expire automatically and continues protecting data until the hold is removed, ensuring that records remain untouched for as long as legally required.

Why this answer

Legal hold (option B) is the correct choice because it is designed to protect blobs from any modification or deletion for an indefinite period, even by storage account owners. Unlike time-based retention policies, a legal hold has no expiration and cannot be removed until explicitly cleared by an authorized user, making it ideal for indefinite legal investigations.

Exam trap

The trap here is that candidates often confuse time-based retention policies (which have a fixed duration) with legal holds (which are indefinite), or assume that soft delete or versioning can prevent modification or deletion by privileged users, when in fact they only provide recovery options and do not block destructive operations.

How to eliminate wrong answers

Option A is wrong because a time-based retention policy enforces a fixed retention period (e.g., 1–146,000 days) and automatically expires, which does not meet the indefinite hold requirement. Option C is wrong because soft delete only protects against accidental deletion by retaining deleted blobs for a configurable retention period (default 7 days), but it does not prevent modification or allow indefinite holds, and storage account owners can still permanently delete blobs if soft delete is disabled. Option D is wrong because blob versioning preserves previous versions of blobs but does not prevent modification or deletion of the current version; storage account owners can still overwrite or delete blobs, and versioning alone cannot enforce an indefinite legal hold.

534
MCQeasy

You are the identity security engineer for a multinational company that uses Microsoft Entra ID. The company has recently experienced a security breach where an attacker compromised a non-administrator user account and then used that account to enumerate all users in the tenant. The attacker then attempted to brute-force passwords for high-privilege accounts. To prevent such attacks, management requires the following: - Users with administrative roles must use phishing-resistant MFA. - Any sign-in from a risky IP address must be blocked. - Users must not be able to enumerate directory information via the Graph API unless they have a specific role. - The solution should be implemented using built-in Microsoft Entra ID features. What should you configure?

A.Enable Security defaults and configure Identity Protection user risk policy to block high-risk users.
B.Configure Conditional Access policy with authentication strength for admins requiring phishing-resistant MFA. Configure Identity Protection sign-in risk policy to block risky sign-ins. Restrict access to the Graph API by requiring a specific role assignment.
C.Configure Conditional Access policy for admins to require phishing-resistant MFA. Use PIM to require approval. Enable Identity Protection sign-in risk policy.
D.Configure PIM for all admin roles. Create access reviews for all users. Enable Identity Protection to detect risky sign-ins.
AnswerB

This is the correct answer because it layers three complementary controls that directly counter the attacker's tactic. Conditional Access with an authentication strength policy requiring phishing-resistant MFA (such as FIDO2 or Windows Hello) prevents credential theft and token replay that bypass ordinary MFA. The Identity Protection sign-in risk policy blocks sign-ins in real time when the risk level is high, such as those coming from anonymous IP addresses or anomalous locations. Restricting access to the Microsoft Graph API by requiring a specific role assignment ensures that only authorized identities can enumerate directory objects, closing the enumeration vector.

Why this answer

Phishing-resistant MFA can be enforced via Conditional Access with authentication strength. Sign-in risk policies in Identity Protection can block sign-ins from risky IPs. To prevent directory enumeration, you can restrict access to the Graph API by requiring a specific role assignment.

Option A is wrong because Security defaults enforce MFA but do not block all enumeration. Option C is wrong because PIM does not block enumeration. Option D is wrong because access reviews do not block enumeration.

535
Drag & Dropmedium

Drag and drop the steps to configure Azure Application Gateway with SSL termination using a Key Vault certificate into the correct order.

Drag or tap steps into the slots.

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

Why this order

SSL termination requires a certificate from Key Vault, configured on the listener.

536
MCQmedium

A company stores highly sensitive data in Azure Blob Storage. The security policy requires that all data is encrypted at rest using a key that is stored in Azure Key Vault, and that the storage account uses its system-assigned managed identity to access the key. Which encryption configuration should they use?

A.Server-side encryption with service-managed keys
B.Server-side encryption with customer-managed keys (CMK)
C.Client-side encryption
D.Azure Disk Encryption
AnswerB

Server-side encryption with customer-managed keys (CMK) encrypts data at rest using a data encryption key wrapped by a customer-controlled key encryption key stored in Azure Key Vault. The storage account's system-assigned managed identity authenticates to Key Vault to perform encryption and decryption of the underlying data key, giving the organization direct control over key rotation, auditing, and revocation. This satisfies the requirement of using a customer-managed key stored in Key Vault and is the appropriate mechanism for enforcing separation of duties and meeting compliance obligations.

Why this answer

Server-side encryption with customer-managed keys (CMK) is required because the security policy mandates that the encryption key be stored in Azure Key Vault and that the storage account uses its system-assigned managed identity to access that key. CMK allows you to bring your own key (BYOK) into Key Vault and grants the storage account access via a managed identity, ensuring the key is under your control and not managed by Azure. Service-managed keys (option A) use Microsoft-managed keys, which do not satisfy the requirement for customer-controlled key storage.

Exam trap

The trap here is that candidates confuse 'encryption at rest' with 'client-side encryption' or 'Azure Disk Encryption', failing to recognize that the requirement for a managed identity to access a Key Vault key directly points to server-side CMK, not client-side or disk-level encryption.

How to eliminate wrong answers

Option A is wrong because server-side encryption with service-managed keys uses keys managed entirely by Microsoft, not stored in the customer's Azure Key Vault, and does not involve a managed identity for access. Option C is wrong because client-side encryption encrypts data before it is sent to Azure Blob Storage, meaning the storage account never accesses the key via its managed identity; the key is managed on the client side. Option D is wrong because Azure Disk Encryption is used to encrypt virtual machine disks (OS and data disks) using BitLocker or DM-Crypt, not Azure Blob Storage data.

537
MCQhard

Your company is implementing a zero-trust security model. You need to ensure that all access to cloud applications is continuously verified based on user identity, device health, and location. Which combination of Microsoft security solutions should you use?

A.Microsoft Sentinel and Azure Policy
B.Microsoft Entra ID Protection and Privileged Identity Management
C.Azure Active Directory Domain Services and Azure Firewall
D.Microsoft Entra ID Conditional Access, Microsoft Intune, and Microsoft Defender for Cloud Apps
AnswerD

Conditional Access acts as the policy enforcement engine that combines user, device, location, and risk signals to require MFA or block sign-in, while Intune supplies the device compliance and configuration evidence that Conditional Access consumes. Defender for Cloud Apps extends enforcement beyond sign-in by applying session controls to discovered SaaS apps, so a flagged user can be allowed in read-only mode or prevented from uploading sensitive files. This identity-device-app trio verifies trust before access, during a session, and on the data plane, which is exactly the continuous verification model zero trust demands.

Why this answer

The zero-trust requirement for continuous verification of user identity, device health, and location is met by combining Microsoft Entra ID Conditional Access (enforces policies based on user, device, and location signals), Microsoft Intune (manages device compliance and health), and Microsoft Defender for Cloud Apps (provides continuous session-level monitoring and control of cloud app access). This trio delivers the real-time, policy-driven access checks that zero trust demands.

Exam trap

The trap here is that candidates often pick Option B (Identity Protection + PIM) because they associate identity protection with zero trust, but they miss the critical need for device health verification (Intune) and continuous session monitoring (Defender for Cloud Apps) that are explicitly required by the question.

How to eliminate wrong answers

Option A is wrong because Microsoft Sentinel is a SIEM/SOAR for threat detection and response, not an access control solution, and Azure Policy enforces resource compliance at the Azure infrastructure layer, not user/device/location-based access to cloud apps. Option B is wrong because Microsoft Entra ID Protection focuses on risk-based detection and remediation of compromised identities, and Privileged Identity Management (PIM) manages just-in-time privileged role activation; neither continuously verifies device health or location for all cloud app access. Option C is wrong because Azure Active Directory Domain Services provides managed domain services (e.g., LDAP, Kerberos) for legacy apps, not modern conditional access, and Azure Firewall is a network-layer firewall that cannot evaluate user identity, device health, or application-level signals.

538
MCQeasy

You need to provide secure remote access to Azure virtual machines without assigning them public IP addresses. Which Azure service should you use?

A.Azure VPN Gateway
B.Azure Firewall
C.Azure Bastion
D.Azure Front Door
AnswerC

Azure Bastion is a fully managed PaaS jump host deployed into a VNet that provides secure RDP and SSH connectivity to Azure VMs over TLS on port 443, directly within the Azure portal. It eliminates the need for each VM to have a public IP address or any inbound NSG rules for RDP/SSH, and it uses Microsoft Entra ID credentials, allowing integration with conditional access and multi-factor authentication. The broker service manages the session, making Azure Bastion the correct service for providing secure remote access to Azure virtual machines.

Why this answer

Azure Bastion provides secure, seamless RDP/SSH connectivity to Azure virtual machines directly in the Azure portal over TLS, without exposing public IP addresses. It uses a hardened, fully managed platform as a service (PaaS) that sits inside your virtual network, eliminating the need for a jump box or public-facing endpoints.

Exam trap

The trap here is that candidates often confuse Azure Bastion with Azure VPN Gateway, assuming a VPN is required for secure remote access, but Bastion is the correct choice when the goal is to avoid any public IP assignment and provide direct portal-based RDP/SSH.

How to eliminate wrong answers

Option A is wrong because Azure VPN Gateway extends your on-premises network to Azure over IPsec/IKE tunnels, but it does not provide browser-based RDP/SSH access to VMs without public IPs; it requires a VPN client and still relies on private IP connectivity. Option B is wrong because Azure Firewall is a stateful network firewall as a service that filters traffic at layers 3-7, but it does not offer RDP/SSH proxy or portal-based VM connectivity. Option D is wrong because Azure Front Door is a global load balancer and application delivery controller for HTTP/HTTPS traffic, not a remote access solution for VM management.

539
MCQeasy

A company uses Microsoft Sentinel to centralize security logs. They need to ensure that incidents from Microsoft Defender XDR are synchronized into Sentinel. Which data connector should they enable?

A.Office 365 connector
B.Windows Security Events connector
C.Microsoft Defender XDR connector
D.Azure Activity connector
AnswerC

The Microsoft Defender XDR connector is the correct data connector to centralize security incidents in Microsoft Sentinel. It connects to the Microsoft Graph Security API and imports incidents and alerts from all Defender XDR workloads—Defender for Endpoint, Defender for Identity, Defender for Office 365, and Defender for Cloud Apps—into Sentinel. This connector keeps incident status, severity, and classification synchronized bidirectionally, so you can manage the full incident lifecycle from Sentinel. Without this connector, Defender XDR incidents would not appear in Sentinel at all, making it the only option that directly satisfies the requirement.

Why this answer

The Microsoft Defender XDR connector (option C) is the correct choice because it is the built-in Microsoft Sentinel data connector designed to ingest and synchronize incidents and alerts from Microsoft Defender XDR into Sentinel, enabling unified incident management across Defender products. The Office 365 connector (option A) only ingests Office 365 audit and activity logs, not Defender XDR incidents. The Windows Security Events connector (option B) collects Windows event logs from agents, and the Azure Activity connector (option D) ingests Azure subscription control-plane activity, neither of which synchronizes Defender XDR incidents.

540
MCQmedium

You are configuring Microsoft Defender for Cloud's continuous export feature. You need to export security alerts and recommendations to a Log Analytics workspace for long-term retention and custom analysis. The export should include only high-severity alerts and recommendations. What should you do?

A.Set up Microsoft Sentinel to ingest Defender for Cloud alerts and then export to the workspace.
B.Enable continuous export in Defender for Cloud and select high-severity alerts and recommendations.
C.Configure diagnostic settings on each Azure resource to send logs to the workspace.
D.Use Azure Event Hubs to stream security alerts to the workspace.
AnswerB

Enabling continuous export in Defender for Cloud is the native, centralized method to stream security data to a Log Analytics workspace. You can filter to high-severity alerts and recommendations at the subscription or management-group level, ensuring only actionable events are stored. This is the intended configuration for satisfying the requirement directly.

Why this answer

Microsoft Defender for Cloud's continuous export feature allows you to directly export security alerts and recommendations to a Log Analytics workspace with granular filtering by severity. This meets the requirement for long-term retention and custom analysis without additional services. Selecting 'high-severity' in the export configuration ensures only the specified alerts and recommendations are exported.

Exam trap

The trap here is that candidates often confuse the continuous export feature with diagnostic settings or assume that a SIEM like Sentinel is required for custom analysis, when in fact Defender for Cloud's built-in export can directly filter and send data to a Log Analytics workspace.

How to eliminate wrong answers

Option A is wrong because Microsoft Sentinel is a SIEM solution that ingests alerts from Defender for Cloud, but it adds unnecessary complexity and cost; the continuous export feature in Defender for Cloud can directly export to a Log Analytics workspace without Sentinel. Option C is wrong because diagnostic settings on individual Azure resources export resource-level logs (e.g., activity logs, metrics), not Defender for Cloud's security alerts and recommendations, which are generated at the subscription or workspace level. Option D is wrong because Azure Event Hubs is used for real-time streaming to external systems, not for direct export to a Log Analytics workspace; continuous export already supports direct workspace export without Event Hubs.

541
MCQmedium

A company has an Azure virtual network with multiple subnets hosting different application tiers. They need to inspect and filter all outbound traffic from VMs to the internet, and they must be able to allow or deny traffic based on fully qualified domain names (FQDNs). Which Azure networking service should they deploy?

A.Azure Firewall.
B.Network Security Groups (NSGs).
C.Azure Application Gateway.
D.Azure VPN Gateway.
AnswerA

Azure Firewall is a managed, cloud-native network security service that enforces application-layer rules based on FQDN. Its application rule collection can allow or deny outbound traffic to specific domain names (e.g., *.windowsupdate.com) independently of IP address, which is critical because many cloud services resolve to changing IPs. Azure Firewall also supports network rules, threat intelligence, and is centrally deployed to inspect all egress traffic, making it the correct choice for application-level outbound filtering.

Why this answer

Azure Firewall is a managed, cloud-based network security service that can inspect and filter outbound traffic from Azure virtual networks to the internet. It supports application rules based on fully qualified domain names (FQDNs), allowing or denying traffic by FQDN, which directly meets the requirement. Unlike simpler filtering options, Azure Firewall provides stateful inspection and integrates with Azure Monitor for logging.

Exam trap

The trap here is that candidates often confuse Network Security Groups (NSGs) with Azure Firewall, assuming NSGs can filter by FQDN because they support service tags, but service tags are IP-based and do not allow granular FQDN-level control.

How to eliminate wrong answers

Option B is wrong because Network Security Groups (NSGs) filter traffic based on source/destination IP addresses, ports, and protocols, but they cannot filter by FQDN; they lack application-layer inspection for domain names. Option C is wrong because Azure Application Gateway is a Layer 7 load balancer that routes HTTP/HTTPS traffic based on URL paths or host headers, but it is not designed for general outbound internet traffic inspection or FQDN-based filtering for all protocols. Option D is wrong because Azure VPN Gateway is used to create encrypted tunnels between on-premises networks and Azure, not for inspecting or filtering outbound internet traffic.

542
Multi-Selecthard

A KQL query in Microsoft Sentinel detects impossible travel but returns many false positives from known VPN egress IP addresses. Which two changes would best reduce noise while preserving useful detections?

Select 2 answers
A.Join or filter against a watchlist of approved VPN egress IPs
B.Disable the SigninLogs connector for the tenant
C.Exclude events where the source IP is in the approved network list
D.Raise the query frequency from 1 hour to 24 hours
AnswersA, C

Joining SigninLogs against a Sentinel watchlist of approved VPN egress IPs lets the query remove or tag sign-ins originating from trusted corporate VPN ranges before the impossible-travel logic is applied. A watchlist is the maintainable, centrally managed artifact for this, and the KQL join (or lookup) against _GetWatchlist('VPN-Egress') is the canonical way to enrich or filter anomalies. This directly targets the false-positive source while preserving all other sign-in telemetry.

Why this answer

Integrating a watchlist of known VPN egress IPs allows the KQL query to filter out these trusted IPs, reducing false positives from impossible travel detections. Option C is also correct because excluding events where the source IP is in an approved network list directly removes noise from legitimate VPN traffic, preserving detection of truly anomalous sign-ins. Both approaches leverage Sentinel's watchlist or allowlist capabilities to maintain detection fidelity while minimizing alert fatigue.

Exam trap

The trap here is that candidates may confuse reducing alert frequency (Option D) with reducing false positives, or think disabling a data connector (Option B) is a valid noise-reduction technique, when in fact both actions cripple detection capability rather than refining it.

543
MCQmedium

Your company uses Azure Files shares to store business documents. You need to ensure that access to the shares is restricted to users who have been granted explicit permissions. What should you configure?

A.Configure a firewall rule to allow only corporate IP ranges.
B.Use storage account access keys to mount the file share.
C.Enable identity-based authentication for Azure Files using Microsoft Entra ID and set share-level permissions.
D.Generate a shared access signature (SAS) with read permissions.
AnswerC

Identity-based authentication via Microsoft Entra ID maps a user's token to a share-level role assignment (Storage File Data SMB Share Reader, Contributor, or Elevated Contributor), so only principals explicitly granted those roles gain access. This satisfies the stem's requirement that access be restricted to users holding granted permissions, unlike storage account key access, which grants unrestricted share access.

Why this answer

Identity-based authentication for Azure Files using Microsoft Entra ID allows you to assign share-level permissions (e.g., Storage File Data SMB Share Contributor) to specific users or groups, ensuring only explicitly authorized identities can access the share. This meets the requirement of restricting access to users with explicit permissions, as opposed to relying on network rules or shared keys.

Exam trap

The trap here is that candidates often confuse network-level restrictions (firewall rules) or token-based access (SAS) with identity-based access control, mistakenly believing that restricting IP ranges or using SAS tokens satisfies the requirement for explicit user permissions, when in fact only identity-based authentication with Microsoft Entra ID provides per-user authorization.

How to eliminate wrong answers

Option A is wrong because configuring a firewall rule to allow only corporate IP ranges restricts access based on network location, not on user identity or explicit permissions; any user from a corporate IP could still access the share if they have the storage account key or SAS. Option B is wrong because using storage account access keys grants full administrative access to the entire storage account, not just the file share, and cannot be scoped to individual users or groups, violating the principle of least privilege. Option D is wrong because a shared access signature (SAS) with read permissions provides time-limited, token-based access that is not tied to a specific user identity and cannot enforce per-user explicit permissions; it also exposes the share to anyone possessing the SAS token.

544
MCQhard

A security analyst uses Microsoft Defender for Cloud. They need to continuously monitor the security posture of their Azure subscription against the Microsoft cloud security benchmark (MCSB). They want to see the current compliance score and specific recommendations for failing controls. Which Defender for Cloud feature should they use?

A.Regulatory compliance dashboard
B.Security posture
C.Workbooks
D.Advanced hunting
AnswerA

The regulatory compliance dashboard continuously assesses resources against MCSB controls, displaying the current compliance score and per-control recommendations for failing items. It satisfies the requirement for ongoing posture monitoring with both an aggregate score and specific remediation guidance, unlike one-off secure score snapshots or alert-based features.

Why this answer

The Regulatory compliance dashboard in Microsoft Defender for Cloud is specifically designed to track compliance against standards like the Microsoft cloud security benchmark (MCSB). It provides a current compliance score and lists specific recommendations for failing controls, enabling continuous monitoring and remediation tracking. This dashboard aggregates assessment results from the secure score and maps them to the controls defined in the selected regulatory standard.

Exam trap

The trap here is that candidates often confuse the 'Security posture' feature (which shows a general secure score) with the 'Regulatory compliance dashboard' (which maps that score to a specific regulatory standard like MCSB), leading them to choose the wrong option because they overlook the requirement for standard-specific compliance tracking.

How to eliminate wrong answers

Option B (Security posture) is wrong because the Security posture feature focuses on the overall secure score and security recommendations based on best practices, not on mapping to a specific regulatory standard like MCSB. Option C (Workbooks) is wrong because Workbooks are customizable Azure Monitor dashboards that can visualize data from multiple sources, but they do not natively provide the out-of-the-box compliance score and control mapping against MCSB. Option D (Advanced hunting) is wrong because Advanced hunting is a query-based threat hunting tool in Microsoft 365 Defender for investigating security incidents, not for monitoring compliance posture or regulatory benchmarks.

545
MCQmedium

A company uses Azure AD Privileged Identity Management (PIM) for the Global Administrator role. They want to ensure that when a user activates the role, the activation request must be approved by a member of the 'Global Admin Approvers' group, and the activation should be time-bound with a maximum of 4 hours. Which PIM settings should they configure?

A.Set the activation maximum duration to 4 hours and require approval from the 'Global Admin Approvers' group.
B.Set the activation maximum duration to 4 hours and enable MFA on activation.
C.Set the activation to require a ticket number justification and set the maximum duration to 8 hours.
D.Set the role to be permanently active but with a just-in-time approval workflow.
AnswerA

Setting the activation maximum duration to 4 hours directly enforces the time limit requirement in PIM's role settings, while requiring approval from the 'Global Admin Approvers' group ensures that every activation request is explicitly reviewed and approved before the role becomes active. This is the only option that fully aligns with both stated conditions: a 4-hour window and an approval workflow with the designated group.

Why this answer

Azure AD PIM allows you to configure role activation settings, including an activation maximum duration (which can be set to 4 hours) and requiring approval from a specified group (in this case, 'Global Admin Approvers'). These settings directly meet the requirement for time-bound activation with approval.

Exam trap

The trap here is that candidates may confuse 'require approval' with 'require MFA' or 'require justification', not realizing that approval is a distinct setting that must be explicitly configured to meet the requirement for a designated approver group.

How to eliminate wrong answers

Option B is wrong because enabling MFA on activation does not satisfy the requirement for approval from the 'Global Admin Approvers' group; MFA is an additional security measure, not a substitute for approval. Option C is wrong because requiring a ticket number justification does not enforce approval, and setting the maximum duration to 8 hours exceeds the required 4-hour limit. Option D is wrong because setting the role to be permanently active contradicts the requirement for time-bound activation, and just-in-time approval workflow does not enforce a maximum duration.

546
MCQeasy

You are configuring an Azure Kubernetes Service (AKS) cluster. You need to ensure that pods can securely access Azure Container Registry (ACR) without storing image pull secrets in the pod specification. What should you do?

A.Create a service principal and store the secret in a Kubernetes secret, then reference it in the pod spec
B.Enable admin account on ACR and use the admin username and password in the pod spec
C.Enable managed identity on AKS and assign the AcrPull role to the kubelet identity
D.Use the storage account key of the attached Azure storage account
AnswerC

When managed identity is enabled on an AKS cluster, the kubelet runs with its own managed identity (the kubelet identity) that can be granted the AcrPull role on the target Azure Container Registry. The kubelet then authenticates to ACR using an Azure AD token obtained from the Azure Instance Metadata Service, eliminating any stored secrets in the cluster. Scoping the AcrPull role to only the registry and the identity to only pulling images follows least privilege, and the token is automatically rotated by Azure.

Why this answer

Enabling managed identity on AKS creates a kubelet identity that can be granted the AcrPull role via Azure RBAC. This allows AKS to authenticate to ACR automatically without storing any secrets in the pod specification, as the kubelet uses the managed identity to pull container images on behalf of the pods.

Exam trap

The trap here is that candidates often confuse using a service principal (Option A) with managed identity, not realizing that a service principal still requires storing a secret, whereas managed identity eliminates the need for any stored credentials in the cluster.

How to eliminate wrong answers

Option A is wrong because it still requires storing a secret (the service principal secret) in a Kubernetes secret and referencing it in the pod spec, which violates the requirement to avoid storing image pull secrets in the pod specification. Option B is wrong because enabling the admin account on ACR and using its username/password in the pod spec stores credentials directly in the pod spec, which is insecure and does not meet the requirement. Option D is wrong because storage account keys are used for accessing Azure Blob Storage, not for authenticating to Azure Container Registry, and they have no relevance to ACR image pull authentication.

547
MCQmedium

A security engineer wants Defender for Cloud to detect threats against Azure SQL Database and SQL Server on Azure VMs. Which plan should be enabled?

A.Defender for Storage
B.Defender for Databases or Defender for SQL coverage as presented in the portal
C.Defender for App Service only
D.Defender External Attack Surface Management
AnswerB

Enabling Defender for Databases or Defender for SQL coverage in the Defender for Cloud portal activates SQL Advanced Threat Protection for supported engines such as Azure SQL Database, SQL Managed Instance, Azure Synapse dedicated SQL pools, and SQL Server on Azure VMs. This control analyzes database audit logs and query activity in real time to detect SQL injection, anomalous access, and brute-force attempts. It is the direct and correct mechanism for database threat detection in Defender for Cloud.

Why this answer

Defender for Databases (or the Defender for SQL coverage option in the portal) is the correct plan because it provides threat detection specifically for Azure SQL Database and SQL Server on Azure VMs. This plan monitors anomalous activities such as SQL injection, brute-force attacks, and unusual access patterns using Microsoft's threat intelligence and machine learning models. It is the only plan that directly covers both PaaS and IaaS SQL workloads as described.

Exam trap

The trap here is that candidates may confuse 'Defender for Storage' with protecting SQL databases because SQL databases store data, but Defender for Storage is specifically for blob, file, and data lake storage, not for relational database engines like SQL Server or Azure SQL Database.

How to eliminate wrong answers

Option A is wrong because Defender for Storage is designed to detect threats against Azure Blob Storage, Azure Files, and Data Lake Storage, not against SQL databases or SQL Server instances. Option C is wrong because Defender for App Service only protects web applications running on Azure App Service, not SQL databases or SQL Server on VMs. Option D is wrong because Defender External Attack Surface Management focuses on discovering and monitoring an organization's external internet-facing assets and attack surfaces, not on detecting threats within Azure SQL Database or SQL Server on VMs.

548
MCQeasy

You need to ensure that all Azure subscriptions in your tenant are automatically assessed for security misconfigurations and compliance against Microsoft cloud security benchmark. What should you configure?

A.Deploy Microsoft Sentinel with automatic data connectors
B.Assign an initiative via Azure Policy to all subscriptions
C.Enable continuous export in Microsoft Defender for Cloud
D.Create a blueprint definition and assign it to management group
AnswerB

Assigning the built-in Microsoft cloud security benchmark initiative through Azure Policy to all subscriptions is the correct and native way to ensure ongoing assessment. This initiative bundles dozens of policy definitions that audit and enforce security controls, such as encryption, network security, and identity management, and Azure Policy continuously evaluates resources against these rules without additional deployment. Assigning the initiative at the subscription scope triggers immediate compliance assessment and produces a compliance report that can be monitored in Defender for Cloud.

Why this answer

The Microsoft cloud security benchmark is a built-in initiative in Azure Policy. By assigning this initiative to all subscriptions, you automatically assess them for security misconfigurations and compliance. Defender for Cloud uses these policies, but ensuring the assessment requires the initiative assignment.

Option C is incorrect because enabling continuous export only streams completed assessment data; it does not trigger the assessment itself.

Exam trap

The trap is confusing Azure Policy initiatives (which enforce compliance) with Defender for Cloud's continuous export (which streams assessment data). The benchmark assessment is triggered by assigning the built-in Azure Policy initiative, not by continuous export.

How to eliminate wrong answers

Option A is wrong because Microsoft Sentinel is a SIEM/SOAR solution for threat detection and response, not a tool for automated compliance assessment against the Microsoft cloud security benchmark; it can ingest data from Defender for Cloud but does not itself perform the benchmark assessment. Option B is wrong because assigning an initiative via Azure Policy enforces compliance rules and remediates resources, but it does not automatically assess subscriptions for security misconfigurations against the Microsoft cloud security benchmark; the benchmark assessment is a feature of Defender for Cloud, not Azure Policy. Option D is wrong because Azure Blueprints are used to define a repeatable set of Azure resources and policies for environment deployment, not for ongoing automated security assessment; they are deprecated in favor of deployment stacks and do not provide continuous compliance monitoring against the benchmark.

549
MCQeasy

Your organization wants to use Microsoft Sentinel to automatically respond to high-severity incidents. Which feature should you configure?

A.Create an analytics rule with a high severity.
B.Create an automation rule that triggers a playbook on incident creation.
C.Create a workbook to visualize incidents.
D.Enable entity behavior analytics.
AnswerB

Automation rules are the native orchestration component in Microsoft Sentinel for centrally managing incident responses. You can configure a trigger such as 'When incident is created' and conditionally invoke an Azure Logic Apps-based playbook to perform actions like opening a ticket, notifying analysts, or applying remediation. This directly achieves automated response because it links incident creation to an executable workflow without manual intervention.

Why this answer

Microsoft Sentinel automation rules allow you to define automated responses to incidents, such as triggering a playbook (a collection of actions based on Azure Logic Apps) when an incident is created. This directly meets the requirement to automatically respond to high-severity incidents without manual intervention.

Exam trap

The trap here is that candidates often confuse analytics rules (which generate incidents) with automation rules (which respond to incidents), leading them to select Option A thinking severity configuration alone enables automated response.

How to eliminate wrong answers

Option A is wrong because creating an analytics rule with a high severity only generates incidents based on detection logic; it does not configure any automated response. Option C is wrong because a workbook is used for visualizing and analyzing data, not for automating responses to incidents. Option D is wrong because entity behavior analytics provides behavioral insights and anomaly detection but does not trigger automated actions like playbooks.

550
MCQmedium

Refer to the exhibit. You are querying the sys.column_master_keys view in an Azure SQL Database. What is the purpose of this query?

A.To check the Dynamic Data Masking policies.
B.To retrieve the column master key configuration for Always Encrypted.
C.To verify the configuration of Transparent Data Encryption (TDE).
D.To list the encryption keys used for column-level encryption.
AnswerB

The sys.column_master_keys catalog view is the correct place to retrieve the column master key (CMK) configuration for Always Encrypted. It contains one row per CMK in the database, including the key name, key store provider name (for example, 'MSSQL_CERTIFICATE_STORE' or 'AZURE_KEY_VAULT'), the key path, and settings such as allow_enclave_computations. This metadata is essential for managing and rotating the keys that protect column encryption keys in the Always Encrypted feature.

Why this answer

The sys.column_master_keys view in Azure SQL Database specifically returns metadata about column master keys (CMKs) used by Always Encrypted. These keys protect the column encryption keys (CEKs) that encrypt sensitive data columns. Therefore, querying this view retrieves the column master key configuration for Always Encrypted, making option B correct.

Exam trap

The trap here is that candidates confuse the sys.column_master_keys view with sys.column_encryption_keys or assume it covers all encryption types (like TDE or Dynamic Data Masking), when it is exclusively for Always Encrypted's master key metadata.

How to eliminate wrong answers

Option A is wrong because Dynamic Data Masking policies are stored in sys.database_scoped_configurations or managed via ALTER TABLE statements, not in sys.column_master_keys. Option C is wrong because Transparent Data Encryption (TDE) configuration is verified using sys.dm_database_encryption_keys or sys.databases, not the column master keys view. Option D is wrong because column-level encryption keys (CEKs) are listed in sys.column_encryption_keys, while sys.column_master_keys only stores the master keys that protect those CEKs.

551
MCQeasy

You need to ensure that when a user's role in Microsoft Entra ID is changed (e.g., from User to Global Administrator), the change is approved by a manager before it takes effect. Additionally, you need to enforce just-in-time (JIT) access for that role. What should you use?

A.Configure Microsoft Entra Privileged Identity Management (PIM) for the role with approval required and JIT activation.
B.Use Microsoft Entra access reviews to review role assignments monthly.
C.Create a Conditional Access policy requiring manager approval for role assignment.
D.Assign the role via Azure RBAC with a custom role.
AnswerA

Microsoft Entra Privileged Identity Management provides eligible role assignments with approval workflows and time-bound JIT activation, so a manager must approve before the Global Administrator role becomes active. Standard role assignment cannot enforce approval or JIT.

Why this answer

Microsoft Entra Privileged Identity Management (PIM) is the correct choice because it is the only service that provides just-in-time (JIT) role activation with an approval workflow, allowing you to require a manager's approval before a role assignment becomes active. In PIM, you configure the role's settings to require approval for activation and set the maximum activation duration, so the user is eligible but not permanently assigned until approved. Access reviews (B) only recertify existing assignments periodically and do not gate activation or provide JIT.

Conditional Access (C) controls access to resources based on signals like user, device, and location, but it cannot require manager approval for a directory role assignment. Azure RBAC custom roles (D) scope permissions on Azure resources but do not provide approval workflows or JIT activation for Microsoft Entra ID roles.

552
MCQeasy

Your company wants to use Microsoft Defender for Cloud's just-in-time (JIT) VM access to reduce the attack surface. You have enabled JIT for a set of VMs. A security administrator reports that they cannot connect via RDP even after requesting access. What is the most likely cause?

A.The JIT policy is set at the subscription level and does not apply to individual VMs.
B.The administrator's source IP address is not in the allowed list for the JIT policy.
C.The VM is not located in a region that supports JIT.
D.The VM does not have the Azure VM agent installed.
AnswerB

The administrator's current source IP address must be included in the allowed source IP/CIDR list when a JIT access request is made. JIT creates an NSG rule that only permits traffic from the specified IP ranges, so if the admin's external IP is not among them, Defender for Cloud will reject the request or no temporary rule is created. The request also must satisfy RBAC permissions, but the source IP match is a separate, mandatory condition for the connection to be opened.

Why this answer

The most likely cause is that the administrator's source IP address is not included in the allowed list for the JIT policy. When a user requests JIT access, Defender for Cloud opens the specified ports (e.g., 3389 for RDP) only to the source IP addresses that are explicitly permitted in the policy. If the administrator's IP is not in the allowed list, the request may be approved but the network security group (NSG) or Azure Firewall rule will not include that IP, resulting in a connection failure.

Exam trap

The trap here is that candidates often assume JIT access automatically allows any authenticated user to connect, but in reality the source IP must be explicitly permitted in the policy, and a common mistake is to overlook the IP restriction when troubleshooting connectivity.

How to eliminate wrong answers

Option A is wrong because JIT policies can be applied at the subscription, resource group, or individual VM level; enabling JIT for a set of VMs means the policy is applied directly to those VMs, not just at the subscription level. Option C is wrong because JIT VM access is supported in all Azure regions where Defender for Cloud is available; there is no regional restriction that would block access. Option D is wrong because while the Azure VM agent is required for some Defender for Cloud features (like vulnerability assessment), JIT access does not depend on the VM agent; it works by modifying NSG or Azure Firewall rules at the platform level.

553
MCQmedium

A company runs a global web application on Azure App Service instances deployed in multiple Azure regions. They want to protect the application from common web attacks such as SQL injection and cross-site scripting (XSS) using a centralized set of managed rules that can be automatically updated. They also need to improve performance by terminating traffic at the nearest point of presence (POP) to end users. Which Azure service should they deploy in front of the App Service?

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

Azure Front Door with WAF is a global layer-7 service that uses the Microsoft global edge network with anycast, ensuring connections are terminated at the nearest point of presence (POP) rather than the origin region. It applies Web Application Firewall rules, including OWASP managed rule sets, at that edge, which blocks malicious requests before they traverse the backbone to your web app. This combination of global load balancing, TLS termination, and built-in WAF protection directly addresses both performance and security requirements for a worldwide audience.

Why this answer

Azure Front Door with WAF is correct because it provides global, centralized protection against common web attacks (SQL injection, XSS) using managed rule sets that are automatically updated, and it terminates traffic at the nearest point of presence (POP) to end users, improving performance through global load balancing and TLS termination. This meets both the security and performance requirements for a multi-region App Service deployment.

Exam trap

The trap here is that candidates often confuse Azure Application Gateway (regional, Layer 7 load balancer with WAF) with Azure Front Door (global, multi-region, with WAF), failing to recognize that only Front Door provides both global POP termination and centralized WAF for multi-region deployments.

How to eliminate wrong answers

Option A is wrong because Azure Application Gateway with WAF is a regional service, not a global one; it cannot terminate traffic at the nearest POP across multiple Azure regions and does not provide the global performance optimization needed. Option C is wrong because Azure Traffic Manager is a DNS-based traffic routing service that does not include a Web Application Firewall or any application-layer attack protection, and it does not terminate traffic at POPs. Option D is wrong because Azure CDN is primarily a content caching and delivery service; while it can improve performance via POPs, it does not include a built-in WAF with managed rules for SQL injection and XSS protection, and its security capabilities are limited to DDoS protection and access restrictions.

554
MCQeasy

Your organization uses Microsoft Sentinel for security information and event management (SIEM). You need to create a custom analytic rule that triggers an incident when a user signs in from an unfamiliar location. Which data source should you use?

A.Azure Activity Logs
B.Microsoft Entra ID Sign-in Logs
C.Azure AD Audit Logs
D.Microsoft 365 Defender Alerts
AnswerB

Microsoft Entra ID Sign-in Logs record every authentication attempt for interactive and non-interactive sign-ins, including the client IP, approximate geolocation, browser/device, and conditional access results. These logs are designed for identity security scenarios, and when streamed to Microsoft Sentinel they enable analytics rules for unfamiliar sign-in detection. The location data is essential, making these logs the correct answer. This is why Sign-in Logs are the appropriate data source.

Why this answer

Microsoft Entra ID Sign-in Logs contain detailed information about user sign-in events, including location data. A custom analytic rule in Microsoft Sentinel can use these logs to detect sign-ins from unfamiliar locations by comparing the location against a user's typical sign-in pattern, which is a common UEBA (User and Entity Behavior Analytics) scenario.

Exam trap

The trap here is that candidates often confuse Azure AD Audit Logs (which track configuration changes) with Sign-in Logs (which track authentication events), leading them to select the audit logs for a sign-in behavior detection rule.

How to eliminate wrong answers

Option A is wrong because Azure Activity Logs track control-plane operations on Azure resources (e.g., creating a VM), not user sign-in events or location data. Option C is wrong because Azure AD Audit Logs record administrative changes in Entra ID (e.g., role assignments, group modifications), not user sign-in attempts or location details. Option D is wrong because Microsoft 365 Defender Alerts are pre-built security alerts from Microsoft 365 Defender, not raw sign-in logs; they do not provide the granular location data needed to define a custom unfamiliar location rule.

555
Multi-Selectmedium

Which TWO of the following are valid methods to ingest data into Microsoft Sentinel? (Select two.)

Select 2 answers
A.Using the Log Analytics agent to send custom logs.
B.Using the Azure PowerShell cmdlets to send events directly.
C.Using Power BI to stream data.
D.Using Azure Policy to forward logs.
E.Using a data connector from the content hub.
AnswersA, E

Custom logs are a legitimate ingestion path in Microsoft Sentinel because the Log Analytics agent can be configured to monitor specific local text files and send their contents to an Azure Log Analytics workspace. Since Sentinel is built on a Log Analytics workspace, data collected by this agent is automatically available for security analytics. This method is useful for legacy on-premises or IaaS workloads where installing an agent is feasible, and it is a first-class ingestion method for custom log sources.

Why this answer

Option A is correct because the Log Analytics agent (MMA/AMA) can be installed on machines to collect custom logs and Windows/Linux events and forward them to the Log Analytics workspace that backs Microsoft Sentinel, including custom log ingestion via the Log Analytics Data Collector API or custom tables. Option E is correct because Microsoft Sentinel ingests data through data connectors, many of which are available from the Content Hub (e.g., Microsoft 365 Defender, Azure Activity, AWS, syslog via AMA), and these connectors are the primary supported ingestion method. Option B is not a valid ingestion method because Azure PowerShell cmdlets manage resources and configuration but do not stream event data directly into Sentinel; ingestion occurs via agents, connectors, or the Data Collector API.

Option C is not valid because Power BI is a visualization and reporting tool, not a data streaming or ingestion pipeline into Sentinel. Option D is not valid because Azure Policy enforces governance and compliance on resources; it does not forward logs to Microsoft Sentinel, though diagnostic settings or connectors are used for that purpose.

Exam trap

The trap here is that candidates often confuse Azure Policy (which enforces rules) with diagnostic settings or data connectors (which actually forward logs), leading them to select Option D incorrectly.

556
MCQmedium

You are designing a network security strategy for a multi-tier application. The web tier must be accessible from the internet, but the application and database tiers must only be accessible from the web tier. Which Azure solution should you use to isolate the tiers?

A.Azure DDoS Protection
B.Azure Firewall with application rules
C.Network security groups (NSGs) on each subnet
D.Azure Private Link
AnswerC

Network security groups (NSGs) are stateful, L3/L4 filtering entities that can be associated to either a subnet or a NIC, making them an ideal tool to isolate tiers within a VNet. For example, you can create a rule on the database subnet that only allows inbound TCP 1433 from the application subnet's address prefix, while denying all other inbound traffic. NSGs provide the required network-level segmentation with no need for a separate gateway or virtual appliance, and they combine easily with service tags and application security groups for maintainability.

Why this answer

Network security groups (NSGs) on each subnet are the correct solution because they provide stateful, layer-3/layer-4 traffic filtering at the subnet level. By placing the web tier in a subnet with an NSG that allows inbound HTTP/HTTPS from the internet, and placing the application and database tiers in separate subnets with NSGs that only allow inbound traffic from the web tier subnet (using source IP ranges or service tags), you effectively isolate the tiers while permitting the required east-west traffic.

Exam trap

The trap here is that candidates often confuse centralized firewall solutions (like Azure Firewall) with subnet-level access control, forgetting that NSGs are the native, lightweight, and correct tool for per-subnet traffic filtering in a multi-tier architecture.

How to eliminate wrong answers

Option A is wrong because Azure DDoS Protection is a defense against volumetric distributed denial-of-service attacks, not a mechanism for network segmentation or tier isolation. Option B is wrong because Azure Firewall with application rules operates at the application layer (FQDN filtering) and is typically deployed as a centralized security boundary, not for per-subnet isolation; it would add unnecessary complexity and cost for simple tier-to-tier access control. Option D is wrong because Azure Private Link exposes a managed service over a private endpoint within a virtual network, but it does not provide the subnet-level traffic filtering needed to restrict access between tiers; it is designed for private connectivity to PaaS services, not for segmenting application tiers.

557
MCQhard

Your organization uses Microsoft Sentinel to detect threats across multiple Azure subscriptions. Security analysts need to query threat intelligence data from Microsoft Defender Threat Intelligence (MDTI) directly within Sentinel. However, analysts report that MDTI indicators are not appearing in ThreatIntelligenceIndicator table. What is the most likely cause?

A.The MDTI data connector is not enabled in Microsoft Sentinel.
B.The Sentinel workspace is located in a region where MDTI is not supported.
C.The subscriptions are not onboarded to Microsoft Defender for Cloud.
D.The Sentinel workspace is not using Azure Lighthouse for cross-subscription management.
AnswerA

The Microsoft Defender Threat Intelligence (MDTI) data connector is the explicit integration point that imports threat indicators — malicious domains, IP addresses, and other observables — into the Log Analytics workspace's ThreatIntelligenceIndicator table. Without this connector enabled in the Sentinel Content hub and properly authenticated via Microsoft Graph, no MDTI indicators will be ingested, so any analytics rules that depend on those indicators will produce no alerts. This directly explains the absence of MDTI-derived detections regardless of the workspace region, subscription posture, or management architecture.

Why this answer

The most likely cause is that the MDTI data connector is not enabled in Microsoft Sentinel. Without enabling this connector, threat intelligence indicators from Microsoft Defender Threat Intelligence will not be ingested into the ThreatIntelligenceIndicator table, regardless of other configurations. The connector must be explicitly installed and configured to pull MDTI data into the workspace.

Exam trap

The trap here is that candidates may assume cross-subscription or cross-tenant configurations (like Azure Lighthouse or Defender for Cloud onboarding) are required for data ingestion, when in fact the missing connector is the direct and most likely cause.

How to eliminate wrong answers

Option B is wrong because MDTI is a global cloud service and is supported in all Azure regions where Microsoft Sentinel is available; regional unavailability is not a known limitation. Option C is wrong because onboarding subscriptions to Microsoft Defender for Cloud is not a prerequisite for ingesting MDTI indicators into Sentinel; MDTI data flows through its own connector independent of Defender for Cloud. Option D is wrong because Azure Lighthouse is used for managing multiple tenants, not for cross-subscription data ingestion within a single tenant; Sentinel can query multiple subscriptions without Lighthouse.

558
MCQhard

A company uses Azure SQL Database with Transparent Data Encryption (TDE) encrypted using a customer-managed key (CMK) stored in Azure Key Vault. The Key Vault is protected by a firewall that denies all public access. The SQL server must be able to access the key for TDE operations. Which additional configuration is necessary in the Key Vault to allow this?

A.Configure a private endpoint for the Key Vault and assign it to the SQL server's virtual network.
B.Enable soft-delete on the Key Vault.
C.Enable the 'Allow trusted Microsoft services to bypass this firewall' setting.
D.Add a firewall rule to allow traffic from the Azure SQL Database's public IP address.
AnswerC

This setting allows Azure services like Azure SQL Database, which are trusted by Azure, to access the Key Vault even when the firewall is enabled to deny public traffic. It is the required configuration to allow TDE operations.

Why this answer

When Azure Key Vault is protected by a firewall that denies all public access, the Azure SQL Database service (a trusted Microsoft service) must be explicitly allowed to bypass the firewall to retrieve the customer-managed key for TDE operations. Enabling the 'Allow trusted Microsoft services to bypass this firewall' setting permits the SQL server's managed identity to authenticate and access the key vault without requiring a public IP address or network rule.

Exam trap

The trap here is that candidates often confuse network-level controls (private endpoints, firewall rules) with the Azure platform's built-in trust mechanism, mistakenly thinking that a private endpoint or a static IP rule is required when the simpler 'trusted Microsoft services' bypass is the correct and intended solution for PaaS services like Azure SQL Database.

How to eliminate wrong answers

Option A is wrong because a private endpoint for Key Vault would require the SQL server to be on the same virtual network, but Azure SQL Database is a PaaS service that does not reside in a customer's virtual network by default; the SQL server's managed identity accesses Key Vault over the Azure backbone, not via a private endpoint. Option B is wrong because soft-delete is a data protection feature that prevents permanent deletion of keys, secrets, or certificates, but it does not control network access or firewall bypass for TDE operations. Option D is wrong because Azure SQL Database does not have a static public IP address; its outbound IPs can change and are not assigned to the logical server, making a firewall rule based on a public IP unreliable and unnecessary when the trusted Microsoft services bypass is available.

559
MCQeasy

You are the Azure Security Engineer for a company that uses Microsoft Entra ID. The company has a policy that all administrative accounts must use multi-factor authentication (MFA) when signing in. You need to enforce this policy for a group of administrators. What is the simplest way to achieve this?

A.Create a Conditional Access policy that requires MFA for the administrator group when accessing all cloud apps.
B.Configure per-user MFA for each administrator account.
C.Enable security defaults in Microsoft Entra ID.
D.Create a Microsoft Entra ID Protection sign-in risk policy that requires MFA for administrators.
AnswerA

A Conditional Access policy can be targeted to a specific group of administrators and require MFA for all cloud apps. This is the simplest and most direct method to enforce MFA for that group. It provides granular control and can be easily managed. This meets the requirement without affecting other users.

Why this answer

The simplest way to enforce MFA for a specific group of administrators is to create a Conditional Access policy that targets that group and requires MFA for all cloud apps. This provides granular control and is easy to manage. Other options either apply to all users, require manual per-user settings, or are risk-based rather than always-on.

Exam trap

The trap here is choosing security defaults or per-user MFA, which are either too broad or too manual, instead of the targeted Conditional Access policy.

560
MCQhard

Refer to the exhibit. You are reviewing an ARM template for an Azure Storage account. Which of the following is true about the deployment?

A.The storage account will use customer-managed keys from Azure Key Vault.
B.The storage account will use locally redundant storage (LRS).
C.The storage account will have a firewall rule to restrict access to specific IPs.
D.The storage account will enforce HTTPS traffic and replicate data to a paired region.
AnswerD

The template sets 'supportsHttpsTrafficOnly' to true, which enforces HTTPS for all client requests and rejects any plaintext HTTP traffic. Additionally, the 'Standard_GRS' SKU enables geo-redundant replication, storing copies in both the primary region and a paired secondary region for disaster recovery. Together, these properties guarantee secure HTTPS-only traffic and automatic data replication to the paired region, which makes this statement correct.

Why this answer

The ARM template configures the storage account with the 'supportsHttpsTrafficOnly' property set to true, which enforces HTTPS for all requests. Additionally, the 'sku.name' is set to 'Standard_GRS', which replicates data to a paired region for geo-redundancy. Therefore, option D correctly identifies both HTTPS enforcement and geo-replication to a paired region.

Exam trap

In Azure exams, candidates often confuse the ARM template properties for encryption (e.g., 'encryption.keySource') with those for network access (e.g., 'networkAcls'). Also, the distinction between storage SKU redundancy levels (LRS, GRS, RA-GRS, ZRS) is frequently tested, and many mistakenly think 'Standard_GRS' means only geo-redundancy without understanding that HTTPS enforcement is a separate property.

How to eliminate wrong answers

Option A is wrong because the template does not include any 'encryption.keySource' or 'keyvaultproperties' settings to indicate customer-managed keys from Azure Key Vault; it defaults to Microsoft-managed keys. Option B is wrong because the SKU is 'Standard_GRS', not 'Standard_LRS', so it uses geo-redundant storage, not locally redundant storage. Option C is wrong because the template lacks any 'networkAcls' or 'ipRules' properties to define a firewall rule restricting access to specific IPs.

561
MCQmedium

A company uses Azure Active Directory (Azure AD) and wants to regularly review the membership of a group that grants access to a critical application. Each member must attest their continued need for access. Which Azure AD feature should they use?

A.Azure AD Identity Governance access reviews
B.Azure AD Privileged Identity Management (PIM)
C.Azure AD Conditional Access
D.Azure AD Identity Protection
AnswerA

Access reviews in Azure AD Identity Governance are the native mechanism for recurring membership attestation. You can target an Azure AD group, application, or access package, and select reviewers—such as resource owners or the members themselves—to confirm each user still needs access. A review can be configured to recur automatically, and the completion logic can remove denied or non-responsive users from the group. This directly matches the requirement to periodically attest group membership and remediate stale access.

Why this answer

Azure AD Identity Governance access reviews enable administrators to create recurring reviews of group memberships, requiring each member to attest their continued need for access. This directly addresses the requirement for regular attestation of group membership for a critical application, as it automates the review process and ensures compliance.

Exam trap

The trap here is that candidates often confuse Privileged Identity Management (PIM) with access reviews, but PIM is for privileged roles (e.g., Global Administrator) while access reviews are for any group or application access, including non-privileged memberships.

How to eliminate wrong answers

Option B is wrong because Azure AD Privileged Identity Management (PIM) is designed for just-in-time privileged role activation and oversight, not for regular attestation of standard group membership access. Option C is wrong because Azure AD Conditional Access enforces access policies based on conditions like location or device state, but does not provide a mechanism for users to attest their need for access. Option D is wrong because Azure AD Identity Protection focuses on detecting and responding to identity risks (e.g., compromised credentials), not on periodic membership attestation.

562
Multi-Selectmedium

You are the identity security engineer for a company that uses Microsoft Entra ID. You need to reduce the risk of credential theft for administrative accounts. Which TWO controls should you implement? (Choose two.)

Select 2 answers
A.Configure a long password expiration interval of 730 days for administrator accounts.
B.Assign the Privileged Authentication Administrator role to a shared helpdesk account.
C.Require passwordless authentication methods such as FIDO2 security keys for administrators.
D.Enable self-service password reset for all administrator accounts.
E.Enable Microsoft Entra Password Protection with a custom banned password list.
AnswersC, E

Passwordless methods remove the shared secret from the sign-in process, so there is no password to phish or steal. Requiring FIDO2 or Windows Hello for Business for administrators significantly reduces credential theft risk because the credential is bound to a device and cannot be replayed.

Why this answer

Passwordless authentication removes the password as a stealable secret, and banned password lists prevent weak or predictable passwords from being set. Together they reduce the likelihood that an administrative credential can be phished, guessed, or reused, which directly addresses credential theft risk.

Exam trap

The trap here is assuming that password expiration policies or self-service password reset reduce credential theft, when they mainly address password age and recovery.

563
MCQmedium

A team wants Sentinel incidents to automatically assign to the Tier 2 queue when severity is High and the product name is Microsoft Defender for Endpoint. What should they configure?

A.A workbook with a dropdown filter
B.A watchlist containing Tier 2 users only
C.An automation rule that updates owner/status based on conditions
D.A data retention policy
AnswerC

An automation rule in Microsoft Sentinel runs when an incident is created or updated and can evaluate conditions such as severity, service, or entity prior to executing actions. Its actions include setting the incident's owner (using a user or group name) and updating its status to Active, which directly satisfies the team's requirement to automatically assign incidents. Rules can also be ordered to ensure assignment happens before other processing, and they provide a consistent, auditable method for ownership.

Why this answer

Automation rules in Microsoft Sentinel allow you to automatically assign incidents to specific owners or queues based on conditions like severity and product name. By configuring an automation rule with a condition that triggers when severity equals 'High' and the product name is 'Microsoft Defender for Endpoint', you can set the incident owner to a specific user or group (e.g., Tier 2 queue) and optionally update the status. This directly meets the requirement without manual intervention.

Exam trap

The trap here is that candidates confuse watchlists or workbooks with operational automation, thinking they can be used for real-time incident routing, when in fact they are designed for data enrichment and visualization, not for triggering actions on incidents.

How to eliminate wrong answers

Option A is wrong because a workbook with a dropdown filter is a visualization tool for querying and displaying data, not for automating incident assignment or ownership changes. Option B is wrong because a watchlist is a static list of values used for correlation or enrichment in analytics rules, not for dynamically assigning incidents to users or queues. Option D is wrong because a data retention policy controls how long log data is stored, not how incidents are routed or assigned.

564
Drag & Dropmedium

Drag and drop the steps to assign an Azure RBAC role to a user at the resource group scope into the correct order.

Drag or tap steps into the slots.

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

Why this order

IAM is used for RBAC, and you add a role assignment by selecting the role and assigning it to a user.

565
MCQhard

Your organization uses Microsoft Defender for Cloud to protect Azure SQL databases. You receive a recommendation that 'SQL databases should have vulnerability findings resolved'. You run a vulnerability assessment scan and find a high-severity finding about a missing firewall rule. How should you resolve this finding?

A.Change the SQL database auditing settings to capture all events.
B.Add a firewall rule to the SQL server allowing traffic from the required IP addresses.
C.Enable Advanced Threat Protection for Azure SQL Database.
D.Enable the 'Defender for SQL' plan on the server.
AnswerB

Add a server-level firewall rule to the Azure SQL Server with the exact start and end IP addresses or CIDR range used by the application clients. By default Azure SQL blocks all external traffic; creating this rule explicitly permits those source IPs to connect while still denying all other ranges. This action directly addresses the Defender for Cloud finding that flagged missing firewall configuration.

Why this answer

The vulnerability assessment finding about a missing firewall rule indicates that the SQL server is accessible from an overly broad range of IP addresses or lacks a necessary restriction. Adding a firewall rule to the SQL server that allows traffic only from the required IP addresses directly resolves the misconfiguration, reducing the attack surface. This aligns with the recommendation to remediate vulnerability findings by applying network access controls.

Exam trap

The trap here is that candidates often confuse vulnerability assessment findings with threat detection or auditing features, mistakenly thinking that enabling security monitoring (like ATP or Defender for SQL) will automatically fix configuration issues, when in fact the finding requires a direct network configuration change.

How to eliminate wrong answers

Option A is wrong because changing SQL database auditing settings to capture all events does not address the missing firewall rule; auditing only logs activities, it does not restrict network access. Option C is wrong because enabling Advanced Threat Protection (ATP) for Azure SQL Database provides threat detection and alerting, but it does not remediate a missing firewall rule or change network access controls. Option D is wrong because enabling the 'Defender for SQL' plan on the server activates additional security features like vulnerability assessment and threat detection, but it does not automatically add or modify firewall rules to resolve the specific finding.

566
MCQmedium

A company uses Azure AD Identity Protection and Conditional Access. A user is detected with a 'High' user risk level due to suspicious activity. The security team wants to automatically block sign-ins for this user, but only when the sign-in originates from a location that is not in the company's list of trusted IPs. They have created a Conditional Access policy targeting all users. Which configuration should they add to the policy to achieve this?

A.Add a condition for 'User risk' set to 'High', and a condition for 'Sign-in risk' set to 'High', then grant 'Block access'.
B.Add a condition for 'User risk' set to 'High' and exclude 'All trusted locations' under the 'Locations' condition, then grant 'Block access'.
C.Add a condition for 'User risk' set to 'High', and under 'Grant', select 'Require multi-factor authentication' and 'Block access'.
D.Add a condition for 'Locations' set to 'Any location' and under 'Grant', select 'Block access' for all users.
AnswerB

This is correct because it combines the specific condition—User risk High—with a location exclusion for all trusted IP ranges, ensuring the block only applies to sign-ins that originate from untrusted locations. Conditional Access evaluates the user risk condition and the location condition together, and with the grant control set to Block access, any matching sign-in is denied. This matches the requirement precisely: only high user risk accounts attempting sign-in from outside the corporate network are blocked.

Why this answer

It combines a condition for 'User risk' set to 'High' with an exclusion of 'All trusted locations' under the 'Locations' condition, then grants 'Block access'. This ensures that the block only applies when the sign-in originates from an untrusted location, meeting the requirement to automatically block sign-ins for high-risk users only from locations not in the company's trusted IP list.

Exam trap

The trap here is that candidates often confuse 'User risk' with 'Sign-in risk' or incorrectly combine 'Block access' with other grant controls, failing to realize that 'Block access' must be the sole grant control and that excluding trusted locations is the correct way to scope the policy to untrusted locations only.

How to eliminate wrong answers

Option A is wrong because it adds a condition for 'Sign-in risk' set to 'High', which is unnecessary and not required; the requirement only specifies 'User risk', and adding 'Sign-in risk' would narrow the policy to only block when both risks are high, potentially missing the intended scenario. Option C is wrong because it selects 'Require multi-factor authentication' alongside 'Block access' under Grant; 'Block access' cannot be combined with other grant controls, and MFA would not block access but instead require additional verification, which does not achieve the automatic block goal. Option D is wrong because it sets 'Locations' to 'Any location' without excluding trusted locations, and grants 'Block access' for all users; this would block all sign-ins from any location, ignoring the requirement to only block when the location is not trusted.

567
MCQmedium

You are reviewing an Azure Resource Manager template for a storage account. The exhibit shows a snippet of the template. Which statement about the template is true?

A.Encryption is disabled for the storage account.
B.The storage account will use customer-managed keys from Azure Key Vault.
C.The storage account will use Microsoft-managed keys for encryption.
D.Encryption is enabled only for blob storage.
AnswerC

The encryption.keySource value of Microsoft.Storage indicates Azure's default encryption mechanism, where Microsoft owns, stores, and rotates the AES-256 keys used to encrypt the storage account. This is the platform-managed key model, applied automatically whenever no Key Vault key is referenced. Combined with enabled: true for blob and file, the account will use Microsoft-managed keys for both services.

Why this answer

The template snippet does not include any encryption-related properties, such as `encryption.keySource` or `encryption.services`, which means the storage account will use the default Microsoft-managed keys for encryption. By default, Azure Storage encrypts all data at rest using Microsoft-managed keys, and no explicit configuration is required. Option C correctly identifies this default behavior.

Exam trap

The trap here is that candidates may assume encryption must be explicitly enabled or that the absence of encryption properties means encryption is disabled, but Azure Storage encryption is always on by default and cannot be turned off.

How to eliminate wrong answers

Option A is wrong because encryption is enabled by default for all Azure Storage accounts; the absence of encryption properties in the template does not disable encryption. Option B is wrong because customer-managed keys require explicit configuration of `encryption.keySource` as `Microsoft.Keyvault` and a reference to a Key Vault key, which is not present in the snippet. Option D is wrong because Azure Storage encryption applies to all storage services (blob, file, queue, table) by default, not just blob storage.

568
MCQeasy

You need to prevent data exfiltration from Azure Storage accounts by controlling which networks can access them. Which Azure feature should you use?

A.Azure Storage shared access signatures (SAS)
B.Azure Firewall
C.Azure Private Link
D.Azure Storage firewalls and virtual network rules
AnswerD

Azure Storage firewalls and virtual network rules allow you to define a set of virtual networks and IP address ranges that are permitted to access the storage account, and all other requests are denied. This directly controls the network origin of clients, so if an attacker outside your trusted networks tries to connect using the storage account endpoint, the request is blocked before it reaches the data. By restricting access to only trusted networks, this feature effectively prevents data exfiltration from unauthorized network locations.

Why this answer

Azure Storage firewalls and virtual network rules (Option D) are the correct choice because they allow you to restrict access to your storage account based on specific IP addresses, IP ranges, or virtual networks, effectively preventing data exfiltration by blocking unauthorized network traffic. This feature works at the network layer, enabling you to create a perimeter around your storage account that only allows trusted sources to connect, which directly addresses the requirement to control network-level access.

Exam trap

The trap here is that candidates often confuse network-level access control (storage firewalls and VNet rules) with identity-based access control (SAS tokens) or connectivity solutions (Private Link), leading them to select Azure Firewall or Private Link instead of the dedicated storage network security feature.

How to eliminate wrong answers

Option A is wrong because Azure Storage shared access signatures (SAS) provide delegated, time-limited access to storage resources at the application level, not network-level access control; they cannot restrict which networks can reach the storage account. Option B is wrong because Azure Firewall is a managed, cloud-based network security service that protects Azure Virtual Network resources, but it does not natively integrate with Azure Storage to control inbound access to storage accounts; storage firewalls and virtual network rules are the dedicated feature for this purpose. Option C is wrong because Azure Private Link enables private connectivity from a virtual network to Azure PaaS services over a private endpoint, but it does not provide granular network-level access control rules (like IP whitelisting or VNet rules) to prevent data exfiltration; it focuses on network isolation rather than access restriction.

569
MCQeasy

Refer to the exhibit. You run the command and see the output. What does the UserType 'Member' indicate?

A.The user is a service principal
B.The user is a guest user
C.The user is an administrator
D.The user is a member of the tenant
AnswerD

When the output shows UserType 'Member', it means the user account is an internal, home-directory member of the Azure AD tenant. Such users are typically created directly in that tenant or synchronized from on-premises Active Directory via Azure AD Connect, and they belong to the tenant organization rather than being invited from outside. This is precisely the correct interpretation: the command returned a user object whose directory membership type is Member, so the user is a member of the tenant.

Why this answer

The UserType 'Member' indicates that the user is a member of the tenant, meaning the user's identity is native to the Azure AD tenant and not from an external directory. This is distinct from 'Guest' (UserType = Guest), which represents external users invited via B2B collaboration. The command shown is likely Get-AzureADUser or a similar cmdlet, where the UserType property directly reflects the user's relationship to the tenant.

Exam trap

The trap here is that candidates confuse the UserType property with the user's role or administrative status, when in fact UserType only distinguishes between native tenant members and external B2B guests, not their permissions or directory roles.

How to eliminate wrong answers

Option A is wrong because a service principal is represented by a ServicePrincipal object, not a User object, and its UserType would not be 'Member'; service principals have their own object type and are not users. Option B is wrong because a guest user has UserType = 'Guest', not 'Member'; the 'Member' value explicitly indicates the user is not a guest. Option C is wrong because being an administrator is a role assignment, not a user type; a user can be a Member and have no admin roles, or be a Guest and have admin roles, so UserType does not indicate administrative status.

570
MCQmedium

An organization has deployed Azure Firewall and wants to inspect all outbound traffic from a virtual network (VNet) to the internet. The VNet already contains subnets with workloads. What is the required networking configuration to force traffic through Azure Firewall?

A.Configure a route table with a default route (0.0.0.0/0) pointing to the Azure Firewall private IP and associate it with the subnets.
B.Add a Network Security Group (NSG) rule that allows all outbound traffic and associate it with the subnets.
C.Deploy an Application Gateway with Web Application Firewall (WAF) in front of the subnets.
D.Enable Azure DDoS Protection Standard on the VNet.
AnswerA

A User Defined Route (UDR) with address prefix 0.0.0.0/0 and next hop type 'VirtualAppliance' set to the Azure Firewall's private IP must be associated with each subnet requiring outbound inspection. This custom route overrides Azure's default system route for internet-bound traffic, forcing every egress packet to be forwarded to the firewall for centralized filtering, logging, and NAT. Without this route, the VNet's implicit 0.0.0.0/0 route sends traffic directly to the internet via its default outbound public IP, bypassing the firewall.

Why this answer

Azure Firewall requires a route table with a default route (0.0.0.0/0) that has the Azure Firewall's private IP as the next hop, associated with each subnet whose traffic must be inspected. This forces all outbound traffic from those subnets to be routed through the firewall, enabling inspection and logging. Without this explicit route, traffic would use the default system route and bypass the firewall.

Exam trap

The trap here is that candidates often assume NSG rules or DDoS protection can redirect traffic, but only a user-defined route (UDR) with a next hop of the firewall's private IP can force traffic through Azure Firewall.

How to eliminate wrong answers

Option B is wrong because an NSG rule allowing all outbound traffic does not force traffic through Azure Firewall; NSGs filter traffic at the subnet or NIC level but do not change the routing path. Option C is wrong because Application Gateway with WAF is a layer-7 load balancer and web application firewall for inbound HTTP/S traffic, not designed to inspect or route all outbound internet traffic. Option D is wrong because Azure DDoS Protection Standard provides mitigation against volumetric DDoS attacks but does not alter routing or force traffic through a firewall.

571
MCQmedium

You need to allow inbound HTTP traffic from the internet to a specific VM in a VNet. The VM is in a subnet with an NSG. What is the correct way to configure access?

A.Add a rule in Azure Firewall to allow HTTP traffic to the VM.
B.Enable Azure DDoS Protection on the VNet.
C.Configure Azure Traffic Manager to route traffic to the VM.
D.Add an inbound security rule in the NSG to allow HTTP traffic.
AnswerD

An NSG is a stateful, Layer-3/4 filter that can be associated with a VM's NIC or its subnet to control inbound and outbound traffic. Adding an inbound security rule with source 'Internet', destination port 80, protocol TCP, and action 'Allow' will permit HTTP traffic to reach the VM, provided the VM has a public IP or is behind a load balancer with proper port forwarding. This is the standard, least-privilege solution for allowing a single port to a VM from the internet.

Why this answer

Network Security Groups (NSGs) operate at the subnet or NIC level and act as a stateful firewall for traffic entering or leaving Azure resources. To allow inbound HTTP (TCP port 80) traffic from the internet to a specific VM, you must add an inbound security rule to the NSG associated with the VM's subnet or NIC, specifying the source as 'Internet', destination port 80, and protocol TCP. This is the direct and correct method for controlling traffic to a VM within a VNet.

Exam trap

The trap here is that candidates often confuse Azure Firewall (a centralized, cross-subnet service) with NSGs (a subnet/NIC-level firewall) and incorrectly assume a firewall is required for inbound internet traffic, when in fact NSGs are the correct and simpler solution for allowing HTTP to a specific VM.

How to eliminate wrong answers

Option A is wrong because Azure Firewall is a managed, centralized firewall service used for controlling outbound and inter-VNet traffic, not for allowing inbound internet traffic to a single VM; NSGs are the appropriate boundary for subnet/NIC-level inbound rules. Option B is wrong because Azure DDoS Protection provides mitigation against distributed denial-of-service attacks but does not allow or deny specific application traffic like HTTP; it is a security enhancement, not an access control mechanism. Option C is wrong because Azure Traffic Manager is a DNS-based traffic load balancer that routes users to endpoints based on routing methods, but it does not open ports or allow traffic through the NSG; the NSG must still permit the traffic.

572
MCQeasy

Your company uses Microsoft Defender for Cloud's regulatory compliance dashboard to track compliance with the PCI DSS standard. You have enabled the PCI DSS initiative on the management group. The dashboard shows that some controls are 'Not started' even though you have implemented the required security configurations. You suspect that the assessment might not be running correctly. You need to ensure that the compliance assessments are triggered for all resources. The environment consists of: - 3 subscriptions under a management group. - All subscriptions have Defender for Cloud enabled with the CSPM plan. - The PCI DSS initiative was assigned at the management group level. - Some resources are in regions that do not support certain policy effects. What is the most likely reason for the 'Not started' status?

A.The compliance dashboard only displays results if you manually run an assessment.
B.The PCI DSS initiative must be assigned to each subscription individually.
C.The Defender Cloud Security Posture Management (CSPM) plan is not enabled on all subscriptions.
D.Some policies in the PCI DSS initiative use effects that are not supported in certain regions, causing the assessment to not run.
AnswerD

Regulatory compliance initiatives like PCI DSS contain a mix of policy effects, including AuditIfNotExists and DeployIfNotExists, some of which depend on resource providers or resource types that may not be available in every Azure region. When a policy's effect cannot run in a given region—either because the needed resource type is unavailable or the effect is unsupported for that region's policy evaluation—the policy engine skips the evaluation, leaving the resource's compliance status as 'Not started' rather than 'Compliant' or 'Non-Compliant'. This regional limitation directly explains the dashboard showing 'Not started' while the initiative is correctly assigned and the CSPM plan is enabled.

Why this answer

The correct answer is D: some policies in the PCI DSS initiative use effects that are not supported in certain regions, causing the assessment to not run. Azure Policy effects such as AuditIfNotExists or DeployIfNotExists depend on regional support and resource provider capabilities; if an effect is unsupported in a resource's region, the policy assignment cannot evaluate that resource, so the control remains 'Not started' rather than showing a compliant or non-compliant result. This matches the scenario's hint that some resources are in regions that do not support certain policy effects.

Option A is wrong because Defender for Cloud continuously evaluates assigned initiatives and does not require manual assessment runs. Option B is wrong because an initiative assigned at the management group level is inherited by all subscriptions in that group. Option C is wrong because the scenario states Defender for Cloud with the CSPM plan is already enabled on all subscriptions.

Exam trap

A common trap is assuming that enabling the CSPM plan is enough, or that management group assignments always work without issue. The real pitfall is regional support for policy effects.

573
MCQeasy

A company develops a web application that runs on Azure App Service. The application needs to access Azure Key Vault to retrieve secrets. The security team wants to avoid using service principals or connection strings. Which identity should they assign to the App Service to authenticate to Key Vault?

A.System-assigned managed identity
B.User-assigned managed identity
C.Azure AD application registration with a client secret
D.Azure AD service principal with certificate-based authentication
AnswerA

A system-assigned managed identity is automatically provisioned for the App Service and is tied to the resource's lifecycle. It can be granted access to Key Vault via RBAC or access policies, and the application code uses Azure SDK to obtain tokens without handling secrets.

Why this answer

A system-assigned managed identity is the correct choice because it provides an automatically managed identity in Azure AD, directly tied to the App Service resource, without requiring any credentials to be stored or rotated. This allows the App Service to authenticate to Key Vault using Azure AD tokens, eliminating the need for service principals or connection strings. The security team's requirement to avoid service principals or connection strings is fully met, as the identity is managed entirely by Azure.

Exam trap

The trap here is that candidates often confuse user-assigned managed identities (Option B) as the only managed identity option, overlooking that system-assigned managed identities are simpler and fully meet the requirement to avoid service principals or connection strings without additional resource management.

How to eliminate wrong answers

Option B is wrong because a user-assigned managed identity, while also avoiding service principals and connection strings, is a standalone resource that must be explicitly created and assigned to the App Service, adding management overhead that the security team's requirement to avoid service principals or connection strings does not necessitate; the simpler system-assigned identity suffices. Option C is wrong because an Azure AD application registration with a client secret is a form of service principal that requires storing and rotating a secret, directly violating the security team's directive to avoid service principals or connection strings. Option D is wrong because an Azure AD service principal with certificate-based authentication is still a service principal, requiring certificate management and lifecycle, which contradicts the requirement to avoid service principals entirely.

574
MCQmedium

A company has an Azure virtual network with a subnet that contains virtual machines. They have deployed Azure Firewall in a hub VNet and peered the spoke VNet to the hub. They have configured a route table on the spoke subnet with a default route (0.0.0.0/0) pointing to the Azure Firewall's private IP as the next hop. However, traffic from the VMs is still going directly to the internet. What is the most likely cause?

A.The route table is not associated with the subnet.
B.The Azure Firewall's private IP is not configured as the next hop; it should be the public IP.
C.The VNet peering is not configured correctly.
D.The Azure Firewall has a default route that bypasses itself.
AnswerA

Correct. A route table only influences traffic after it is associated with a subnet. Without that association, the subnet's effective routes remain the system defaults, so internet-bound traffic bypasses the Azure Firewall and egresses directly via the virtual NIC's default SNAT. The forced-tunneling UDR must be attached to the specific spoke subnet to redirect its default route to the firewall's private IP.

Why this answer

The most likely cause is that the route table containing the default route (0.0.0.0/0) with the Azure Firewall's private IP as the next hop has not been associated with the spoke subnet. Without this association, the subnet's VMs will use the system default route, which sends internet-bound traffic directly out via the Azure default gateway (0.0.0.0/0, next hop type Internet), bypassing the firewall entirely.

Exam trap

The trap here is that candidates often assume that simply creating a route table with a default route to the firewall is sufficient, but they overlook the critical step of associating that route table with the subnet, which is a separate action in the Azure portal or via PowerShell/CLI.

How to eliminate wrong answers

Option B is wrong because the next hop for forced tunneling through Azure Firewall must be the firewall's private IP address, not its public IP; using a public IP would cause asymmetric routing and break the firewall's stateful inspection. Option C is wrong because VNet peering is correctly configured (the spoke is peered to the hub), and peering alone does not redirect traffic to the firewall—a route table with the firewall as next hop is required. Option D is wrong because Azure Firewall does not have a default route that bypasses itself; it uses the effective routes from its subnet, and a default route on the firewall would point to the internet via its public IP, which is normal and does not cause traffic to bypass the firewall.

575
Multi-Selectmedium

A managed identity is used by an Azure Function to access Key Vault. Which two configurations are required?

Select 2 answers
A.A client secret stored in the function app settings
B.A system-assigned or user-assigned managed identity enabled on the function app
C.A public IP address on the function app
D.Key Vault permissions granted to that managed identity
AnswersB, D

Enabling a system-assigned or user-assigned managed identity on the function app creates an Azure AD identity automatically managed by Azure and tied to the app's lifecycle. The function can then request an access token from the Azure Instance Metadata Service (IMDS) endpoint without any stored secrets, which is exactly the mechanism required to securely authenticate to an Azure key vault.

Why this answer

A managed identity (either system-assigned or user-assigned) provides an Azure AD-authenticated identity for the function app, eliminating the need for credentials like client secrets. This identity is used to obtain an Azure AD access token for authenticating to Key Vault. Option D is also required because the managed identity must be granted explicit Key Vault permissions (e.g., via an access policy or RBAC role) to read secrets; without these permissions, token-based authentication will fail with a 403 Forbidden error.

Exam trap

The trap here is that candidates often assume a client secret (Option A) is required for any Azure AD authentication, failing to recognize that managed identities provide a passwordless, credential-free authentication mechanism via Azure AD tokens.

576
MCQhard

You have an Azure SQL Database that stores credit card numbers. You need to encrypt the column containing the credit card numbers so that only authorized applications can decrypt the data. The database administrator should not be able to view the plaintext data. Which feature should you use?

A.Transparent Data Encryption (TDE)
B.Column-level encryption using SQL Server built-in functions
C.Dynamic Data Masking
D.Always Encrypted with secure enclaves
AnswerD

Always Encrypted with secure enclaves encrypts sensitive columns such that the database engine never sees the plaintext. The column encryption key is protected by a column master key stored outside SQL Server, so a DBA with full server access only sees ciphertext. An enclave allows the engine to perform computations on encrypted values by loading the keys into a protected memory region, but the DBA cannot access that enclave or the keys. This is the only option that truly prevents a DBA from reading the credit card numbers.

Why this answer

Always Encrypted with secure enclaves (Option D) is correct because it ensures that credit card numbers are encrypted at rest and in memory, and only client applications with the column encryption key can decrypt the data. The database administrator (DBA) cannot access the plaintext because the encryption keys are never revealed to SQL Server or Azure SQL Database, and secure enclaves allow rich computations (e.g., equality, pattern matching) on encrypted data without exposing the plaintext to the database engine.

Exam trap

The trap here is that candidates often confuse Dynamic Data Masking (which only hides data from query results but does not encrypt it) with Always Encrypted, or assume TDE provides column-level protection, when in fact TDE does not prevent the DBA from viewing plaintext data.

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 the DBA or from being viewed in plaintext by authorized users—the DBA can still query and see the credit card numbers. Option B is wrong because column-level encryption using SQL Server built-in functions (e.g., ENCRYPTBYPASSPHRASE) requires the encryption key to be stored in the database or managed by the DBA, allowing the DBA to access the plaintext if they have the key. Option C is wrong because Dynamic Data Masking only obfuscates data in query results for unauthorized users, but the underlying data remains unencrypted in storage and can be read by the DBA or anyone with direct database access.

577
MCQmedium

A security team has a list of known malicious IP addresses from an external threat intelligence feed in CSV format. They want to import this list into Microsoft Sentinel and use it in analytics rules to detect incoming attacks. Which feature should they use?

A.Watchlists
B.Threat intelligence indicators
C.Bookmark
D.User and Entity Behavior Analytics (UEBA)
AnswerA

Watchlists are the correct choice because Microsoft Sentinel's Watchlists feature allows you to import CSV files directly and store them in your workspace, making them queryable via the _GetWatchlist function. You can create a watchlist from a CSV containing your known malicious IP addresses, then reference it in analytics rules with KQL to match against incoming events, enabling custom threat intelligence without a formal TI feed.

Why this answer

Watchlists in Microsoft Sentinel allow you to import external data sources, such as CSV files containing known malicious IP addresses, and use them directly in analytics rules for detection. This feature is designed for lightweight, custom threat intelligence that doesn't require the full threat intelligence indicator (TI) lifecycle, making it ideal for ad-hoc lists from CSV feeds.

Exam trap

The trap here is confusing Watchlists with Threat intelligence indicators, as both can handle IP lists, but TI indicators require a formal TI platform integration and STIX/TAXII protocols, whereas Watchlists are the correct choice for simple CSV imports without additional infrastructure.

How to eliminate wrong answers

Option B is wrong because Threat intelligence indicators are used for structured, normalized threat data (e.g., STIX format) and require integration with a TI platform or API, not direct CSV import. Option C is wrong because Bookmarks are used to preserve specific search results or investigation states for later review, not to import external threat data for rule-based detection. Option D is wrong because User and Entity Behavior Analytics (UEBA) is a behavioral analytics feature that profiles user and entity activities to detect anomalies, not a mechanism for importing static IP lists.

578
MCQmedium

Your organization uses Azure Virtual Network Manager (AVNM) to manage network groups. You need to ensure that all virtual networks in a network group are automatically peered with a hub VNet. Which AVNM configuration should you use?

A.Create a connectivity configuration with Hub and Spoke topology
B.Create a network group and assign it to a connectivity configuration
C.Create a security admin configuration
D.Use Azure Policy to enforce peering
AnswerA

In Azure Virtual Network Manager, a connectivity configuration defines the actual network topology you want to establish. When you select Hub and Spoke, AVNM automatically creates VNet peering between the hub VNet and all spoke VNets assigned to that configuration, eliminating the need for manual peering. This configuration also manages transitive routing, so spokes can communicate through the hub without requiring individual peerings between every spoke. Thus, creating a connectivity configuration with hub-and-spoke topology is the correct and direct mechanism to automate peering in AVNM.

Why this answer

To automatically peer all virtual networks in a network group with a hub VNet, you need a connectivity configuration with Hub and Spoke topology. AVNM's connectivity configuration defines the network topology (e.g., hub-and-spoke or mesh) and automatically creates the necessary VNet peering connections between the hub and all spoke VNets in the assigned network group, without manual peering setup.

Exam trap

The trap here is that candidates confuse a network group (a logical container) with a connectivity configuration (which defines the actual topology and peering), leading them to select Option B without realizing the configuration type is required.

How to eliminate wrong answers

Option B is wrong because a network group alone is just a logical grouping of VNets; it does not define any connectivity or peering. Assigning it to a connectivity configuration is necessary, but the configuration itself must specify the topology (hub-and-spoke) to enable peering. Option C is wrong because a security admin configuration is used to enforce security rules (e.g., blocking traffic or applying firewall policies), not to create VNet peering.

Option D is wrong because Azure Policy can enforce compliance (e.g., requiring a specific tag or resource location) but cannot directly create or manage VNet peering; peering must be configured via AVNM connectivity configurations or manually.

579
MCQmedium

A security operations team uses Microsoft Sentinel to centralize security monitoring across their hybrid environment. They need to ingest AWS CloudTrail logs from an Amazon Web Services account to detect suspicious activities in their AWS environment. Which data connector should they configure in Microsoft Sentinel?

A.Azure Activity log connector
B.AWS CloudTrail connector
C.Syslog connector
D.Common Event Format (CEF) connector
AnswerB

The AWS CloudTrail connector is the purpose-built Data Connector in Microsoft Sentinel that ingests CloudTrail management and data events by reading a trail's Amazon S3 bucket, with optional SQS queue delivery for near real-time event collection. It requires you to create an AWS IAM role (with a cross-account or same-account trust) and configure the trail to forward logs to Sentinel, after which the connector normalizes AWS logs into the AWSCloudTrail table. This makes it the only option among these that directly supports the centralization of AWS security logs into Sentinel.

Why this answer

The AWS CloudTrail connector is the correct data connector for ingesting AWS CloudTrail logs into Microsoft Sentinel. It requires configuring an S3 bucket in AWS to receive CloudTrail logs and then connecting that bucket to Sentinel via the connector, enabling the detection of suspicious activities such as unauthorized API calls or privilege escalations in the AWS environment.

Exam trap

The trap here is that candidates may confuse the Azure Activity log connector with a generic cloud activity log connector, but it only works for Azure, not for AWS CloudTrail.

How to eliminate wrong answers

Option A is wrong because the Azure Activity log connector is designed to ingest logs from Azure subscription-level events, not from external cloud providers like AWS. Option C is wrong because the Syslog connector is used to collect logs from on-premises or network devices using the syslog protocol (UDP/TCP), not from AWS CloudTrail. Option D is wrong because the Common Event Format (CEF) connector is used to ingest logs from security appliances that forward CEF-formatted syslog messages, such as firewalls or IDS/IPS, not from AWS CloudTrail.

580
MCQmedium

A company uses Azure Front Door to accelerate and secure its public web application. The security team wants to limit the number of requests from a single client IP address to 100 per minute to prevent a single user from overwhelming the backend. Which configuration should they add to the Web Application Firewall (WAF) policy associated with the Front Door?

A.Add a custom rule with a rate limit condition.
B.Enable a managed rule set for the WAF policy.
C.Configure a bot protection rule set.
D.Set a geolocation filter to block all traffic except from allowed countries.
AnswerA

Azure Front Door's WAF supports custom rules with a rate limit condition, which tracks the number of requests from a client IP address within a defined time window (e.g., 60 seconds). Once the threshold is exceeded, you can specify an action such as Block to immediately drop subsequent requests until the window resets. This is the only option that directly implements per-IP request throttling to protect against aggressive scraping or brute-force attempts, making it the correct choice for the stated requirement.

Why this answer

Azure Front Door's WAF supports custom rate limit rules that can restrict the number of requests from a single client IP address within a specified time window. By creating a custom rule with a rate limit condition set to 100 requests per minute, the security team can prevent a single client from overwhelming the backend while allowing legitimate traffic. This is the only option that directly addresses the requirement to limit requests per client IP.

Exam trap

The trap here is that candidates often confuse rate limiting with bot protection or managed rule sets, assuming that enabling a managed rule set or bot protection will automatically handle request throttling, but neither provides per-IP rate limiting—they focus on attack signatures and bot detection, respectively.

How to eliminate wrong answers

Option B is wrong because enabling a managed rule set (e.g., OWASP or Microsoft default rule set) provides pre-configured signatures to block common web attacks like SQL injection or XSS, but it does not enforce per-IP request rate limits. Option C is wrong because bot protection rule sets are designed to identify and mitigate automated bot traffic (e.g., by categorizing known bots or detecting anomalies), not to cap the number of requests from a single client IP. Option D is wrong because a geolocation filter restricts traffic based on geographic origin (e.g., blocking all countries except allowed ones), which does not limit the request rate from any specific client IP.

581
MCQeasy

You need to securely store secrets, such as connection strings and API keys, for use by an Azure Functions app. The solution must automatically rotate the secrets and audit access. What should you use?

A.Azure Key Vault
B.Azure Blob Storage with encryption
C.Managed Identity
D.Application settings in the function app configuration
AnswerA

Azure Key Vault is the correct choice because it is a purpose-built secret management service that stores connection strings and other secrets encrypted at rest, with granular access policies integrated with Azure AD. It provides native secret versioning and rotation, full audit logging via diagnostics, and soft-delete/purge protection to prevent accidental or malicious loss. Applications can securely retrieve secrets at runtime using service principals or Managed Identity, eliminating the need to embed credentials in code or configuration.

Why this answer

Azure Key Vault is the correct choice because it provides a centralized, secure store for secrets like connection strings and API keys, with built-in support for automatic rotation via integration with Azure Key Vault references in Azure Functions and access auditing through diagnostic logs and Azure Monitor. This meets the requirements of secure storage, automated secret rotation, and audit trail generation.

Exam trap

The trap here is that candidates often confuse Managed Identity with a secret storage solution, but Managed Identity is an authentication mechanism, not a store for secrets like connection strings or API keys.

How to eliminate wrong answers

Option B is wrong because Azure Blob Storage with encryption only provides at-rest encryption for stored data, but lacks native secret rotation capabilities and does not offer granular access auditing for secret retrieval. Option C is wrong because Managed Identity provides an identity for the function app to authenticate to Azure services without storing credentials, but it does not store or rotate secrets like connection strings or API keys. Option D is wrong because application settings in the function app configuration store secrets in plain text (though encrypted at rest by Azure App Service), but they cannot be automatically rotated and do not provide detailed access auditing for secret usage.

582
MCQhard

Your organization has a Microsoft Entra ID tenant and uses Azure Virtual Desktop (AVD). You need to ensure that AVD session hosts in a virtual network can access on-premises resources securely without exposing the session hosts to the internet. The on-premises network is connected to Azure via ExpressRoute. All AVD traffic should be routed through the ExpressRoute connection. You have already deployed a reverse connect transport for AVD. What else should you configure to meet the requirements?

A.Configure VNet peering between the AVD virtual network and the on-premises network.
B.Add a user-defined route (UDR) in the AVD subnet for the on-premises IP prefixes with next hop to the ExpressRoute gateway.
C.Disable reverse connect transport and allow inbound RDP traffic from the internet.
D.Create a private endpoint for the AVD control plane.
AnswerB

A user-defined route (UDR) associated with the AVD subnet can explicitly direct traffic destined for the on-premises IP prefixes to the ExpressRoute virtual network gateway by setting the next hop type to 'VirtualNetworkGateway'. This forces all matching traffic from session hosts to traverse the ExpressRoute connection instead of default internet routing, ensuring secure and predictable connectivity to on-premises resources. Without such a route, traffic might bypass the gateway or use an unintended path, depending on the existing route table.

Why this answer

Adding a user-defined route (UDR) in the AVD subnet for on-premises IP prefixes with the next hop set to the ExpressRoute gateway forces all traffic destined for on-premises resources to traverse the ExpressRoute connection. This ensures secure, private connectivity without exposing session hosts to the internet, while the reverse connect transport already handles AVD control plane traffic securely.

Exam trap

The trap here is that candidates often confuse VNet peering (which connects VNets within Azure) with hybrid connectivity to on-premises, or mistakenly think a private endpoint for the control plane alone satisfies all routing requirements for session host traffic.

How to eliminate wrong answers

Option A is wrong because VNet peering connects Azure virtual networks, not an Azure VNet to an on-premises network; on-premises connectivity requires ExpressRoute or VPN, not peering. Option C is wrong because disabling reverse connect transport and allowing inbound RDP from the internet would expose session hosts to the internet, violating the requirement to keep them secure and not internet-facing. Option D is wrong because a private endpoint for the AVD control plane secures the control plane connection but does not route session host traffic to on-premises resources; it does not replace the need for a UDR to direct traffic through ExpressRoute.

583
MCQhard

A custom Azure role should allow operators to restart virtual machines but not delete them or change networking. Which permission design is most appropriate?

A.Assign Contributor at the resource group scope
B.Create a custom role with Microsoft.Compute/virtualMachines/restart/action and required read permissions at the narrowest scope
C.Assign Virtual Machine Contributor at subscription scope
D.Assign Reader and ask operators to use Run Command
AnswerB

This is the correct approach because a custom role definition containing exactly Microsoft.Compute/virtualMachines/restart/action and Microsoft.Compute/virtualMachines/read provides only the control-plane action needed to restart a VM and the read permission required for the resource to be displayed and identified in Azure. By then assigning this custom role at the narrowest scope, such as the specific virtual machine resource, you guarantee operators cannot affect any other VM or resource. This satisfies the stated requirement while adhering to least privilege and is the most direct, security-focused solution.

Why this answer

It grants the specific 'restart/action' permission on virtual machines while excluding destructive actions like delete or network changes. Custom roles in Azure RBAC allow fine-grained control by including only the required data actions and read permissions, ensuring operators can restart VMs without the ability to delete them or modify networking.

Exam trap

The trap here is that candidates often confuse built-in roles like Contributor or Virtual Machine Contributor with the ability to restrict actions, not realizing these roles include delete and network write permissions that exceed the narrow restart-only requirement.

How to eliminate wrong answers

Option A is wrong because the Contributor role at any scope includes full management rights, allowing deletion and network changes, which violates the requirement. Option C is wrong because Virtual Machine Contributor at subscription scope includes permissions to delete VMs and modify networking (e.g., Microsoft.Network/*), exceeding the allowed actions. Option D is wrong because Reader only provides read access and does not include the restart action; Run Command is a separate feature that requires additional permissions and does not grant the restart capability.

584
MCQmedium

A security engineer connects Azure virtual machines to Microsoft Defender for Cloud. The team wants vulnerability findings without installing a vulnerability scanner extension on each VM. Which capability should be enabled?

A.Agentless vulnerability assessment for machines in Defender for Servers
B.Microsoft Sentinel User and Entity Behavior Analytics
C.Azure Firewall threat intelligence mode
D.Microsoft Entra Identity Protection sign-in risk
AnswerA

Agentless vulnerability assessment in Defender for Servers scans Azure VM operating system and installed software against the Microsoft Defender Vulnerability Management knowledge base without deploying any agent or extension on the machine. It leverages Azure-native metadata and managed disk snapshots to identify missing security updates and misconfigurations, directly satisfying the requirement to find vulnerabilities without agent installation. This makes it the correct solution for the scenario.

Why this answer

Agentless vulnerability assessment for machines in Defender for Servers is the correct capability because it uses Microsoft Defender for Cloud's built-in scanning engine to assess VMs for vulnerabilities without requiring any agent or extension installation. This feature leverages the VM's existing configuration and cloud APIs to perform scans, meeting the team's requirement to avoid installing a vulnerability scanner extension on each VM.

Exam trap

The trap here is that candidates often assume vulnerability scanning always requires an agent or extension, but Microsoft Defender for Cloud offers an agentless option that uses cloud-native APIs and OS-level data to perform assessments without any local software.

How to eliminate wrong answers

Option B is wrong because Microsoft Sentinel User and Entity Behavior Analytics (UEBA) is a security analytics feature that detects anomalous user and entity behavior, not a vulnerability assessment tool for VMs. Option C is wrong because Azure Firewall threat intelligence mode filters traffic based on known malicious IPs and domains, but it does not scan VMs for vulnerabilities. Option D is wrong because Microsoft Entra Identity Protection sign-in risk evaluates sign-in risks for user identities, not vulnerabilities on Azure virtual machines.

585
MCQeasy

A security team uses Microsoft Defender for Cloud to improve their security posture across multiple subscriptions. They want to quickly identify which security recommendations have the highest potential to improve their security score if remediated. Which dashboard or feature should they use?

A.Regulatory Compliance dashboard
B.Security Alerts dashboard
C.Secure Score dashboard
D.Inventory dashboard
AnswerC

The Secure Score dashboard is the correct location because it is built around the secure score calculation and assigns a concrete score increase to every recommendation in the Microsoft cloud security benchmark. Each recommendation shows 'Potential score increase' alongside the number of affected resources and health status, letting teams compare high-impact controls like enabling MFA against lower-priority hardening steps. This direct linkage between remediation actions and numeric score gain is exactly the prioritization information the security team needs.

Why this answer

The Secure Score dashboard in Microsoft Defender for Cloud is specifically designed to show security recommendations ranked by their potential impact on the overall security score. Each recommendation includes a 'score impact' value, allowing the team to prioritize remediation actions that will most effectively improve their security posture across multiple subscriptions.

Exam trap

The trap here is that candidates may confuse the Secure Score dashboard with the Regulatory Compliance dashboard, thinking compliance improvements always correlate with security score gains, but the Secure Score dashboard is the only tool that explicitly quantifies the score impact of each recommendation.

How to eliminate wrong answers

Option A is wrong because the Regulatory Compliance dashboard focuses on compliance with standards like ISO 27001 or SOC 2, not on prioritizing recommendations for score improvement. Option B is wrong because the Security Alerts dashboard displays active threats and incidents, not recommendations for proactive security hardening. Option D is wrong because the Inventory dashboard provides a list of resources and their configurations, but does not rank recommendations by score impact.

586
MCQeasy

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

A.Microsoft Purview Information Protection
B.Conditional Access App Control
C.Cloud App Discovery
D.OAuth app policies
AnswerB

Conditional Access App Control, part of Microsoft Defender for Cloud Apps, integrates with Microsoft Entra ID Conditional Access to reroute user sessions through a reverse proxy, enabling real-time monitoring and control. It analyzes signals such as user behavior, device compliance, and location to enforce granular actions like blocking downloads, restricting uploads, or requiring step-up authentication during the session. This precisely matches the requirement for session-level access control based on behavior and device health, making it the correct solution.

Why this answer

Conditional Access App Control (CAAC) is a feature of Microsoft Defender for Cloud Apps that integrates with Microsoft Entra ID Conditional Access policies to monitor and control access to cloud applications in real time. It enforces access controls based on user behavior (e.g., risky sign-ins) and device health (e.g., compliance status from Intune), allowing actions like blocking downloads or requiring session monitoring. This directly meets the requirement to monitor and control access based on user behavior and device health.

Exam trap

The trap here is that candidates often confuse Cloud App Discovery (which only identifies apps in use) with Conditional Access App Control (which enforces real-time access policies based on user behavior and device health), leading them to select Option C incorrectly.

How to eliminate wrong answers

Option A is wrong because Microsoft Purview Information Protection focuses on classifying, labeling, and protecting sensitive data (e.g., encryption, rights management), not on monitoring or controlling access based on user behavior or device health. Option C is wrong because Cloud App Discovery is a feature that identifies shadow IT by discovering cloud apps in use across the organization, but it does not provide real-time access control or session monitoring based on user behavior or device health. Option D is wrong because OAuth app policies in Defender for Cloud Apps govern permissions granted to third-party OAuth apps (e.g., revoking or approving app consent), not user behavior or device health-based access control.

587
MCQmedium

Your company has deployed Azure Kubernetes Service (AKS) in a virtual network. The AKS cluster needs to pull images from a private Azure Container Registry (ACR) that has a private endpoint configured. The virtual network where AKS is deployed is peered to the ACR's virtual network. You have configured the AKS cluster to use managed identity for authentication to ACR. However, the AKS cluster is unable to pull images from the ACR. You need to resolve the connectivity issue without exposing the ACR to the internet. What should you do?

A.Link the private DNS zone of the ACR private endpoint to the AKS virtual network.
B.Update the AKS cluster's DNS server to use a custom DNS that can resolve the private endpoint.
C.Delete the private endpoint and configure ACR firewall rules to allow the AKS subnet.
D.Recreate the AKS cluster with a different managed identity that has ACR pull permissions.
AnswerA

Linking the private DNS zone of the ACR's private endpoint to the AKS virtual network is the required fix. This DNS link enables Azure's DNS resolution to map the ACR's private endpoint FQDN to the private IP address inside the AKS VNet, allowing the kubelet to reach the registry over the private endpoint. Without this link, AKS nodes will attempt to resolve the ACR login server to its public IP, which is blocked when public access is disabled. This is the standard, supported method for private ACR connectivity to AKS.

Why this answer

The AKS cluster cannot pull images from the private ACR because the private endpoint's DNS resolution is not propagated to the AKS virtual network. By linking the private DNS zone of the ACR private endpoint to the AKS virtual network, the AKS nodes can resolve the ACR's private FQDN to the private IP address of the endpoint, enabling connectivity without exposing the ACR to the internet.

Exam trap

The trap here is that candidates often assume peering alone provides full connectivity, but they overlook that private endpoint DNS resolution requires explicit linking of the private DNS zone to the peered virtual network.

How to eliminate wrong answers

Option B is wrong because updating the AKS cluster's DNS server to a custom DNS that can resolve the private endpoint is unnecessary and may break other DNS resolutions; the correct approach is to link the private DNS zone to the AKS virtual network, which automatically handles resolution via Azure's DNS infrastructure. Option C is wrong because deleting the private endpoint and configuring ACR firewall rules would expose the ACR to the internet (even if restricted to the AKS subnet), violating the requirement to keep the ACR private. Option D is wrong because the managed identity already has ACR pull permissions (as stated), and recreating the cluster with a different identity does not address the DNS resolution or network connectivity issue.

588
MCQeasy

A security team needs to analyze network traffic to and from Azure virtual machines to investigate a potential security incident. They want to capture information such as source IP, destination IP, port, and protocol. Which Azure service should they enable on the network security groups (NSGs) associated with the virtual machine subnets?

A.Network Watcher NSG flow logs
B.Azure Monitor logs
C.Traffic Analytics
D.Azure Firewall logs
AnswerA

NSG flow logs are the definitive source for IP-level traffic to/from VMs because they record the five-tuple (source IP, destination IP, source port, destination port, protocol) and the allow/deny action for every flow tested against the NSG. Unlike broad resource logs, these logs are specifically designed to answer 'who talked to whom' at the network layer, making them indispensable for security investigations. They capture both direction and state, so the team can trace the exact packets that were permitted or refused.

Why this answer

Network Watcher NSG flow logs capture IP traffic flowing through Network Security Groups, recording source IP, destination IP, port, and protocol for each flow. This directly meets the requirement to analyze network traffic to and from Azure VMs for security incident investigation.

Exam trap

The trap here is that candidates confuse Traffic Analytics (a visualization/analysis layer) with the underlying data capture mechanism (NSG flow logs), or mistakenly think Azure Monitor logs or Azure Firewall logs provide the same subnet-level flow data without additional configuration.

How to eliminate wrong answers

Option B is wrong because Azure Monitor logs is a general log analytics service that ingests data from various sources, but it does not natively capture per-flow network traffic details like source/destination IP and port from NSGs without NSG flow logs being enabled first. Option C is wrong because Traffic Analytics is a solution that processes NSG flow logs to provide visualizations and insights; it is not the underlying data capture mechanism and requires NSG flow logs to be enabled. Option D is wrong because Azure Firewall logs capture traffic that passes through Azure Firewall, not traffic filtered by NSGs on subnets; NSG flow logs are the correct service for subnet-level traffic analysis.

589
MCQeasy

Your organization uses Microsoft Defender for Cloud to protect Azure resources. You need to ensure that storage accounts are only accessible via HTTPS. What should you configure?

A.Configure a storage account firewall to block HTTP
B.Use a private endpoint for the storage account
C.Enable 'Secure transfer required' in the storage account's configuration
D.Create an Azure Policy to audit storage accounts that do not require secure transfer
AnswerC

Enabling 'Secure transfer required' (the supportsHttpsTrafficOnly property) makes Azure Storage reject any request sent over HTTP, including requests via the REST API, Azure SDKs, and file shares, and returns an error requiring the client to use HTTPS. It forces all data-plane traffic to be encrypted in transit and can be combined with a minimum TLS version for further control. This is the account-level control that directly implements the requirement to disallow insecure HTTP.

Why this answer

Enabling 'Secure transfer required' on a storage account enforces HTTPS for all requests to the storage account, rejecting any HTTP traffic. This setting ensures that data in transit is encrypted using TLS, which aligns with the requirement to only allow HTTPS access.

Exam trap

The trap here is that candidates often confuse network-level controls (firewall, private endpoint) with protocol-level enforcement, mistakenly thinking they can block HTTP when they only restrict network access or provide private connectivity.

How to eliminate wrong answers

Option A is wrong because a storage account firewall controls network access based on IP addresses or virtual networks, not the protocol (HTTP vs. HTTPS); it cannot block HTTP traffic specifically. Option B is wrong because a private endpoint provides a private IP address for the storage account within a virtual network, but it does not enforce HTTPS; it still allows HTTP traffic unless combined with other settings.

Option D is wrong because an Azure Policy can audit or enforce compliance, but it does not directly configure the storage account to require HTTPS; it only reports or remediates non-compliant resources, not block HTTP access at the storage account level.

590
MCQmedium

You are a security engineer at Contoso. The company has an Azure virtual network named VNet1 with a subnet named WebSubnet that hosts internet-facing Linux VMs. You need to restrict inbound traffic to WebSubnet so that only HTTP (TCP 80) and HTTPS (TCP 443) from the internet are allowed, and all other inbound traffic is denied. The VMs must remain reachable over SSH from a jump host in another subnet for management. What should you configure?

A.Create a network security group (NSG) and associate it with WebSubnet. Add inbound rules allowing TCP 80 and 443 from source Internet, allowing TCP 22 from the jump host subnet, and a final rule denying all other inbound traffic with a higher priority number.
B.Create a user-defined route (UDR) on WebSubnet that sends all traffic to a virtual network gateway, and configure the gateway to allow only TCP 80 and 443.
C.Configure a service endpoint for Microsoft.Storage on WebSubnet and create a storage account firewall rule that allows only HTTP and HTTPS.
D.Create an Azure Firewall in a GatewaySubnet and configure DNAT rules to forward TCP 80 and 443 to the web VMs, and network rules to deny all other inbound traffic.
AnswerA

This is correct because an NSG applied to WebSubnet filters traffic at the subnet level. Rules are processed by priority, lowest number first. Allowing 80/443 from Internet, allowing 22 from the jump host subnet, and adding a low-priority deny-all rule enforces the required restriction while preserving management access from the jump host.

Why this answer

A network security group attached to WebSubnet enforces inbound rules at the subnet boundary. Allowing TCP 80 and 443 from Internet, allowing TCP 22 from the jump host subnet, and placing a deny-all rule at a higher priority number blocks all other inbound traffic. This satisfies both the internet restriction and the management requirement without extra routing changes.

Exam trap

The trap here is assuming that a user-defined route or Azure Firewall DNAT can replace an NSG for restricting inbound ports to a subnet, when only an NSG provides stateful, subnet-level inbound filtering.

591
MCQmedium

You are a security engineer for a company that uses Azure Virtual Networks and Azure Private Endpoints. You have a storage account with a private endpoint in VNet1. You need to ensure that all DNS queries for the storage account's private endpoint resolve to the private IP address from any virtual machine in VNet1. The virtual machines use the default Azure-provided DNS servers. What should you do?

A.Create a private DNS zone named privatelink.blob.core.windows.net and link it to VNet1.
B.Enable Azure DNS Private Resolver in VNet1 and configure a forwarding rule to the storage account's private IP.
C.Add a DNS record for the storage account's public FQDN pointing to the private IP address in the VNet's DNS settings.
D.Configure a conditional forwarder on the Azure-provided DNS servers to forward queries for the storage account to an on-premises DNS server.
AnswerA

Azure Private Endpoints require a private DNS zone to resolve the private IP. The zone name must match the service's privatelink domain, such as privatelink.blob.core.windows.net for Blob storage. Linking the zone to VNet1 ensures that VMs using Azure-provided DNS can resolve the private endpoint FQDN to the private IP, enabling secure, private connectivity.

Why this answer

Private Endpoints require DNS resolution to the private IP. Azure Private DNS zones with names like privatelink.blob.core.windows.net are the standard method. Linking the zone to the virtual network enables Azure-provided DNS to resolve the private endpoint FQDN correctly.

Other options either misuse features or do not provide the required DNS resolution.

Exam trap

The trap here is assuming that Azure-provided DNS can be customized with conditional forwarders or custom records, which it cannot.

592
MCQhard

Refer to the exhibit. You are reviewing a policy assignment in Microsoft Defender for Cloud that deploys the Log Analytics agent to Azure VMs. The policy uses 'DeployIfNotExists' effect and specifies a workspace. However, newly created VMs are not showing the agent installed. What is the most likely cause?

A.The workspace ID is incorrect.
B.The policy assignment does not have a managed identity assigned.
C.The policy effect is set to 'Disabled'.
D.The Log Analytics workspace is in a different region than the VMs.
AnswerB

DeployIfNotExists policies require a managed identity to execute the deployment template that installs the Log Analytics agent. Without a system-assigned or user-assigned managed identity on the policy assignment, Azure Policy cannot perform any remediation actions, so the agent is never deployed. The exhibit likely omits this identity, making it the most probable reason no installation occurs.

Why this answer

The 'DeployIfNotExists' effect in Azure Policy requires a managed identity to perform remediation tasks, such as installing the Log Analytics agent. Without a managed identity assigned to the policy assignment, the policy can evaluate compliance but cannot execute the deployment action. This is the most likely cause because the policy is correctly configured but lacks the necessary identity to write resources (agent installation) to the VM.

Exam trap

The trap here is that candidates often assume a policy with 'DeployIfNotExists' automatically has permissions to deploy resources, but Azure Policy requires an explicit managed identity assignment for remediation actions, which is a common oversight in exam scenarios.

How to eliminate wrong answers

Option A is wrong because an incorrect workspace ID would cause the agent to install but connect to the wrong workspace, not fail to install entirely; the policy deployment action would still run. Option C is wrong because if the policy effect were set to 'Disabled', the policy would not evaluate at all, and the question states the policy is assigned and evaluating (new VMs are not showing the agent, implying evaluation occurs but deployment fails). Option D is wrong because the Log Analytics agent can connect to workspaces in any region; region mismatch does not prevent agent installation, only may cause data latency or cross-region charges.

593
MCQeasy

A company stores sensitive data in Azure Blob Storage. They want to ensure that the data is encrypted at rest using a customer-managed key (CMK) stored in Azure Key Vault. Additionally, they need the ability to immediately make the data inaccessible in case of a security breach. Which configuration on the storage account enables this?

A.Enable Azure Storage encryption with a customer-managed key (CMK)
B.Enable infrastructure encryption
C.Enable soft delete for the storage account
D.Enable Azure AD authentication for Blob Storage
AnswerA

Customer-managed keys (CMK) give you explicit control over the key hierarchy used to encrypt Azure Storage. Under envelope encryption, the CMK is a key encryption key (KEK) stored in Azure Key Vault that protects the data encryption key (DEK) used for blob encryption. Revoking or disabling the CMK in Key Vault causes Azure Storage to reject any attempt to decrypt the DEK, effectively making the data inaccessible almost immediately. This provides a deliberate, auditable kill switch that meets the requirement to block access on demand.

Why this answer

Enabling Azure Storage encryption with a customer-managed key (CMK) stored in Azure Key Vault allows the customer to control the encryption key used for data at rest. In the event of a security breach, the customer can immediately revoke access to the CMK in Key Vault (e.g., by disabling the key or deleting the key vault), which renders the encrypted Blob Storage data inaccessible because Azure Storage cannot decrypt it without the key. This satisfies both the encryption-at-rest requirement and the ability to make data inaccessible on demand.

Exam trap

The trap here is that candidates often confuse soft delete (which protects against accidental deletion) with the ability to make data inaccessible via key revocation, or they assume infrastructure encryption or Azure AD authentication provide the same control as CMK, but only CMK with key revocation in Key Vault gives the customer direct, immediate control over data accessibility.

How to eliminate wrong answers

Option B is wrong because infrastructure encryption provides an additional layer of encryption at the storage infrastructure level using platform-managed keys, but it does not use customer-managed keys and does not allow the customer to revoke access to make data inaccessible. Option C is wrong because soft delete for the storage account protects against accidental deletion by retaining deleted data for a retention period, but it does not provide encryption with customer-managed keys or the ability to immediately make data inaccessible during a breach. Option D is wrong because Azure AD authentication for Blob Storage controls access to data via identity-based authorization, but it does not encrypt data at rest with customer-managed keys or provide a mechanism to revoke encryption keys to make data inaccessible.

594
MCQmedium

A security operations team uses Microsoft Sentinel. They want to enable User and Entity Behavior Analytics (UEBA) to detect anomalous user activities. Which configuration is required?

A.Enable UEBA in the Sentinel settings
B.Install the UEBA data connector
C.Create an analytics rule with UEBA template
D.Assign the Security Reader role to Sentinel
AnswerA

UEBA must be explicitly turned on in Microsoft Sentinel by navigating to Settings > Entity behavior and toggling the feature. It does not require any separate deployment or data source configuration because it operates on data already ingested through existing connectors, such as Azure Active Directory and Windows Security Events. The toggle immediately activates behavioral profiling for entities like users and hosts, so without this action, no UEBA-based alerts or insights will appear.

Why this answer

UEBA in Microsoft Sentinel is a built-in feature that must be explicitly enabled in the Sentinel configuration settings under 'Entity behavior analytics'. It does not require a separate data connector or analytics rule template; once enabled, Sentinel automatically ingests and analyzes existing log data (e.g., Azure AD sign-ins, Office 365 audit logs) to establish behavioral baselines and detect anomalies.

Exam trap

The trap here is that candidates often confuse enabling a feature with installing a connector or creating a rule, but UEBA is a toggle in Sentinel settings, not a data source or alert rule.

How to eliminate wrong answers

Option B is wrong because UEBA does not have a dedicated data connector; it leverages data already collected by other connectors (e.g., Azure AD, Office 365, Windows Security Events). Option C is wrong because UEBA is not activated by creating an analytics rule with a template; it is a platform-level feature that must be toggled on in settings, after which anomaly detection rules are automatically generated. Option D is wrong because assigning the Security Reader role to Sentinel does not enable UEBA; it only grants read permissions to Sentinel resources, not the behavioral analytics engine.

595
MCQmedium

Traffic from a spoke VNet must reach the internet through a firewall in the hub VNet. What routing configuration is required on the spoke subnets?

A.A route to Internet with next hop Internet
B.A default route to the Azure Firewall private IP or virtual appliance next hop
C.An NSG deny rule for 0.0.0.0/0
D.A service endpoint policy
AnswerB

A default route (0.0.0.0/0) with a next hop of the Azure Firewall private IP or the NVA interface is the standard way to implement forced tunneling from a spoke VNet to a hub. This user-defined route overrides Azure's default Internet route and steers all outbound traffic to the firewall, which can then apply rules, NAT, and logging before sending it to the internet. For an NVA, IP forwarding must be enabled on the NIC, and for Azure Firewall, the next hop is simply the firewall's private IP.

Why this answer

To force spoke traffic to the internet through a firewall in the hub VNet, you must create a user-defined route (UDR) on the spoke subnet with an address prefix of 0.0.0.0/0 and a next hop of the Azure Firewall's private IP or the virtual appliance's IP. This overrides the default system route that would otherwise send internet-bound traffic directly out via Azure's edge, ensuring all egress traffic is inspected and controlled by the firewall.

Exam trap

The trap here is that candidates often confuse NSG rules with routing, thinking a deny rule for 0.0.0.0/0 can force traffic through a firewall, when in fact only a UDR with a specific next hop can redirect traffic to a network virtual appliance.

How to eliminate wrong answers

Option A is wrong because a route to Internet with next hop Internet would send traffic directly to the internet via Azure's default path, bypassing the firewall entirely. Option C is wrong because an NSG deny rule for 0.0.0.0/0 would block all outbound traffic, including legitimate internet access, and does not route traffic through a firewall. Option D is wrong because a service endpoint policy restricts access to specific Azure services (e.g., Storage, SQL) from a subnet, not general internet routing or firewall enforcement.

596
MCQhard

Your organization runs a critical application on an Azure VM that generates sensitive data. You need to ensure that only approved applications can execute on the VM to prevent malware. You have Microsoft Defender for Cloud enabled with the Defender for Servers plan P2. Which feature provides application control without requiring custom rules?

A.Configure AppLocker via Group Policy.
B.Enable Just-in-time VM access on the VM.
C.Enable Windows Defender Application Control (WDAC) on the VM.
D.Enable Adaptive application controls in Defender for Cloud.
AnswerD

Adaptive application controls in Microsoft Defender for Cloud are the correct solution because they automatically build an allowlist of known-good processes using machine learning and behavioral analysis. Defender for Cloud monitors running processes across the VM, generates a baseline, and applies an application control policy that permits only trusted applications while blocking untrusted executables. It also provides security recommendations and alerts when deviations occur, all managed from the Defender for Cloud portal without the need to manually construct rule sets, making it the only option that meets the requirement for an automatic, centrally managed application control.

Why this answer

Adaptive application controls in Microsoft Defender for Cloud (option D) is the correct choice because, with the Defender for Servers P2 plan, it uses machine learning to automatically analyze VM behavior and create a baseline of approved applications, generating allowlist recommendations without requiring you to author custom rules. It then enforces these allowlists to block untrusted executables, directly meeting the requirement to prevent malware execution. AppLocker via Group Policy (A) also provides application control but requires manually defining and maintaining rules, so it does not fit the 'no custom rules' requirement.

Just-in-time VM access (B) only restricts inbound network access to management ports and does not control which applications can execute. WDAC (C) is a valid application control mechanism, but it likewise requires you to create and manage policies rather than automatically generating them from Defender for Cloud's adaptive recommendations.

597
MCQmedium

You are a security engineer at Fabrikam Inc. The company has an Azure subscription with a single virtual network (VNet1) that contains a production workload. The network is connected to an on-premises data center via a site-to-site VPN. The security team requires that all Remote Desktop Protocol (RDP) and Secure Shell (SSH) access to virtual machines in VNet1 must be brokered through Azure Bastion. Additionally, the team wants to ensure that no public IP addresses are assigned to any virtual machines in the production environment. Currently, there are several VMs with public IPs. You need to implement the requirements with minimal downtime. The solution must also ensure that administrators can access the VMs using Azure Bastion without any additional client software. What should you do?

A.Create a point-to-site VPN for administrators and remove public IPs from VMs.
B.Deploy Azure Bastion in the virtual network, then configure Just-In-Time (JIT) VM access for all VMs.
C.Disassociate public IPs from all VMs, then deploy Azure Bastion in the same virtual network.
D.Deploy Azure Bastion in the virtual network and then remove the public IP addresses from all VMs.
AnswerD

Deploying Azure Bastion in the same virtual network as the target VMs first establishes a secure, fully managed PaaS service that brokers RDP and SSH sessions over TLS using the HTML5 client, with no additional client software required. Once Bastion reports a healthy status, removing the VMs' public IPs keeps administrative access uninterrupted because Bastion connects to the VMs over their private IP addresses. This ordering ensures zero downtime for administrators and aligns exactly with the requirements to eliminate public exposure and avoid client configuration.

Why this answer

Option D is correct because Azure Bastion must be deployed in the same virtual network as the target VMs (or a peered VNet) before public IPs are removed, since Bastion provides RDP/SSH connectivity over TLS port 443 through the Azure portal without requiring any client software or public IPs on the VMs. Deploying Bastion first ensures administrators retain access while the public IPs are disassociated, minimizing downtime. Option A is wrong because a point-to-site VPN does not broker RDP/SSH through Bastion and does not satisfy the no-public-IP requirement by itself.

Option B is wrong because JIT VM access is a Microsoft Defender for Cloud feature that reduces exposure but does not replace Bastion or eliminate the need for public IPs. Option C is wrong because removing public IPs before Bastion is deployed would cut off RDP/SSH access and cause downtime.

598
MCQhard

Your organization has Microsoft Entra ID and uses Microsoft Copilot for Microsoft 365. You need to ensure that Copilot interactions are logged and accessible for security investigations. What should you configure?

A.Configure Microsoft Sentinel to collect Copilot logs via the Office 365 connector
B.Enable diagnostic settings in Azure Monitor to collect Copilot logs
C.Ensure that auditing is enabled in Microsoft Purview to capture Copilot interactions
D.Deploy Microsoft Defender for Cloud Apps to monitor Copilot usage
AnswerC

Microsoft Purview's unified audit log is the authoritative repository for compliance-related events across Microsoft 365, including Copilot user prompts and responses. When Purview auditing is enabled at the tenant level, the audit engine records Copilot interaction metadata such as the user, timestamp, and action performed, making these records searchable in the Purview compliance portal. This audit trail can also be exported through the Office 365 Management Activity API or integrated with Microsoft Sentinel after the logs have been collected by Purview, but the core requirement is enabling Purview auditing itself.

Why this answer

Microsoft Copilot for Microsoft 365 interactions are audited through the Microsoft Purview audit log. Enabling auditing in Purview captures detailed records of Copilot prompts and responses, which are then accessible for security investigations via the Purview compliance portal or through the Office 365 Management Activity API. This is the designated mechanism for logging Copilot activity, as Copilot interactions are considered Microsoft 365 workload events.

Exam trap

The trap here is that candidates often assume Copilot logs are collected via Azure Monitor or Microsoft Sentinel connectors by default, when in reality Copilot auditing is a Microsoft Purview feature that must be explicitly enabled and is not automatically routed to Azure monitoring tools.

How to eliminate wrong answers

Option A is wrong because Microsoft Sentinel's Office 365 connector ingests logs from the Office 365 Management Activity API, but it does not natively collect Copilot-specific interaction logs; Copilot logs require Purview auditing to be enabled first, and even then, Sentinel can only consume them if Purview auditing is already active. Option B is wrong because Azure Monitor diagnostic settings are used to collect telemetry from Azure resources (e.g., VMs, App Services), not from Microsoft 365 workloads like Copilot; Copilot logs are not emitted to Azure Monitor. Option D is wrong because Microsoft Defender for Cloud Apps focuses on shadow IT discovery and session-level monitoring for SaaS apps, not on capturing detailed Copilot prompt/response audit logs; it can use Purview audit logs as a source but does not replace the need for Purview auditing.

599
MCQhard

An analyst creates a Sentinel automation rule and a playbook. The playbook should run only when incidents are created from a specific analytics rule and severity is High. Where should this filtering be configured?

A.Automation rule conditions
B.Logic App recurrence trigger
C.Log Analytics workspace retention settings
D.Analytics rule suppression only
AnswerA

Automation rule conditions are the correct answer because Microsoft Sentinel automation rules evaluate real-time alert or incident attributes—such as severity, status, entity types, and custom property values—against defined conditions. Only when every condition is satisfied does the rule invoke the linked Logic App playbook, providing precise, context-aware automation. This is exactly how Sentinel is designed to conditionally run playbooks, unlike the other options.

Why this answer

Automation rules in Microsoft Sentinel are designed to trigger actions based on incident creation or update events. By configuring conditions within the automation rule, you can specify that the associated playbook should only run when the incident is created from a specific analytics rule and has a severity of High. This is the correct and intended location for such filtering, as automation rules evaluate conditions before invoking the playbook.

Exam trap

The trap here is that candidates may confuse automation rule conditions with analytics rule suppression or Logic App triggers, mistakenly thinking filtering should be done at the analytics rule or Logic App level rather than in the automation rule that orchestrates the playbook execution.

How to eliminate wrong answers

Option B is wrong because the Logic App recurrence trigger is used for scheduled, time-based execution, not for event-driven responses to Sentinel incidents; it cannot filter on analytics rule or severity at incident creation. Option C is wrong because Log Analytics workspace retention settings control how long data is stored, not the triggering conditions for playbooks or automation rules. Option D is wrong because analytics rule suppression only prevents the rule from creating incidents or alerts for a specified period after an alert is generated; it does not filter which incidents trigger a playbook.

600
MCQmedium

A company stores confidential data in Azure Blob Storage. They need to ensure that all data at rest is encrypted and they must be able to quickly rotate the encryption key on demand in case of a security breach. They also want to minimize administrative overhead. Which encryption option should they use?

A.Server-side encryption with Microsoft-managed keys
B.Server-side encryption with customer-managed keys (CMK) stored in Azure Key Vault
C.Client-side encryption
D.Azure Disk Encryption
AnswerB

Server-side encryption with customer-managed keys (CMK) stored in Azure Key Vault allows your organization to control the root encryption key used for encrypting Azure Blob Storage. With CMK, you can rotate keys on your own schedule, disable or revoke a key immediately if compromised, and audit key usage through Key Vault diagnostics, which helps meet compliance and governance requirements. Azure Storage implements CMK through envelope encryption, where the key in Key Vault encrypts the data encryption key, providing both strong encryption and operational flexibility without requiring application changes.

Why this answer

Server-side encryption with customer-managed keys (CMK) stored in Azure Key Vault allows the organization to control and rotate the encryption key on demand, meeting the security breach response requirement. This option encrypts data at rest in Azure Blob Storage while minimizing administrative overhead because Azure manages the encryption process, and the customer only manages the key lifecycle in Key Vault.

Exam trap

The trap here is that candidates confuse Azure Disk Encryption (which encrypts VM disks) with Azure Storage encryption, or assume that Microsoft-managed keys support on-demand rotation, when in fact only customer-managed keys allow the customer to control the key lifecycle.

How to eliminate wrong answers

Option A is wrong because Microsoft-managed keys cannot be rotated on demand by the customer; the rotation schedule is controlled by Microsoft, which fails the requirement for quick key rotation in a breach. Option C is wrong because client-side encryption requires the application to manage encryption and key rotation, increasing administrative overhead and complexity, which contradicts the goal of minimizing overhead. Option D is wrong because Azure Disk Encryption is designed for encrypting virtual machine disks (OS and data disks), not for Azure Blob Storage data at rest.

Page 7

Page 8 of 9

Page 9

All pages