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 36

Question 350

An Azure security engineer investigates the following incident: An Application Gateway intermittently returns 502 even though backend VMs are up because the health probe checks an incorrect hostname and path. Which safeguard would best prevent this issue from recurring?

  1. Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services.
  2. Validate probe host/path behavior whenever application URLs or certificates change.
  3. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  4. Review the APIM tier's supported private networking features before selecting gateway architecture.

Explanation

Correct Answer

B:

This guardrail addresses application gateway backend health probes: The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. The prevention measure is: Validate probe host/path behavior whenever application URLs or certificates change. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The function hosting plan and network integration/DNS are not configured for the required private destination. “Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services” would address that alternative cause, not the condition in this question: the backend health probe is failing due to its configured request host, path or expected response rather than VM availability.

C:

“Test TLS protocol settings and certificate expiry after changes to public application endpoints” responds to this separate finding: the app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. This question instead needs “Validate probe host/path behavior whenever application URLs or certificates change”, so the alternative does not meet the stated condition.

D:

The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. “Review the APIM tier's supported private networking features before selecting gateway architecture” applies to that separate problem. The observed case is an Application Gateway intermittently returns 502 even though backend VMs are up because the health probe checks an incorrect hostname and path; choosing this alternative would address the wrong failure mode.

Question 351

The cloud operations team reviews the following risk: An attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events. Which remediation best addresses the specific issue?

  1. Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators.
  2. Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories.
  3. Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw.
  4. Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook.

Explanation

Correct Answer

A:

The cause is: Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. The appropriate change is: Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators. Verify it with this outcome: A controlled suspicious management-plane action produces the expected Defender alert and activity context.

Incorrect Answers

B:

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 Control-plane Resource Manager activity can require dedicated detection separate from guest server security events.

C:

This action concerns vulnerability risk prioritization by exposure, where Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. The corrective response here is “Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators”; this alternative does not provide that response.

D:

This action concerns defender for cloud workflow automation trigger scope, where A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. The stem reports an attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events; this control addresses a different failure condition.

Question 352

While validating an Azure workload, the security team finds: A secret-reading application was migrated to a Key Vault private endpoint but continues resolving the vault hostname to a public IP address. Which condition most directly explains the failure?

  1. Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions.
  2. Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client.
  3. A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design.
  4. Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry.

Explanation

Correct Answer

B:

The described technical condition is: Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client. The appropriate corrective action is: Link the appropriate privatelink vault DNS zone and verify correct private records from the application virtual network. Confirm with: The application resolves the vault to its approved private address and secret retrieval succeeds without public vault access.

Incorrect Answers

A:

Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. “Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope” would address that alternative cause, not the condition in this question: private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client.

C:

“Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported” responds to this separate finding: a service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. This question instead needs “Link the appropriate privatelink vault DNS zone and verify correct private records from the application virtual network”, so the alternative does not meet the stated condition.

D:

Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. “Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications” applies to that separate problem. The observed case is a secret-reading application was migrated to a Key Vault private endpoint but continues resolving the vault hostname to a public IP address; choosing this alternative would address the wrong failure mode.

Question 353

A production Azure security implementation shows this failure: A machine-level extension installs arbitrary scripts using an overprivileged credential, and operators have no approved process to review its payload. Which operating control most directly reduces this recurring risk?

  1. Audit installed extensions and review guest-level execution privileges after VM changes.
  2. Review JIT requests and ensure routine administrative ports remain closed outside authorized windows.
  3. Schedule OS-level update compliance checks independent of ARM deployment status.
  4. Confirm supported VM sizes and host encryption settings before regulated VM deployment.

Explanation

Correct Answer

A:

This guardrail addresses vm extension least privilege: Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. The prevention measure is: Audit installed extensions and review guest-level execution privileges after VM changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The VM's NSG exposes a persistent management port rather than enforcing just-in-time access. “Review JIT requests and ensure routine administrative ports remain closed outside authorized windows” would address that alternative cause, not the condition in this question: unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access.

C:

“Schedule OS-level update compliance checks independent of ARM deployment status” responds to this separate finding: azure resource deployment health does not automatically establish guest operating system patch compliance. This question instead needs “Audit installed extensions and review guest-level execution privileges after VM changes”, so the alternative does not meet the stated condition.

