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 45

Question 440

A production Azure security implementation shows this failure: A security engineer deploys a new Azure VM with no endpoint agent and assumes the VM cannot be assessed for known software vulnerabilities. Which recurring validation best protects against the observed problem?

  1. Include App Service protection in onboarding checks for Internet-exposed web applications.
  2. Continuously combine vulnerability severity with external reachability and asset importance in remediation planning.
  3. Keep management-plane threat detection enabled for governed subscriptions independent of server-agent deployment.
  4. Review supported scan coverage and inventory accuracy when adding agentless-protected compute resources.

Explanation

Correct Answer

D:

This guardrail addresses defender for servers agentless vulnerability scanning: Supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent. The prevention measure is: Review supported scan coverage and inventory accuracy when adding agentless-protected compute resources. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. “Include App Service protection in onboarding checks for Internet-exposed web applications” would address that alternative cause, not the condition in this question: supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent.

B:

“Continuously combine vulnerability severity with external reachability and asset importance in remediation planning” responds to this separate finding: patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. This question instead needs “Review supported scan coverage and inventory accuracy when adding agentless-protected compute resources”, so the alternative does not meet the stated condition.

C:

Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. “Keep management-plane threat detection enabled for governed subscriptions independent of server-agent deployment” applies to that separate problem. The observed case is a security engineer deploys a new Azure VM with no endpoint agent and assumes the VM cannot be assessed for known software vulnerabilities; choosing this alternative would address the wrong failure mode.

Question 441

While validating an Azure workload, the security team finds: A web service requires encryption to backend instances, but an Application Gateway listener terminates HTTPS and forwards plaintext HTTP downstream. What governance practice would best prevent the same failure?

  1. Test regional edge WAF policies with representative client source conditions and observe false positives.
  2. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  3. Review WAF mode, tuning and false-positive impact before promoting a policy to production.
  4. Include listener-to-backend encryption checks in application gateway security reviews.

Explanation

Correct Answer

D:

This guardrail addresses application gateway end to end tls: Backend HTTP settings do not enforce the required HTTPS connection to backend servers. The prevention measure is: Include listener-to-backend encryption checks in application gateway security reviews. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. “Test regional edge WAF policies with representative client source conditions and observe false positives” would address that alternative cause, not the condition in this question: backend HTTP settings do not enforce the required HTTPS connection to backend servers.

B:

“Test TLS protocol settings and certificate expiry after changes to public application endpoints” responds to this separate finding: the app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. This question instead needs “Include listener-to-backend encryption checks in application gateway security reviews”, so the alternative does not meet the stated condition.

C:

The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. “Review WAF mode, tuning and false-positive impact before promoting a policy to production” applies to that separate problem. The observed case is a web service requires encryption to backend instances, but an Application Gateway listener terminates HTTPS and forwards plaintext HTTP downstream; choosing this alternative would address the wrong failure mode.

Question 442

During a cloud security review, the operations team observes: A web application redirects OAuth sign-in callbacks to an address different from its registered URI and receives a redirect mismatch error. Which recurring validation best protects against the observed problem?

  1. Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents.
  2. Inventory service principal credential expiry and automate safe replacement before deadlines.
  3. Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes.
  4. Control redirect URI changes through code review and restrict registrations to trusted application owners.

Explanation

Correct Answer

D:

This guardrail addresses app registration redirect uri validation: The application's registered redirect URI does not match the callback URI used in the authorization request. The prevention measure is: Control redirect URI changes through code review and restrict registrations to trusted application owners. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

No effective user-risk-based identity protection response has been configured for the relevant identities. “Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents” would address that alternative cause, not the condition in this question: the application's registered redirect URI does not match the callback URI used in the authorization request.

B:

“Inventory service principal credential expiry and automate safe replacement before deadlines” responds to this separate finding: the app registration client credential has expired and the workload has no safe rotation mechanism. This question instead needs “Control redirect URI changes through code review and restrict registrations to trusted application owners”, so the alternative does not meet the stated condition.

C:

The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. “Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes” applies to that separate problem. The observed case is a web application redirects OAuth sign-in callbacks to an address different from its registered URI and receives a redirect mismatch error; choosing this alternative would address the wrong failure mode.

Question 443

A Microsoft Azure administrator receives this requirement: A highly sensitive VM workload requires protecting guest memory and boot state, but the design uses only ordinary managed disk encryption. Which underlying control gap is responsible for the issue?

  1. Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections.
  2. Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow.
  3. The VM's NSG exposes a persistent management port rather than enforcing just-in-time access.
  4. Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory.

Explanation

Correct Answer

D:

The described technical condition is: Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory. The appropriate corrective action is: Choose supported confidential VM features and configure the correct security type and encryption settings. Confirm with: A test VM reports the intended confidential security posture and protected boot chain.

