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 8

Question 70

A Microsoft Azure administrator receives this requirement: A SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation. What technical cause best accounts for the described behavior?

  1. The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline.
  2. The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge.
  3. Backend HTTP settings do not enforce the required HTTPS connection to backend servers.
  4. SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.

Explanation

Correct Answer

D:

The described technical condition is: SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The appropriate corrective action is: Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls. Confirm with: The managed instance deploys in the intended delegated subnet and responds only to permitted connections.

Incorrect Answers

A:

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: sQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.

B:

“Create the approved Front Door WAF geographic match rule with a documented action and exclusions” responds to this separate finding: the access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. This question instead needs “Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls”, so the alternative does not meet the stated condition.

C:

Backend HTTP settings do not enforce the required HTTPS connection to backend servers. “Configure backend HTTPS with appropriate certificate trust and listener/backend settings” applies to that separate problem. The observed case is a SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation; choosing this alternative would address the wrong failure mode.

Question 71

A platform security assessment reveals this issue: A pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure. Which underlying control gap is responsible for the issue?

  1. Cluster authorization is not aligned with identity-based RBAC and separation of duties.
  2. The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.
  3. Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules.
  4. Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories.

Explanation

Correct Answer

B:

The described technical condition is: The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. The appropriate corrective action is: Configure workload identity on the service account and scoped access to the target Key Vault. Confirm with: The pod obtains a short-lived token and reads only the approved secret without stored client secrets.

Incorrect Answers

A:

Cluster authorization is not aligned with identity-based RBAC and separation of duties. “Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope” 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:

“Enable the supported network policy option and enforce namespace/pod label based allowlists” 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 “Configure workload identity on the service account and scoped access to the target Key Vault”, so the alternative does not meet the stated condition.

D:

Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. “Move credentials into a managed secrets service and use approved persistent data storage where needed” 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 72

A Microsoft Azure administrator receives this requirement: A production Windows VM passes an Azure resource configuration check but its guest OS remains months behind security patches and is vulnerable to known flaws. What technical cause best accounts for the described behavior?

  1. Azure resource deployment health does not automatically establish guest operating system patch compliance.
  2. Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access.
  3. Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow.
  4. Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections.

Explanation

Correct Answer

A:

The described technical condition is: Azure resource deployment health does not automatically establish guest operating system patch compliance. The appropriate corrective action is: Apply approved Azure Update Manager or supported guest patch orchestration and verify patch installation. Confirm with: The targeted VM reports the required security updates installed with service continuity preserved.

Incorrect Answers

B:

Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. “Configure the encryption set and supported Key Vault key permissions, then associate eligible disks” would address that alternative cause, not the condition in this question: azure resource deployment health does not automatically establish guest operating system patch compliance.

C:

“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 “Apply approved Azure Update Manager or supported guest patch orchestration and verify patch installation”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a production Windows VM passes an Azure resource configuration check but its guest OS remains months behind security patches and is vulnerable to known flaws; choosing this alternative would address the wrong failure mode.

Question 73

While validating an Azure workload, the security team finds: 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 result confirms the relevant security control is effective?

  1. Both functions obtain tokens for the approved user-assigned identity without duplicating secrets.
  2. The recreated VM authenticates to its approved resource using the newly granted managed identity.
  3. The managed identity writes only approved blobs after role propagation and cannot access excluded storage.
  4. The authorized browser sign-in returns only to the registered callback, rejecting unlisted redirect targets.

Explanation

Correct Answer

A:

This validates the specific control for user assigned managed identity reuse: Separate system-assigned identities do not provide the stable reusable principal desired across resources. The associated corrective action is: Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly. Testing a different component would not establish this result.

Incorrect Answers

B:

A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. “Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal” 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.

C:

“Grant the appropriate storage blob data role to the VM identity at the least necessary scope” responds to this separate finding: creating a managed identity alone does not grant the target resource's required data-plane role. 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:

The application's registered redirect URI does not match the callback URI used in the authorization request. “Register the exact approved redirect URI and update the app client flow accordingly” 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 74

