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 23

Question 220

A Microsoft Azure administrator receives this requirement: An App Service allows deprecated TLS versions for an API that handles sensitive data although newer clients support TLS 1.2 or later. Which operating control most directly reduces this recurring risk?

  1. Assess ASE deployment and subnet requirements before choosing it for strict regulated isolation.
  2. Test regional edge WAF policies with representative client source conditions and observe false positives.
  3. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  4. Track custom domain certificate validity and binding renewal before expiration.

Explanation

Correct Answer

C:

This guardrail addresses minimum tls protocol enforcement: The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. The prevention measure is: Test TLS protocol settings and certificate expiry after changes to public application endpoints. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. “Assess ASE deployment and subnet requirements before choosing it for strict regulated isolation” would address that alternative cause, not the condition in this question: the app's minimum TLS version configuration permits an outdated protocol that violates the security baseline.

B:

“Test regional edge WAF policies with representative client source conditions and observe false positives” responds to this separate finding: the access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. This question instead needs “Test TLS protocol settings and certificate expiry after changes to public application endpoints”, so the alternative does not meet the stated condition.

D:

The custom domain has no correct TLS certificate binding for the expected host name. “Track custom domain certificate validity and binding renewal before expiration” applies to that separate problem. The observed case is an App Service allows deprecated TLS versions for an API that handles sensitive data although newer clients support TLS 1.2 or later; choosing this alternative would address the wrong failure mode.

Question 221

During a cloud security review, the operations team observes: An incident automation rule calls a Logic App but the playbook cannot isolate an identified malicious IP because the workflow identity has no access to its firewall. What is the most appropriate corrective step?

  1. Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection.
  2. Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes.
  3. Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay.
  4. Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging.

Explanation

Correct Answer

A:

The cause is: Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. The appropriate change is: Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection. Verify it with this outcome: A controlled test incident causes the approved containment change and produces an auditable action record.

Incorrect Answers

B:

This action concerns sentinel data retention investigation needs, where Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. The reported incident instead involves Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents.

C:

This action concerns sentinel analytics frequency lookback mismatch, where A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. The corrective response here is “Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection”; this alternative does not provide that response.

D:

This action concerns network security diagnostic logs to log analytics, where Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. The stem reports an incident automation rule calls a Logic App but the playbook cannot isolate an identified malicious IP because the workflow identity has no access to its firewall; this control addresses a different failure condition.

Question 222

While validating an Azure workload, the security team finds: A regulated Azure SQL database must encrypt database files and backups at rest, but administrators focus only on the client TLS connection. Which remediation best addresses the specific issue?

  1. Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access.
  2. Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers.
  3. Configure the Microsoft Entra administrator and create appropriate contained database users and roles.
  4. Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration.

Explanation

Correct Answer

D:

The cause is: TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. The appropriate change is: Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration. Verify it with this outcome: The database reports TDE enabled and encrypted at-rest backups while client connections remain supported.

Incorrect Answers

A:

This action concerns azure sql private endpoint dns and public disable, where The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. The reported incident instead involves TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.

B:

This action concerns dynamic data masking limited disclosure, where SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. The corrective response here is “Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration”; this alternative does not provide that response.

C:

This action concerns azure sql microsoft entra administrator auth, where The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. The stem reports a regulated Azure SQL database must encrypt database files and backups at rest, but administrators focus only on the client TLS connection; this control addresses a different failure condition.

Question 223

A regulated Azure tenant has this security condition: A private endpoint connection is approved, but VMs keep resolving a storage hostname to the service's public IP from an unlinked VNet. Which safeguard would best prevent this issue from recurring?

  1. Review separate inbound private endpoint and outbound integration settings for each App Service.
  2. Verify DNS zone links and forwarders for all VNets consuming a private service.
  3. Inventory subnet service endpoint configuration and service firewall allowances together.
  4. Check supported private endpoint network policy settings before relying on subnet inspection rules.

Explanation

Correct Answer

B:

This guardrail addresses private dns zone linking for endpoint: The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. The prevention measure is: Verify DNS zone links and forwarders for all VNets consuming a private service. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. “Review separate inbound private endpoint and outbound integration settings for each App Service” would address that alternative cause, not the condition in this question: the private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address.

C:

“Inventory subnet service endpoint configuration and service firewall allowances together” responds to this separate finding: the required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. This question instead needs “Verify DNS zone links and forwarders for all VNets consuming a private service”, so the alternative does not meet the stated condition.

D:

Private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. “Check supported private endpoint network policy settings before relying on subnet inspection rules” applies to that separate problem. The observed case is a private endpoint connection is approved, but VMs keep resolving a storage hostname to the service's public IP from an unlinked VNet; choosing this alternative would address the wrong failure mode.

Question 224

A Microsoft Azure administrator receives this requirement: A Key Vault security team permits public network access for every client because some automation jobs cannot reach the vault after firewall restrictions. Which operating control most directly reduces this recurring risk?

  1. Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule.
  2. Audit Key Vault public exposure and the exact network dependencies of each application after changes.
  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 firewall trusted bypass scope: Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. The prevention measure is: Audit Key Vault public exposure and the exact network dependencies of each application after changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. “Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule” would address that alternative cause, not the condition in this question: key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads.

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 “Audit Key Vault public exposure and the exact network dependencies of each application after changes”, 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 a Key Vault security team permits public network access for every client because some automation jobs cannot reach the vault after firewall restrictions; choosing this alternative would address the wrong failure mode.

Question 225

A platform security assessment reveals this issue: Remote engineers connect to a virtual network using shared VPN credentials even though the requirement is individual identity verification and conditional access. Which recurring validation best protects against the observed problem?

  1. Reconcile VNet DNS settings with firewall proxy deployment during hub-spoke changes.
  2. Review point-to-site authentication configuration and certificate or client profile lifecycle regularly.
  3. Test parent-child firewall policy precedence when onboarding a new business workload.
  4. Test routing intent against all hub connections rather than assuming firewall presence enforces steering.

Explanation

Correct Answer

B:

This guardrail addresses point to site vpn entra authentication: The point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. The prevention measure is: Review point-to-site authentication configuration and certificate or client profile lifecycle regularly. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. “Reconcile VNet DNS settings with firewall proxy deployment during hub-spoke changes” would address that alternative cause, not the condition in this question: the point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration.

C:

“Test parent-child firewall policy precedence when onboarding a new business workload” responds to this separate finding: azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. This question instead needs “Review point-to-site authentication configuration and certificate or client profile lifecycle regularly”, 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 remote engineers connect to a virtual network using shared VPN credentials even though the requirement is individual identity verification and conditional access; choosing this alternative would address the wrong failure mode.

Question 226

During a cloud security review, the operations team observes: A spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet. Which recurring validation best protects against the observed problem?

  1. Review exposed DNAT entries against asset owners and remove obsolete Internet listeners.
  2. Review FQDN-based application rules for wildcard overreach and domain ownership changes.
  3. Review network group membership drift after subscription and resource tagging changes.
  4. Audit shared gateway peering settings whenever a new spoke joins the hub.

Explanation

Correct Answer

D:

This guardrail addresses gateway transit peering configuration: Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The prevention measure is: Audit shared gateway peering settings whenever a new spoke joins the hub. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. “Review exposed DNAT entries against asset owners and remove obsolete Internet listeners” would address that alternative cause, not the condition in this question: gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.

B:

“Review FQDN-based application rules for wildcard overreach and domain ownership changes” responds to this separate finding: a broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. This question instead needs “Audit shared gateway peering settings whenever a new spoke joins the hub”, so the alternative does not meet the stated condition.

C:

The dynamic network group criteria do not include the intended VNet attributes or scope. “Review network group membership drift after subscription and resource tagging changes” applies to that separate problem. The observed case is a spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet; choosing this alternative would address the wrong failure mode.

Question 227

An Azure security engineer investigates the following incident: An attacker overwrites a blob with incorrect content but its latest object still exists, and administrators have no prior version to restore. What governance practice would best prevent the same failure?

  1. Test storage account public network access and network rules after resource redeployment.
  2. Validate version history and lifecycle management for sensitive mutable blob data.
  3. Review data-plane RBAC separately from account administration roles for every application.
  4. Test customer-managed key rotation and access recovery before changing storage encryption configuration.

Explanation

Correct Answer

B:

This guardrail addresses blob versioning prior content recovery: Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The prevention measure is: Validate version history and lifecycle management for sensitive mutable blob data. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. “Test storage account public network access and network rules after resource redeployment” would address that alternative cause, not the condition in this question: blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning.

