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 15

Question 140

While validating an Azure workload, the security team finds: A security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions. Which condition most directly explains the failure?

  1. A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.
  2. NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule.
  3. Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.
  4. Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.

Explanation

Correct Answer

C:

The described technical condition is: Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The appropriate corrective action is: Assign the approved read-only role at a suitable management group with the intended child subscription coverage. Confirm with: The operator views security inventory in both existing and newly attached eligible subscriptions.

Incorrect Answers

A:

A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” would address that alternative cause, not the condition in this question: per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.

B:

“Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment” responds to this separate finding: notActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. This question instead needs “Assign the approved read-only role at a suitable management group with the intended child subscription coverage”, so the alternative does not meet the stated condition.

D:

Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” applies to that separate problem. The observed case is a security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions; choosing this alternative would address the wrong failure mode.

Question 141

An Azure security engineer investigates the following incident: A partner-facing API requires client certificates but accepts arbitrary TLS connections without checking the presented identity. Which configuration change most directly resolves this problem?

  1. Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks.
  2. Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles.
  3. Enable appropriate APIM subscription requirements and validate product/API associations.
  4. Configure supported APIM client certificate validation and trusted certificate criteria.

Explanation

Correct Answer

D:

The cause is: The API gateway has not enforced the required mutual TLS certificate validation for partner clients. The appropriate change is: Configure supported APIM client certificate validation and trusted certificate criteria. Verify it with this outcome: Approved client certificates are accepted and unknown or expired certificates are rejected.

Incorrect Answers

A:

This action concerns acr image retention and digest hygiene, where Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. The reported incident instead involves The API gateway has not enforced the required mutual TLS certificate validation for partner clients.

B:

This action concerns acr administrator account disablement, where The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The corrective response here is “Configure supported APIM client certificate validation and trusted certificate criteria”; this alternative does not provide that response.

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 stem reports a partner-facing API requires client certificates but accepts arbitrary TLS connections without checking the presented identity; this control addresses a different failure condition.

Question 142

A platform security assessment reveals this issue: A container group deployment exposes an API password as an ordinary public environment variable in its template and diagnostic output. Which operating control most directly reduces this recurring risk?

  1. Monitor policy effects and exceptions as part of AKS release governance.
  2. Scan container deployment manifests and logs for accidentally exposed credentials.
  3. Test AKS diagnostic collection coverage after cluster upgrades and namespace changes.
  4. Include node operating system image lifecycle in AKS maintenance plans.

Explanation

Correct Answer

B:

This guardrail addresses container instances environment secret handling: Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. The prevention measure is: Scan container deployment manifests and logs for accidentally exposed credentials. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. “Monitor policy effects and exceptions as part of AKS release governance” would address that alternative cause, not the condition in this question: sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references.

C:

“Test AKS diagnostic collection coverage after cluster upgrades and namespace changes” responds to this separate finding: aKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. This question instead needs “Scan container deployment manifests and logs for accidentally exposed credentials”, so the alternative does not meet the stated condition.

D:

Control-plane version compliance is distinct from node OS image and node pool security patch state. “Include node operating system image lifecycle in AKS maintenance plans” applies to that separate problem. The observed case is a container group deployment exposes an API password as an ordinary public environment variable in its template and diagnostic output; choosing this alternative would address the wrong failure mode.

Question 143

An Azure security engineer investigates the following incident: An Azure DevOps organization shows as connected, but one newly created project has no infrastructure-as-code security findings. Which configuration change most directly resolves this problem?

  1. Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories.
  2. Review project and repository connector coverage and enable the supported assessment pipeline for the missing project.
  3. Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment.
  4. Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access.

Explanation

Correct Answer

B:

The cause is: A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. The appropriate change is: Review project and repository connector coverage and enable the supported assessment pipeline for the missing project. Verify it with this outcome: The new project's eligible repositories appear with relevant infrastructure-as-code findings or documented exclusions.

Incorrect Answers

A:

This action concerns defender for cloud devops gitlab integration, where Code security inventory and posture coverage depend on a supported connector for the actual source-control platform. The reported incident instead involves A DevOps connector does not guarantee automatic security scan visibility for every new project and repository.

