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 47

Question 460

A Microsoft Azure administrator receives this requirement: A security program expects passwordless sign-in but permits only password-and-SMS methods in the authentication methods policy. What is the most appropriate corrective step?

  1. Enable the approved passwordless method and complete secure user registration.
  2. Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate.
  3. Provision or consent the enterprise application service principal and configure appropriate access and controls.
  4. Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly.

Explanation

Correct Answer

A:

The cause is: Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. The appropriate change is: Enable the approved passwordless method and complete secure user registration. Verify it with this outcome: A pilot user signs in with the intended passwordless credential under Conditional Access enforcement.

Incorrect Answers

B:

This action concerns identity protection user risk response, where No effective user-risk-based identity protection response has been configured for the relevant identities. The reported incident instead involves Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.

C:

This action concerns enterprise application service principal, where The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. The corrective response here is “Enable the approved passwordless method and complete secure user registration”; this alternative does not provide that response.

D:

This action concerns user assigned managed identity reuse, where Separate system-assigned identities do not provide the stable reusable principal desired across resources. The stem reports a security program expects passwordless sign-in but permits only password-and-SMS methods in the authentication methods policy; this control addresses a different failure condition.

Question 461

While validating an Azure workload, the security team finds: A spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet. Which explanation fits the observed symptoms most closely?

  1. An enforced security admin deny rule has higher governance precedence than the workload NSG allow.
  2. Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port.
  3. Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.
  4. An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.

Explanation

Correct Answer

C:

The described technical condition is: Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The appropriate corrective action is: Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints. Confirm with: A spoke workload reaches the on-premises network via the shared hub gateway without deploying a second gateway.

Incorrect Answers

A:

An enforced security admin deny rule has higher governance precedence than the workload NSG allow. “Change the governing security admin policy through approved central administration rather than widening local NSGs” would address that alternative cause, not the condition in this question: gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.

B:

“Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service” responds to this separate finding: inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. This question instead needs “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints”, so the alternative does not meet the stated condition.

D:

An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. “Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow” applies to that separate problem. The observed case is a spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet; choosing this alternative would address the wrong failure mode.

Question 462

A platform security assessment reveals this issue: A team treats ExpressRoute private connectivity as equivalent to end-to-end payload encryption for regulated traffic between sites and Azure. What observation is the strongest validation evidence?

  1. A capture or configuration review confirms sensitive payloads are cryptographically protected over the private circuit.
  2. Authorized consumer private endpoints connect to the provider service while unapproved consumers are rejected.
  3. Clients inside authorized networks reach the app over the private endpoint while public requests fail.
  4. The web app reaches the internal backend over the intended outbound integrated network path.

Explanation

Correct Answer

A:

This validates the specific control for expressroute encryption requirement: ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. The associated corrective action is: Implement supported IPsec over ExpressRoute or application-layer TLS encryption according to the threat model. Testing a different component would not establish this result.

Incorrect Answers

B:

The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval” would address that alternative cause, not the condition in this question: expressRoute private connectivity does not by itself guarantee encryption of application data in transit.

C:

“Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required” responds to this separate finding: regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. This question instead needs “Implement supported IPsec over ExpressRoute or application-layer TLS encryption according to the threat model”, so the alternative does not meet the stated condition.

D:

App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. “Configure regional App Service VNet integration and the necessary subnet routing and DNS” applies to that separate problem. The observed case is a team treats ExpressRoute private connectivity as equivalent to end-to-end payload encryption for regulated traffic between sites and Azure; choosing this alternative would address the wrong failure mode.

Question 463

The cloud operations team reviews the following risk: A SOC deploys Azure Monitor Agent to Windows servers but receives no required security event IDs in the security analytics workspace. Which condition most directly explains the failure?

  1. Azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association.
  2. Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.
  3. Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions.
  4. Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended.

Explanation

Correct Answer

A:

The described technical condition is: Azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association. The appropriate corrective action is: Create or correct the DCR Windows event selection and associate it with the eligible Windows machines. Confirm with: The selected security events arrive in the expected Log Analytics table with correct computer and event identifiers.

