mcAfee Secure Website
23

Microsoft AZ-500 Bundle

Exam Code: AZ-500

Exam Name Microsoft Azure Security Technologies

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Security Engineer Associate

AZ-500 Training Materials $44.99

Reliable & Actual Study Materials for AZ-500 Exam Success

The Latest AZ-500 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-500 Questions & Answers

    523 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-500 Video Course

    AZ-500 Training Course

    73 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-500 Study Guide

    635 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Security Technologies (AZ-500) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    523 Questions

    $124.99
    exam =35
  • exam =37
    AZ-500 Video Course

    Training Course

    73 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    635 PDF Pages

    $29.99

Microsoft AZ-500 Practice Test 14

Question 130

An Azure security engineer investigates the following incident: A Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants. Which safeguard would best prevent this issue from recurring?

  1. Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated.
  2. Review playbook connection identities and least-privilege rights before enabling automated containment.
  3. Retest analytic watchlist joins after source schema or naming normalization changes.
  4. Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators.

Explanation

Correct Answer

C:

This guardrail addresses sentinel watchlist match normalization: Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The prevention measure is: Retest analytic watchlist joins after source schema or naming normalization changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated” would address that alternative cause, not the condition in this question: watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.

B:

“Review playbook connection identities and least-privilege rights before enabling automated containment” responds to this separate finding: playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. This question instead needs “Retest analytic watchlist joins after source schema or naming normalization changes”, so the alternative does not meet the stated condition.

D:

Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators” applies to that separate problem. The observed case is a Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants; choosing this alternative would address the wrong failure mode.

Question 131

The cloud operations team reviews the following risk: A regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints. Which remediation best addresses the specific issue?

  1. Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap.
  2. Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains.
  3. Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements.
  4. Clear or expand the inventory filter and verify the evaluated scope against resource ownership records.

Explanation

Correct Answer

C:

The cause is: A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. The appropriate change is: Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements. Verify it with this outcome: The compliance record distinguishes benchmark guidance from enforceable obligations and documents any controlled exceptions.

Incorrect Answers

A:

This action concerns defender for cloud secure score priority, where Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. The reported incident instead involves A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation.

B:

This action concerns defender easm externally visible asset discovery, where Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. The corrective response here is “Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements”; this alternative does not provide that response.

D:

This action concerns defender for cloud inventory filters multi-region, where Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. The stem reports a regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints; this control addresses a different failure condition.

Question 132

A platform security assessment reveals this issue: A firewall administrator enables a network rule and assumes that traffic is being audited despite no diagnostic setting on the firewall resource. What technical cause best accounts for the described behavior?

  1. Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings.
  2. Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events.
  3. Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.
  4. Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation.

Explanation

Correct Answer

A:

The described technical condition is: Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. The appropriate corrective action is: Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging. Confirm with: A controlled allowed and denied connection produces correlatable firewall records in the intended workspace.

Incorrect Answers

B:

Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Change the automation rule to the correct incident-created trigger with the intended scoped conditions” would address that alternative cause, not the condition in this question: network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings.

C:

“Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches” responds to this separate finding: watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. This question instead needs “Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging”, so the alternative does not meet the stated condition.

D:

Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics” applies to that separate problem. The observed case is a firewall administrator enables a network rule and assumes that traffic is being audited despite no diagnostic setting on the firewall resource; choosing this alternative would address the wrong failure mode.

Question 133

A Microsoft Azure administrator receives this requirement: A VM scanner lists a high-severity operating system vulnerability and the operator closes the ticket without applying any patch. What should the engineer implement first to address the weakness?

  1. Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories.
  2. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.
  3. Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster.
  4. Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment.

Explanation

Correct Answer

B:

The cause is: A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The appropriate change is: Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation. Verify it with this outcome: A subsequent scan no longer detects the affected vulnerable package or documents a justified protected exception.

Incorrect Answers

A:

This action concerns defender for cloud devops github connector scope, where DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. The reported incident instead involves A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified.

C:

This action concerns defender for containers kubernetes posture, where Node management alone does not provide full supported Defender for Containers security posture and workload protection. The corrective response here is “Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation”; this alternative does not provide that response.

