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 98

Question 970

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. Which underlying control gap is responsible for the issue?

  1. Cluster authorization is not aligned with identity-based RBAC and separation of duties.
  2. Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault.
  3. The cluster uses a public API server endpoint rather than a supported private AKS cluster design.
  4. The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.

Explanation

Correct Answer

A:

The described technical condition is: Cluster authorization is not aligned with identity-based RBAC and separation of duties. The appropriate corrective action is: Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope. Confirm with: Developers perform only authorized namespace tasks and cluster-admin operations require eligible roles.

Incorrect Answers

B:

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” 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:

“Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths” responds to this separate finding: the cluster uses a public API server endpoint rather than a supported private AKS cluster design. 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:

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” 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 971

A production Azure security implementation shows this failure: A security owner exports a list of all VMs but accidentally filters only resources tagged Production while untagged systems remain deployed. What is the most appropriate corrective step?

  1. Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope.
  2. Validate exemption justification, owner, expiry and business controls or actually remediate the resource.
  3. Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances.
  4. Query all in-scope Azure resources first and then classify missing or unexpected tags for correction.

Explanation

Correct Answer

D:

The cause is: Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. The appropriate change is: Query all in-scope Azure resources first and then classify missing or unexpected tags for correction. Verify it with this outcome: The report includes the full resource inventory and separately highlights untagged or misclassified resources.

Incorrect Answers

A:

This action concerns azure policy remediation managed identity permissions, where DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. The reported incident instead involves Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth.

B:

This action concerns defender secure score excluded resource handling, where An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. The corrective response here is “Query all in-scope Azure resources first and then classify missing or unexpected tags for correction”; this alternative does not provide that response.

C:

This action concerns defender for cloud cross-account connected aws plans, where Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. The stem reports a security owner exports a list of all VMs but accidentally filters only resources tagged Production while untagged systems remain deployed; this control addresses a different failure condition.

Question 972

The cloud operations team reviews the following risk: An application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress. Which configuration change most directly resolves this problem?

  1. Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable.
  2. Configure a supported Private Link origin and restrict direct public access to the origin service.
  3. Associate intended eligible VNets with the correct plan and validate protection settings.
  4. Inspect effective routes and run Network Watcher next hop against the intended destination IP.

Explanation

Correct Answer

D:

The cause is: A user-defined or propagated route controls the next hop independently of NSG allow decisions. The appropriate change is: Inspect effective routes and run Network Watcher next hop against the intended destination IP. Verify it with this outcome: The identified next hop matches the approved routing design after changes, with no unintended appliance loop.

Incorrect Answers

A:

This action concerns front door origin bypass mitigation, where The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. The reported incident instead involves A user-defined or propagated route controls the next hop independently of NSG allow decisions.

B:

This action concerns front door private link origin protection, where The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. The corrective response here is “Inspect effective routes and run Network Watcher next hop against the intended destination IP”; this alternative does not provide that response.

C:

This action concerns ddos plan coverage and ownership, where Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The stem reports an application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress; this control addresses a different failure condition.

Question 973

A production Azure security implementation shows this failure: A pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure. Which operating control most directly reduces this recurring risk?

  1. Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates.
  2. Audit service accounts and federated identity subjects when deploying workload identities.
  3. Test both ingress and egress network policies with real pods after label changes.
  4. Review snapshot export and managed disk permissions as part of sensitive VM data governance.

Explanation

Correct Answer

B:

This guardrail addresses aks workload identity federation: The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. The prevention measure is: Audit service accounts and federated identity subjects when deploying workload identities. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. “Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates” would address that alternative cause, not the condition in this question: the workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.

C:

“Test both ingress and egress network policies with real pods after label changes” responds to this separate finding: namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. This question instead needs “Audit service accounts and federated identity subjects when deploying workload identities”, so the alternative does not meet the stated condition.

