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 94

Question 930

During a cloud security review, the operations team observes: A recently acquired corporate domain hosts forgotten Internet-exposed services that are absent from internal Azure subscription inventory. Which recurring validation best protects against the observed problem?

  1. Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes.
  2. Require attribution evidence and review of discovered assets before initiating high-impact external remediation.
  3. Review the organization-specific regulatory standard list and scoped assessment coverage at each audit cycle.
  4. Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts.

Explanation

Correct Answer

A:

This guardrail addresses defender easm externally visible asset discovery: Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. The prevention measure is: Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. “Require attribution evidence and review of discovered assets before initiating high-impact external remediation” would address that alternative cause, not the condition in this question: internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet.

C:

“Review the organization-specific regulatory standard list and scoped assessment coverage at each audit cycle” responds to this separate finding: additional regulatory compliance standards require supported selection, assessment availability and assignment at the appropriate management scope. This question instead needs “Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes”, so the alternative does not meet the stated condition.

D:

Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. “Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts” applies to that separate problem. The observed case is a recently acquired corporate domain hosts forgotten Internet-exposed services that are absent from internal Azure subscription inventory; choosing this alternative would address the wrong failure mode.

Question 931

An Azure security engineer investigates the following incident: Password spray attacks target a legacy authentication protocol that does not support modern MFA controls, but the organization only requires MFA for interactive clients. Which explanation fits the observed symptoms most closely?

  1. The targeted policy does not include the guest or external user population for the protected application.
  2. The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow.
  3. The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities.
  4. The named location definition is stale and no longer reflects current verified branch egress address ranges.

Explanation

Correct Answer

C:

The described technical condition is: The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. The appropriate corrective action is: Create a policy that blocks legacy client authentication for the necessary users and applications. Confirm with: The targeted legacy authentication attempt is rejected while modern approved sign-in remains operational.

Incorrect Answers

A:

The targeted policy does not include the guest or external user population for the protected application. “Extend the policy to the correct external-user categories and trust settings using supported B2B controls” 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:

“Add an appropriately scoped Conditional Access grant control requiring a compliant device, with emergency exceptions” responds to this separate finding: the Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. 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:

The named location definition is stale and no longer reflects current verified branch egress address ranges. “Update the trusted named location with validated new egress ranges and test the affected policy conditions” 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 932

An Azure security engineer investigates the following incident: A secret-reading application was migrated to a Key Vault private endpoint but continues resolving the vault hostname to a public IP address. Which outcome most clearly verifies that the issue is resolved?

  1. A protected backup deletion request fails until a separate authorized security approver grants the required permission.
  2. A new prohibited public IP deployment is rejected while existing resources appear in policy compliance reporting.
  3. Authorized operators can restore data while prohibited backup protection reduction operations are rejected.
  4. The application resolves the vault to its approved private address and secret retrieval succeeds without public vault access.

Explanation

Correct Answer

D:

This validates the specific control for key vault private endpoint dns resolution: Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client. The associated corrective action is: Link the appropriate privatelink vault DNS zone and verify correct private records from the application virtual network. Testing a different component would not establish this result.

Incorrect Answers

A:

Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. “Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers” 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.

B:

“Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type” responds to this separate finding: the Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect. 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.

C:

An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. “Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing” 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 933

A Microsoft Azure administrator receives this requirement: An API gateway exposes internal APIs using a publicly accessible endpoint even though clients and backends are expected to remain on private networks. After remediation, which test result best proves the intended change?

  1. Application Gateway reports healthy targets and completes an end-to-end request to the application.
  2. Deprecated TLS clients fail negotiation while approved modern clients connect securely.
  3. Authorized internal clients call the API through a permitted private path and public probes fail.
  4. Controlled malicious request patterns are blocked while normal requests pass and logs record rule decisions.

Explanation

Correct Answer

C:

This validates the specific control for api management private network access: The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. The associated corrective action is: Configure a supported APIM private networking option and restrict public gateway exposure as required. Testing a different component would not establish this result.

Incorrect Answers

A:

The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. “Correct the custom health probe to match the actual service endpoint and backend settings” would address that alternative cause, not the condition in this question: the chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary.

B:

“Set the supported minimum TLS version to an approved modern value and verify certificate configuration” 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 “Configure a supported APIM private networking option and restrict public gateway exposure as required”, so the alternative does not meet the stated condition.

D:

The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. “After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener” applies to that separate problem. The observed case is an API gateway exposes internal APIs using a publicly accessible endpoint even though clients and backends are expected to remain on private networks; choosing this alternative would address the wrong failure mode.

Question 934

A platform security assessment reveals this issue: A privileged engineer is eligible for Owner through Microsoft Entra PIM but attempts to change subscription access without activating the assignment. What observation is the strongest validation evidence?

  1. The analyst lists authorized blobs with Entra authentication but cannot change account-level configuration.
  2. Authorized tagged blobs can be updated while attempted writes to excluded blobs are rejected.
  3. The protected operation succeeds during the approved activation window and fails after activation expires.
  4. The operator views security inventory in both existing and newly attached eligible subscriptions.

Explanation

Correct Answer

C:

This validates the specific control for pim eligible versus active role: A PIM eligible assignment is not an active role grant until the user completes the configured activation process. The associated corrective action is: Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” would address that alternative cause, not the condition in this question: a PIM eligible assignment is not an active role grant until the user completes the configured activation process.

B:

“Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” 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 “Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change”, so the alternative does not meet the stated condition.

D:

Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. “Assign the approved read-only role at a suitable management group with the intended child subscription coverage” applies to that separate problem. The observed case is a privileged engineer is eligible for Owner through Microsoft Entra PIM but attempts to change subscription access without activating the assignment; choosing this alternative would address the wrong failure mode.

Question 935

A platform security assessment reveals this issue: Two site-to-site VPN peers disagree on encryption and integrity parameters, preventing IKE negotiation even though their public endpoints are reachable. What should the engineer implement first to address the weakness?

  1. Adjust Azure Firewall private IP ranges and route design to preserve source addresses for approved private traffic.
  2. Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation.
  3. Align supported IPsec/IKE policy, keys and proposal parameters between the two authorized peers.
  4. Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies.

Explanation

Correct Answer

C:

The cause is: The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings. The appropriate change is: Align supported IPsec/IKE policy, keys and proposal parameters between the two authorized peers. Verify it with this outcome: The tunnel establishes with the intended cryptographic suite and routes pass protected traffic.

Incorrect Answers

A:

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 reported incident instead involves The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings.

B:

This action concerns firewall threat intelligence mode, where The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. The corrective response here is “Align supported IPsec/IKE policy, keys and proposal parameters between the two authorized peers”; this alternative does not provide that response.

D:

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 stem reports two site-to-site VPN peers disagree on encryption and integrity parameters, preventing IKE negotiation even though their public endpoints are reachable; this control addresses a different failure condition.

Question 936

The cloud operations team reviews the following risk: An AKS public API endpoint remains reachable from any source address though administration should originate only from a controlled office IP range. What governance practice would best prevent the same failure?

  1. Review app revision changes for insecure arguments and secret-reference drift.
  2. Recheck API authorization ranges whenever management egress IPs change.
  3. Review Container Apps ingress exposure after new revisions and environment changes.
  4. Scan container deployment manifests and logs for accidentally exposed credentials.

Explanation

Correct Answer

B:

This guardrail addresses aks api server authorized ip ranges: The cluster's public API server authorized IP ranges were not configured for restricted administrative access. The prevention measure is: Recheck API authorization ranges whenever management egress IPs change. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. “Review app revision changes for insecure arguments and secret-reference drift” would address that alternative cause, not the condition in this question: the cluster's public API server authorized IP ranges were not configured for restricted administrative access.

C:

“Review Container Apps ingress exposure after new revisions and environment changes” responds to this separate finding: the application's ingress configuration enables external exposure instead of internal-only routing. This question instead needs “Recheck API authorization ranges whenever management egress IPs change”, so the alternative does not meet the stated condition.

D:

Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. “Scan container deployment manifests and logs for accidentally exposed credentials” applies to that separate problem. The observed case is an AKS public API endpoint remains reachable from any source address though administration should originate only from a controlled office IP range; choosing this alternative would address the wrong failure mode.

Question 937

An Azure security engineer investigates the following incident: A broad Conditional Access policy blocks all administrators including both recovery accounts, leaving no viable emergency access route after a policy misconfiguration. Which explanation fits the observed symptoms most closely?

  1. Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle.
  2. The policy targets protected emergency principals without the approved tightly controlled recovery exclusions.
  3. The grant control operator allows any selected requirement rather than requiring all specified requirements.
  4. The targeted policy does not include the guest or external user population for the protected application.

