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 54

Question 530

During a cloud security review, the operations team observes: An App Service allows deprecated TLS versions for an API that handles sensitive data although newer clients support TLS 1.2 or later. After remediation, which test result best proves the intended change?

  1. The function reaches the private SQL endpoint with no public database network dependency.
  2. The managed instance deploys in the intended delegated subnet and responds only to permitted connections.
  3. A test flow negotiates TLS to both gateway and backend without exposing plaintext on the internal leg.
  4. Deprecated TLS clients fail negotiation while approved modern clients connect securely.

Explanation

Correct Answer

D:

This validates the specific control for minimum tls protocol enforcement: The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. The associated corrective action is: Set the supported minimum TLS version to an approved modern value and verify certificate configuration. Testing a different component would not establish this result.

Incorrect Answers

A:

The function hosting plan and network integration/DNS are not configured for the required private destination. “Configure a supported Functions hosting plan with VNet integration and correct private DNS resolution” 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:

“Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls” responds to this separate finding: sQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. This question instead needs “Set the supported minimum TLS version to an approved modern value and verify certificate configuration”, so the alternative does not meet the stated condition.

C:

Backend HTTP settings do not enforce the required HTTPS connection to backend servers. “Configure backend HTTPS with appropriate certificate trust and listener/backend settings” 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 531

A production Azure security implementation shows this failure: A security owner exports a list of all VMs but accidentally filters only resources tagged Production while untagged systems remain deployed. What technical cause best accounts for the described behavior?

  1. A connector's project enrollment or organization-level integration scope may omit newly created GCP projects.
  2. Defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans.
  3. Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption.
  4. Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth.

Explanation

Correct Answer

D:

The described technical condition is: Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. The appropriate corrective action is: Query all in-scope Azure resources first and then classify missing or unexpected tags for correction. Confirm with: The report includes the full resource inventory and separately highlights untagged or misclassified resources.

Incorrect Answers

A:

A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. “Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects” would address that alternative cause, not the condition in this question: tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth.

B:

“Onboard the supported on-premises servers through Azure Arc and configure the relevant Defender for Cloud protection” responds to this separate finding: defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans. This question instead needs “Query all in-scope Azure resources first and then classify missing or unexpected tags for correction”, so the alternative does not meet the stated condition.

C:

Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. “Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope” applies to that separate problem. The observed case is a security owner exports a list of all VMs but accidentally filters only resources tagged Production while untagged systems remain deployed; choosing this alternative would address the wrong failure mode.

Question 532

A platform security assessment reveals this issue: A partner-facing API requires client certificates but accepts arbitrary TLS connections without checking the presented identity. Which operating control most directly reduces this recurring risk?

  1. Review client certificate trust and renewal processes for all privileged API consumers.
  2. Test client OS support, outbound port requirements and SMB security before migrations.
  3. Maintain owner-assigned storage key rotation plans and detect dependencies on old keys.
  4. Validate ACR private link and data endpoint DNS as part of cluster network changes.

Explanation

Correct Answer

A:

This guardrail addresses apim mutual tls client certificate control: The API gateway has not enforced the required mutual TLS certificate validation for partner clients. The prevention measure is: Review client certificate trust and renewal processes for all privileged API consumers. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The file access path needs compatible secure SMB protocol and supported encrypted transport settings. “Test client OS support, outbound port requirements and SMB security before migrations” would address that alternative cause, not the condition in this question: the API gateway has not enforced the required mutual TLS certificate validation for partner clients.

C:

“Maintain owner-assigned storage key rotation plans and detect dependencies on old keys” responds to this separate finding: the client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. This question instead needs “Review client certificate trust and renewal processes for all privileged API consumers”, so the alternative does not meet the stated condition.

D:

Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. “Validate ACR private link and data endpoint DNS as part of cluster network changes” applies to that separate problem. The observed case is a partner-facing API requires client certificates but accepts arbitrary TLS connections without checking the presented identity; choosing this alternative would address the wrong failure mode.

Question 533

A platform security assessment reveals this issue: A data lake receives unusual external blob reads and the organization relies only on daily access log exports for incident detection. What should the engineer implement first to address the weakness?

  1. Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings.
  2. Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment.
  3. Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts.
  4. Enable the appropriate Defender for SQL or Databases protection plan and configure supported alert routing.

Explanation

Correct Answer

C:

The cause is: Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. The appropriate change is: Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts. Verify it with this outcome: A controlled suspicious access simulation generates a triageable security alert containing the impacted storage context.

Incorrect Answers

A:

This action concerns defender for containers container registry vulnerabilities, where Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. The reported incident instead involves Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior.

B:

This action concerns defender for cloud alert investigation evidence, where A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. The corrective response here is “Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts”; this alternative does not provide that response.

D:

This action concerns microsoft defender for databases sql coverage, where Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. The stem reports a data lake receives unusual external blob reads and the organization relies only on daily access log exports for incident detection; this control addresses a different failure condition.

Question 534

While validating an Azure workload, the security team finds: 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 safeguard would best prevent this issue from recurring?

  1. Reassess container images when new vulnerabilities emerge, not only when application source code changes.
  2. Include App Service protection in onboarding checks for Internet-exposed web applications.
  3. Continuously combine vulnerability severity with external reachability and asset importance in remediation planning.
  4. Verify vault threat-protection plan coverage and escalation routing after every critical vault rollout.

Explanation

Correct Answer

D:

This guardrail addresses defender for key vault anomalous access protection: Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations. The prevention measure is: Verify vault threat-protection plan coverage and escalation routing after every critical vault rollout. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. “Reassess container images when new vulnerabilities emerge, not only when application source code changes” 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:

“Include App Service protection in onboarding checks for Internet-exposed web applications” responds to this separate finding: inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. This question instead needs “Verify vault threat-protection plan coverage and escalation routing after every critical vault rollout”, so the alternative does not meet the stated condition.

C:

Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. “Continuously combine vulnerability severity with external reachability and asset importance in remediation planning” 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 535

A Microsoft Azure administrator receives this requirement: A Virtual WAN deployment relies on branch-created firewall rules at every spoke despite a requirement to manage inspection centrally in secured virtual hubs. Which underlying control gap is responsible for the issue?

  1. The topology lacks the intended central security policy and routing intent in Azure Firewall Manager.
  2. Azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions.
  3. Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently.
  4. The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings.

Explanation

Correct Answer

A:

The described technical condition is: The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. The appropriate corrective action is: Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic. Confirm with: Selected branch and VNet flows pass through the secured hub firewall with centralized control.

Incorrect Answers

B:

Azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. “Review inherited policy evaluation and adjust approved parent or child rule design with central authorization” would address that alternative cause, not the condition in this question: the topology lacks the intended central security policy and routing intent in Azure Firewall Manager.

C:

“Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address” responds to this separate finding: spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. This question instead needs “Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic”, so the alternative does not meet the stated condition.

D:

The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings. “Align supported IPsec/IKE policy, keys and proposal parameters between the two authorized peers” applies to that separate problem. The observed case is a Virtual WAN deployment relies on branch-created firewall rules at every spoke despite a requirement to manage inspection centrally in secured virtual hubs; choosing this alternative would address the wrong failure mode.

Question 536

A production Azure security implementation shows this failure: Two applications are moved into VNets with overlapping private address ranges, and administrators attempt to establish a direct VNet peering between them. What should the engineer implement first to address the weakness?

  1. Renumber or redesign the address space before establishing peering or use an approved translation architecture.
  2. Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service.
  3. Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints.
  4. Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls.

Explanation

Correct Answer

A:

The cause is: Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. The appropriate change is: Renumber or redesign the address space before establishing peering or use an approved translation architecture. Verify it with this outcome: The two VNets establish valid connectivity only after address overlap is eliminated or appropriately translated.

Incorrect Answers

B:

This action concerns azure firewall dnat published service, where Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. The reported incident instead involves Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.

C:

This action concerns gateway transit peering configuration, where Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The corrective response here is “Renumber or redesign the address space before establishing peering or use an approved translation architecture”; this alternative does not provide that response.

D:

This action concerns service tag outbound allow scoping, where A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. The stem reports two applications are moved into VNets with overlapping private address ranges, and administrators attempt to establish a direct VNet peering between them; this control addresses a different failure condition.

Question 537

A production Azure security implementation shows this failure: 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. Which operating control most directly reduces this recurring risk?

  1. Review playbook connection identities and least-privilege rights before enabling automated containment.
  2. Require a reproducible evidence trail and peer review for high-severity Sentinel incident closure.
  3. Retest analytic watchlist joins after source schema or naming normalization changes.
  4. Monitor ingestion delay and align scheduled rule lookback to actual source latency.

