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 38

Question 370

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. What should the engineer implement first to address the weakness?

  1. Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints.
  2. Renumber or redesign the address space before establishing peering or use an approved translation architecture.
  3. Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy.
  4. Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs.

Explanation

Correct Answer

A:

The cause is: Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The appropriate change is: Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints. Verify it with this outcome: A spoke workload reaches the on-premises network via the shared hub gateway without deploying a second gateway.

Incorrect Answers

B:

This action concerns overlapping vnet address spaces, where Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. The reported incident instead involves Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.

C:

This action concerns azure firewall application rule fqdn filtering, where A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. The corrective response here is “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints”; this alternative does not provide that response.

D:

This action concerns vnet peering non transitivity, where VNet peering does not inherently create transitive routing between other independently peered VNets. The stem reports 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; this control addresses a different failure condition.

Question 371

While validating an Azure workload, the security team finds: A Defender for Cloud assessment lists a legacy appliance as exempted, and the team treats the entire recommendation as permanently remediated. Which configuration change most directly resolves this problem?

  1. Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains.
  2. Validate exemption justification, owner, expiry and business controls or actually remediate the resource.
  3. Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls.
  4. Check supported AWS assessment coverage, connector health and applicable cloud-specific configuration rules before comparing results.

Explanation

Correct Answer

B:

The cause is: An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. The appropriate change is: Validate exemption justification, owner, expiry and business controls or actually remediate the resource. Verify it with this outcome: The assessment clearly distinguishes justified exceptions from technical fixes and tracks residual risk ownership.

Incorrect Answers

A:

This action concerns defender easm externally visible asset discovery, where Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. The reported incident instead involves An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed.

C:

This action concerns risk acceptance versus secure score remediation, where Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. The corrective response here is “Validate exemption justification, owner, expiry and business controls or actually remediate the resource”; this alternative does not provide that response.

D:

This action concerns microsoft defender for cloud aws security benchmark coverage, where Control applicability and enabled cloud connectors differ across providers, so absent assessment coverage is not equivalent to a passing control. The stem reports a Defender for Cloud assessment lists a legacy appliance as exempted, and the team treats the entire recommendation as permanently remediated; this control addresses a different failure condition.

Question 372

A regulated Azure tenant has this security condition: A production cluster identity can push or delete container images in ACR even though it only needs to retrieve signed deployment images. What governance practice would best prevent the same failure?

  1. Validate ACR private link and data endpoint DNS as part of cluster network changes.
  2. Separate build-pipeline image publishing identity from runtime image-pull identity.
  3. Maintain owner-assigned storage key rotation plans and detect dependencies on old keys.
  4. Review APIM API and product access configuration when introducing new routes.

Explanation

Correct Answer

B:

This guardrail addresses acr push and pull role separation: The workload has an overly broad registry data role instead of the necessary pull-only authorization. The prevention measure is: Separate build-pipeline image publishing identity from runtime image-pull identity. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the workload has an overly broad registry data role instead of the necessary pull-only authorization.

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 “Separate build-pipeline image publishing identity from runtime image-pull identity”, so the alternative does not meet the stated condition.

D:

The API or product does not require the intended APIM subscription key or equivalent authentication control. “Review APIM API and product access configuration when introducing new routes” applies to that separate problem. The observed case is a production cluster identity can push or delete container images in ACR even though it only needs to retrieve signed deployment images; choosing this alternative would address the wrong failure mode.

Question 373

A platform security assessment reveals this issue: A compliance owner expects an industry framework dashboard in Defender for Cloud but finds only default cloud security benchmark controls. After remediation, which test result best proves the intended change?

  1. Previously unknown externally reachable assets are identified, attributed to an owner and queued for risk assessment.
  2. The framework appears with applicable control statuses and a traceable set of evidence-backed recommendations.
  3. The report includes the full resource inventory and separately highlights untagged or misclassified resources.
  4. Selected connected AWS instances appear in the correct Defender plan with expected scanning and alert coverage.

Explanation

Correct Answer

B:

This validates the specific control for defender for cloud regulatory standard assignment: Additional regulatory compliance standards require supported selection, assessment availability and assignment at the appropriate management scope. The associated corrective action is: Enable the relevant supported regulatory standard and verify its assessment mappings for the intended environment. Testing a different component would not establish this result.

Incorrect Answers

A:

Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. “Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains” would address that alternative cause, not the condition in this question: additional regulatory compliance standards require supported selection, assessment availability and assignment at the appropriate management scope.