Incorrect Answers

B:

Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” would address that alternative cause, not the condition in this question: azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association.

C:

“Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace” responds to this separate finding: guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. This question instead needs “Create or correct the DCR Windows event selection and associate it with the eligible Windows machines”, so the alternative does not meet the stated condition.

D:

Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. “Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition” applies to that separate problem. The observed case is a SOC deploys Azure Monitor Agent to Windows servers but receives no required security event IDs in the security analytics workspace; choosing this alternative would address the wrong failure mode.

Question 464

The cloud operations team reviews the following risk: A records container must resist deletion for a required retention period, but standard user write permissions allow documents to be overwritten. What governance practice would best prevent the same failure?

  1. Test WORM retention enforcement and approved release procedures before storing regulated records.
  2. Review data-plane RBAC separately from account administration roles for every application.
  3. Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry.
  4. Validate version history and lifecycle management for sensitive mutable blob data.

Explanation

Correct Answer

A:

This guardrail addresses blob immutable storage legal hold: Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. The prevention measure is: Test WORM retention enforcement and approved release procedures before storing regulated records. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Management-plane storage Contributor does not necessarily include blob data read DataActions. “Review data-plane RBAC separately from account administration roles for every application” would address that alternative cause, not the condition in this question: data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone.

C:

“Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry” responds to this separate finding: account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. This question instead needs “Test WORM retention enforcement and approved release procedures before storing regulated records”, so the alternative does not meet the stated condition.

D:

Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. “Validate version history and lifecycle management for sensitive mutable blob data” applies to that separate problem. The observed case is a records container must resist deletion for a required retention period, but standard user write permissions allow documents to be overwritten; choosing this alternative would address the wrong failure mode.

Question 465

The cloud operations team reviews the following risk: Two incident automation rules are meant to route high-severity cases to the SOC, but a broad earlier rule marks every incident closed first. Which condition most directly explains the failure?

  1. Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended.
  2. Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance.
  3. Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings.
  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: Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. The appropriate corrective action is: Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition. Confirm with: High-severity test incidents reach the correct responder without being prematurely closed.

Incorrect Answers

B:

Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. “Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes” would address that alternative cause, not the condition in this question: automation rule ordering and stopping behavior can prevent more specific rules from executing as intended.

C:

“Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging” responds to this separate finding: network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. This question instead needs “Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition”, 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 two incident automation rules are meant to route high-severity cases to the SOC, but a broad earlier rule marks every incident closed first; choosing this alternative would address the wrong failure mode.

Question 466

A Microsoft Azure administrator receives this requirement: Several workloads show a recommendation to close Internet-exposed management ports, but the security team wants to suppress the recommendation rather than inspect actual reachable paths. What is the most appropriate corrective step?

  1. Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives.
  2. Query all in-scope Azure resources first and then classify missing or unexpected tags for correction.
  3. Onboard the supported on-premises servers through Azure Arc and configure the relevant Defender for Cloud protection.
  4. Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements.

Explanation

Correct Answer

A:

The cause is: A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. The appropriate change is: Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives. Verify it with this outcome: Public SSH and RDP access is denied from unauthorized networks and the security assessment updates accordingly.

Incorrect Answers

B:

This action concerns defender for cloud azure resource graph query validation, where Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. The reported incident instead involves A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration.

C:

This action concerns azure arc hybrid server posture, where Defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans. The corrective response here is “Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives”; this alternative does not provide that response.

D:

This action concerns defender for cloud cloud security benchmark, where A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. The stem reports several workloads show a recommendation to close Internet-exposed management ports, but the security team wants to suppress the recommendation rather than inspect actual reachable paths; this control addresses a different failure condition.

Question 467

A production Azure security implementation shows this failure: An auditor requests a bespoke compliance requirement absent from built-in regulatory mappings, and the governance team attempts to edit a built-in standard directly. Which operating control most directly reduces this recurring risk?

  1. Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners.
  2. Test destructive-operation safeguards and backup restore regularly instead of relying on successful job status alone.
  3. Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan.
  4. Review immutability settings and approval gates before changing backup security or recovery policies.