D:

Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. “Review snapshot export and managed disk permissions as part of sensitive VM data governance” applies to that separate problem. The observed case is a pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure; choosing this alternative would address the wrong failure mode.

Question 974

A regulated Azure tenant has this security condition: A Kubernetes developer creates privileged containers that violate corporate policy because the AKS cluster has no centrally evaluated workload restrictions. Which configuration change most directly resolves this problem?

  1. Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings.
  2. Configure a secure Container Apps secret reference or managed identity for database access.
  3. Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels.
  4. Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components.

Explanation

Correct Answer

D:

The cause is: Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. The appropriate change is: Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components. Verify it with this outcome: Noncompliant privileged pod manifests are rejected or audited according to policy while compliant ones run.

Incorrect Answers

A:

This action concerns aks legacy pod identity migration, where The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. The reported incident instead involves Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control.

B:

This action concerns container apps secret references, where Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. The corrective response here is “Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components”; this alternative does not provide that response.

C:

This action concerns aks control plane and container logging, where AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. The stem reports a Kubernetes developer creates privileged containers that violate corporate policy because the AKS cluster has no centrally evaluated workload restrictions; this control addresses a different failure condition.

Question 975

An Azure security engineer investigates the following incident: A container group deployment exposes an API password as an ordinary public environment variable in its template and diagnostic output. Which result confirms the relevant security control is effective?

  1. The workload authenticates without printing or exposing the password in revision configuration.
  2. Normal deployment reports do not reveal the secret, and approved workloads still authenticate to dependencies.
  3. A test workload acquires the required Azure resource token on the supported cluster version.
  4. Security analysts can correlate pod restart, audit and security signals for the affected workload.

Explanation

Correct Answer

B:

This validates the specific control for container instances environment secret handling: Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. The associated corrective action is: Use secure value handling or managed identity based authentication for the containerized application. Testing a different component would not establish this result.

Incorrect Answers

A:

Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. “Configure a secure Container Apps secret reference or managed identity for database access” 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:

“Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings” responds to this separate finding: the workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. This question instead needs “Use secure value handling or managed identity based authentication for the containerized application”, so the alternative does not meet the stated condition.

D:

AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. “Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels” 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 976

The cloud operations team reviews the following risk: Remote engineers connect to a virtual network using shared VPN credentials even though the requirement is individual identity verification and conditional access. Which result confirms the relevant security control is effective?

  1. BGP sessions establish and only approved prefixes appear on both sides of the encrypted connection.
  2. Spoke queries traverse the DNS proxy and the service's allowed FQDN policy operates consistently.
  3. Selected branch and VNet flows pass through the secured hub firewall with centralized control.
  4. Approved named users connect with the required authentication and removed users lose future VPN eligibility.

Explanation

Correct Answer

D:

This validates the specific control for point to site vpn entra authentication: The point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. The associated corrective action is: Configure an appropriate Azure VPN gateway point-to-site authentication method using Microsoft Entra ID. Testing a different component would not establish this result.

Incorrect Answers

A:

The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. “Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state” would address that alternative cause, not the condition in this question: the point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration.

B:

“Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address” responds to this separate finding: spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. This question instead needs “Configure an appropriate Azure VPN gateway point-to-site authentication method using Microsoft Entra ID”, so the alternative does not meet the stated condition.

C:

The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. “Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic” applies to that separate problem. The observed case is remote engineers connect to a virtual network using shared VPN credentials even though the requirement is individual identity verification and conditional access; choosing this alternative would address the wrong failure mode.

Question 977

The cloud operations team reviews the following risk: A subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet. Which outcome most clearly verifies that the issue is resolved?

  1. The app subnet's outbound flows traverse the central inspection appliance and are visible in policy logs.
  2. A test public connection to TCP 3389 fails while legitimate approved administration uses its intended path.
  3. Effective route inspection shows only intended propagated and explicit routes for the target subnet.
  4. Unauthorized Internet egress fails while approved endpoints remain reachable through logged channels.

Explanation

Correct Answer