C:

“Query all in-scope Azure resources first and then classify missing or unexpected tags for correction” responds to this separate finding: tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. This question instead needs “Enable the relevant supported regulatory standard and verify its assessment mappings for the intended environment”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a compliance owner expects an industry framework dashboard in Defender for Cloud but finds only default cloud security benchmark controls; choosing this alternative would address the wrong failure mode.

Question 374

An Azure security engineer investigates the following incident: A SOC imports suspicious IP indicators into Sentinel once and uses the unchanged list indefinitely without considering expiry or source reliability. Which remediation best addresses the specific issue?

  1. Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters.
  2. Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition.
  3. Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics.
  4. Create or enable the scheduled analytic rule with appropriate query frequency, lookback and incident configuration.

Explanation

Correct Answer

C:

The cause is: Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. The appropriate change is: Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics. Verify it with this outcome: Expired indicators stop driving automatic actions and fresh verified indicators can be correlated with current events.

Incorrect Answers

A:

This action concerns dcr workspace destination configuration, where A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. The reported incident instead involves Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation.

B:

This action concerns sentinel incident investigation timeline, where Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The corrective response here is “Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics”; this alternative does not provide that response.

D:

This action concerns sentinel analytics scheduled rule query, where A saved KQL query does not generate incidents until a supported analytic rule is enabled with schedule and alert grouping settings. The stem reports a SOC imports suspicious IP indicators into Sentinel once and uses the unchanged list indefinitely without considering expiry or source reliability; this control addresses a different failure condition.

Question 375

During a cloud security review, the operations team observes: A data lake receives unusual external blob reads and the organization relies only on daily access log exports for incident detection. What technical cause best accounts for the described behavior?

  1. A DevOps connector does not guarantee automatic security scan visibility for every new project and repository.
  2. Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior.
  3. Supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent.
  4. Node management alone does not provide full supported Defender for Containers security posture and workload protection.

Explanation

Correct Answer

B:

The described technical condition is: Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. The appropriate corrective action is: Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts. Confirm with: A controlled suspicious access simulation generates a triageable security alert containing the impacted storage context.

Incorrect Answers

A:

A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. “Review project and repository connector coverage and enable the supported assessment pipeline for the missing project” would address that alternative cause, not the condition in this question: access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior.

C:

“Enable the supported agentless scanning capability and verify its resource scope, prerequisites and results” responds to this separate finding: supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent. This question instead needs “Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts”, so the alternative does not meet the stated condition.

D:

Node management alone does not provide full supported Defender for Containers security posture and workload protection. “Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster” applies to that separate problem. The observed case is a data lake receives unusual external blob reads and the organization relies only on daily access log exports for incident detection; choosing this alternative would address the wrong failure mode.

Question 376

A Microsoft Azure administrator receives this requirement: A Microsoft Sentinel automation rule is intended to respond to incident creation but triggers only on updates, so newly created incidents are ignored. What observation is the strongest validation evidence?

  1. A fresh qualifying incident invokes the authorized workflow, while unrelated new incidents are unaffected.
  2. High-severity test incidents reach the correct responder without being prematurely closed.
  3. The expected records appear only in approved production destinations and analysts can query them within the retention policy.
  4. Representative security events remain analyzable without exposing the prohibited personal payload fields.

Explanation

Correct Answer

A:

This validates the specific control for sentinel automation rule trigger selection: Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. The associated corrective action is: Change the automation rule to the correct incident-created trigger with the intended scoped conditions. Testing a different component would not establish this result.

Incorrect Answers

B:

Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. “Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition” 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:

“Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters” responds to this separate finding: a DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. This question instead needs “Change the automation rule to the correct incident-created trigger with the intended scoped conditions”, 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. “Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema” 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 377

While validating an Azure workload, the security team finds: An administrator edits Virtual Network Manager configuration definitions but never deploys the configuration to the required target regions. Which result confirms the relevant security control is effective?

  1. The new VNet appears in the proper network group and receives the intended security admin rules.
  2. Approved HTTPS hosts are reachable and unrelated hosts in the same IP ranges are rejected.
  3. The destination VNet shows the new intended connectivity or security policy after successful deployment.
  4. The VM reaches its approved Azure service while unrelated Internet destinations remain blocked.

Explanation

Correct Answer

C:

This validates the specific control for central network intent deployment region: Saving network manager intent does not itself apply connectivity or security configuration to target regions. The associated corrective action is: Deploy the approved configuration to the correct regions and verify the deployed state. Testing a different component would not establish this result.

