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 48

Question 470

A regulated Azure tenant has this security condition: A security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events. What governance practice would best prevent the same failure?

  1. Audit TDE status and key rotation separately from transport TLS compliance.
  2. Review client-driver support, key custody and query limitations before Always Encrypted rollout.
  3. Validate SQL private connectivity and public network restrictions during application onboarding.
  4. Test audit data delivery and access controls after SQL platform and diagnostic changes.

Explanation

Correct Answer

D:

This guardrail addresses azure sql auditing destination configuration: Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. The prevention measure is: Test audit data delivery and access controls after SQL platform and diagnostic changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Audit TDE status and key rotation separately from transport TLS compliance” 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.

B:

“Review client-driver support, key custody and query limitations before Always Encrypted rollout” responds to this separate finding: tDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. This question instead needs “Test audit data delivery and access controls after SQL platform and diagnostic changes”, so the alternative does not meet the stated condition.

C:

The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. “Validate SQL private connectivity and public network restrictions during application onboarding” 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 471

A platform security assessment reveals this issue: A short-lived Azure Container Instance job uses a copied account key to fetch blobs, and its image logs inadvertently disclose the key. Which underlying control gap is responsible for the issue?

  1. Control-plane version compliance is distinct from node OS image and node pool security patch state.
  2. The container group relies on a long-lived shared credential rather than supported managed identity authorization.
  3. The application's ingress configuration enables external exposure instead of internal-only routing.
  4. Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control.

Explanation

Correct Answer

B:

The described technical condition is: The container group relies on a long-lived shared credential rather than supported managed identity authorization. The appropriate corrective action is: Enable an appropriate managed identity on the container group and grant limited blob data access. Confirm with: The container reads approved blobs using its identity without a stored storage key.

Incorrect Answers

A:

Control-plane version compliance is distinct from node OS image and node pool security patch state. “Schedule supported AKS node image updates and verify rollout health across node pools” would address that alternative cause, not the condition in this question: the container group relies on a long-lived shared credential rather than supported managed identity authorization.

C:

“Configure internal ingress and supported network isolation for the Container App environment” responds to this separate finding: the application's ingress configuration enables external exposure instead of internal-only routing. This question instead needs “Enable an appropriate managed identity on the container group and grant limited blob data access”, so the alternative does not meet the stated condition.

D:

Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. “Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components” applies to that separate problem. The observed case is a short-lived Azure Container Instance job uses a copied account key to fetch blobs, and its image logs inadvertently disclose the key; choosing this alternative would address the wrong failure mode.

Question 472

A production Azure security implementation shows this failure: A ransomware response plan assumes that ordinary backup retention settings prevent all privileged administrators from modifying recovery point protections. Which recurring validation best protects against the observed problem?

  1. Audit Key Vault public exposure and the exact network dependencies of each application after changes.
  2. Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change.
  3. Audit exclusions whenever subscriptions move between management groups or baseline assignments change.
  4. Review immutability settings and approval gates before changing backup security or recovery policies.

Explanation

Correct Answer

D:

This guardrail addresses azure backup immutable vault controls: An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. The prevention measure is: Review immutability settings and approval gates before changing backup security or recovery policies. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. “Audit Key Vault public exposure and the exact network dependencies of each application after changes” would address that alternative cause, not the condition in this question: an immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection.

B:

“Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change” responds to this separate finding: private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client. This question instead needs “Review immutability settings and approval gates before changing backup security or recovery policies”, so the alternative does not meet the stated condition.

C:

An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. “Audit exclusions whenever subscriptions move between management groups or baseline assignments change” applies to that separate problem. The observed case is a ransomware response plan assumes that ordinary backup retention settings prevent all privileged administrators from modifying recovery point protections; choosing this alternative would address the wrong failure mode.

Question 473

A production Azure security implementation shows this failure: A machine-level extension installs arbitrary scripts using an overprivileged credential, and operators have no approved process to review its payload. What is the most appropriate corrective step?

  1. Restrict extension publishers and deployment rights and deploy only signed or approved scripts.
  2. Configure the Microsoft Entra administrator and create appropriate contained database users and roles.
  3. Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration.
  4. Configure the encryption set and supported Key Vault key permissions, then associate eligible disks.

Explanation

Correct Answer

