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 41

Question 400

A Microsoft Azure administrator receives this requirement: A spoke-to-datacenter private flow is unexpectedly source-translated, making the backend see the firewall address instead of the original client IP. Which operating control most directly reduces this recurring risk?

  1. Review firewall SNAT private-range configuration after acquiring new hybrid address spaces.
  2. Periodically validate threat intelligence enforcement mode and false-positive handling.
  3. Validate tunnel state and dynamic route exchange independently during VPN acceptance.
  4. Test routing intent against all hub connections rather than assuming firewall presence enforces steering.

Explanation

Correct Answer

A:

This guardrail addresses azure firewall snat private range design: The firewall's configured private address space for SNAT exemption omits the datacenter destination range. The prevention measure is: Review firewall SNAT private-range configuration after acquiring new hybrid address spaces. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. “Periodically validate threat intelligence enforcement mode and false-positive handling” would address that alternative cause, not the condition in this question: the firewall's configured private address space for SNAT exemption omits the datacenter destination range.

C:

“Validate tunnel state and dynamic route exchange independently during VPN acceptance” responds to this separate finding: the encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. This question instead needs “Review firewall SNAT private-range configuration after acquiring new hybrid address spaces”, so the alternative does not meet the stated condition.

D:

The secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured. “Test routing intent against all hub connections rather than assuming firewall presence enforces steering” applies to that separate problem. The observed case is a spoke-to-datacenter private flow is unexpectedly source-translated, making the backend see the firewall address instead of the original client IP; choosing this alternative would address the wrong failure mode.

Question 401

During a cloud security review, the operations team observes: A Windows operations team wants SSH clients to reach private Linux VMs, but the deployment assumes every connection must expose the VM on a public IP. What observation is the strongest validation evidence?

  1. An approved SSH client reaches the private VM through Bastion without a VM public IP.
  2. The disk references the approved encryption set and retains correct key-access connectivity.
  3. The targeted VM reports the required security updates installed with service continuity preserved.
  4. A test request from the approved address succeeds temporarily while arbitrary Internet sources remain denied.

Explanation

Correct Answer

A:

This validates the specific control for bastion native client security control: Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. The associated corrective action is: Use a supported Bastion native-client connection and required RBAC and network prerequisites. Testing a different component would not establish this result.

Incorrect Answers

B:

Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. “Configure the encryption set and supported Key Vault key permissions, then associate eligible disks” would address that alternative cause, not the condition in this question: supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow.

C:

“Apply approved Azure Update Manager or supported guest patch orchestration and verify patch installation” responds to this separate finding: azure resource deployment health does not automatically establish guest operating system patch compliance. This question instead needs “Use a supported Bastion native-client connection and required RBAC and network prerequisites”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a Windows operations team wants SSH clients to reach private Linux VMs, but the deployment assumes every connection must expose the VM on a public IP; choosing this alternative would address the wrong failure mode.

Question 402

A regulated Azure tenant has this security condition: A pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure. Which result confirms the relevant security control is effective?

  1. A deletion attempt cannot immediately eradicate protected backup recovery points and recovery remains possible.
  2. The pod obtains a short-lived token and reads only the approved secret without stored client secrets.
  3. An unauthorized operator cannot generate snapshot access while recovery administrators retain documented access.
  4. Approved application flows succeed while prohibited cross-namespace traffic is dropped.

Explanation

Correct Answer

B:

This validates the specific control for aks workload identity federation: The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. The associated corrective action is: Configure workload identity on the service account and scoped access to the target Key Vault. Testing a different component would not establish this result.

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: the workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.

C:

“Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals” responds to this separate finding: snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. This question instead needs “Configure workload identity on the service account and scoped access to the target Key Vault”, so the alternative does not meet the stated condition.

D:

Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. “Enable the supported network policy option and enforce namespace/pod label based allowlists” applies to that separate problem. The observed case is a pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure; choosing this alternative would address the wrong failure mode.

Question 403

A Microsoft Azure administrator receives this requirement: A GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments. Which underlying control gap is responsible for the issue?

  1. A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified.
  2. Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan.
  3. DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.
  4. Control-plane Resource Manager activity can require dedicated detection separate from guest server security events.

Explanation

Correct Answer

C:

The described technical condition is: DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. The appropriate corrective action is: Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories. Confirm with: The previously omitted repositories appear in DevOps Security findings and receive appropriate code scanning coverage.

Incorrect Answers

A:

A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. “Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation” would address that alternative cause, not the condition in this question: devOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.

B:

“Enable the appropriate Defender for SQL or Databases protection plan and configure supported alert routing” responds to this separate finding: database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. This question instead needs “Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories”, so the alternative does not meet the stated condition.

D:

Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. “Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators” applies to that separate problem. The observed case is a GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments; choosing this alternative would address the wrong failure mode.

Question 404

A Microsoft Azure administrator receives this requirement: Database administrators can see sensitive customer identifiers in plaintext despite a policy requiring only client applications to decrypt those values. What technical cause best accounts for the described behavior?

  1. Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.
  2. Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model.
  3. The file access path needs compatible secure SMB protocol and supported encrypted transport settings.
  4. TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing.

Explanation

Correct Answer

D:

The described technical condition is: TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. The appropriate corrective action is: Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients. Confirm with: Sensitive columns remain encrypted to the database engine while authorized clients decrypt needed values.

Incorrect Answers

A:

Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. “Configure supported SQL driver encryption with certificate chain and hostname validation enabled” would address that alternative cause, not the condition in this question: tDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing.

B:

“Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs” responds to this separate finding: shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. This question instead needs “Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients”, so the alternative does not meet the stated condition.

C:

The file access path needs compatible secure SMB protocol and supported encrypted transport settings. “Use supported modern SMB client configuration and private connectivity or TLS where applicable” applies to that separate problem. The observed case is database administrators can see sensitive customer identifiers in plaintext despite a policy requiring only client applications to decrypt those values; choosing this alternative would address the wrong failure mode.

Question 405

During a cloud security review, the operations team observes: An application needs to send DNS queries to a custom resolver over UDP, but Azure Firewall has only an HTTPS application rule for the resolver host. Which operating control most directly reduces this recurring risk?

  1. Track central security admin policy impacts before granting application network exceptions.
  2. Review exposed DNAT entries against asset owners and remove obsolete Internet listeners.
  3. Audit shared gateway peering settings whenever a new spoke joins the hub.
  4. Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy.

Explanation

Correct Answer

D:

This guardrail addresses azure firewall network rule ip protocol: An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. The prevention measure is: Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

An enforced security admin deny rule has higher governance precedence than the workload NSG allow. “Track central security admin policy impacts before granting application network exceptions” would address that alternative cause, not the condition in this question: an HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.

B:

“Review exposed DNAT entries against asset owners and remove obsolete Internet listeners” responds to this separate finding: inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. This question instead needs “Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy”, so the alternative does not meet the stated condition.

C:

Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. “Audit shared gateway peering settings whenever a new spoke joins the hub” applies to that separate problem. The observed case is an application needs to send DNS queries to a custom resolver over UDP, but Azure Firewall has only an HTTPS application rule for the resolver host; choosing this alternative would address the wrong failure mode.

Question 406

A regulated Azure tenant has this security condition: A tenant permits employees to consent to any third-party application, resulting in a rogue app receiving broad mailbox-related scopes. What governance practice would best prevent the same failure?

  1. Version and review exposed API scopes so newly added privileges require explicit consent.
  2. Retain and monitor workload identity sign-in events separately from human sign-in telemetry.
  3. Review enterprise app permission grants and maintain a governed consent escalation process.
  4. Recertify high-impact OAuth application permissions and remove obsolete grants.

Explanation

Correct Answer

C:

This guardrail addresses user consent policies for third party apps: The user consent configuration permits risky OAuth grants without publisher and permission restrictions. The prevention measure is: Review enterprise app permission grants and maintain a governed consent escalation process. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The protected application registration has not exposed an OAuth permission scope for the required delegated operation. “Version and review exposed API scopes so newly added privileges require explicit consent” would address that alternative cause, not the condition in this question: the user consent configuration permits risky OAuth grants without publisher and permission restrictions.

B:

“Retain and monitor workload identity sign-in events separately from human sign-in telemetry” responds to this separate finding: non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. This question instead needs “Review enterprise app permission grants and maintain a governed consent escalation process”, so the alternative does not meet the stated condition.

D:

The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. “Recertify high-impact OAuth application permissions and remove obsolete grants” applies to that separate problem. The observed case is a tenant permits employees to consent to any third-party application, resulting in a rogue app receiving broad mailbox-related scopes; choosing this alternative would address the wrong failure mode.

Question 407