Incorrect Answers

A:

The dynamic network group criteria do not include the intended VNet attributes or scope. “Correct the group membership query or approved explicit membership and deploy the security configuration” would address that alternative cause, not the condition in this question: saving network manager intent does not itself apply connectivity or security configuration to target regions.

B:

“Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy” 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 “Deploy the approved configuration to the correct regions and verify the deployed state”, so the alternative does not meet the stated condition.

D:

A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. “Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls” applies to that separate problem. The observed case is an administrator edits Virtual Network Manager configuration definitions but never deploys the configuration to the required target regions; choosing this alternative would address the wrong failure mode.

Question 378

During a cloud security review, the operations team observes: Kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job. After remediation, which test result best proves the intended change?

  1. Developers perform only authorized namespace tasks and cluster-admin operations require eligible roles.
  2. The pod obtains a short-lived token and reads only the approved secret without stored client secrets.
  3. A deletion attempt cannot immediately eradicate protected backup recovery points and recovery remains possible.
  4. The vulnerable image is detected and a patched replacement is deployed before production exposure.

Explanation

Correct Answer

A:

This validates the specific control for aks microsoft entra and kubernetes rbac: Cluster authorization is not aligned with identity-based RBAC and separation of duties. The associated corrective action is: Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope. Testing a different component would not establish this result.

Incorrect Answers

B:

The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. “Configure workload identity on the service account and scoped access to the target Key Vault” would address that alternative cause, not the condition in this question: cluster authorization is not aligned with identity-based RBAC and separation of duties.

C:

“Enable supported vault soft delete and enhanced protection settings including immutable backup where required” responds to this separate finding: backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. This question instead needs “Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope”, so the alternative does not meet the stated condition.

D:

Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. “Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation” applies to that separate problem. The observed case is kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job; choosing this alternative would address the wrong failure mode.

Question 379

While validating an Azure workload, the security team finds: An Azure DevOps organization shows as connected, but one newly created project has no infrastructure-as-code security findings. Which explanation fits the observed symptoms most closely?

  1. A DevOps connector does not guarantee automatic security scan visibility for every new project and repository.
  2. Code security inventory and posture coverage depend on a supported connector for the actual source-control platform.
  3. Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan.
  4. Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace.

Explanation

Correct Answer

A:

The described technical condition is: A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. The appropriate corrective action is: Review project and repository connector coverage and enable the supported assessment pipeline for the missing project. Confirm with: The new project's eligible repositories appear with relevant infrastructure-as-code findings or documented exclusions.

Incorrect Answers

B:

Code security inventory and posture coverage depend on a supported connector for the actual source-control platform. “Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories” would address that alternative cause, not the condition in this question: a DevOps connector does not guarantee automatic security scan visibility for every new project and repository.

C:

“Enable the applicable App Service workload protection and route findings to the approved responder queue” 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 “Review project and repository connector coverage and enable the supported assessment pipeline for the missing project”, so the alternative does not meet the stated condition.

D:

Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. “Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion” applies to that separate problem. The observed case is an Azure DevOps organization shows as connected, but one newly created project has no infrastructure-as-code security findings; choosing this alternative would address the wrong failure mode.

Question 380

A Microsoft Azure administrator receives this requirement: A team patches every informational finding on isolated lab servers but ignores a critical exploitable vulnerability on an Internet-exposed production VM. What observation is the strongest validation evidence?

  1. The new project's eligible repositories appear with relevant infrastructure-as-code findings or documented exclusions.
  2. An eligible Defender alert appears in Sentinel with its workload context and appropriate incident correlation.
  3. The critical exposed resource is patched or protected first and the residual exposure is documented.
  4. Security operations receive actionable alert context tied to an unusual Key Vault access pattern.

Explanation

Correct Answer

C:

This validates the specific control for vulnerability risk prioritization by exposure: Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. The associated corrective action is: Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw. Testing a different component would not establish this result.

Incorrect Answers

A:

A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. “Review project and repository connector coverage and enable the supported assessment pipeline for the missing project” would address that alternative cause, not the condition in this question: patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue.

B:

“Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion” responds to this separate finding: defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. This question instead needs “Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw”, so the alternative does not meet the stated condition.

D:

Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations. “Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access” applies to that separate problem. The observed case is a team patches every informational finding on isolated lab servers but ignores a critical exploitable vulnerability on an Internet-exposed production VM; choosing this alternative would address the wrong failure mode.