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 96

Question 950

A platform security assessment reveals this issue: A team treats ExpressRoute private connectivity as equivalent to end-to-end payload encryption for regulated traffic between sites and Azure. Which operating control most directly reduces this recurring risk?

  1. Verify DNS zone links and forwarders for all VNets consuming a private service.
  2. Check supported private endpoint network policy settings before relying on subnet inspection rules.
  3. Treat private transport and payload encryption as separate security controls in architecture reviews.
  4. Choose Private Link when an actual private service endpoint is required, rather than equating it with service endpoints.

Explanation

Correct Answer

C:

This guardrail addresses expressroute encryption requirement: ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. The prevention measure is: Treat private transport and payload encryption as separate security controls in architecture reviews. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Verify DNS zone links and forwarders for all VNets consuming a private service” would address that alternative cause, not the condition in this question: expressRoute private connectivity does not by itself guarantee encryption of application data in transit.

B:

“Check supported private endpoint network policy settings before relying on subnet inspection rules” responds to this separate finding: private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. This question instead needs “Treat private transport and payload encryption as separate security controls in architecture reviews”, so the alternative does not meet the stated condition.

D:

Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. “Choose Private Link when an actual private service endpoint is required, rather than equating it with service endpoints” applies to that separate problem. The observed case is a team treats ExpressRoute private connectivity as equivalent to end-to-end payload encryption for regulated traffic between sites and Azure; choosing this alternative would address the wrong failure mode.

Question 951

A regulated Azure tenant has this security condition: An AKS project relies on a deprecated pod-identity approach, and a newer cluster deployment fails to authenticate pods to Azure resources. Which condition most directly explains the failure?

  1. The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model.
  2. The cluster's public API server authorized IP ranges were not configured for restricted administrative access.
  3. Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control.
  4. Control-plane version compliance is distinct from node OS image and node pool security patch state.

Explanation

Correct Answer

A:

The described technical condition is: The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. The appropriate corrective action is: Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings. Confirm with: A test workload acquires the required Azure resource token on the supported cluster version.

Incorrect Answers

B:

The cluster's public API server authorized IP ranges were not configured for restricted administrative access. “Configure approved API server authorized IP ranges or move to private control-plane access” would address that alternative cause, not the condition in this question: the workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model.

C:

“Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components” responds to this separate finding: cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. This question instead needs “Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings”, 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. “Schedule supported AKS node image updates and verify rollout health across node pools” applies to that separate problem. The observed case is an AKS project relies on a deprecated pod-identity approach, and a newer cluster deployment fails to authenticate pods to Azure resources; choosing this alternative would address the wrong failure mode.

Question 952

While validating an Azure workload, the security team finds: A custom operations role includes virtual machine start action but also excludes it in NotActions, so its assigned users cannot initiate expected power operations. Which condition most directly explains the failure?

  1. PIM role settings have not required the intended multifactor or authentication-strength control at activation.
  2. NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule.
  3. Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted.
  4. Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.

Explanation

Correct Answer

B:

The described technical condition is: NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. The appropriate corrective action is: Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment. Confirm with: A test identity starts the intended VM and remains unable to delete unrelated resources.

Incorrect Answers

A:

PIM role settings have not required the intended multifactor or authentication-strength control at activation. “Configure the PIM role activation requirements to demand the approved strong authentication method” would address that alternative cause, not the condition in this question: notActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule.

C:

“Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope” responds to this separate finding: azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. This question instead needs “Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment”, so the alternative does not meet the stated condition.

D:

Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. “Assign the approved read-only role at a suitable management group with the intended child subscription coverage” applies to that separate problem. The observed case is a custom operations role includes virtual machine start action but also excludes it in NotActions, so its assigned users cannot initiate expected power operations; choosing this alternative would address the wrong failure mode.

Question 953

During a cloud security review, the operations team observes: A design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint. What observation is the strongest validation evidence?

  1. Authorized consumer private endpoints connect to the provider service while unapproved consumers are rejected.
  2. The service resolves to a VNet private address and only permitted private clients connect.
  3. Clients inside authorized networks reach the app over the private endpoint while public requests fail.
  4. A capture or configuration review confirms sensitive payloads are cryptographically protected over the private circuit.