Explanation

Correct Answer

A:

This guardrail addresses azure policy custom regulatory rule mapping: Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. The prevention measure is: Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules. “Test destructive-operation safeguards and backup restore regularly instead of relying on successful job status alone” would address that alternative cause, not the condition in this question: built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment.

C:

“Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan” responds to this separate finding: key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. This question instead needs “Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners”, so the alternative does not meet the stated condition.

D:

An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. “Review immutability settings and approval gates before changing backup security or recovery policies” applies to that separate problem. The observed case is an auditor requests a bespoke compliance requirement absent from built-in regulatory mappings, and the governance team attempts to edit a built-in standard directly; choosing this alternative would address the wrong failure mode.

Question 468

While validating an Azure workload, the security team finds: Developers redeploy vulnerable old container tags because artifact repositories retain uncontrolled image versions without review. Which outcome most clearly verifies that the issue is resolved?

  1. Approved client certificates are accepted and unknown or expired certificates are rejected.
  2. A test deployment uses the reviewed digest and obsolete unapproved images are no longer deployable.
  3. Applications remain available through rotation and old leaked keys cease to authorize access.
  4. The partner can perform only the approved blob operation while account key access is not disclosed.

Explanation

Correct Answer

B:

This validates the specific control for acr image retention and digest hygiene: Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. The associated corrective action is: Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks. Testing a different component would not establish this result.

Incorrect Answers

A:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Configure supported APIM client certificate validation and trusted certificate criteria” would address that alternative cause, not the condition in this question: unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment.

C:

“Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys” responds to this separate finding: the client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. This question instead needs “Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks”, so the alternative does not meet the stated condition.

D:

Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. “Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys” applies to that separate problem. The observed case is developers redeploy vulnerable old container tags because artifact repositories retain uncontrolled image versions without review; choosing this alternative would address the wrong failure mode.

Question 469

The cloud operations team reviews the following risk: A branch app subnet sends outbound Internet traffic straight to its default system route despite an architecture requiring inspection by a central Azure Firewall. Which condition most directly explains the failure?

  1. The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.
  2. Network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny.
  3. No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance.
  4. Both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another.

Explanation

Correct Answer

C:

The described technical condition is: No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. The appropriate corrective action is: Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP. Confirm with: The app subnet's outbound flows traverse the central inspection appliance and are visible in policy logs.

Incorrect Answers

A:

The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. “Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs” would address that alternative cause, not the condition in this question: no effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance.

B:

“Remove or narrow the broad allow rule and position the applicable deny ahead of competing permissive rules” responds to this separate finding: network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny. This question instead needs “Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP”, so the alternative does not meet the stated condition.

D:

Both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. “Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope” applies to that separate problem. The observed case is a branch app subnet sends outbound Internet traffic straight to its default system route despite an architecture requiring inspection by a central Azure Firewall; choosing this alternative would address the wrong failure mode.

Question 470

A regulated Azure tenant has this security condition: A security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events. What governance practice would best prevent the same failure?

  1. Audit TDE status and key rotation separately from transport TLS compliance.
  2. Review client-driver support, key custody and query limitations before Always Encrypted rollout.
  3. Validate SQL private connectivity and public network restrictions during application onboarding.
  4. Test audit data delivery and access controls after SQL platform and diagnostic changes.

Explanation

Correct Answer

D:

This guardrail addresses azure sql auditing destination configuration: Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. The prevention measure is: Test audit data delivery and access controls after SQL platform and diagnostic changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Audit TDE status and key rotation separately from transport TLS compliance” would address that alternative cause, not the condition in this question: azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination.

B:

“Review client-driver support, key custody and query limitations before Always Encrypted rollout” responds to this separate finding: tDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. This question instead needs “Test audit data delivery and access controls after SQL platform and diagnostic changes”, so the alternative does not meet the stated condition.

C:

The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. “Validate SQL private connectivity and public network restrictions during application onboarding” applies to that separate problem. The observed case is a security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events; choosing this alternative would address the wrong failure mode.