D:

Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. “Confirm supported VM sizes and host encryption settings before regulated VM deployment” applies to that separate problem. The observed case is a machine-level extension installs arbitrary scripts using an overprivileged credential, and operators have no approved process to review its payload; choosing this alternative would address the wrong failure mode.

Question 354

During a cloud security review, the operations team observes: A broad Conditional Access policy blocks all administrators including both recovery accounts, leaving no viable emergency access route after a policy misconfiguration. What should the engineer implement first to address the weakness?

  1. Include the intended enterprise application or cloud resource in the Conditional Access assignment.
  2. Apply the documented emergency access exclusion and protect recovery identities with independent safeguards.
  3. Configure a justified sign-in frequency session control for the appropriate protected application.
  4. Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods.

Explanation

Correct Answer

B:

The cause is: The policy targets protected emergency principals without the approved tightly controlled recovery exclusions. The appropriate change is: Apply the documented emergency access exclusion and protect recovery identities with independent safeguards. Verify it with this outcome: A supervised break-glass validation succeeds while ordinary privileged users remain subject to strong controls.

Incorrect Answers

A:

This action concerns conditional access cloud app targeting, where The target cloud application selection is wrong and policy enforcement does not cover the actual resource. The reported incident instead involves The policy targets protected emergency principals without the approved tightly controlled recovery exclusions.

C:

This action concerns conditional access sign in frequency, where The relevant Conditional Access session control lacks the required sign-in frequency and session behavior. The corrective response here is “Apply the documented emergency access exclusion and protect recovery identities with independent safeguards”; this alternative does not provide that response.

D:

This action concerns phishing resistant authentication strength, where The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. The stem reports a broad Conditional Access policy blocks all administrators including both recovery accounts, leaving no viable emergency access route after a policy misconfiguration; this control addresses a different failure condition.

Question 355

A production Azure security implementation shows this failure: A team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged. Which operating control most directly reduces this recurring risk?

  1. Review local secret storage during VM image automation and prefer managed identities and Key Vault.
  2. Test both ingress and egress network policies with real pods after label changes.
  3. Test backup restore and deletion resistance periodically under approved adversarial scenarios.
  4. Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates.

Explanation

Correct Answer

A:

This guardrail addresses ephemeral disk data handling: Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. The prevention measure is: Review local secret storage during VM image automation and prefer managed identities and Key Vault. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. “Test both ingress and egress network policies with real pods after label changes” would address that alternative cause, not the condition in this question: ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories.

C:

“Test backup restore and deletion resistance periodically under approved adversarial scenarios” responds to this separate finding: backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. This question instead needs “Review local secret storage during VM image automation and prefer managed identities and Key Vault”, so the alternative does not meet the stated condition.

D:

Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. “Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates” applies to that separate problem. The observed case is a team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged; choosing this alternative would address the wrong failure mode.

Question 356

The cloud operations team reviews the following risk: A spoke sends DNS to an external resolver directly although a central Azure Firewall DNS proxy was required for reliable FQDN policy evaluation. Which configuration change most directly resolves this problem?

  1. Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies.
  2. Adjust Azure Firewall private IP ranges and route design to preserve source addresses for approved private traffic.
  3. Review inherited policy evaluation and adjust approved parent or child rule design with central authorization.
  4. Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address.

Explanation

Correct Answer

D:

The cause is: Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. The appropriate change is: Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address. Verify it with this outcome: Spoke queries traverse the DNS proxy and the service's allowed FQDN policy operates consistently.

Incorrect Answers

A:

This action concerns firewall premium tls inspection trust, where TLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients. The reported incident instead involves Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently.

B:

This action concerns azure firewall snat private range design, where The firewall's configured private address space for SNAT exemption omits the datacenter destination range. The corrective response here is “Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address”; this alternative does not provide that response.

C:

This action concerns firewall policy inheritance and rule collections, where Azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. The stem reports a spoke sends DNS to an external resolver directly although a central Azure Firewall DNS proxy was required for reliable FQDN policy evaluation; this control addresses a different failure condition.

Question 357