C:

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 “Review project and repository connector coverage and enable the supported assessment pipeline for the missing project”; this alternative does not provide that response.

D:

This action concerns defender for key vault anomalous access protection, where Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations. The stem reports an Azure DevOps organization shows as connected, but one newly created project has no infrastructure-as-code security findings; this control addresses a different failure condition.

Question 144

During a cloud security review, the operations team observes: An organization enables agentless scanning for Azure servers and assumes the same setting activates threat protection for its connected AWS virtual machines. After remediation, which test result best proves the intended change?

  1. Selected connected AWS instances appear in the correct Defender plan with expected scanning and alert coverage.
  2. Previously unknown externally reachable assets are identified, attributed to an owner and queued for risk assessment.
  3. The report includes the full resource inventory and separately highlights untagged or misclassified resources.
  4. The owner can demonstrate a mitigated exposure or a formally governed residual risk with appropriate expiration.

Explanation

Correct Answer

A:

This validates the specific control for defender for cloud cross-account connected aws plans: Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. The associated corrective action is: Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances. Testing a different component would not establish this result.

Incorrect Answers

B:

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: protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions.

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 “Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances”, so the alternative does not meet the stated condition.

D:

Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. “Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls” applies to that separate problem. The observed case is an organization enables agentless scanning for Azure servers and assumes the same setting activates threat protection for its connected AWS virtual machines; choosing this alternative would address the wrong failure mode.

Question 145

A Microsoft Azure administrator receives this requirement: Just-in-time access has been enabled on a VM, but emergency users request an unrestricted source-address exception rather than their current approved workstation IP. What should the engineer implement first to address the weakness?

  1. Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration.
  2. Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules.
  3. Configure the encryption set and supported Key Vault key permissions, then associate eligible disks.
  4. Restrict extension publishers and deployment rights and deploy only signed or approved scripts.

Explanation

Correct Answer

A:

The cause is: JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. The appropriate change is: Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration. Verify it with this outcome: A test request from the approved address succeeds temporarily while arbitrary Internet sources remain denied.

Incorrect Answers

B:

This action concerns azure bastion without public vm ip, where Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. The reported incident instead involves JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly.

C:

This action concerns disk customer managed key disk encryption set, where Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The corrective response here is “Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration”; this alternative does not provide that response.

D:

This action concerns vm extension least privilege, where Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. The stem reports just-in-time access has been enabled on a VM, but emergency users request an unrestricted source-address exception rather than their current approved workstation IP; this control addresses a different failure condition.

Question 146

A Microsoft Azure administrator receives this requirement: An Azure API Management product accepts anonymous calls to a sensitive paid API because subscription enforcement is disabled. Which operating control most directly reduces this recurring risk?

  1. Test negative token cases after identity provider and APIM policy changes.
  2. Prohibit sharing account keys with external consumers and inventory issued SAS capabilities.
  3. Review APIM API and product access configuration when introducing new routes.
  4. Review client certificate trust and renewal processes for all privileged API consumers.

Explanation

Correct Answer

C:

This guardrail addresses api management subscription key usage: The API or product does not require the intended APIM subscription key or equivalent authentication control. The prevention measure is: Review APIM API and product access configuration when introducing new routes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. “Test negative token cases after identity provider and APIM policy changes” would address that alternative cause, not the condition in this question: the API or product does not require the intended APIM subscription key or equivalent authentication control.

B:

“Prohibit sharing account keys with external consumers and inventory issued SAS capabilities” responds to this separate finding: disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. This question instead needs “Review APIM API and product access configuration when introducing new routes”, 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. “Review client certificate trust and renewal processes for all privileged API consumers” applies to that separate problem. The observed case is an Azure API Management product accepts anonymous calls to a sensitive paid API because subscription enforcement is disabled; choosing this alternative would address the wrong failure mode.

Question 147

A platform security assessment reveals this issue: A Defender for Cloud alert reports suspicious VM command execution, but analysts close it immediately because the VM currently appears healthy. After remediation, which test result best proves the intended change?

  1. The case records corroborated benign activity or documented remediation of the suspicious command chain.
  2. The new VM has a completed supported agentless assessment with software vulnerability recommendations visible to security owners.
  3. The migrated GitLab infrastructure-as-code repositories become visible with supported security findings.
  4. The critical exposed resource is patched or protected first and the residual exposure is documented.