A:

The cause is: Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. The appropriate change is: Restrict extension publishers and deployment rights and deploy only signed or approved scripts. Verify it with this outcome: An unauthorized extension request is rejected and approved changes are traceable in configuration history.

Incorrect Answers

B:

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 reported incident instead involves Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access.

C:

This action concerns jit request ip restriction, where JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. The corrective response here is “Restrict extension publishers and deployment rights and deploy only signed or approved scripts”; this alternative does not provide that response.

D:

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 stem reports a machine-level extension installs arbitrary scripts using an overprivileged credential, and operators have no approved process to review its payload; this control addresses a different failure condition.

Question 474

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. What observation is the strongest validation evidence?

  1. A request without authorized API credentials is rejected and approved subscribers receive normal responses.
  2. Approved CI pipelines push or pull with attributable identities and the shared admin login fails.
  3. The cluster retrieves approved images using private addresses while public registry access stays disabled.
  4. The partner can perform only the approved blob operation while account key access is not disclosed.

Explanation

Correct Answer

A:

This validates the specific control for api management subscription key usage: The API or product does not require the intended APIM subscription key or equivalent authentication control. The associated corrective action is: Enable appropriate APIM subscription requirements and validate product/API associations. Testing a different component would not establish this result.

Incorrect Answers

B:

The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. “Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles” 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.

C:

“Configure eligible ACR private endpoints and DNS paths for all required registry endpoints” responds to this separate finding: private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. This question instead needs “Enable appropriate APIM subscription requirements and validate product/API associations”, so the alternative does not meet the stated condition.

D:

Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. “Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys” 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 475

While validating an Azure workload, the security team finds: An organization enables agentless scanning for Azure servers and assumes the same setting activates threat protection for its connected AWS virtual machines. Which explanation fits the observed symptoms most closely?

  1. A connector's project enrollment or organization-level integration scope may omit newly created GCP projects.
  2. A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration.
  3. A multicloud connector can exist while its required permissions, services or security plan settings are incomplete.
  4. Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions.

Explanation

Correct Answer

D:

The described technical condition is: Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. The appropriate corrective action is: Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances. Confirm with: Selected connected AWS instances appear in the correct Defender plan with expected scanning and alert coverage.

Incorrect Answers

A:

A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. “Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects” 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.

B:

“Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives” responds to this separate finding: a recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. 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.

C:

A multicloud connector can exist while its required permissions, services or security plan settings are incomplete. “Review and repair the AWS connector's authorized access and enable applicable posture assessment capabilities” 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 476

A regulated Azure tenant has this security condition: A storage account is limited to selected VNets but a newly created workload subnet reaches only the public service and fails its access restriction. Which explanation fits the observed symptoms most closely?

  1. ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit.
  2. Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint.
  3. The provider has not published a supported Private Link Service behind an eligible standard internal load balancer.
  4. The required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall.

Explanation

Correct Answer

D:

The described technical condition is: The required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. The appropriate corrective action is: Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage. Confirm with: The selected subnet accesses the restricted account while unlisted subnets remain blocked.

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 required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall.

B:

“Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required” responds to this separate finding: regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. This question instead needs “Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage”, so the alternative does not meet the stated condition.

C:

The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval” applies to that separate problem. The observed case is a storage account is limited to selected VNets but a newly created workload subnet reaches only the public service and fails its access restriction; choosing this alternative would address the wrong failure mode.

Question 477

A Microsoft Azure administrator receives this requirement: A regulated Azure SQL database must encrypt database files and backups at rest, but administrators focus only on the client TLS connection. Which underlying control gap is responsible for the issue?

  1. The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction.
  2. TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.
  3. The file access path needs compatible secure SMB protocol and supported encrypted transport settings.
  4. Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.

Explanation

Correct Answer

B:

The described technical condition is: TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. The appropriate corrective action is: Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration. Confirm with: The database reports TDE enabled and encrypted at-rest backups while client connections remain supported.

Incorrect Answers

A:

The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. “Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access” would address that alternative cause, not the condition in this question: tLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.

C:

“Use supported modern SMB client configuration and private connectivity or TLS where applicable” responds to this separate finding: the file access path needs compatible secure SMB protocol and supported encrypted transport settings. This question instead needs “Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration”, so the alternative does not meet the stated condition.