D:

This action concerns defender for cloud devops iac misconfiguration, where Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The stem reports a VM scanner lists a high-severity operating system vulnerability and the operator closes the ticket without applying any patch; this control addresses a different failure condition.

Question 134

A regulated Azure tenant has this security condition: A security team deploys Log Analytics and expects the workspace to provide Microsoft Sentinel analytics and incidents without onboarding Sentinel. Which explanation fits the observed symptoms most closely?

  1. Alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit.
  2. Azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association.
  3. A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace.
  4. A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities.

Explanation

Correct Answer

D:

The described technical condition is: A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. The appropriate corrective action is: Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content. Confirm with: The workspace exposes Sentinel analytics, incident management and authorized security content appropriately.

Incorrect Answers

A:

Alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit. “Configure the supported analytic-rule event or alert grouping window and matching fields for the intended incident unit” would address that alternative cause, not the condition in this question: a Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities.

B:

“Create or correct the DCR Windows event selection and associate it with the eligible Windows machines” responds to this separate finding: azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association. This question instead needs “Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content”, so the alternative does not meet the stated condition.

C:

A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters” applies to that separate problem. The observed case is a security team deploys Log Analytics and expects the workspace to provide Microsoft Sentinel analytics and incidents without onboarding Sentinel; choosing this alternative would address the wrong failure mode.

Question 135

A platform security assessment reveals this issue: Linux servers ship system telemetry but their authentication facility events are missing from the central detection environment. Which recurring validation best protects against the observed problem?

  1. Recheck monitored Linux facilities and filtering after operating system or detection-content upgrades.
  2. Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators.
  3. Test cloud identity telemetry coverage whenever tenant logging or connector permissions change.
  4. Monitor ingestion delay and align scheduled rule lookback to actual source latency.

Explanation

Correct Answer

A:

This guardrail addresses azure monitor dcr linux syslog facility: A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. The prevention measure is: Recheck monitored Linux facilities and filtering after operating system or detection-content upgrades. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators” would address that alternative cause, not the condition in this question: a DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination.

C:

“Test cloud identity telemetry coverage whenever tenant logging or connector permissions change” responds to this separate finding: microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. This question instead needs “Recheck monitored Linux facilities and filtering after operating system or detection-content upgrades”, so the alternative does not meet the stated condition.

D:

A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. “Monitor ingestion delay and align scheduled rule lookback to actual source latency” applies to that separate problem. The observed case is linux servers ship system telemetry but their authentication facility events are missing from the central detection environment; choosing this alternative would address the wrong failure mode.

Question 136

A Microsoft Azure administrator receives this requirement: A spoke subnet unexpectedly learns routes from an attached virtual network gateway and uses an unwanted path despite a locally maintained route table. What observation is the strongest validation evidence?

  1. The app subnet's outbound flows traverse the central inspection appliance and are visible in policy logs.
  2. HTTPS reaches the approved VM only when both applicable NSG layers permit the connection.
  3. New prohibited connections fail and the team documents disposition of any previously established flows.
  4. Effective route inspection shows only intended propagated and explicit routes for the target subnet.

Explanation

Correct Answer

D:

This validates the specific control for BGP gateway route propagation control: Gateway route propagation remains enabled for the route table and influences effective routing selections. The associated corrective action is: Disable BGP route propagation on the relevant route table where the approved design requires static steering. Testing a different component would not establish this result.

Incorrect Answers

A:

No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. “Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP” would address that alternative cause, not the condition in this question: gateway route propagation remains enabled for the route table and influences effective routing selections.

B:

“Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope” responds to this separate finding: both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. This question instead needs “Disable BGP route propagation on the relevant route table where the approved design requires static steering”, so the alternative does not meet the stated condition.

C:

NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. “Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes” applies to that separate problem. The observed case is a spoke subnet unexpectedly learns routes from an attached virtual network gateway and uses an unwanted path despite a locally maintained route table; choosing this alternative would address the wrong failure mode.

Question 137

