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 63

Question 620

A Microsoft Azure administrator receives this requirement: A SOC deploys Azure Monitor Agent to Windows servers but receives no required security event IDs in the security analytics workspace. Which operating control most directly reduces this recurring risk?

  1. Review management-plane telemetry source coverage separately from endpoint and operating-system logs.
  2. Require a reproducible evidence trail and peer review for high-severity Sentinel incident closure.
  3. Validate DCR associations and event filtering with a known test event after agent or scope changes.
  4. Review collection transformations for data minimization and unintended loss of detection-critical attributes.

Explanation

Correct Answer

C:

This guardrail addresses azure monitor dcr windows event filtering: Azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association. The prevention measure is: Validate DCR associations and event filtering with a known test event after agent or scope changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. “Review management-plane telemetry source coverage separately from endpoint and operating-system logs” would address that alternative cause, not the condition in this question: azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association.

B:

“Require a reproducible evidence trail and peer review for high-severity Sentinel incident closure” responds to this separate finding: incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. This question instead needs “Validate DCR associations and event filtering with a known test event after agent or scope changes”, 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 a SOC deploys Azure Monitor Agent to Windows servers but receives no required security event IDs in the security analytics workspace; choosing this alternative would address the wrong failure mode.

Question 621

An Azure security engineer investigates the following incident: A service experiences intermittent TCP resets, but operators have no packet-level evidence and rely only on Azure resource health statuses. Which explanation fits the observed symptoms most closely?

  1. A user-defined or propagated route controls the next hop independently of NSG allow decisions.
  2. A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues.
  3. The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path.
  4. Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets.

Explanation

Correct Answer

D:

The described technical condition is: Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. The appropriate corrective action is: Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow. Confirm with: A filtered packet trace identifies the reset sender and supports a targeted remediation decision.

Incorrect Answers

A:

A user-defined or propagated route controls the next hop independently of NSG allow decisions. “Inspect effective routes and run Network Watcher next hop against the intended destination IP” would address that alternative cause, not the condition in this question: control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets.

B:

“Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results” responds to this separate finding: a point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. This question instead needs “Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow”, so the alternative does not meet the stated condition.

C:

The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. “Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable” applies to that separate problem. The observed case is a service experiences intermittent TCP resets, but operators have no packet-level evidence and rely only on Azure resource health statuses; choosing this alternative would address the wrong failure mode.

Question 622

A regulated Azure tenant has this security condition: A network team adds an outbound deny rule and assumes it will immediately terminate every existing TCP session previously allowed through the subnet NSG. Which result confirms the relevant security control is effective?

  1. The app subnet's outbound flows traverse the central inspection appliance and are visible in policy logs.
  2. Effective route inspection shows only intended propagated and explicit routes for the target subnet.
  3. New prohibited connections fail and the team documents disposition of any previously established flows.
  4. The newly assigned web VM receives authorized application traffic while non-member VMs remain excluded.

Explanation

Correct Answer

C:

This validates the specific control for stateful nsg return traffic behavior: NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. The associated corrective action is: Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes. Testing a different component would not establish this result.

Incorrect Answers

A:

No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. “Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP” would address that alternative cause, not the condition in this question: nSGs are stateful and existing established flows can persist until their flow records expire despite rule changes.

B:

“Disable BGP route propagation on the relevant route table where the approved design requires static steering” responds to this separate finding: gateway route propagation remains enabled for the route table and influences effective routing selections. This question instead needs “Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes”, so the alternative does not meet the stated condition.

D:

An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. “Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria” applies to that separate problem. The observed case is a network team adds an outbound deny rule and assumes it will immediately terminate every existing TCP session previously allowed through the subnet NSG; choosing this alternative would address the wrong failure mode.

Question 623

The cloud operations team reviews the following risk: An App Service allows deprecated TLS versions for an API that handles sensitive data although newer clients support TLS 1.2 or later. Which condition most directly explains the failure?

  1. The function hosting plan and network integration/DNS are not configured for the required private destination.
  2. SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.
  3. The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline.
  4. Backend HTTP settings do not enforce the required HTTPS connection to backend servers.

Explanation

Correct Answer

C:

The described technical condition is: The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. The appropriate corrective action is: Set the supported minimum TLS version to an approved modern value and verify certificate configuration. Confirm with: Deprecated TLS clients fail negotiation while approved modern clients connect securely.

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.