Explanation

Correct Answer

B:

The described technical condition is: The policy targets protected emergency principals without the approved tightly controlled recovery exclusions. The appropriate corrective action is: Apply the documented emergency access exclusion and protect recovery identities with independent safeguards. Confirm with: A supervised break-glass validation succeeds while ordinary privileged users remain subject to strong controls.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the policy targets protected emergency principals without the approved tightly controlled recovery exclusions.

C:

“Select the required combination of grant controls and confirm the intended AND behavior” responds to this separate finding: the grant control operator allows any selected requirement rather than requiring all specified requirements. This question instead needs “Apply the documented emergency access exclusion and protect recovery identities with independent safeguards”, so the alternative does not meet the stated condition.

D:

The targeted policy does not include the guest or external user population for the protected application. “Extend the policy to the correct external-user categories and trust settings using supported B2B controls” applies to that separate problem. The observed case is a broad Conditional Access policy blocks all administrators including both recovery accounts, leaving no viable emergency access route after a policy misconfiguration; choosing this alternative would address the wrong failure mode.

Question 938

A platform security assessment reveals this issue: A company wants consumers in other VNets to access its internally hosted load-balanced service privately without exposing a public listener. What is the most appropriate corrective step?

  1. Enable supported private endpoint network policies for the subnet and validate the intended NSG controls.
  2. Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval.
  3. Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service.
  4. Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage.

Explanation

Correct Answer

B:

The cause is: The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. The appropriate change is: Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval. Verify it with this outcome: Authorized consumer private endpoints connect to the provider service while unapproved consumers are rejected.

Incorrect Answers

A:

This action concerns private endpoint subnet network policies, where Private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. The reported incident instead involves The provider has not published a supported Private Link Service behind an eligible standard internal load balancer.

C:

This action concerns private endpoint versus service endpoint isolation, where Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. The corrective response here is “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval”; this alternative does not provide that response.

D:

This action concerns vnet service endpoint network scope, where The required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. The stem reports a company wants consumers in other VNets to access its internally hosted load-balanced service privately without exposing a public listener; this control addresses a different failure condition.

Question 939

While validating an Azure workload, the security team finds: A container image with known vulnerable packages is pulled into production AKS because teams check only that the registry login succeeds. Which configuration change most directly resolves this problem?

  1. Use controlled SSH public-key authentication and restrict access through Bastion or approved private management.
  2. Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation.
  3. Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals.
  4. Configure workload identity on the service account and scoped access to the target Key Vault.

Explanation

Correct Answer

B:

The cause is: Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. The appropriate change is: Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation. Verify it with this outcome: The vulnerable image is detected and a patched replacement is deployed before production exposure.

Incorrect Answers

A:

This action concerns linux ssh key management, where Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. The reported incident instead involves Authentication to a container registry does not establish that deployed images meet vulnerability security requirements.

C:

This action concerns managed disk snapshot permission scope, where Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. The corrective response here is “Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation”; this alternative does not provide that response.

D:

This action concerns aks workload identity federation, where The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. The stem reports a container image with known vulnerable packages is pulled into production AKS because teams check only that the registry login succeeds; this control addresses a different failure condition.

Question 940

A Microsoft Azure administrator receives this requirement: A business-critical public IP in an Azure VNet is exposed to volumetric attacks but the organization relies only on application WAF rules. What observation is the strongest validation evidence?

  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. Authorized flow records are available for investigation with correct source, destination and decision context.
  4. The identified next hop matches the approved routing design after changes, with no unintended appliance loop.

Explanation

Correct Answer

A:

This validates the specific control for ddos protection virtual network coverage: An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. The associated corrective action is: Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources. Testing a different component would not establish this result.

Incorrect Answers

B:

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” would address that alternative cause, not the condition in this question: an application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs.

C:

“Enable the supported Virtual Network flow logs and associated analytics or storage retention” responds to this separate finding: network flow logging has not been configured for the relevant virtual network monitoring scope. This question instead needs “Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources”, so the alternative does not meet the stated condition.

D:

A user-defined or propagated route controls the next hop independently of NSG allow decisions. “Inspect effective routes and run Network Watcher next hop against the intended destination IP” applies to that separate problem. The observed case is a business-critical public IP in an Azure VNet is exposed to volumetric attacks but the organization relies only on application WAF rules; choosing this alternative would address the wrong failure mode.