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 19

Question 180

An Azure security engineer investigates the following incident: A privileged assignment remains active through an entire weekend after an engineer performs a short maintenance task because the activation maximum is excessive. Which outcome most clearly verifies that the issue is resolved?

  1. Security receives and investigates alerts for new permanent privileged assignments, reducing unnecessary standing admins.
  2. Elevated access expires at the configured short interval and does not persist beyond its intended purpose.
  3. A pending activation cannot be used before an authorized approver reviews and approves it.
  4. A controlled risky sign-in is blocked in enforced mode and appears with the applied policy result.

Explanation

Correct Answer

B:

This validates the specific control for pim maximum activation duration: The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. The associated corrective action is: Reduce the permitted activation period and require fresh activation for subsequent privileged tasks. Testing a different component would not establish this result.

Incorrect Answers

A:

Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. “Review permanent assignments and configure PIM alerts, justification and eligible access where feasible” would address that alternative cause, not the condition in this question: the PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window.

C:

“Configure approval and valid approvers for activation of the sensitive Azure resource role” responds to this separate finding: the PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. This question instead needs “Reduce the permitted activation period and require fresh activation for subsequent privileged tasks”, so the alternative does not meet the stated condition.

D:

A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. “Review report-only results, correct exclusions and switch the approved policy to On for enforcement” applies to that separate problem. The observed case is a privileged assignment remains active through an entire weekend after an engineer performs a short maintenance task because the activation maximum is excessive; choosing this alternative would address the wrong failure mode.

Question 181

A regulated Azure tenant has this security condition: A security analyst concludes there are no vulnerable resources because the Defender inventory is filtered to a single region rather than the global workload footprint. Which outcome most clearly verifies that the issue is resolved?

  1. Selected connected AWS instances appear in the correct Defender plan with expected scanning and alert coverage.
  2. The inventory includes the acquired subscriptions, identifies owners and reveals previously unreviewed internet-exposed machines.
  3. Previously hidden resources are included and their vulnerability or configuration status can be assessed.
  4. Confirmed owned exposures enter the remediation queue while unrelated third-party assets are excluded with reasons.

Explanation

Correct Answer

C:

This validates the specific control for defender for cloud inventory filters multi-region: Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. The associated corrective action is: Clear or expand the inventory filter and verify the evaluated scope against resource ownership records. Testing a different component would not establish this result.

Incorrect Answers

A:

Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. “Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances” would address that alternative cause, not the condition in this question: inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types.

B:

“Build an authorized inventory from Defender for Cloud and Azure Resource Graph across governed subscriptions and management groups” responds to this separate finding: a security inventory that excludes child subscriptions and connected accounts cannot give complete exposure or asset ownership coverage. This question instead needs “Clear or expand the inventory filter and verify the evaluated scope against resource ownership records”, so the alternative does not meet the stated condition.

D:

Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. “Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution” applies to that separate problem. The observed case is a security analyst concludes there are no vulnerable resources because the Defender inventory is filtered to a single region rather than the global workload footprint; choosing this alternative would address the wrong failure mode.

Question 182

A platform security assessment reveals this issue: Known malicious destinations are still reachable because a firewall's threat-intelligence configuration only logs indicators instead of denying them. What technical cause best accounts for the described behavior?

  1. The topology lacks the intended central security policy and routing intent in Azure Firewall Manager.
  2. The point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration.
  3. The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior.
  4. Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently.

Explanation

Correct Answer

C:

The described technical condition is: The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. The appropriate corrective action is: Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation. Confirm with: A controlled known-bad test destination is denied while the firewall logs the associated indicator.

Incorrect Answers

A:

The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. “Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic” would address that alternative cause, not the condition in this question: the configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior.

B:

“Configure an appropriate Azure VPN gateway point-to-site authentication method using Microsoft Entra ID” responds to this separate finding: the point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. This question instead needs “Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation”, so the alternative does not meet the stated condition.

D:

Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. “Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address” applies to that separate problem. The observed case is known malicious destinations are still reachable because a firewall's threat-intelligence configuration only logs indicators instead of denying them; choosing this alternative would address the wrong failure mode.

Question 183

While validating an Azure workload, the security team finds: A company wants consumers in other VNets to access its internally hosted load-balanced service privately without exposing a public listener. Which result confirms the relevant security control is effective?

  1. The selected subnet accesses the restricted account while unlisted subnets remain blocked.
  2. Authorized consumer private endpoints connect to the provider service while unapproved consumers are rejected.
  3. The web app reaches the internal backend over the intended outbound integrated network path.
  4. A capture or configuration review confirms sensitive payloads are cryptographically protected over the private circuit.

Explanation

Correct Answer

B:

This validates the specific control for private link service provider design: The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. The associated corrective action is: Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval. Testing a different component would not establish this result.