While validating an Azure workload, the security team finds: An administrator enables the Key Vault Azure RBAC permission model but assumes previously configured vault access policies still grant secret read operations. What governance practice would best prevent the same failure?

  1. Keep configuration policy checks separate from identity, data-plane and network access acceptance tests.
  2. Document the active Key Vault permission model and review role migration before switching authorization modes.
  3. Evaluate policy effect and assignment scope in predeployment tests before assuming an audit finding blocks resource creation.
  4. Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners.

Explanation

Correct Answer

B:

This guardrail addresses key vault rbac versus access policy authorization: Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active. The prevention measure is: Document the active Key Vault permission model and review role migration before switching authorization modes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. “Keep configuration policy checks separate from identity, data-plane and network access acceptance tests” would address that alternative cause, not the condition in this question: key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active.

C:

“Evaluate policy effect and assignment scope in predeployment tests before assuming an audit finding blocks resource creation” 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 “Document the active Key Vault permission model and review role migration before switching authorization modes”, so the alternative does not meet the stated condition.

D:

Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. “Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners” applies to that separate problem. The observed case is an administrator enables the Key Vault Azure RBAC permission model but assumes previously configured vault access policies still grant secret read operations; choosing this alternative would address the wrong failure mode.

Question 408

The cloud operations team reviews the following risk: 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 configuration change most directly resolves this problem?

  1. Associate intended eligible VNets with the correct plan and validate protection settings.
  2. Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable.
  3. Configure relevant firewall diagnostic categories and secure retention for rule and threat events.
  4. Run Network Watcher IP flow verify with the test source, destination, direction and port.

Explanation

Correct Answer

B:

The cause is: The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. The appropriate change is: Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable. Verify it with this outcome: Direct origin requests are rejected while requests passing the edge WAF are served.

Incorrect Answers

A:

This action concerns ddos plan coverage and ownership, where Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The reported incident instead involves The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path.

C:

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 corrective response here is “Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable”; this alternative does not provide that response.

D:

This action concerns network watcher ip flow verification, where The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. The stem reports a security team deploys a WAF at Azure Front Door but clients can bypass all filtering by requesting the publicly reachable origin hostname directly; this control addresses a different failure condition.

Question 409

A platform security assessment reveals this issue: Security analysts can query VM logs but cannot investigate anomalous Microsoft Entra sign-ins because identity logs are absent. Which recurring validation best protects against the observed problem?

  1. Monitor ingestion delay and align scheduled rule lookback to actual source latency.
  2. Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators.
  3. Test cloud identity telemetry coverage whenever tenant logging or connector permissions change.
  4. Review collection transformations for data minimization and unintended loss of detection-critical attributes.

Explanation

Correct Answer

C:

This guardrail addresses sentinel microsoft entra sign in connector: Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. The prevention measure is: Test cloud identity telemetry coverage whenever tenant logging or connector permissions change. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. “Monitor ingestion delay and align scheduled rule lookback to actual source latency” would address that alternative cause, not the condition in this question: microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions.

B:

“Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators” responds to this separate finding: threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. This question instead needs “Test cloud identity telemetry coverage whenever tenant logging or connector permissions change”, so the alternative does not meet the stated condition.

D:

Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. “Review collection transformations for data minimization and unintended loss of detection-critical attributes” applies to that separate problem. The observed case is security analysts can query VM logs but cannot investigate anomalous Microsoft Entra sign-ins because identity logs are absent; choosing this alternative would address the wrong failure mode.

Question 410

The cloud operations team reviews the following risk: A public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources. What governance practice would best prevent the same failure?

  1. Reassess API throttling limits and correlation identifiers following traffic-pattern changes.
  2. Review client certificate trust and renewal processes for all privileged API consumers.
  3. Test negative token cases after identity provider and APIM policy changes.
  4. Review APIM API and product access configuration when introducing new routes.

Explanation

Correct Answer

A:

This guardrail addresses apim throttling policy for abuse: The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. The prevention measure is: Reassess API throttling limits and correlation identifiers following traffic-pattern changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Review client certificate trust and renewal processes for all privileged API consumers” would address that alternative cause, not the condition in this question: the API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.

C:

“Test negative token cases after identity provider and APIM policy changes” responds to this separate finding: aPI Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. This question instead needs “Reassess API throttling limits and correlation identifiers following traffic-pattern changes”, so the alternative does not meet the stated condition.

D:

The API or product does not require the intended APIM subscription key or equivalent authentication control. “Review APIM API and product access configuration when introducing new routes” applies to that separate problem. The observed case is a public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources; choosing this alternative would address the wrong failure mode.