D:

This validates the specific control for default outbound network access control: Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. The associated corrective action is: Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls. Testing a different component would not establish this result.

Incorrect Answers

A:

No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. “Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP” would address that alternative cause, not the condition in this question: default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply.

B:

“Remove or narrow the broad allow rule and position the applicable deny ahead of competing permissive rules” responds to this separate finding: network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny. This question instead needs “Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls”, so the alternative does not meet the stated condition.

C:

Gateway route propagation remains enabled for the route table and influences effective routing selections. “Disable BGP route propagation on the relevant route table where the approved design requires static steering” applies to that separate problem. The observed case is a subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet; choosing this alternative would address the wrong failure mode.

Question 978

A platform security assessment reveals this issue: A security team creates a Logic App response workflow but expects Defender for Cloud to invoke it automatically without configuring any workflow automation trigger. What observation is the strongest validation evidence?

  1. A matching test alert triggers the intended notification or ticket while unrelated findings do not invoke it.
  2. The migrated GitLab infrastructure-as-code repositories become visible with supported security findings.
  3. The new VM has a completed supported agentless assessment with software vulnerability recommendations visible to security owners.
  4. The new project's eligible repositories appear with relevant infrastructure-as-code findings or documented exclusions.

Explanation

Correct Answer

A:

This validates the specific control for defender for cloud workflow automation trigger scope: A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. The associated corrective action is: Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook. Testing a different component would not establish this result.

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 Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions.

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 the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a security team creates a Logic App response workflow but expects Defender for Cloud to invoke it automatically without configuring any workflow automation trigger; choosing this alternative would address the wrong failure mode.

Question 979

The cloud operations team reviews the following risk: A Key Vault security team permits public network access for every client because some automation jobs cannot reach the vault after firewall restrictions. Which outcome most clearly verifies that the issue is resolved?

  1. The resource is compliant and unauthorized blob reads are independently denied by the appropriate storage permissions.
  2. Authorized operators can restore data while prohibited backup protection reduction operations are rejected.
  3. Approved services retrieve permitted secrets through the expected path while unauthorized public requests fail.
  4. The application authenticates using the current secret and monitoring alerts before the next scheduled expiration.

Explanation

Correct Answer

C:

This validates the specific control for key vault firewall trusted bypass scope: Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. The associated corrective action is: Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. “Validate the configured policy baseline and separately test data-plane role assignments and storage access controls” would address that alternative cause, not the condition in this question: key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads.

B:

“Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing” responds to this separate finding: an immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. This question instead needs “Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path”, so the alternative does not meet the stated condition.

D:

Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. “Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications” applies to that separate problem. The observed case is a Key Vault security team permits public network access for every client because some automation jobs cannot reach the vault after firewall restrictions; choosing this alternative would address the wrong failure mode.

Question 980

A regulated Azure tenant has this security condition: Azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week. Which configuration change most directly resolves this problem?

  1. Inspect effective routes and run Network Watcher next hop against the intended destination IP.
  2. Associate intended eligible VNets with the correct plan and validate protection settings.
  3. Configure relevant firewall diagnostic categories and secure retention for rule and threat events.
  4. Run Network Watcher IP flow verify with the test source, destination, direction and port.

Explanation

Correct Answer

C:

The cause is: Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The appropriate change is: Configure relevant firewall diagnostic categories and secure retention for rule and threat events. Verify it with this outcome: The security team queries the required firewall rule-match records for a controlled test flow.

Incorrect Answers

A:

This action concerns network watcher next hop diagnosis, where A user-defined or propagated route controls the next hop independently of NSG allow decisions. The reported incident instead involves Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination.

B:

This action concerns ddos plan coverage and ownership, where Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The corrective response here is “Configure relevant firewall diagnostic categories and secure retention for rule and threat events”; this alternative does not provide that response.

D:

This action concerns network watcher ip flow verification, where The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. The stem reports azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week; this control addresses a different failure condition.