Explanation

Correct Answer

B:

This validates the specific control for private endpoint versus service endpoint isolation: Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. The associated corrective action is: Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.

C:

“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 “Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint; choosing this alternative would address the wrong failure mode.

Question 954

A production Azure security implementation shows this failure: A workload subnet is supposed to block inbound RDP from the Internet, but an allow rule with priority 100 permits port 3389 before a deny rule at priority 300. Which underlying control gap is responsible for the issue?

  1. Network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny.
  2. An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group.
  3. The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.
  4. Gateway route propagation remains enabled for the route table and influences effective routing selections.

Explanation

Correct Answer

A:

The described technical condition is: Network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny. The appropriate corrective action is: Remove or narrow the broad allow rule and position the applicable deny ahead of competing permissive rules. Confirm with: A test public connection to TCP 3389 fails while legitimate approved administration uses its intended path.

Incorrect Answers

B:

An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. “Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria” would address that alternative cause, not the condition in this question: network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny.

C:

“Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs” responds to this separate finding: the necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. This question instead needs “Remove or narrow the broad allow rule and position the applicable deny ahead of competing permissive rules”, so the alternative does not meet the stated condition.

D:

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 workload subnet is supposed to block inbound RDP from the Internet, but an allow rule with priority 100 permits port 3389 before a deny rule at priority 300; choosing this alternative would address the wrong failure mode.

Question 955

A platform security assessment reveals this issue: A tenant permits employees to consent to any third-party application, resulting in a rogue app receiving broad mailbox-related scopes. What should the engineer implement first to address the weakness?

  1. Have an authorized administrator evaluate and grant only the required application permission after review.
  2. Configure a certificate credential or supported workload federation and remove the leaked text secret.
  3. Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow.
  4. Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles.

Explanation

Correct Answer

C:

The cause is: The user consent configuration permits risky OAuth grants without publisher and permission restrictions. The appropriate change is: Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow. Verify it with this outcome: A test unverified high-risk application cannot gain requested scopes through ordinary user consent.

Incorrect Answers

A:

This action concerns admin consent for sensitive application permission, where The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. The reported incident instead involves The user consent configuration permits risky OAuth grants without publisher and permission restrictions.

B:

This action concerns certificate based app credential, where The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. The corrective response here is “Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow”; this alternative does not provide that response.

D:

This action concerns cross tenant service principal consent, where Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The stem reports a tenant permits employees to consent to any third-party application, resulting in a rogue app receiving broad mailbox-related scopes; this control addresses a different failure condition.

Question 956

A production Azure security implementation shows this failure: A public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application. Which underlying control gap is responsible for the issue?

  1. The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode.
  2. The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline.
  3. SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.
  4. The custom domain has no correct TLS certificate binding for the expected host name.

Explanation

Correct Answer

A:

The described technical condition is: The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. The appropriate corrective action is: After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener. Confirm with: Controlled malicious request patterns are blocked while normal requests pass and logs record rule decisions.

Incorrect Answers

B:

The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. “Set the supported minimum TLS version to an approved modern value and verify certificate configuration” would address that alternative cause, not the condition in this question: the Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode.

C:

“Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls” responds to this separate finding: sQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. This question instead needs “After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener”, so the alternative does not meet the stated condition.

D:

The custom domain has no correct TLS certificate binding for the expected host name. “Bind a valid certificate to the custom hostname using an approved App Service certificate mechanism” applies to that separate problem. The observed case is a public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application; choosing this alternative would address the wrong failure mode.

Question 957

A platform security assessment reveals this issue: A data lake receives unusual external blob reads and the organization relies only on daily access log exports for incident detection. Which recurring validation best protects against the observed problem?

  1. Assess database threat protection plan coverage separately from firewall and SQL audit configuration.
  2. Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly.
  3. Reassess container images when new vulnerabilities emerge, not only when application source code changes.
  4. Review cloud storage protection coverage and alert destinations whenever sensitive data accounts are created.

Explanation