D:

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 624

While validating an Azure workload, the security team finds: An AWS account appears in Defender for Cloud inventory but its resources have no useful configuration findings after onboarding. Which safeguard would best prevent this issue from recurring?

  1. Normalize control applicability and data freshness when reporting cross-cloud posture trends.
  2. Check connector health, least-privilege permissions and cloud account scope after onboarding or role changes.
  3. Verify assignment identity rights with a pilot remediation instead of granting subscription Owner as a workaround.
  4. Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy.

Explanation

Correct Answer

B:

This guardrail addresses multicloud aws connector permissions: A multicloud connector can exist while its required permissions, services or security plan settings are incomplete. The prevention measure is: Check connector health, least-privilege permissions and cloud account scope after onboarding or role changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Control applicability and enabled cloud connectors differ across providers, so absent assessment coverage is not equivalent to a passing control. “Normalize control applicability and data freshness when reporting cross-cloud posture trends” would address that alternative cause, not the condition in this question: a multicloud connector can exist while its required permissions, services or security plan settings are incomplete.

C:

“Verify assignment identity rights with a pilot remediation instead of granting subscription Owner as a workaround” responds to this separate finding: deployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. This question instead needs “Check connector health, least-privilege permissions and cloud account scope after onboarding or role changes”, so the alternative does not meet the stated condition.

D:

A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. “Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy” applies to that separate problem. The observed case is an AWS account appears in Defender for Cloud inventory but its resources have no useful configuration findings after onboarding; choosing this alternative would address the wrong failure mode.

Question 625

A platform security assessment reveals this issue: A multi-tenant SaaS app authenticates users successfully but grants every signed-in user an administrator feature because role assignments are absent. After remediation, which test result best proves the intended change?

  1. Authorized clients request the named scope and the API rejects tokens without the required permission.
  2. Only the approved workflow obtains short-lived Azure tokens without transmitting a static client secret.
  3. Consent records show authorized approval and the application uses the narrower intended permission.
  4. A basic user receives only permitted features while a role-assigned administrator gets controlled privileges.

Explanation

Correct Answer

D:

This validates the specific control for application role assignment authorization: Successful authentication does not establish application authorization; app roles and assignments are not enforced. The associated corrective action is: Define application roles, assign them to approved users or groups and validate role claims in the app. Testing a different component would not establish this result.

Incorrect Answers

A:

The protected application registration has not exposed an OAuth permission scope for the required delegated operation. “Define and publish the intended API scope and update client permissions and authorization enforcement” would address that alternative cause, not the condition in this question: successful authentication does not establish application authorization; app roles and assignments are not enforced.

B:

“Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret” responds to this separate finding: secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. This question instead needs “Define application roles, assign them to approved users or groups and validate role claims in the app”, so the alternative does not meet the stated condition.

C:

The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. “Have an authorized administrator evaluate and grant only the required application permission after review” applies to that separate problem. The observed case is a multi-tenant SaaS app authenticates users successfully but grants every signed-in user an administrator feature because role assignments are absent; choosing this alternative would address the wrong failure mode.

Question 626

A production Azure security implementation shows this failure: A firewall administrator enables a network rule and assumes that traffic is being audited despite no diagnostic setting on the firewall resource. After remediation, which test result best proves the intended change?

  1. A fresh qualifying incident invokes the authorized workflow, while unrelated new incidents are unaffected.
  2. An authorized six-month historical query retrieves the necessary security events or documents correctly archived data access.
  3. The selected security events arrive in the expected Log Analytics table with correct computer and event identifiers.
  4. A controlled allowed and denied connection produces correlatable firewall records in the intended workspace.

Explanation

Correct Answer

D:

This validates the specific control for network security diagnostic logs to log analytics: Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. The associated corrective action is: Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging. Testing a different component would not establish this result.

Incorrect Answers

A:

Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Change the automation rule to the correct incident-created trigger with the intended scoped conditions” would address that alternative cause, not the condition in this question: network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings.

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 “Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging”, so the alternative does not meet the stated condition.

C:

Azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association. “Create or correct the DCR Windows event selection and associate it with the eligible Windows machines” applies to that separate problem. The observed case is a firewall administrator enables a network rule and assumes that traffic is being audited despite no diagnostic setting on the firewall resource; choosing this alternative would address the wrong failure mode.

Question 627

A platform security assessment reveals this issue: A security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events. Which underlying control gap is responsible for the issue?

  1. Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination.
  2. The file access path needs compatible secure SMB protocol and supported encrypted transport settings.
  3. The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction.
  4. Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls.

Explanation

Correct Answer

A:

The described technical condition is: Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. The appropriate corrective action is: Enable supported SQL auditing with the necessary categories and protected retention settings. Confirm with: A controlled database operation produces an accessible audit record with principal and action details.

Incorrect Answers

B:

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” would address that alternative cause, not the condition in this question: azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination.

C:

“Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access” responds to this separate finding: the SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. This question instead needs “Enable supported SQL auditing with the necessary categories and protected retention settings”, so the alternative does not meet the stated condition.

D:

Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. “Enable supported secret encryption and external secret management using Key Vault where required” applies to that separate problem. The observed case is a security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events; choosing this alternative would address the wrong failure mode.

Question 628

An Azure security engineer investigates the following incident: A public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources. Which remediation best addresses the specific issue?

  1. Grant the appropriate ACR pull permission and remove excess push or management roles.
  2. Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions.
  3. Enable appropriate APIM subscription requirements and validate product/API associations.
  4. Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys.

Explanation

Correct Answer

B:

The cause is: The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. The appropriate change is: Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions. Verify it with this outcome: An abusive test caller is throttled while independent legitimate clients retain service availability.

Incorrect Answers

A:

This action concerns acr push and pull role separation, where The workload has an overly broad registry data role instead of the necessary pull-only authorization. The reported incident instead involves The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.

C:

This action concerns api management subscription key usage, where The API or product does not require the intended APIM subscription key or equivalent authentication control. The corrective response here is “Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions”; this alternative does not provide that response.

D:

This action concerns storage shared key versus sas distinction, where Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. The stem reports a public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources; this control addresses a different failure condition.

Question 629

While validating an Azure workload, the security team finds: An attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events. What governance practice would best prevent the same failure?

  1. Reassess container images when new vulnerabilities emerge, not only when application source code changes.
  2. Keep management-plane threat detection enabled for governed subscriptions independent of server-agent deployment.
  3. Require evidence-based alert closure with escalation for unresolved high-severity cloud threats.
  4. Link vulnerability closure to post-remediation evidence rather than administrative ticket state alone.

Explanation

Correct Answer

B:

This guardrail addresses defender for resource manager suspicious activity: Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. The prevention measure is: Keep management-plane threat detection enabled for governed subscriptions independent of server-agent deployment. 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: control-plane Resource Manager activity can require dedicated detection separate from guest server security events.

C:

“Require evidence-based alert closure with escalation for unresolved high-severity cloud threats” responds to this separate finding: a single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. This question instead needs “Keep management-plane threat detection enabled for governed subscriptions independent of server-agent deployment”, so the alternative does not meet the stated condition.

D:

A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. “Link vulnerability closure to post-remediation evidence rather than administrative ticket state alone” applies to that separate problem. The observed case is an attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events; choosing this alternative would address the wrong failure mode.

Question 630

A Microsoft Azure administrator receives this requirement: A shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs. What observation is the strongest validation evidence?

  1. An abusive test caller is throttled while independent legitimate clients retain service availability.
  2. A request without authorized API credentials is rejected and approved subscribers receive normal responses.
  3. Approved CI pipelines push or pull with attributable identities and the shared admin login fails.
  4. A test deployment uses the reviewed digest and obsolete unapproved images are no longer deployable.

Explanation

Correct Answer

C:

This validates the specific control for acr administrator account disablement: The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The associated corrective action is: Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles. Testing a different component would not establish this result.

Incorrect Answers

A:

The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. “Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions” would address that alternative cause, not the condition in this question: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.

B:

“Enable appropriate APIM subscription requirements and validate product/API associations” responds to this separate finding: the API or product does not require the intended APIM subscription key or equivalent authentication control. This question instead needs “Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles”, so the alternative does not meet the stated condition.

D:

Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. “Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks” applies to that separate problem. The observed case is a shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs; choosing this alternative would address the wrong failure mode.