C:

“Review data-plane RBAC separately from account administration roles for every application” responds to this separate finding: management-plane storage Contributor does not necessarily include blob data read DataActions. This question instead needs “Validate version history and lifecycle management for sensitive mutable blob data”, so the alternative does not meet the stated condition.

D:

Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. “Test customer-managed key rotation and access recovery before changing storage encryption configuration” applies to that separate problem. The observed case is an attacker overwrites a blob with incorrect content but its latest object still exists, and administrators have no prior version to restore; choosing this alternative would address the wrong failure mode.

Question 228

The cloud operations team reviews the following risk: A detection emits separate incidents for dozens of identical events from one compromised user in a short interval, overwhelming triage. Which result confirms the relevant security control is effective?

  1. The generated incident displays the correct user and IP entities and can correlate related events.
  2. A controlled test incident causes the approved containment change and produces an auditable action record.
  3. The expected records appear only in approved production destinations and analysts can query them within the retention policy.
  4. A controlled burst of related events creates the documented consolidated incident without merging unrelated users.

Explanation

Correct Answer

D:

This validates the specific control for sentinel incident grouping duplicate alerts: Alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit. The associated corrective action is: Configure the supported analytic-rule event or alert grouping window and matching fields for the intended incident unit. Testing a different component would not establish this result.

Incorrect Answers

A:

Useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers. “Map the rule output's user account and IP fields to the appropriate Sentinel entity types and identifiers” would address that alternative cause, not the condition in this question: alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit.

B:

“Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection” responds to this separate finding: playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. This question instead needs “Configure the supported analytic-rule event or alert grouping window and matching fields for the intended incident unit”, so the alternative does not meet the stated condition.

C:

A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters” applies to that separate problem. The observed case is a detection emits separate incidents for dozens of identical events from one compromised user in a short interval, overwhelming triage; choosing this alternative would address the wrong failure mode.

Question 229

A production Azure security implementation shows this failure: Partners with B2B guest accounts can open a project management application even though the workforce policy requires stronger authentication only for employees. What is the most appropriate corrective step?

  1. Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods.
  2. Configure a justified sign-in frequency session control for the appropriate protected application.
  3. Extend the policy to the correct external-user categories and trust settings using supported B2B controls.
  4. Add an appropriately scoped Conditional Access grant control requiring a compliant device, with emergency exceptions.

Explanation

Correct Answer

C:

The cause is: The targeted policy does not include the guest or external user population for the protected application. The appropriate change is: Extend the policy to the correct external-user categories and trust settings using supported B2B controls. Verify it with this outcome: An external guest satisfies the required authentication challenge while unauthorized cross-tenant access is rejected.

Incorrect Answers

A:

This action concerns phishing resistant authentication strength, where The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. The reported incident instead involves The targeted policy does not include the guest or external user population for the protected application.

B:

This action concerns conditional access sign in frequency, where The relevant Conditional Access session control lacks the required sign-in frequency and session behavior. The corrective response here is “Extend the policy to the correct external-user categories and trust settings using supported B2B controls”; this alternative does not provide that response.

D:

This action concerns require compliant device condition, where The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. The stem reports partners with B2B guest accounts can open a project management application even though the workforce policy requires stronger authentication only for employees; this control addresses a different failure condition.

Question 230

The cloud operations team reviews the following risk: Linux servers ship system telemetry but their authentication facility events are missing from the central detection environment. Which explanation fits the observed symptoms most closely?

  1. A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities.
  2. Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance.
  3. Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.
  4. A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination.

Explanation

Correct Answer

D:

The described technical condition is: A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. The appropriate corrective action is: Enable the required syslog facility and severity in the Linux data collection rule and verify agent association. Confirm with: A controlled authentication test yields a timestamped syslog record in the authorized workspace.

Incorrect Answers

A:

A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. “Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content” would address that alternative cause, not the condition in this question: a DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination.

B:

“Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes” responds to this separate finding: security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. This question instead needs “Enable the required syslog facility and severity in the Linux data collection rule and verify agent association”, so the alternative does not meet the stated condition.

C:

Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” applies to that separate problem. The observed case is linux servers ship system telemetry but their authentication facility events are missing from the central detection environment; choosing this alternative would address the wrong failure mode.