While validating an Azure workload, the security team finds: An administrator opens a public RDP endpoint on every production VM even though security rules prohibit direct Internet-facing management ports. Which configuration change most directly resolves this problem?

  1. Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules.
  2. Use a supported Bastion native-client connection and required RBAC and network prerequisites.
  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

A:

The cause is: Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. The appropriate change is: Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules. Verify it with this outcome: Approved administrators reach private VMs using Bastion while direct Internet RDP and SSH attempts fail.

Incorrect Answers

B:

This action concerns bastion native client security control, where Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. The reported incident instead involves Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections.

C:

This action concerns vm extension least privilege, where Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. The corrective response here is “Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules”; this alternative does not provide that response.

D:

This action concerns disk customer managed key disk encryption set, where Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The stem reports an administrator opens a public RDP endpoint on every production VM even though security rules prohibit direct Internet-facing management ports; this control addresses a different failure condition.

Question 358

During a cloud security review, the operations team observes: A service experiences intermittent TCP resets, but operators have no packet-level evidence and rely only on Azure resource health statuses. What should the engineer implement first to address the weakness?

  1. Configure relevant firewall diagnostic categories and secure retention for rule and threat events.
  2. Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable.
  3. Enable the supported Virtual Network flow logs and associated analytics or storage retention.
  4. Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow.

Explanation

Correct Answer

D:

The cause is: Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. The appropriate change is: Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow. Verify it with this outcome: A filtered packet trace identifies the reset sender and supports a targeted remediation decision.

Incorrect Answers

A:

This action concerns firewall diagnostic settings and retention, where Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The reported incident instead involves Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets.

B:

This action concerns front door origin bypass mitigation, where The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. The corrective response here is “Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow”; this alternative does not provide that response.

C:

This action concerns virtual network flow logs monitoring, where Network flow logging has not been configured for the relevant virtual network monitoring scope. The stem reports a service experiences intermittent TCP resets, but operators have no packet-level evidence and rely only on Azure resource health statuses; this control addresses a different failure condition.

Question 359

A Microsoft Azure administrator receives this requirement: A developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off. Which underlying control gap is responsible for the issue?

  1. The storage account lacks blob soft delete retention to recover recently removed objects.
  2. Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account.
  3. The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks.
  4. The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose.

Explanation

Correct Answer

A:

The described technical condition is: The storage account lacks blob soft delete retention to recover recently removed objects. The appropriate corrective action is: Enable blob soft delete with an appropriate retention period and verify the restore process. Confirm with: A controlled deletion can be reversed within retention without rebuilding the entire account.

Incorrect Answers

B:

Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. “Configure customer-managed key encryption and grant the storage account identity the required key permissions” would address that alternative cause, not the condition in this question: the storage account lacks blob soft delete retention to recover recently removed objects.

C:

“Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required” responds to this separate finding: the storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. This question instead needs “Enable blob soft delete with an appropriate retention period and verify the restore process”, so the alternative does not meet the stated condition.

D:

The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. “Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions” applies to that separate problem. The observed case is a developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off; choosing this alternative would address the wrong failure mode.

Question 360

An Azure security engineer investigates the following incident: A multi-subscription organization buys a DDoS protection plan but forgets to associate eligible production VNets containing exposed public services. Which remediation best addresses the specific issue?

  1. Associate intended eligible VNets with the correct plan and validate protection settings.
  2. Configure relevant firewall diagnostic categories and secure retention for rule and threat events.
  3. Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow.
  4. Enable the supported Virtual Network flow logs and associated analytics or storage retention.

Explanation

Correct Answer

A:

The cause is: Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The appropriate change is: Associate intended eligible VNets with the correct plan and validate protection settings. Verify it with this outcome: Security inventory shows production VNets under the required DDoS protection configuration.

Incorrect Answers

B:

This action concerns firewall diagnostic settings and retention, where Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The reported incident instead involves Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet.

C:

This action concerns network watcher packet capture evidence, where Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. The corrective response here is “Associate intended eligible VNets with the correct plan and validate protection settings”; this alternative does not provide that response.

D:

This action concerns virtual network flow logs monitoring, where Network flow logging has not been configured for the relevant virtual network monitoring scope. The stem reports a multi-subscription organization buys a DDoS protection plan but forgets to associate eligible production VNets containing exposed public services; this control addresses a different failure condition.