An Azure security engineer investigates the following incident: Three VNets are peered as A-to-hub and hub-to-B, but application teams expect A and B to communicate automatically without routes or appliances. Which outcome most clearly verifies that the issue is resolved?

  1. Traffic between the two spokes uses the intended hub transit path and is subject to inspection.
  2. The VM reaches its approved Azure service while unrelated Internet destinations remain blocked.
  3. Approved HTTPS hosts are reachable and unrelated hosts in the same IP ranges are rejected.
  4. The destination VNet shows the new intended connectivity or security policy after successful deployment.

Explanation

Correct Answer

A:

This validates the specific control for vnet peering non transitivity: VNet peering does not inherently create transitive routing between other independently peered VNets. The associated corrective action is: Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs. Testing a different component would not establish this result.

Incorrect Answers

B:

A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. “Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls” would address that alternative cause, not the condition in this question: vNet peering does not inherently create transitive routing between other independently peered VNets.

C:

“Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy” responds to this separate finding: a broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. This question instead needs “Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs”, so the alternative does not meet the stated condition.

D:

Saving network manager intent does not itself apply connectivity or security configuration to target regions. “Deploy the approved configuration to the correct regions and verify the deployed state” applies to that separate problem. The observed case is three VNets are peered as A-to-hub and hub-to-B, but application teams expect A and B to communicate automatically without routes or appliances; choosing this alternative would address the wrong failure mode.

Question 75

An Azure security engineer investigates the following incident: Password spray attacks target a legacy authentication protocol that does not support modern MFA controls, but the organization only requires MFA for interactive clients. Which configuration change most directly resolves this problem?

  1. Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification.
  2. Create a policy that blocks legacy client authentication for the necessary users and applications.
  3. Include the intended enterprise application or cloud resource in the Conditional Access assignment.
  4. Update the trusted named location with validated new egress ranges and test the affected policy conditions.

Explanation

Correct Answer

B:

The cause is: The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. The appropriate change is: Create a policy that blocks legacy client authentication for the necessary users and applications. Verify it with this outcome: The targeted legacy authentication attempt is rejected while modern approved sign-in remains operational.

Incorrect Answers

A:

This action concerns fido2 passkey enrollment governance, where Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. The reported incident instead involves The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities.

C:

This action concerns conditional access cloud app targeting, where The target cloud application selection is wrong and policy enforcement does not cover the actual resource. The corrective response here is “Create a policy that blocks legacy client authentication for the necessary users and applications”; this alternative does not provide that response.

D:

This action concerns named location ipv4 range update, where The named location definition is stale and no longer reflects current verified branch egress address ranges. The stem reports password spray attacks target a legacy authentication protocol that does not support modern MFA controls, but the organization only requires MFA for interactive clients; this control addresses a different failure condition.

Question 76

During a cloud security review, the operations team observes: A protected custom API expects clients to request a least-privilege read scope, but the scope is not defined in the API's app registration. Which underlying control gap is responsible for the issue?

  1. The protected application registration has not exposed an OAuth permission scope for the required delegated operation.
  2. Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls.
  3. Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra.
  4. Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions.

Explanation

Correct Answer

A:

The described technical condition is: The protected application registration has not exposed an OAuth permission scope for the required delegated operation. The appropriate corrective action is: Define and publish the intended API scope and update client permissions and authorization enforcement. Confirm with: Authorized clients request the named scope and the API rejects tokens without the required permission.

Incorrect Answers

B:

Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. “Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles” would address that alternative cause, not the condition in this question: the protected application registration has not exposed an OAuth permission scope for the required delegated operation.

C:

“Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret” responds to this separate finding: secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. This question instead needs “Define and publish the intended API scope and update client permissions and authorization enforcement”, so the alternative does not meet the stated condition.

D:

Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. “Select approved application permissions with administrator consent and configure client-credentials access” applies to that separate problem. The observed case is a protected custom API expects clients to request a least-privilege read scope, but the scope is not defined in the API's app registration; choosing this alternative would address the wrong failure mode.

Question 77