D:

Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. “Configure supported SQL driver encryption with certificate chain and hostname validation enabled” applies to that separate problem. The observed case is a regulated Azure SQL database must encrypt database files and backups at rest, but administrators focus only on the client TLS connection; choosing this alternative would address the wrong failure mode.

Question 478

A platform security assessment reveals this issue: A Conditional Access policy requiring strong auth is assigned only to a test application, leaving a production administration application outside its scope. What is the most appropriate corrective step?

  1. Configure a justified sign-in frequency session control for the appropriate protected application.
  2. Include the intended enterprise application or cloud resource in the Conditional Access assignment.
  3. Create a policy that blocks legacy client authentication for the necessary users and applications.
  4. Select the required combination of grant controls and confirm the intended AND behavior.

Explanation

Correct Answer

B:

The cause is: The target cloud application selection is wrong and policy enforcement does not cover the actual resource. The appropriate change is: Include the intended enterprise application or cloud resource in the Conditional Access assignment. Verify it with this outcome: Production sign-in logs show the relevant policy applied and the protected authentication requirement enforced.

Incorrect Answers

A:

This action concerns conditional access sign in frequency, where The relevant Conditional Access session control lacks the required sign-in frequency and session behavior. The reported incident instead involves The target cloud application selection is wrong and policy enforcement does not cover the actual resource.

C:

This action concerns legacy authentication blocking, where The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. The corrective response here is “Include the intended enterprise application or cloud resource in the Conditional Access assignment”; this alternative does not provide that response.

D:

This action concerns conditional access multiple grant controls, where The grant control operator allows any selected requirement rather than requiring all specified requirements. The stem reports a Conditional Access policy requiring strong auth is assigned only to a test application, leaving a production administration application outside its scope; this control addresses a different failure condition.

Question 479

During a cloud security review, the operations team observes: A pod mounts static secrets in its deployment manifest even though the enterprise wants rotating secrets from Azure Key Vault. What observation is the strongest validation evidence?

  1. Approved application flows succeed while prohibited cross-namespace traffic is dropped.
  2. An unauthorized operator cannot generate snapshot access while recovery administrators retain documented access.
  3. A deletion attempt cannot immediately eradicate protected backup recovery points and recovery remains possible.
  4. The running pod obtains the required secret without the value embedded in the deployed manifest.

Explanation

Correct Answer

D:

This validates the specific control for aks key vault csi secret retrieval: Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. The associated corrective action is: Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible. Testing a different component would not establish this result.

Incorrect Answers

A:

Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. “Enable the supported network policy option and enforce namespace/pod label based allowlists” would address that alternative cause, not the condition in this question: application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration.

B:

“Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals” responds to this separate finding: snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. This question instead needs “Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible”, so the alternative does not meet the stated condition.

C:

Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. “Enable supported vault soft delete and enhanced protection settings including immutable backup where required” applies to that separate problem. The observed case is a pod mounts static secrets in its deployment manifest even though the enterprise wants rotating secrets from Azure Key Vault; choosing this alternative would address the wrong failure mode.

Question 480

While validating an Azure workload, the security team finds: A private service is reachable from some VMs but times out from a specific subnet, and the team needs path-based evidence of the failure. Which outcome most clearly verifies that the issue is resolved?

  1. Security inventory shows production VNets under the required DDoS protection configuration.
  2. The identified next hop matches the approved routing design after changes, with no unintended appliance loop.
  3. Direct origin requests are rejected while requests passing the edge WAF are served.
  4. The connection test identifies reachability and applicable hop failures before and after the repair.

Explanation

Correct Answer

D:

This validates the specific control for connection troubleshoot destination metrics: A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. The associated corrective action is: Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results. Testing a different component would not establish this result.

Incorrect Answers

A:

Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. “Associate intended eligible VNets with the correct plan and validate protection settings” would address that alternative cause, not the condition in this question: a point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues.

B:

“Inspect effective routes and run Network Watcher next hop against the intended destination IP” responds to this separate finding: a user-defined or propagated route controls the next hop independently of NSG allow decisions. This question instead needs “Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results”, 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 private service is reachable from some VMs but times out from a specific subnet, and the team needs path-based evidence of the failure; choosing this alternative would address the wrong failure mode.