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 55

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.

Question 541

The cloud operations team reviews the following risk: An application issues shared-key SAS tokens to end users while security requires tokens to derive from Microsoft Entra authorization. Which outcome most clearly verifies that the issue is resolved?

  1. The storage account reports infrastructure encryption enabled in addition to regular service-side encryption.
  2. A delegated client accesses only intended blobs without possession of the storage account key.
  3. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.
  4. Authorized reads continue while deletes or overwrites prohibited by retention are rejected.

Explanation

Correct Answer

B:

This validates the specific control for user delegation sas for blob storage: Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. The associated corrective action is: Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege. Testing a different component would not establish this result.

Incorrect Answers

A:

The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. “Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage” would address that alternative cause, not the condition in this question: account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model.

C:

“Configure customer-managed key encryption and grant the storage account identity the required key permissions” responds to this separate finding: storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. This question instead needs “Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege”, so the alternative does not meet the stated condition.

D:

Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. “Configure the appropriate time-based immutability policy or legal hold for the protected container” applies to that separate problem. The observed case is an application issues shared-key SAS tokens to end users while security requires tokens to derive from Microsoft Entra authorization; choosing this alternative would address the wrong failure mode.

Question 542

A regulated Azure tenant has this security condition: A public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources. Which explanation fits the observed symptoms most closely?

  1. API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy.
  2. Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment.
  3. The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.
  4. Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access.

Explanation

Correct Answer

C:

The described technical condition is: The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. The appropriate corrective action is: Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions. Confirm with: An abusive test caller is throttled while independent legitimate clients retain service availability.

Incorrect Answers

A:

API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. “Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims” 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.

B:

“Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks” responds to this separate finding: unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. This question instead needs “Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions”, 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. “Configure eligible ACR private endpoints and DNS paths for all required registry endpoints” 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.

Question 543

A platform security assessment reveals this issue: A public scan associates a similarly named third-party domain with the enterprise and analysts attempt to shut it down as their own asset. Which underlying control gap is responsible for the issue?

  1. Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions.
  2. Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path.
  3. Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation.
  4. An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed.

Explanation

Correct Answer

C:

The described technical condition is: Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. The appropriate corrective action is: Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution. Confirm with: Confirmed owned exposures enter the remediation queue while unrelated third-party assets are excluded with reasons.

Incorrect Answers

A:

Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. “Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances” would address that alternative cause, not the condition in this question: attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation.

B:

“Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls” responds to this separate finding: recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. This question instead needs “Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution”, so the alternative does not meet the stated condition.

D:

An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. “Validate exemption justification, owner, expiry and business controls or actually remediate the resource” applies to that separate problem. The observed case is a public scan associates a similarly named third-party domain with the enterprise and analysts attempt to shut it down as their own asset; choosing this alternative would address the wrong failure mode.

Question 544

A platform security assessment reveals this issue: A regulated storage service must use two separate layers of encryption, but a team enables only the default server-side encryption layer. What observation is the strongest validation evidence?

  1. A delegated client accesses only intended blobs without possession of the storage account key.
  2. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.
  3. The storage account reports infrastructure encryption enabled in addition to regular service-side encryption.
  4. Approved clients access data and unauthorized public source IPs receive network access denial.

Explanation

Correct Answer

C:

This validates the specific control for storage infrastructure double encryption: The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. The associated corrective action is: Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage. Testing a different component would not establish this result.

Incorrect Answers

A:

Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. “Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege” would address that alternative cause, not the condition in this question: the specified infrastructure encryption requirement needs the supported additional service-side encryption layer.

B:

“Configure customer-managed key encryption and grant the storage account identity the required key permissions” responds to this separate finding: storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. This question instead needs “Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage”, so the alternative does not meet the stated condition.

D:

The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. “Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required” applies to that separate problem. The observed case is a regulated storage service must use two separate layers of encryption, but a team enables only the default server-side encryption layer; choosing this alternative would address the wrong failure mode.

Question 545

An Azure security engineer investigates the following incident: A team protects a resource through group-based RBAC but all members keep standing membership in the privileged group despite an on-demand access requirement. Which explanation fits the observed symptoms most closely?

  1. Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments.
  2. Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles.
  3. Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs.
  4. A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block.

Explanation

Correct Answer

B:

The described technical condition is: Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. The appropriate corrective action is: Configure PIM for Groups with eligible membership and required activation controls where supported. Confirm with: An engineer gains temporary group-derived resource access only during an approved activation.

Incorrect Answers

A:

Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. “Review permanent assignments and configure PIM alerts, justification and eligible access where feasible” would address that alternative cause, not the condition in this question: permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles.

C:

“Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context” responds to this separate finding: azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. This question instead needs “Configure PIM for Groups with eligible membership and required activation controls where supported”, so the alternative does not meet the stated condition.

D:

A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. “Review report-only results, correct exclusions and switch the approved policy to On for enforcement” applies to that separate problem. The observed case is a team protects a resource through group-based RBAC but all members keep standing membership in the privileged group despite an on-demand access requirement; choosing this alternative would address the wrong failure mode.

Question 546

