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 86

Question 850

While validating an Azure workload, the security team finds: A team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged. Which outcome most clearly verifies that the issue is resolved?

  1. Recreated instances retrieve approved secrets securely without relying on local ephemeral disk recovery.
  2. Only approved private keys authenticate to the private Linux VM and shared password login is unavailable.
  3. The vulnerable image is detected and a patched replacement is deployed before production exposure.
  4. Developers perform only authorized namespace tasks and cluster-admin operations require eligible roles.

Explanation

Correct Answer

A:

This validates the specific control for ephemeral disk data handling: Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. The associated corrective action is: Move credentials into a managed secrets service and use approved persistent data storage where needed. Testing a different component would not establish this result.

Incorrect Answers

B:

Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. “Use controlled SSH public-key authentication and restrict access through Bastion or approved private management” would address that alternative cause, not the condition in this question: ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories.

C:

“Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation” responds to this separate finding: authentication to a container registry does not establish that deployed images meet vulnerability security requirements. This question instead needs “Move credentials into a managed secrets service and use approved persistent data storage where needed”, so the alternative does not meet the stated condition.

D:

Cluster authorization is not aligned with identity-based RBAC and separation of duties. “Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope” applies to that separate problem. The observed case is a team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged; choosing this alternative would address the wrong failure mode.

Question 851

While validating an Azure workload, the security team finds: A branch app subnet sends outbound Internet traffic straight to its default system route despite an architecture requiring inspection by a central Azure Firewall. Which result confirms the relevant security control is effective?

  1. Unauthorized Internet egress fails while approved endpoints remain reachable through logged channels.
  2. The app subnet's outbound flows traverse the central inspection appliance and are visible in policy logs.
  3. The diagnostic result identifies the NSG rule responsible and the approved flow passes after targeted remediation.
  4. Spoke-to-spoke traffic reaches its destination through the approved hub appliance and no unintended direct path exists.

Explanation

Correct Answer

B:

This validates the specific control for user defined default route to inspection: No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. The associated corrective action is: Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP. Testing a different component would not establish this result.

Incorrect Answers

A:

Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. “Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls” would address that alternative cause, not the condition in this question: no effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance.

C:

“Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision” responds to this separate finding: the active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view. This question instead needs “Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP”, so the alternative does not meet the stated condition.

D:

The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. “Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs” applies to that separate problem. The observed case is a branch app subnet sends outbound Internet traffic straight to its default system route despite an architecture requiring inspection by a central Azure Firewall; choosing this alternative would address the wrong failure mode.

Question 852

During a cloud security review, the operations team observes: A shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs. What should the engineer implement first to address the weakness?

  1. Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles.
  2. Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims.
  3. Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions.
  4. Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys.

Explanation

Correct Answer

A:

The cause is: The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The appropriate change is: Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles. Verify it with this outcome: Approved CI pipelines push or pull with attributable identities and the shared admin login fails.

Incorrect Answers

B:

This action concerns api management validate jwt policy, where API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. The reported incident instead involves The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.

C:

This action concerns apim throttling policy for abuse, where The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. The corrective response here is “Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles”; 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 shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs; this control addresses a different failure condition.

Question 853

A regulated Azure tenant has this security condition: A legacy VM uses Azure Disk Encryption but a required Key Vault key or secret is disabled during rotation and the VM cannot unlock encrypted volumes. Which safeguard would best prevent this issue from recurring?

  1. Test Bastion SKU and client feature support before designing remote-administration access.
  2. Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts.
  3. Review JIT requests and ensure routine administrative ports remain closed outside authorized windows.
  4. Audit installed extensions and review guest-level execution privileges after VM changes.

Explanation

Correct Answer

B:

This guardrail addresses azure disk encryption key vault dependency: Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. The prevention measure is: Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. “Test Bastion SKU and client feature support before designing remote-administration access” would address that alternative cause, not the condition in this question: azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk.

C:

“Review JIT requests and ensure routine administrative ports remain closed outside authorized windows” responds to this separate finding: the VM's NSG exposes a persistent management port rather than enforcing just-in-time access. This question instead needs “Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts”, 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 legacy VM uses Azure Disk Encryption but a required Key Vault key or secret is disabled during rotation and the VM cannot unlock encrypted volumes; choosing this alternative would address the wrong failure mode.