Correct Answer

D:

This guardrail addresses defender for storage sensitive data threat detection: Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. The prevention measure is: Review cloud storage protection coverage and alert destinations whenever sensitive data accounts are created. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. “Assess database threat protection plan coverage separately from firewall and SQL audit configuration” would address that alternative cause, not the condition in this question: access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior.

B:

“Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly” responds to this separate finding: a Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. This question instead needs “Review cloud storage protection coverage and alert destinations whenever sensitive data accounts are created”, so the alternative does not meet the stated condition.

C:

Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. “Reassess container images when new vulnerabilities emerge, not only when application source code changes” applies to that separate problem. The observed case is a data lake receives unusual external blob reads and the organization relies only on daily access log exports for incident detection; choosing this alternative would address the wrong failure mode.

Question 958

A regulated Azure tenant has this security condition: A global web service must block traffic from a prohibited geography, but the team configures only a regional backend NSG that lacks end-user geographic context. Which configuration change most directly resolves this problem?

  1. Deploy a supported internal App Service Environment and configure ingress and outbound network controls.
  2. Configure backend HTTPS with appropriate certificate trust and listener/backend settings.
  3. Create the approved Front Door WAF geographic match rule with a documented action and exclusions.
  4. Configure a supported APIM private networking option and restrict public gateway exposure as required.

Explanation

Correct Answer

C:

The cause is: The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. The appropriate change is: Create the approved Front Door WAF geographic match rule with a documented action and exclusions. Verify it with this outcome: Requests from the test blocked geography receive the intended WAF response at the edge.

Incorrect Answers

A:

This action concerns internal app service environment isolation, where The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. The reported incident instead involves The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge.

B:

This action concerns application gateway end to end tls, where Backend HTTP settings do not enforce the required HTTPS connection to backend servers. The corrective response here is “Create the approved Front Door WAF geographic match rule with a documented action and exclusions”; this alternative does not provide that response.

D:

This action concerns api management private network access, where The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. The stem reports a global web service must block traffic from a prohibited geography, but the team configures only a regional backend NSG that lacks end-user geographic context; this control addresses a different failure condition.

Question 959

A platform security assessment reveals this issue: A Windows operations team wants SSH clients to reach private Linux VMs, but the deployment assumes every connection must expose the VM on a public IP. Which underlying control gap is responsible for the issue?

  1. Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow.
  2. Azure resource deployment health does not automatically establish guest operating system patch compliance.
  3. Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections.
  4. JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly.

Explanation

Correct Answer

A:

The described technical condition is: Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. The appropriate corrective action is: Use a supported Bastion native-client connection and required RBAC and network prerequisites. Confirm with: An approved SSH client reaches the private VM through Bastion without a VM public IP.

Incorrect Answers

B:

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: supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow.

C:

“Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules” responds to this separate finding: direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. This question instead needs “Use a supported Bastion native-client connection and required RBAC and network prerequisites”, so the alternative does not meet the stated condition.

D:

JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. “Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration” applies to that separate problem. The observed case is a Windows operations team wants SSH clients to reach private Linux VMs, but the deployment assumes every connection must expose the VM on a public IP; choosing this alternative would address the wrong failure mode.

Question 960

A platform security assessment reveals this issue: An attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events. What technical cause best accounts for the described behavior?

  1. DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.
  2. Control-plane Resource Manager activity can require dedicated detection separate from guest server security events.
  3. A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines.
  4. Code security inventory and posture coverage depend on a supported connector for the actual source-control platform.

Explanation

Correct Answer

B:

The described technical condition is: Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. The appropriate corrective action is: Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators. Confirm with: A controlled suspicious management-plane action produces the expected Defender alert and activity context.

Incorrect Answers

A:

DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. “Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories” would address that alternative cause, not the condition in this question: control-plane Resource Manager activity can require dedicated detection separate from guest server security events.

C:

“Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment” responds to this separate finding: a single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. This question instead needs “Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an attacker uses compromised automation credentials to attempt destructive Azure Resource Manager operations while security monitors only guest operating system events; choosing this alternative would address the wrong failure mode.