Incorrect Answers

A:

The required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. “Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage” would address that alternative cause, not the condition in this question: the provider has not published a supported Private Link Service behind an eligible standard internal load balancer.

C:

“Configure regional App Service VNet integration and the necessary subnet routing and DNS” responds to this separate finding: app Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. This question instead needs “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval”, so the alternative does not meet the stated condition.

D:

ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. “Implement supported IPsec over ExpressRoute or application-layer TLS encryption according to the threat model” applies to that separate problem. The observed case is a company wants consumers in other VNets to access its internally hosted load-balanced service privately without exposing a public listener; choosing this alternative would address the wrong failure mode.

Question 184

A regulated Azure tenant has this security condition: A PIM role activation succeeds for a sensitive administrator without a fresh strong authentication check because the role settings omit MFA. What governance practice would best prevent the same failure?

  1. Investigate deny assignments as well as allow grants when diagnosing apparent RBAC permission anomalies.
  2. Test conditioned Azure RBAC access against both permitted and forbidden resource attributes.
  3. Inspect privileged role activation settings and evidence of MFA enforcement during periodic access reviews.
  4. Validate custom-role definitions through effective permission tests before applying them widely.

Explanation

Correct Answer

C:

This guardrail addresses pim activation mfa prerequisite: PIM role settings have not required the intended multifactor or authentication-strength control at activation. The prevention measure is: Inspect privileged role activation settings and evidence of MFA enforcement during periodic access reviews. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. “Investigate deny assignments as well as allow grants when diagnosing apparent RBAC permission anomalies” would address that alternative cause, not the condition in this question: pIM role settings have not required the intended multifactor or authentication-strength control at activation.

B:

“Test conditioned Azure RBAC access against both permitted and forbidden resource attributes” responds to this separate finding: a broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. This question instead needs “Inspect privileged role activation settings and evidence of MFA enforcement during periodic access reviews”, so the alternative does not meet the stated condition.

D:

NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. “Validate custom-role definitions through effective permission tests before applying them widely” applies to that separate problem. The observed case is a PIM role activation succeeds for a sensitive administrator without a fresh strong authentication check because the role settings omit MFA; choosing this alternative would address the wrong failure mode.

Question 185

A production Azure security implementation shows this failure: A tenant blocks every sign-in from outside headquarters but never distinguishes genuine low-risk travel from high-risk credential misuse. What is the most appropriate corrective step?

  1. Configure approval and valid approvers for activation of the sensitive Azure resource role.
  2. Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed.
  3. Reduce the permitted activation period and require fresh activation for subsequent privileged tasks.
  4. Configure PIM for Groups with eligible membership and required activation controls where supported.

Explanation

Correct Answer

B:

The cause is: Network location alone does not substitute for appropriate risk signals and risk-based access controls. The appropriate change is: Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed. Verify it with this outcome: High-risk sign-ins receive the configured stronger response while ordinary travel follows approved policy.

Incorrect Answers

A:

This action concerns pim role activation approval, where The PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. The reported incident instead involves Network location alone does not substitute for appropriate risk signals and risk-based access controls.

C:

This action concerns pim maximum activation duration, where The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. The corrective response here is “Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed”; this alternative does not provide that response.

D:

This action concerns pim for groups role elevation, where Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. The stem reports a tenant blocks every sign-in from outside headquarters but never distinguishes genuine low-risk travel from high-risk credential misuse; this control addresses a different failure condition.

Question 186

An Azure security engineer investigates the following incident: Two Kubernetes namespaces in AKS exchange traffic freely although finance workloads must not be reachable from untrusted pods. Which condition most directly explains the failure?

  1. Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault.
  2. Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration.
  3. Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization.
  4. Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules.

Explanation

Correct Answer

D:

The described technical condition is: Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. The appropriate corrective action is: Enable the supported network policy option and enforce namespace/pod label based allowlists. Confirm with: Approved application flows succeed while prohibited cross-namespace traffic is dropped.

Incorrect Answers

A:

Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. “Enable supported vault soft delete and enhanced protection settings including immutable backup where required” would address that alternative cause, not the condition in this question: namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules.

B:

“Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible” responds to this separate finding: application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. This question instead needs “Enable the supported network policy option and enforce namespace/pod label based allowlists”, so the alternative does not meet the stated condition.

C:

Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. “Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals” applies to that separate problem. The observed case is two Kubernetes namespaces in AKS exchange traffic freely although finance workloads must not be reachable from untrusted pods; choosing this alternative would address the wrong failure mode.

Question 187

While validating an Azure workload, the security team finds: An Azure VM has TCP 3389 permanently exposed from all Internet addresses, and a security owner needs time-limited emergency access instead. What governance practice would best prevent the same failure?

  1. Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts.
  2. Audit VM management ports and prefer controlled bastion connectivity with MFA and access logging.
  3. Audit installed extensions and review guest-level execution privileges after VM changes.
  4. Review JIT requests and ensure routine administrative ports remain closed outside authorized windows.