Incorrect Answers

A:

Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. “Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules” would address that alternative cause, not the condition in this question: disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory.

B:

“Use a supported Bastion native-client connection and required RBAC and network prerequisites” responds to this separate finding: supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. This question instead needs “Choose supported confidential VM features and configure the correct security type and encryption settings”, so the alternative does not meet the stated condition.

C:

The VM's NSG exposes a persistent management port rather than enforcing just-in-time access. “Configure supported just-in-time VM access and remove persistent open management rules” applies to that separate problem. The observed case is a highly sensitive VM workload requires protecting guest memory and boot state, but the design uses only ordinary managed disk encryption; choosing this alternative would address the wrong failure mode.

Question 444

An Azure security engineer investigates the following incident: A tenant blocks every sign-in from outside headquarters but never distinguishes genuine low-risk travel from high-risk credential misuse. Which safeguard would best prevent this issue from recurring?

  1. Review risk detections and false-positive effects before broadening sensitive access restrictions.
  2. Recertify high-impact OAuth application permissions and remove obsolete grants.
  3. Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications.
  4. Review eligible and active group membership together with inherited resource role effects.

Explanation

Correct Answer

A:

This guardrail addresses risk based conditional access policy: Network location alone does not substitute for appropriate risk signals and risk-based access controls. The prevention measure is: Review risk detections and false-positive effects before broadening sensitive access restrictions. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. “Recertify high-impact OAuth application permissions and remove obsolete grants” would address that alternative cause, not the condition in this question: network location alone does not substitute for appropriate risk signals and risk-based access controls.

C:

“Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications” responds to this separate finding: per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. This question instead needs “Review risk detections and false-positive effects before broadening sensitive access restrictions”, so the alternative does not meet the stated condition.

D:

Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. “Review eligible and active group membership together with inherited resource role effects” applies to that separate problem. The observed case is a tenant blocks every sign-in from outside headquarters but never distinguishes genuine low-risk travel from high-risk credential misuse; choosing this alternative would address the wrong failure mode.

Question 445

While validating an Azure workload, the security team finds: A team protects a resource through group-based RBAC but all members keep standing membership in the privileged group despite an on-demand access requirement. Which configuration change most directly resolves this problem?

  1. Review report-only results, correct exclusions and switch the approved policy to On for enforcement.
  2. Configure PIM for Groups with eligible membership and required activation controls where supported.
  3. Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context.
  4. Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed.

Explanation

Correct Answer

B:

The cause is: Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. The appropriate change is: Configure PIM for Groups with eligible membership and required activation controls where supported. Verify it with this outcome: An engineer gains temporary group-derived resource access only during an approved activation.

Incorrect Answers

A:

This action concerns conditional access report only mode, where A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. The reported incident instead involves Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles.

C:

This action concerns role assignment audit history, where Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. The corrective response here is “Configure PIM for Groups with eligible membership and required activation controls where supported”; this alternative does not provide that response.

D:

This action concerns risk based conditional access policy, where Network location alone does not substitute for appropriate risk signals and risk-based access controls. The stem reports a team protects a resource through group-based RBAC but all members keep standing membership in the privileged group despite an on-demand access requirement; this control addresses a different failure condition.

Question 446

During a cloud security review, the operations team observes: An organization creates a strict Conditional Access block for risky Azure portal sessions but users continue signing in because administrators never enable the policy. After remediation, which test result best proves the intended change?

  1. A controlled risky sign-in is blocked in enforced mode and appears with the applied policy result.
  2. A pending activation cannot be used before an authorized approver reviews and approves it.
  3. Targeted users meet the required control under the specified access conditions, and excluded accounts follow documented exceptions.
  4. Security receives and investigates alerts for new permanent privileged assignments, reducing unnecessary standing admins.

Explanation

Correct Answer

A:

This validates the specific control for conditional access report only mode: A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. The associated corrective action is: Review report-only results, correct exclusions and switch the approved policy to On for enforcement. Testing a different component would not establish this result.

Incorrect Answers

B:

The PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. “Configure approval and valid approvers for activation of the sensitive Azure resource role” would address that alternative cause, not the condition in this question: a Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block.

C:

“Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app” responds to this separate finding: per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. This question instead needs “Review report-only results, correct exclusions and switch the approved policy to On for enforcement”, so the alternative does not meet the stated condition.

D:

Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. “Review permanent assignments and configure PIM alerts, justification and eligible access where feasible” applies to that separate problem. The observed case is an organization creates a strict Conditional Access block for risky Azure portal sessions but users continue signing in because administrators never enable the policy; choosing this alternative would address the wrong failure mode.

Question 447