Explanation

Correct Answer

A:

This guardrail addresses sentinel playbook managed identity permissions: Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. The prevention measure is: Review playbook connection identities and least-privilege rights before enabling automated containment. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. “Require a reproducible evidence trail and peer review for high-severity Sentinel incident closure” would address that alternative cause, not the condition in this question: playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents.

C:

“Retest analytic watchlist joins after source schema or naming normalization changes” responds to this separate finding: watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. This question instead needs “Review playbook connection identities and least-privilege rights before enabling automated containment”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 538

A platform security assessment reveals this issue: A developer creates a SAS token for a single blob but shares the storage account key with a partner to construct it, enabling broader access than intended. What observation is the strongest validation evidence?

  1. A request without authorized API credentials is rejected and approved subscribers receive normal responses.
  2. The partner can perform only the approved blob operation while account key access is not disclosed.
  3. Approved CI pipelines push or pull with attributable identities and the shared admin login fails.
  4. Approved client certificates are accepted and unknown or expired certificates are rejected.

Explanation

Correct Answer

B:

This validates the specific control for storage shared key versus sas distinction: Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. The associated corrective action is: Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys. Testing a different component would not establish this result.

Incorrect Answers

A:

The API or product does not require the intended APIM subscription key or equivalent authentication control. “Enable appropriate APIM subscription requirements and validate product/API associations” would address that alternative cause, not the condition in this question: disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation.

C:

“Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles” responds to this separate finding: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. This question instead needs “Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys”, so the alternative does not meet the stated condition.

D:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Configure supported APIM client certificate validation and trusted certificate criteria” applies to that separate problem. The observed case is a developer creates a SAS token for a single blob but shares the storage account key with a partner to construct it, enabling broader access than intended; choosing this alternative would address the wrong failure mode.

Question 539

An Azure security engineer investigates the following incident: An Internet-facing App Service is listed in Defender for Cloud inventory but has no platform-specific attack detection despite known attempts. Which result confirms the relevant security control is effective?

  1. A matching test alert triggers the intended notification or ticket while unrelated findings do not invoke it.
  2. The hybrid server reports covered status and expected security telemetry reaches the authorized investigation view.
  3. A safe supported test activity can be correlated with a relevant App Service threat alert and workload identity.
  4. A controlled suspicious access simulation generates a triageable security alert containing the impacted storage context.

Explanation

Correct Answer

C:

This validates the specific control for defender for app service protection plan: Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. The associated corrective action is: Enable the applicable App Service workload protection and route findings to the approved responder queue. Testing a different component would not establish this result.

Incorrect Answers

A:

A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. “Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook” would address that alternative cause, not the condition in this question: inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan.

B:

“Enable the appropriate Defender for Servers plan and verify supported hybrid machine monitoring prerequisites” responds to this separate finding: azure Arc inventory presence alone does not guarantee that applicable Defender for Servers protection and monitoring dependencies are enabled. This question instead needs “Enable the applicable App Service workload protection and route findings to the approved responder queue”, so the alternative does not meet the stated condition.

D:

Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. “Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts” applies to that separate problem. The observed case is an Internet-facing App Service is listed in Defender for Cloud inventory but has no platform-specific attack detection despite known attempts; choosing this alternative would address the wrong failure mode.

Question 540

While validating an Azure workload, the security team finds: A Sentinel incident includes high-risk authentication events from multiple hosts but the analyst reviews only its headline before dismissing the incident. Which remediation best addresses the specific issue?

  1. Configure the supported Entra sign-in log integration into Sentinel and verify enabled categories and consent.
  2. Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema.
  3. Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition.
  4. Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches.

Explanation

Correct Answer

C:

The cause is: Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The appropriate change is: Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition. Verify it with this outcome: The case includes a clear event chronology and evidence-backed conclusion or documented containment steps.

Incorrect Answers

A:

This action concerns sentinel microsoft entra sign in connector, where Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. The reported incident instead involves Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation.

B:

This action concerns azure monitor transformation for sensitive fields, where Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. The corrective response here is “Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition”; this alternative does not provide that response.

D:

This action concerns sentinel watchlist match normalization, where Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The stem reports a Sentinel incident includes high-risk authentication events from multiple hosts but the analyst reviews only its headline before dismissing the incident; this control addresses a different failure condition.