While validating an Azure workload, the security team finds: A SOC deploys Azure Monitor Agent to Windows servers but receives no required security event IDs in the security analytics workspace. Which configuration change most directly resolves this problem?

  1. Map the rule output's user account and IP fields to the appropriate Sentinel entity types and identifiers.
  2. Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches.
  3. Configure the Azure Firewall diagnostic categories and approved Log Analytics destination for necessary network-rule logging.
  4. Create or correct the DCR Windows event selection and associate it with the eligible Windows machines.

Explanation

Correct Answer

D:

The cause is: Azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association. The appropriate change is: Create or correct the DCR Windows event selection and associate it with the eligible Windows machines. Verify it with this outcome: The selected security events arrive in the expected Log Analytics table with correct computer and event identifiers.

Incorrect Answers

A:

This action concerns sentinel entity mapping accuracy, where Useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers. The reported incident instead involves Azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association.

B:

This action concerns sentinel watchlist match normalization, where Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The corrective response here is “Create or correct the DCR Windows event selection and associate it with the eligible Windows machines”; this alternative does not provide that response.

C:

This action concerns network security diagnostic logs to log analytics, where Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. The stem reports a SOC deploys Azure Monitor Agent to Windows servers but receives no required security event IDs in the security analytics workspace; this control addresses a different failure condition.

Question 78

While validating an Azure workload, the security team finds: An enterprise requires VM host-level encryption for temporary disks and caches, but only customer-managed guest volume encryption is enabled. Which condition most directly explains the failure?

  1. Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections.
  2. Unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access.
  3. Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement.
  4. JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly.

Explanation

Correct Answer

C:

The described technical condition is: Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. The appropriate corrective action is: Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability. Confirm with: The VM configuration shows host encryption enabled and temporary data is protected as required.

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: guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement.

B:

“Restrict extension publishers and deployment rights and deploy only signed or approved scripts” responds to this separate finding: unrestricted VM extension permissions and unreviewed scripts can execute code with privileged guest access. This question instead needs “Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability”, 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 an enterprise requires VM host-level encryption for temporary disks and caches, but only customer-managed guest volume encryption is enabled; choosing this alternative would address the wrong failure mode.

Question 79

The cloud operations team reviews the following risk: A development subscription has a temporary exception to deny public network access, but the exception remains active long after the approved change window. Which safeguard would best prevent this issue from recurring?

  1. Monitor external TLS endpoints separately from Key Vault certificate inventory and verify renewal propagation.
  2. Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule.
  3. Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners.
  4. Audit Key Vault public exposure and the exact network dependencies of each application after changes.

Explanation

Correct Answer

B:

This guardrail addresses azure policy exemption expiration: An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. The prevention measure is: Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. “Monitor external TLS endpoints separately from Key Vault certificate inventory and verify renewal propagation” would address that alternative cause, not the condition in this question: an exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration.

C:

“Version custom security-control mappings and confirm both scope and measurement evidence with compliance owners” responds to this separate finding: built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. This question instead needs “Review exemption owners, scopes, categories and expiry dates on a recurring governance schedule”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a development subscription has a temporary exception to deny public network access, but the exception remains active long after the approved change window; choosing this alternative would address the wrong failure mode.

Question 80

The cloud operations team reviews the following risk: A single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements. Which result confirms the relevant security control is effective?

  1. Key metadata and approved validation demonstrate hardware-backed protection for the sensitive workload.
  2. A protected backup deletion request fails until a separate authorized security approver grants the required permission.
  3. The expired exemption no longer suppresses enforcement and any remaining public access is reported under the intended policy.
  4. The production subscription enters the relevant compliance assessment and its resources receive the expected enforcement.

Explanation

Correct Answer

B:

This validates the specific control for backup multiuser authorization resource guard: Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. The associated corrective action is: Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers. Testing a different component would not establish this result.

Incorrect Answers

A:

Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. “Provision supported HSM-protected keys in the appropriate vault tier and migrate applications according to key-dependency rules” would address that alternative cause, not the condition in this question: critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary.

C:

“Set time-limited exemptions with accountable justification and remove or renew each only after security review” responds to this separate finding: an exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. This question instead needs “Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers”, so the alternative does not meet the stated condition.

D:

An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. “Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control” applies to that separate problem. The observed case is a single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements; choosing this alternative would address the wrong failure mode.