During a cloud security review, the operations team observes: A business-critical public IP in an Azure VNet is exposed to volumetric attacks but the organization relies only on application WAF rules. Which recurring validation best protects against the observed problem?

  1. Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames.
  2. Separate route next-hop verification from access-control rule checks in network troubleshooting.
  3. Differentiate network-volume DDoS defenses from layer-seven WAF filtering during threat modeling.
  4. Verify firewall diagnostic export completeness after routing or workspace configuration changes.

Explanation

Correct Answer

C:

This guardrail addresses 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 prevention measure is: Differentiate network-volume DDoS defenses from layer-seven WAF filtering during threat modeling. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. “Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames” 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.

B:

“Separate route next-hop verification from access-control rule checks in network troubleshooting” responds to this separate finding: a user-defined or propagated route controls the next hop independently of NSG allow decisions. This question instead needs “Differentiate network-volume DDoS defenses from layer-seven WAF filtering during threat modeling”, so the alternative does not meet the stated condition.

D:

Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. “Verify firewall diagnostic export completeness after routing or workspace configuration changes” 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.

Question 547

A Microsoft Azure administrator receives this requirement: 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. Which recurring validation best protects against the observed problem?

  1. Schedule OS-level update compliance checks independent of ARM deployment status.
  2. Test Bastion SKU and client feature support before designing remote-administration access.
  3. Inventory Disk Encryption Set and key lifecycle dependencies before rotating CMKs.
  4. Audit installed extensions and review guest-level execution privileges after VM changes.

Explanation

Correct Answer

B:

This guardrail addresses bastion native client security control: Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. The prevention measure is: Test Bastion SKU and client feature support before designing remote-administration access. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure resource deployment health does not automatically establish guest operating system patch compliance. “Schedule OS-level update compliance checks independent of ARM deployment status” 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:

“Inventory Disk Encryption Set and key lifecycle dependencies before rotating CMKs” responds to this separate finding: azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. This question instead needs “Test Bastion SKU and client feature support before designing remote-administration access”, so the alternative does not meet the stated condition.

D:

Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. “Audit installed extensions and review guest-level execution privileges after VM changes” 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 548

A platform security assessment reveals this issue: A Microsoft Sentinel automation rule is intended to respond to incident creation but triggers only on updates, so newly created incidents are ignored. Which operating control most directly reduces this recurring risk?

  1. Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators.
  2. Test create and update automation triggers independently after SOC workflow changes.
  3. Monitor ingestion delay and align scheduled rule lookback to actual source latency.
  4. Review security telemetry retention alongside legal requirements and realistic incident lookback needs.

Explanation

Correct Answer

B:

This guardrail addresses sentinel automation rule trigger selection: Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. The prevention measure is: Test create and update automation triggers independently after SOC workflow changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators” would address that alternative cause, not the condition in this question: sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events.

C:

“Monitor ingestion delay and align scheduled rule lookback to actual source latency” responds to this separate finding: a rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. This question instead needs “Test create and update automation triggers independently after SOC workflow changes”, so the alternative does not meet the stated condition.

D:

Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. “Review security telemetry retention alongside legal requirements and realistic incident lookback needs” applies to that separate problem. The observed case is a Microsoft Sentinel automation rule is intended to respond to incident creation but triggers only on updates, so newly created incidents are ignored; choosing this alternative would address the wrong failure mode.

Question 549

A Microsoft Azure administrator receives this requirement: An AKS public API endpoint remains reachable from any source address though administration should originate only from a controlled office IP range. Which underlying control gap is responsible for the issue?

  1. The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model.
  2. The cluster's public API server authorized IP ranges were not configured for restricted administrative access.
  3. The application's ingress configuration enables external exposure instead of internal-only routing.
  4. AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health.

Explanation

Correct Answer

B:

The described technical condition is: The cluster's public API server authorized IP ranges were not configured for restricted administrative access. The appropriate corrective action is: Configure approved API server authorized IP ranges or move to private control-plane access. Confirm with: An allowed management source can connect while test sources outside the ranges are blocked.

Incorrect Answers

A:

The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. “Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings” 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:

“Configure internal ingress and supported network isolation for the Container App environment” responds to this separate finding: the application's ingress configuration enables external exposure instead of internal-only routing. This question instead needs “Configure approved API server authorized IP ranges or move to private control-plane access”, so the alternative does not meet the stated condition.

D:

AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. “Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels” 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 550

The cloud operations team reviews the following risk: An Azure Policy remediation task repeatedly fails with authorization errors although its definition and target resources are correct. Which configuration change most directly resolves this problem?

  1. Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap.
  2. Enable the relevant supported regulatory standard and verify its assessment mappings for the intended environment.
  3. Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope.
  4. Onboard the supported on-premises servers through Azure Arc and configure the relevant Defender for Cloud protection.

Explanation

Correct Answer

C:

The cause is: DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. The appropriate change is: Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope. Verify it with this outcome: The remediation operation succeeds and creates or updates only the intended governed configuration.

Incorrect Answers

A:

This action concerns defender for cloud secure score priority, where Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. The reported incident instead involves DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope.

B:

This action concerns defender for cloud regulatory standard assignment, where Additional regulatory compliance standards require supported selection, assessment availability and assignment at the appropriate management scope. The corrective response here is “Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope”; this alternative does not provide that response.

D:

This action concerns azure arc hybrid server posture, where Defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans. The stem reports an Azure Policy remediation task repeatedly fails with authorization errors although its definition and target resources are correct; this control addresses a different failure condition.