Explanation

Correct Answer

D:

This guardrail addresses defender for cloud jit vm management: The VM's NSG exposes a persistent management port rather than enforcing just-in-time access. The prevention measure is: Review JIT requests and ensure routine administrative ports remain closed outside authorized windows. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. “Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts” would address that alternative cause, not the condition in this question: the VM's NSG exposes a persistent management port rather than enforcing just-in-time access.

B:

“Audit VM management ports and prefer controlled bastion connectivity with MFA and access logging” responds to this separate finding: direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. This question instead needs “Review JIT requests and ensure routine administrative ports remain closed outside authorized windows”, so the alternative does not meet the stated condition.

C:

Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. “Audit installed extensions and review guest-level execution privileges after VM changes” applies to that separate problem. The observed case is an Azure VM has TCP 3389 permanently exposed from all Internet addresses, and a security owner needs time-limited emergency access instead; choosing this alternative would address the wrong failure mode.

Question 188

During a cloud security review, the operations team observes: A legacy VM uses Azure Disk Encryption but a required Key Vault key or secret is disabled during rotation and the VM cannot unlock encrypted volumes. After remediation, which test result best proves the intended change?

  1. A test request from the approved address succeeds temporarily while arbitrary Internet sources remain denied.
  2. The VM successfully mounts its protected volume after an approved recovery and retains encryption.
  3. The VM configuration shows host encryption enabled and temporary data is protected as required.
  4. The targeted VM reports the required security updates installed with service continuity preserved.

Explanation

Correct Answer

B:

This validates the specific control for azure disk encryption key vault dependency: Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. The associated corrective action is: Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies. Testing a different component would not establish this result.

Incorrect Answers

A:

JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. “Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration” would address that alternative cause, not the condition in this question: azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk.

C:

“Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability” responds to this separate finding: guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. This question instead needs “Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies”, so the alternative does not meet the stated condition.

D:

Azure resource deployment health does not automatically establish guest operating system patch compliance. “Apply approved Azure Update Manager or supported guest patch orchestration and verify patch installation” applies to that separate problem. The observed case is a legacy VM uses Azure Disk Encryption but a required Key Vault key or secret is disabled during rotation and the VM cannot unlock encrypted volumes; choosing this alternative would address the wrong failure mode.

Question 189

During a cloud security review, the operations team observes: A hub appliance receives packets from a spoke VNet, but forwarding to another spoke fails because peerings were configured only for ordinary direct VNet traffic. Which operating control most directly reduces this recurring risk?

  1. Validate both directions of protected flows after any UDR, peering or subnet address change.
  2. Validate ASG membership as part of VM deployment and automated network acceptance tests.
  3. Test actual outbound reachability instead of relying on the presence of an NSG attachment alone.
  4. Test forwarded-traffic settings and route tables together when adding new peerings.

Explanation

Correct Answer

D:

This guardrail addresses vnet peering forwarded traffic setting: The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. The prevention measure is: Test forwarded-traffic settings and route tables together when adding new peerings. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. “Validate both directions of protected flows after any UDR, peering or subnet address change” would address that alternative cause, not the condition in this question: the necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.

B:

“Validate ASG membership as part of VM deployment and automated network acceptance tests” responds to this separate finding: an ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. This question instead needs “Test forwarded-traffic settings and route tables together when adding new peerings”, so the alternative does not meet the stated condition.

C:

Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. “Test actual outbound reachability instead of relying on the presence of an NSG attachment alone” applies to that separate problem. The observed case is a hub appliance receives packets from a spoke VNet, but forwarding to another spoke fails because peerings were configured only for ordinary direct VNet traffic; choosing this alternative would address the wrong failure mode.

Question 190

During a cloud security review, the operations team observes: A Terraform change introduces publicly reachable database configuration, but teams review only whether the deployment pipeline passed syntax validation. What should the engineer implement first to address the weakness?

  1. Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment.
  2. Enable the applicable App Service workload protection and route findings to the approved responder queue.
  3. Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook.
  4. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.

Explanation

Correct Answer

A:

The cause is: Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The appropriate change is: Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment. Verify it with this outcome: The updated template passes the security assessment and the deployed database is not unintentionally public.

Incorrect Answers

B:

This action concerns defender for app service protection plan, where Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. The reported incident instead involves Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls.

C:

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 corrective response here is “Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment”; this alternative does not provide that response.

D:

This action concerns defender vulnerability management remediation validation, where A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The stem reports a Terraform change introduces publicly reachable database configuration, but teams review only whether the deployment pipeline passed syntax validation; this control addresses a different failure condition.