Explanation

Correct Answer

A:

This validates the specific control for defender for cloud alert investigation evidence: A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. The associated corrective action is: Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment. Testing a different component would not establish this result.

Incorrect Answers

B:

Supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent. “Enable the supported agentless scanning capability and verify its resource scope, prerequisites and results” would address that alternative cause, not the condition in this question: a single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines.

C:

“Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories” responds to this separate finding: code security inventory and posture coverage depend on a supported connector for the actual source-control platform. This question instead needs “Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment”, so the alternative does not meet the stated condition.

D:

Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. “Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw” applies to that separate problem. The observed case is a Defender for Cloud alert reports suspicious VM command execution, but analysts close it immediately because the VM currently appears healthy; choosing this alternative would address the wrong failure mode.

Question 148

A platform security assessment reveals this issue: An administrator edits Virtual Network Manager configuration definitions but never deploys the configuration to the required target regions. Which operating control most directly reduces this recurring risk?

  1. Include deployment status and region target verification in network manager change closeout.
  2. Include address-plan collision checks before authorizing VNet creation or peering requests.
  3. Review exposed DNAT entries against asset owners and remove obsolete Internet listeners.
  4. Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy.

Explanation

Correct Answer

A:

This guardrail addresses central network intent deployment region: Saving network manager intent does not itself apply connectivity or security configuration to target regions. The prevention measure is: Include deployment status and region target verification in network manager change closeout. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. “Include address-plan collision checks before authorizing VNet creation or peering requests” 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.

C:

“Review exposed DNAT entries against asset owners and remove obsolete Internet listeners” responds to this separate finding: inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. This question instead needs “Include deployment status and region target verification in network manager change closeout”, so the alternative does not meet the stated condition.

D:

An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. “Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy” 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 149

While validating an Azure workload, the security team finds: An administrator opens a public RDP endpoint on every production VM even though security rules prohibit direct Internet-facing management ports. Which explanation fits the observed symptoms most closely?

  1. Azure resource deployment health does not automatically establish guest operating system patch compliance.
  2. Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access.
  3. Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk.
  4. Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections.

Explanation

Correct Answer

D:

The described technical condition is: Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. The appropriate corrective action is: Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules. Confirm with: Approved administrators reach private VMs using Bastion while direct Internet RDP and SSH attempts fail.

Incorrect Answers

A:

Azure resource deployment health does not automatically establish guest operating system patch compliance. “Apply approved Azure Update Manager or supported guest patch orchestration and verify patch installation” would address that alternative cause, not the condition in this question: direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections.

B:

“Configure the encryption set and supported Key Vault key permissions, then associate eligible disks” 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 “Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules”, so the alternative does not meet the stated condition.

C:

Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. “Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies” applies to that separate problem. The observed case is an administrator opens a public RDP endpoint on every production VM even though security rules prohibit direct Internet-facing management ports; choosing this alternative would address the wrong failure mode.

Question 150

The cloud operations team reviews the following risk: A pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure. Which configuration change most directly resolves this problem?

  1. Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope.
  2. Configure workload identity on the service account and scoped access to the target Key Vault.
  3. Enable the supported network policy option and enforce namespace/pod label based allowlists.
  4. Move credentials into a managed secrets service and use approved persistent data storage where needed.

Explanation

Correct Answer

B:

The cause is: The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. The appropriate change is: Configure workload identity on the service account and scoped access to the target Key Vault. Verify it with this outcome: The pod obtains a short-lived token and reads only the approved secret without stored client secrets.

Incorrect Answers

A:

This action concerns aks microsoft entra and kubernetes rbac, where Cluster authorization is not aligned with identity-based RBAC and separation of duties. The reported incident instead involves The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.

C:

This action concerns aks pod network policy isolation, where Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. The corrective response here is “Configure workload identity on the service account and scoped access to the target Key Vault”; this alternative does not provide that response.

D:

This action concerns ephemeral disk data handling, where Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. The stem reports a pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure; this control addresses a different failure condition.