A regulated Azure tenant has this security condition: Two Azure Functions need a consistent workload principal across independent deployments, but each uses a transient system-assigned identity that breaks shared policy references. Which condition most directly explains the failure?

  1. No effective user-risk-based identity protection response has been configured for the relevant identities.
  2. The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy.
  3. Separate system-assigned identities do not provide the stable reusable principal desired across resources.
  4. Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.

Explanation

Correct Answer

C:

The described technical condition is: Separate system-assigned identities do not provide the stable reusable principal desired across resources. The appropriate corrective action is: Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly. Confirm with: Both functions obtain tokens for the approved user-assigned identity without duplicating secrets.

Incorrect Answers

A:

No effective user-risk-based identity protection response has been configured for the relevant identities. “Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate” would address that alternative cause, not the condition in this question: separate system-assigned identities do not provide the stable reusable principal desired across resources.

B:

“Provision or consent the enterprise application service principal and configure appropriate access and controls” responds to this separate finding: the multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. This question instead needs “Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly”, so the alternative does not meet the stated condition.

D:

Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. “Enable the approved passwordless method and complete secure user registration” applies to that separate problem. The observed case is two Azure Functions need a consistent workload principal across independent deployments, but each uses a transient system-assigned identity that breaks shared policy references; choosing this alternative would address the wrong failure mode.

Question 448

The cloud operations team reviews the following risk: A production application breaks after a storage account key rotation because all clients use one static key with no staged rollover design. Which explanation fits the observed symptoms most closely?

  1. The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes.
  2. Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access.
  3. Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment.
  4. The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.

Explanation

Correct Answer

A:

The described technical condition is: The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. The appropriate corrective action is: Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys. Confirm with: Applications remain available through rotation and old leaked keys cease to authorize access.

Incorrect Answers

B:

Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. “Configure eligible ACR private endpoints and DNS paths for all required registry endpoints” would address that alternative cause, not the condition in this question: the client authentication design has no key rotation or identity-based alternative and assumes an account key never changes.

C:

“Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks” responds to this separate finding: unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. This question instead needs “Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a production application breaks after a storage account key rotation because all clients use one static key with no staged rollover design; choosing this alternative would address the wrong failure mode.

Question 449

While validating an Azure workload, the security team finds: A private endpoint connection is approved, but VMs keep resolving a storage hostname to the service's public IP from an unlinked VNet. Which configuration change most directly resolves this problem?

  1. Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage.
  2. Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval.
  3. Configure the correct privatelink DNS zone record and link the client VNet to the zone.
  4. Implement supported IPsec over ExpressRoute or application-layer TLS encryption according to the threat model.

Explanation

Correct Answer

C:

The cause is: The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. The appropriate change is: Configure the correct privatelink DNS zone record and link the client VNet to the zone. Verify it with this outcome: The storage service hostname resolves to the intended private endpoint IP from authorized clients.

Incorrect Answers

A:

This action concerns vnet service endpoint network scope, where The required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. The reported incident instead involves The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address.

B:

This action concerns private link service provider design, where The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. The corrective response here is “Configure the correct privatelink DNS zone record and link the client VNet to the zone”; this alternative does not provide that response.

D:

This action concerns expressroute encryption requirement, where ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. The stem reports a private endpoint connection is approved, but VMs keep resolving a storage hostname to the service's public IP from an unlinked VNet; this control addresses a different failure condition.

Question 450

A Microsoft Azure administrator receives this requirement: A read-only VM operator can unexpectedly download managed disk snapshots because broad storage and compute role permissions expose sensitive snapshot artifacts. Which operating control most directly reduces this recurring risk?

  1. Audit service accounts and federated identity subjects when deploying workload identities.
  2. Validate secret refresh and authorization when rotating Key Vault credentials consumed by clusters.
  3. Test backup restore and deletion resistance periodically under approved adversarial scenarios.
  4. Review snapshot export and managed disk permissions as part of sensitive VM data governance.

Explanation

Correct Answer

D:

This guardrail addresses managed disk snapshot permission scope: Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. The prevention measure is: Review snapshot export and managed disk permissions as part of sensitive VM data governance. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. “Audit service accounts and federated identity subjects when deploying workload identities” would address that alternative cause, not the condition in this question: snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization.

B:

“Validate secret refresh and authorization when rotating Key Vault credentials consumed by clusters” responds to this separate finding: application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. This question instead needs “Review snapshot export and managed disk permissions as part of sensitive VM data governance”, 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. “Test backup restore and deletion resistance periodically under approved adversarial scenarios” applies to that separate problem. The observed case is a read-only VM operator can unexpectedly download managed disk snapshots because broad storage and compute role permissions expose sensitive snapshot artifacts; choosing this alternative would address the wrong failure mode.