A Microsoft Azure administrator receives this requirement: A team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged. What should the engineer implement first to address the weakness?

  1. Move credentials into a managed secrets service and use approved persistent data storage where needed.
  2. Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation.
  3. Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope.
  4. Enable the supported network policy option and enforce namespace/pod label based allowlists.

Explanation

Correct Answer

A:

The cause is: Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. The appropriate change is: Move credentials into a managed secrets service and use approved persistent data storage where needed. Verify it with this outcome: Recreated instances retrieve approved secrets securely without relying on local ephemeral disk recovery.

Incorrect Answers

B:

This action concerns aks workload image scanning, where Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. The reported incident instead involves Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories.

C:

This action concerns aks microsoft entra and kubernetes rbac, where Cluster authorization is not aligned with identity-based RBAC and separation of duties. The corrective response here is “Move credentials into a managed secrets service and use approved persistent data storage where needed”; this alternative does not provide that response.

D:

This action concerns aks pod network policy isolation, where Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. The stem reports a team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged; this control addresses a different failure condition.

Question 138

While validating an Azure workload, the security team finds: An App Service must accept application requests only through private network connectivity, but the team uses outbound VNet integration alone. Which condition most directly explains the failure?

  1. The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations.
  2. Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.
  3. Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint.
  4. A private endpoint has not been configured or public network access has not been restricted for the resource.

Explanation

Correct Answer

C:

The described technical condition is: Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. The appropriate corrective action is: Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required. Confirm with: Clients inside authorized networks reach the app over the private endpoint while public requests fail.

Incorrect Answers

A:

The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations. “Apply an appropriate service endpoint policy restricting the subnet to approved storage resources” would address that alternative cause, not the condition in this question: regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint.

B:

“Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service” responds to this separate finding: service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. This question instead needs “Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required”, so the alternative does not meet the stated condition.

D:

A private endpoint has not been configured or public network access has not been restricted for the resource. “Create an approved Private Endpoint in the workload VNet and disable or restrict the service's public access” applies to that separate problem. The observed case is an App Service must accept application requests only through private network connectivity, but the team uses outbound VNet integration alone; choosing this alternative would address the wrong failure mode.

Question 139

A regulated Azure tenant has this security condition: A regulated VM disk must use organization-controlled encryption keys but a team assumes a Key Vault secret access policy alone attaches the key to a disk. Which remediation best addresses the specific issue?

  1. Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules.
  2. Apply approved Azure Update Manager or supported guest patch orchestration and verify patch installation.
  3. Restrict extension publishers and deployment rights and deploy only signed or approved scripts.
  4. Configure the encryption set and supported Key Vault key permissions, then associate eligible disks.

Explanation

Correct Answer

D:

The cause is: Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The appropriate change is: Configure the encryption set and supported Key Vault key permissions, then associate eligible disks. Verify it with this outcome: The disk references the approved encryption set and retains correct key-access connectivity.

Incorrect Answers

A:

This action concerns azure bastion without public vm ip, where Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. The reported incident instead involves Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access.

B:

This action concerns guest os patch compliance, where Azure resource deployment health does not automatically establish guest operating system patch compliance. The corrective response here is “Configure the encryption set and supported Key Vault key permissions, then associate eligible disks”; this alternative does not provide that response.

C:

This action concerns vm extension least privilege, where Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. The stem reports a regulated VM disk must use organization-controlled encryption keys but a team assumes a Key Vault secret access policy alone attaches the key to a disk; this control addresses a different failure condition.

Question 140

While validating an Azure workload, the security team finds: A security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions. Which condition most directly explains the failure?

  1. A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.
  2. NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule.
  3. Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.
  4. Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.

Explanation

Correct Answer

C:

The described technical condition is: Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The appropriate corrective action is: Assign the approved read-only role at a suitable management group with the intended child subscription coverage. Confirm with: The operator views security inventory in both existing and newly attached eligible subscriptions.

Incorrect Answers

A:

A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” would address that alternative cause, not the condition in this question: per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.

B:

“Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment” responds to this separate finding: notActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. This question instead needs “Assign the approved read-only role at a suitable management group with the intended child subscription coverage”, so the alternative does not meet the stated condition.

D:

Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” applies to that separate problem. The observed case is a security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions; choosing this alternative would address the wrong failure mode.