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 77

Question 760

A regulated Azure tenant has this security condition: An application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress. Which result confirms the relevant security control is effective?

  1. Direct origin requests are rejected while requests passing the edge WAF are served.
  2. The identified next hop matches the approved routing design after changes, with no unintended appliance loop.
  3. Front Door continues serving approved requests but direct Internet calls to the origin are blocked.
  4. The security team queries the required firewall rule-match records for a controlled test flow.

Explanation

Correct Answer

B:

This validates the specific control for network watcher next hop diagnosis: A user-defined or propagated route controls the next hop independently of NSG allow decisions. The associated corrective action is: Inspect effective routes and run Network Watcher next hop against the intended destination IP. Testing a different component would not establish this result.

Incorrect Answers

A:

The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. “Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable” would address that alternative cause, not the condition in this question: a user-defined or propagated route controls the next hop independently of NSG allow decisions.

C:

“Configure a supported Private Link origin and restrict direct public access to the origin service” responds to this separate finding: the Front Door origin connection is not constrained through a supported private-link origin with public access restriction. This question instead needs “Inspect effective routes and run Network Watcher next hop against the intended destination IP”, so the alternative does not meet the stated condition.

D:

Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. “Configure relevant firewall diagnostic categories and secure retention for rule and threat events” applies to that separate problem. The observed case is an application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress; choosing this alternative would address the wrong failure mode.

Question 761

While validating an Azure workload, the security team finds: An AKS cluster is enrolled in Azure and its nodes receive basic VM updates, but cluster configuration threats and workload alerts are not monitored. Which result confirms the relevant security control is effective?

  1. The cluster reports supported posture assessments and security alerts for its monitored Kubernetes workloads.
  2. The new project's eligible repositories appear with relevant infrastructure-as-code findings or documented exclusions.
  3. A matching test alert triggers the intended notification or ticket while unrelated findings do not invoke it.
  4. The critical exposed resource is patched or protected first and the residual exposure is documented.

Explanation

Correct Answer

A:

This validates the specific control for defender for containers kubernetes posture: Node management alone does not provide full supported Defender for Containers security posture and workload protection. The associated corrective action is: Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster. Testing a different component would not establish this result.

Incorrect Answers

B:

A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. “Review project and repository connector coverage and enable the supported assessment pipeline for the missing project” would address that alternative cause, not the condition in this question: node management alone does not provide full supported Defender for Containers security posture and workload protection.

C:

“Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook” responds to this separate finding: a Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. This question instead needs “Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster”, so the alternative does not meet the stated condition.

D:

Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. “Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw” applies to that separate problem. The observed case is an AKS cluster is enrolled in Azure and its nodes receive basic VM updates, but cluster configuration threats and workload alerts are not monitored; choosing this alternative would address the wrong failure mode.

Question 762

A platform security assessment reveals this issue: Password spray attacks target a legacy authentication protocol that does not support modern MFA controls, but the organization only requires MFA for interactive clients. What observation is the strongest validation evidence?

  1. A test sign-in with only MFA fails, while one meeting both MFA and device compliance succeeds.
  2. An SMS-only sign-in fails the privileged requirement while an authorized phishing-resistant method succeeds.
  3. The targeted legacy authentication attempt is rejected while modern approved sign-in remains operational.
  4. A lost key can be revoked and replaced without allowing unverified MFA bypass.

Explanation

Correct Answer

C:

This validates the specific control for legacy authentication blocking: The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. The associated corrective action is: Create a policy that blocks legacy client authentication for the necessary users and applications. Testing a different component would not establish this result.

Incorrect Answers

A:

The grant control operator allows any selected requirement rather than requiring all specified requirements. “Select the required combination of grant controls and confirm the intended AND behavior” would address that alternative cause, not the condition in this question: the tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities.

B:

“Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods” responds to this separate finding: the selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. This question instead needs “Create a policy that blocks legacy client authentication for the necessary users and applications”, so the alternative does not meet the stated condition.

D:

Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. “Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification” applies to that separate problem. The observed case is password spray attacks target a legacy authentication protocol that does not support modern MFA controls, but the organization only requires MFA for interactive clients; choosing this alternative would address the wrong failure mode.

Question 763

During a cloud security review, the operations team observes: An Azure subscription suddenly has a new Owner and the incident team inspects VM guest logs instead of Azure resource authorization events. Which operating control most directly reduces this recurring risk?

  1. Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective.
  2. Monitor and retain Azure role assignment changes through the correct governance logging pipeline.
  3. Review eligible and active group membership together with inherited resource role effects.
  4. Set activation duration according to risk and monitor unusually long privilege activations.