Question 854

A Microsoft Azure administrator receives this requirement: An analyst receives generic Azure Contributor access at a storage account yet cannot list blobs using Microsoft Entra authorization, despite managing account settings. What technical cause best accounts for the described behavior?

  1. Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.
  2. The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.
  3. PIM role settings have not required the intended multifactor or authentication-strength control at activation.
  4. A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.

Explanation

Correct Answer

A:

The described technical condition is: Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. The appropriate corrective action is: Assign Storage Blob Data Reader or another appropriate data role at the least required scope. Confirm with: The analyst lists authorized blobs with Entra authentication but cannot change account-level configuration.

Incorrect Answers

B:

The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. “Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized” would address that alternative cause, not the condition in this question: azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.

C:

“Configure the PIM role activation requirements to demand the approved strong authentication method” responds to this separate finding: pIM role settings have not required the intended multifactor or authentication-strength control at activation. This question instead needs “Assign Storage Blob Data Reader or another appropriate data role at the least required scope”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an analyst receives generic Azure Contributor access at a storage account yet cannot list blobs using Microsoft Entra authorization, despite managing account settings; choosing this alternative would address the wrong failure mode.

Question 855

While validating an Azure workload, the security team finds: A company wants consumers in other VNets to access its internally hosted load-balanced service privately without exposing a public listener. Which explanation fits the observed symptoms most closely?

  1. ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit.
  2. The provider has not published a supported Private Link Service behind an eligible standard internal load balancer.
  3. App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections.
  4. Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint.

Explanation

Correct Answer

B:

The described technical condition is: The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. The appropriate corrective action is: Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval. Confirm with: Authorized consumer private endpoints connect to the provider service while unapproved consumers are rejected.

Incorrect Answers

A:

ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. “Implement supported IPsec over ExpressRoute or application-layer TLS encryption according to the threat model” would address that alternative cause, not the condition in this question: the provider has not published a supported Private Link Service behind an eligible standard internal load balancer.

C:

“Configure regional App Service VNet integration and the necessary subnet routing and DNS” responds to this separate finding: app Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. This question instead needs “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval”, so the alternative does not meet the stated condition.

D:

Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. “Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required” applies to that separate problem. The observed case is a company wants consumers in other VNets to access its internally hosted load-balanced service privately without exposing a public listener; choosing this alternative would address the wrong failure mode.

Question 856

During a cloud security review, the operations team observes: A web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured. Which underlying control gap is responsible for the issue?

  1. App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections.
  2. Private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended.
  3. A private endpoint has not been configured or public network access has not been restricted for the resource.
  4. The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address.

Explanation

Correct Answer

A:

The described technical condition is: App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. The appropriate corrective action is: Configure regional App Service VNet integration and the necessary subnet routing and DNS. Confirm with: The web app reaches the internal backend over the intended outbound integrated network path.

Incorrect Answers

B:

Private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. “Enable supported private endpoint network policies for the subnet and validate the intended NSG controls” would address that alternative cause, not the condition in this question: app Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections.

C:

“Create an approved Private Endpoint in the workload VNet and disable or restrict the service's public access” responds to this separate finding: a private endpoint has not been configured or public network access has not been restricted for the resource. This question instead needs “Configure regional App Service VNet integration and the necessary subnet routing and DNS”, so the alternative does not meet the stated condition.

D:

The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Configure the correct privatelink DNS zone record and link the client VNet to the zone” applies to that separate problem. The observed case is a web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured; choosing this alternative would address the wrong failure mode.

Question 857

A regulated Azure tenant has this security condition: A VM cannot reach a backend on TCP 5432, and an operator keeps guessing which NSG is responsible without testing effective decisions. Which condition most directly explains the failure?

  1. An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs.
  2. A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues.
  3. Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets.
  4. The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template.

Explanation

Correct Answer

D:

The described technical condition is: The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. The appropriate corrective action is: Run Network Watcher IP flow verify with the test source, destination, direction and port. Confirm with: Diagnostics identify the exact applicable rule and the corrected flow matches approved connectivity.

Incorrect Answers

A:

An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. “Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources” would address that alternative cause, not the condition in this question: the blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template.

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 “Run Network Watcher IP flow verify with the test source, destination, direction and port”, so the alternative does not meet the stated condition.

C:

Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. “Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow” applies to that separate problem. The observed case is a VM cannot reach a backend on TCP 5432, and an operator keeps guessing which NSG is responsible without testing effective decisions; choosing this alternative would address the wrong failure mode.

Question 858

While validating an Azure workload, the security team finds: An AKS team stores production credentials in Kubernetes Secrets and assumes base64 encoding alone provides strong confidentiality of stored secret values. Which remediation best addresses the specific issue?

  1. Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access.
  2. Enable supported secret encryption and external secret management using Key Vault where required.
  3. Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients.
  4. Configure the Microsoft Entra administrator and create appropriate contained database users and roles.

Explanation

Correct Answer

B:

The cause is: Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. The appropriate change is: Enable supported secret encryption and external secret management using Key Vault where required. Verify it with this outcome: Secrets are protected in the intended storage path and only approved workload identities can retrieve values.

Incorrect Answers

A:

This action concerns azure sql private endpoint dns and public disable, where The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. The reported incident instead involves Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls.

C:

This action concerns sql always encrypted client column isolation, where TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. The corrective response here is “Enable supported secret encryption and external secret management using Key Vault where required”; this alternative does not provide that response.

D:

This action concerns azure sql microsoft entra administrator auth, where The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. The stem reports an AKS team stores production credentials in Kubernetes Secrets and assumes base64 encoding alone provides strong confidentiality of stored secret values; this control addresses a different failure condition.

Question 859

A production Azure security implementation shows this failure: A PIM role activation succeeds for a sensitive administrator without a fresh strong authentication check because the role settings omit MFA. What is the most appropriate corrective step?

  1. Configure the PIM role activation requirements to demand the approved strong authentication method.
  2. Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations.
  3. Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized.
  4. Assign the approved read-only role at a suitable management group with the intended child subscription coverage.

Explanation

Correct Answer

A:

The cause is: PIM role settings have not required the intended multifactor or authentication-strength control at activation. The appropriate change is: Configure the PIM role activation requirements to demand the approved strong authentication method. Verify it with this outcome: Activation is rejected until the applicant satisfies the configured challenge and succeeds only for authorized operators.

Incorrect Answers

B:

This action concerns storage blob rbac conditions, where A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. The reported incident instead involves PIM role settings have not required the intended multifactor or authentication-strength control at activation.

C:

This action concerns reader role versus resource modification, where The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. The corrective response here is “Configure the PIM role activation requirements to demand the approved strong authentication method”; this alternative does not provide that response.

D:

This action concerns management group security assignment, where Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The stem reports a PIM role activation succeeds for a sensitive administrator without a fresh strong authentication check because the role settings omit MFA; this control addresses a different failure condition.

Question 860

An Azure security engineer investigates the following incident: A regulated organization needs to apply a coordinated security baseline to ten subscriptions, but administrators assign isolated definitions with inconsistent parameters. Which safeguard would best prevent this issue from recurring?

  1. Keep configuration policy checks separate from identity, data-plane and network access acceptance tests.
  2. Audit exclusions whenever subscriptions move between management groups or baseline assignments change.
  3. Review initiative versions and parameter mappings before every organization wide compliance rollout.
  4. Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change.

Explanation

Correct Answer

C:

This guardrail addresses azure policy initiative and parameter assignments: Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. The prevention measure is: Review initiative versions and parameter mappings before every organization wide compliance rollout. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. “Keep configuration policy checks separate from identity, data-plane and network access acceptance tests” would address that alternative cause, not the condition in this question: without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions.

B:

“Audit exclusions whenever subscriptions move between management groups or baseline assignments change” responds to this separate finding: an excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. This question instead needs “Review initiative versions and parameter mappings before every organization wide compliance rollout”, so the alternative does not meet the stated condition.

D:

Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client. “Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change” applies to that separate problem. The observed case is a regulated organization needs to apply a coordinated security baseline to ten subscriptions, but administrators assign isolated definitions with inconsistent parameters; choosing this alternative would address the wrong failure mode.