Explanation

Correct Answer

B:

This guardrail addresses role assignment audit history: Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. The prevention measure is: Monitor and retain Azure role assignment changes through the correct governance logging pipeline. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. “Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective” would address that alternative cause, not the condition in this question: azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs.

C:

“Review eligible and active group membership together with inherited resource role effects” responds to this separate finding: permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. This question instead needs “Monitor and retain Azure role assignment changes through the correct governance logging pipeline”, so the alternative does not meet the stated condition.

D:

The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. “Set activation duration according to risk and monitor unusually long privilege activations” applies to that separate problem. The observed case is an Azure subscription suddenly has a new Owner and the incident team inspects VM guest logs instead of Azure resource authorization events; choosing this alternative would address the wrong failure mode.

Question 764

During a cloud security review, the operations team observes: A support analyst runs SELECT against a customer table and sees full personal identifiers although the business requirement is to mask those fields for nonprivileged readers. After remediation, which test result best proves the intended change?

  1. A low-privilege test user sees masked values while approved privileged users follow their allowed data access.
  2. Sensitive columns remain encrypted to the database engine while authorized clients decrypt needed values.
  3. The database reports TDE enabled and encrypted at-rest backups while client connections remain supported.
  4. A controlled database operation produces an accessible audit record with principal and action details.

Explanation

Correct Answer

A:

This validates the specific control for dynamic data masking limited disclosure: SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. The associated corrective action is: Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers. Testing a different component would not establish this result.

Incorrect Answers

B:

TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. “Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients” would address that alternative cause, not the condition in this question: sQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege.

C:

“Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration” responds to this separate finding: tLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. This question instead needs “Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers”, so the alternative does not meet the stated condition.

D:

Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. “Enable supported SQL auditing with the necessary categories and protected retention settings” applies to that separate problem. The observed case is a support analyst runs SELECT against a customer table and sees full personal identifiers although the business requirement is to mask those fields for nonprivileged readers; choosing this alternative would address the wrong failure mode.

Question 765

A Microsoft Azure administrator receives this requirement: A vault administrator sees a burst of unexpected secret retrievals from an unfamiliar source but relies only on manually reviewing activity history once per month. Which underlying control gap is responsible for the issue?

  1. Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue.
  2. DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.
  3. Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations.
  4. A DevOps connector does not guarantee automatic security scan visibility for every new project and repository.

Explanation

Correct Answer

C:

The described technical condition is: Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations. The appropriate corrective action is: Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access. Confirm with: Security operations receive actionable alert context tied to an unusual Key Vault access pattern.

Incorrect Answers

A:

Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. “Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw” would address that alternative cause, not the condition in this question: vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations.

B:

“Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories” responds to this separate finding: devOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. This question instead needs “Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access”, so the alternative does not meet the stated condition.

D:

A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. “Review project and repository connector coverage and enable the supported assessment pipeline for the missing project” applies to that separate problem. The observed case is a vault administrator sees a burst of unexpected secret retrievals from an unfamiliar source but relies only on manually reviewing activity history once per month; choosing this alternative would address the wrong failure mode.

Question 766

A platform security assessment reveals this issue: An audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions. What technical cause best accounts for the described behavior?

  1. A PIM eligible assignment is not an active role grant until the user completes the configured activation process.
  2. Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.
  3. The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.
  4. Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted.

Explanation

Correct Answer

C:

The described technical condition is: The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. The appropriate corrective action is: Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized. Confirm with: An authorized test modifies the intended tags while the operator retains no additional administration privileges.

Incorrect Answers

A:

A PIM eligible assignment is not an active role grant until the user completes the configured activation process. “Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change” would address that alternative cause, not the condition in this question: the Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.

B:

“Assign the approved read-only role at a suitable management group with the intended child subscription coverage” responds to this separate finding: per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. This question instead needs “Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized”, so the alternative does not meet the stated condition.

D:

Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope” applies to that separate problem. The observed case is an audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions; choosing this alternative would address the wrong failure mode.

Question 767

The cloud operations team reviews the following risk: Kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job. Which safeguard would best prevent this issue from recurring?

  1. Test backup restore and deletion resistance periodically under approved adversarial scenarios.
  2. Use private API endpoint requirements during AKS cluster provisioning and access reviews.
  3. Review local secret storage during VM image automation and prefer managed identities and Key Vault.
  4. Review AKS role assignments and test actual API privileges for nonadministrative principals.

Explanation

Correct Answer

D:

This guardrail addresses aks microsoft entra and kubernetes rbac: Cluster authorization is not aligned with identity-based RBAC and separation of duties. The prevention measure is: Review AKS role assignments and test actual API privileges for nonadministrative principals. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. “Test backup restore and deletion resistance periodically under approved adversarial scenarios” would address that alternative cause, not the condition in this question: cluster authorization is not aligned with identity-based RBAC and separation of duties.

B:

“Use private API endpoint requirements during AKS cluster provisioning and access reviews” responds to this separate finding: the cluster uses a public API server endpoint rather than a supported private AKS cluster design. This question instead needs “Review AKS role assignments and test actual API privileges for nonadministrative principals”, so the alternative does not meet the stated condition.

C:

Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. “Review local secret storage during VM image automation and prefer managed identities and Key Vault” applies to that separate problem. The observed case is kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job; choosing this alternative would address the wrong failure mode.

Question 768

A regulated Azure tenant has this security condition: A SOC imports suspicious IP indicators into Sentinel once and uses the unchanged list indefinitely without considering expiry or source reliability. Which explanation fits the observed symptoms most closely?

  1. A saved KQL query does not generate incidents until a supported analytic rule is enabled with schedule and alert grouping settings.
  2. Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation.
  3. Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.
  4. Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended.

Explanation

Correct Answer

B:

The described technical condition is: Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. The appropriate corrective action is: Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics. Confirm with: Expired indicators stop driving automatic actions and fresh verified indicators can be correlated with current events.

Incorrect Answers

A:

A saved KQL query does not generate incidents until a supported analytic rule is enabled with schedule and alert grouping settings. “Create or enable the scheduled analytic rule with appropriate query frequency, lookback and incident configuration” would address that alternative cause, not the condition in this question: threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation.

C:

“Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” responds to this separate finding: workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. This question instead needs “Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics”, 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 imports suspicious IP indicators into Sentinel once and uses the unchanged list indefinitely without considering expiry or source reliability; choosing this alternative would address the wrong failure mode.

Question 769

While validating an Azure workload, the security team finds: A financial services team needs internal cryptographic-key controls shown alongside standard assessments, but no built-in assessment matches their policy. Which explanation fits the observed symptoms most closely?

  1. A multicloud connector can exist while its required permissions, services or security plan settings are incomplete.
  2. DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope.
  3. An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed.
  4. Custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions.

Explanation

Correct Answer

D:

The described technical condition is: Custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions. The appropriate corrective action is: Build the supported custom standard from approved Azure Policy content and map its controls to the organization's documented obligations. Confirm with: The custom standard displays measurable compliance results for relevant encrypted resources rather than unsupported manual declarations.

Incorrect Answers

A:

A multicloud connector can exist while its required permissions, services or security plan settings are incomplete. “Review and repair the AWS connector's authorized access and enable applicable posture assessment capabilities” would address that alternative cause, not the condition in this question: custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions.

B:

“Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope” responds to this separate finding: deployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. This question instead needs “Build the supported custom standard from approved Azure Policy content and map its controls to the organization's documented obligations”, so the alternative does not meet the stated condition.

C:

An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. “Validate exemption justification, owner, expiry and business controls or actually remediate the resource” applies to that separate problem. The observed case is a financial services team needs internal cryptographic-key controls shown alongside standard assessments, but no built-in assessment matches their policy; choosing this alternative would address the wrong failure mode.

Question 770

An Azure security engineer investigates the following incident: A security team deploys a WAF at Azure Front Door but clients can bypass all filtering by requesting the publicly reachable origin hostname directly. Which outcome most clearly verifies that the issue is resolved?

  1. A controlled policy review confirms protection coverage and attack telemetry for the targeted public endpoint.
  2. The security team queries the required firewall rule-match records for a controlled test flow.
  3. Direct origin requests are rejected while requests passing the edge WAF are served.
  4. Diagnostics identify the exact applicable rule and the corrected flow matches approved connectivity.

Explanation

Correct Answer

C:

This validates the specific control for front door origin bypass mitigation: The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. The associated corrective action is: Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable. Testing a different component would not establish this result.

Incorrect Answers

A:

An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. “Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources” would address that alternative cause, not the condition in this question: the origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path.

B:

“Configure relevant firewall diagnostic categories and secure retention for rule and threat events” responds to this separate finding: required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. This question instead needs “Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable”, so the alternative does not meet the stated condition.

D:

The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. “Run Network Watcher IP flow verify with the test source, destination, direction and port” applies to that separate problem. The observed case is a security team deploys a WAF at Azure Front Door but clients can bypass all filtering by requesting the publicly reachable origin hostname directly; choosing this alternative would address the wrong failure mode.