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 13

Question 120

During a cloud security review, the operations team observes: An Azure Function calls a storage account using a client secret embedded in configuration, and secret rotation regularly breaks the application. After remediation, which test result best proves the intended change?

  1. The application resolves the required secret without receiving broad Key Vault management permission.
  2. The recreated VM authenticates to its approved resource using the newly granted managed identity.
  3. A pilot user signs in with the intended passwordless credential under Conditional Access enforcement.
  4. The function uses token-based access without a stored application client secret and writes only permitted blobs.

Explanation

Correct Answer

D:

This validates the specific control for managed identity replaces embedded secret: The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. The associated corrective action is: Enable an appropriate managed identity and grant narrowly scoped storage data authorization to that identity. Testing a different component would not establish this result.

Incorrect Answers

A:

Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. “Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity” would address that alternative cause, not the condition in this question: the workload is not using its platform-managed identity and therefore depends on long-lived application secrets.

B:

“Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal” responds to this separate finding: a system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. This question instead needs “Enable an appropriate managed identity and grant narrowly scoped storage data authorization to that identity”, so the alternative does not meet the stated condition.

C:

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 an Azure Function calls a storage account using a client secret embedded in configuration, and secret rotation regularly breaks the application; choosing this alternative would address the wrong failure mode.

Question 121

A regulated Azure tenant has this security condition: A branch app subnet sends outbound Internet traffic straight to its default system route despite an architecture requiring inspection by a central Azure Firewall. Which safeguard would best prevent this issue from recurring?

  1. Check gateway propagation behavior and route specificity before applying default-route policy.
  2. Assess effective rules at subnet and interface levels before approving firewall exceptions.
  3. Validate both directions of protected flows after any UDR, peering or subnet address change.
  4. Review route table association and next-hop validity during onboarding of new application subnets.

Explanation

Correct Answer

D:

This guardrail addresses user defined default route to inspection: No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. The prevention measure is: Review route table association and next-hop validity during onboarding of new application subnets. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Gateway route propagation remains enabled for the route table and influences effective routing selections. “Check gateway propagation behavior and route specificity before applying default-route policy” would address that alternative cause, not the condition in this question: no effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance.

B:

“Assess effective rules at subnet and interface levels before approving firewall exceptions” responds to this separate finding: both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. This question instead needs “Review route table association and next-hop validity during onboarding of new application subnets”, so the alternative does not meet the stated condition.

C:

Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. “Validate both directions of protected flows after any UDR, peering or subnet address change” applies to that separate problem. The observed case is a branch app subnet sends outbound Internet traffic straight to its default system route despite an architecture requiring inspection by a central Azure Firewall; choosing this alternative would address the wrong failure mode.

Question 122

While validating an Azure workload, the security team finds: An application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress. Which safeguard would best prevent this issue from recurring?

  1. Differentiate network-volume DDoS defenses from layer-seven WAF filtering during threat modeling.
  2. Maintain controlled packet capture procedures that protect sensitive payloads and access to stored traces.
  3. Audit DDoS resource coverage whenever a public service or subscription is added.
  4. Separate route next-hop verification from access-control rule checks in network troubleshooting.

Explanation

Correct Answer

D:

This guardrail addresses network watcher next hop diagnosis: A user-defined or propagated route controls the next hop independently of NSG allow decisions. The prevention measure is: Separate route next-hop verification from access-control rule checks in network troubleshooting. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. “Differentiate network-volume DDoS defenses from layer-seven WAF filtering during threat modeling” would address that alternative cause, not the condition in this question: a user-defined or propagated route controls the next hop independently of NSG allow decisions.

B:

“Maintain controlled packet capture procedures that protect sensitive payloads and access to stored traces” responds to this separate finding: control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. This question instead needs “Separate route next-hop verification from access-control rule checks in network troubleshooting”, so the alternative does not meet the stated condition.

C:

Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. “Audit DDoS resource coverage whenever a public service or subscription is added” applies to that separate problem. The observed case is an application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress; choosing this alternative would address the wrong failure mode.

Question 123

During a cloud security review, the operations team observes: An enterprise requires VM host-level encryption for temporary disks and caches, but only customer-managed guest volume encryption is enabled. What is the most appropriate corrective step?

  1. Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability.
  2. Choose supported confidential VM features and configure the correct security type and encryption settings.
  3. Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration.
  4. Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies.

Explanation

Correct Answer

A:

The cause is: Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. The appropriate change is: Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability. Verify it with this outcome: The VM configuration shows host encryption enabled and temporary data is protected as required.

Incorrect Answers

B:

This action concerns confidential vm protected boot and encryption, where Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory. The reported incident instead involves Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement.

C:

This action concerns jit request ip restriction, where JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. The corrective response here is “Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability”; this alternative does not provide that response.

D:

This action concerns azure disk encryption key vault dependency, where Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. The stem reports an enterprise requires VM host-level encryption for temporary disks and caches, but only customer-managed guest volume encryption is enabled; this control addresses a different failure condition.

Question 124

A regulated Azure tenant has this security condition: A front-end subnet rule references an Application Security Group intended for web VMs, but a newly deployed VM is missing from the ASG and cannot receive traffic. Which explanation fits the observed symptoms most closely?

  1. An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group.
  2. The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.
  3. The active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view.
  4. No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance.

Explanation

Correct Answer

A:

The described technical condition is: An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. The appropriate corrective action is: Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria. Confirm with: The newly assigned web VM receives authorized application traffic while non-member VMs remain excluded.

Incorrect Answers

B:

The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. “Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs” would address that alternative cause, not the condition in this question: an ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group.

C:

“Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision” responds to this separate finding: the active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view. This question instead needs “Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a front-end subnet rule references an Application Security Group intended for web VMs, but a newly deployed VM is missing from the ASG and cannot receive traffic; choosing this alternative would address the wrong failure mode.

Question 125

An Azure security engineer investigates the following incident: A sensitive browser session persists for many days without a fresh sign-in despite a policy requiring shorter high-risk session exposure. Which result confirms the relevant security control is effective?

  1. The application authenticates with its secured credential while the old secret is revoked and unusable.
  2. A test sign-in with only MFA fails, while one meeting both MFA and device compliance succeeds.
  3. Legitimate branch users match the correct location policy and unrelated public addresses are not trusted.
  4. A controlled session prompts for renewed authentication at the configured interval within product limitations.

Explanation

Correct Answer

D:

This validates the specific control for conditional access sign in frequency: The relevant Conditional Access session control lacks the required sign-in frequency and session behavior. The associated corrective action is: Configure a justified sign-in frequency session control for the appropriate protected application. Testing a different component would not establish this result.

Incorrect Answers

A:

The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. “Configure a certificate credential or supported workload federation and remove the leaked text secret” would address that alternative cause, not the condition in this question: the relevant Conditional Access session control lacks the required sign-in frequency and session behavior.

B:

“Select the required combination of grant controls and confirm the intended AND behavior” responds to this separate finding: the grant control operator allows any selected requirement rather than requiring all specified requirements. This question instead needs “Configure a justified sign-in frequency session control for the appropriate protected application”, so the alternative does not meet the stated condition.

C:

The named location definition is stale and no longer reflects current verified branch egress address ranges. “Update the trusted named location with validated new egress ranges and test the affected policy conditions” applies to that separate problem. The observed case is a sensitive browser session persists for many days without a fresh sign-in despite a policy requiring shorter high-risk session exposure; choosing this alternative would address the wrong failure mode.

Question 126

A production Azure security implementation shows this failure: An AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured. What should the engineer implement first to address the weakness?

  1. Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks.
  2. Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys.
  3. Configure eligible ACR private endpoints and DNS paths for all required registry endpoints.
  4. Enable appropriate APIM subscription requirements and validate product/API associations.

Explanation

Correct Answer

C:

The cause is: Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. The appropriate change is: Configure eligible ACR private endpoints and DNS paths for all required registry endpoints. Verify it with this outcome: The cluster retrieves approved images using private addresses while public registry access stays disabled.

Incorrect Answers

A:

This action concerns acr image retention and digest hygiene, where Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. The reported incident instead involves Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access.

B:

This action concerns storage account key rotation continuity, where The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. The corrective response here is “Configure eligible ACR private endpoints and DNS paths for all required registry endpoints”; this alternative does not provide that response.

D:

This action concerns api management subscription key usage, where The API or product does not require the intended APIM subscription key or equivalent authentication control. The stem reports an AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured; this control addresses a different failure condition.

Question 127

A platform security assessment reveals this issue: A security team allows all Internet outbound destinations because a VM must access Azure Storage, bypassing an existing policy intended to restrict egress. Which underlying control gap is responsible for the issue?

  1. A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges.
  2. Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port.
  3. The dynamic network group criteria do not include the intended VNet attributes or scope.
  4. Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.

Explanation

Correct Answer

A:

The described technical condition is: A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. The appropriate corrective action is: Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls. Confirm with: The VM reaches its approved Azure service while unrelated Internet destinations remain blocked.

Incorrect Answers

B:

Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. “Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service” would address that alternative cause, not the condition in this question: a broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges.

C:

“Correct the group membership query or approved explicit membership and deploy the security configuration” responds to this separate finding: the dynamic network group criteria do not include the intended VNet attributes or scope. This question instead needs “Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls”, so the alternative does not meet the stated condition.

D:

Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. “Renumber or redesign the address space before establishing peering or use an approved translation architecture” applies to that separate problem. The observed case is a security team allows all Internet outbound destinations because a VM must access Azure Storage, bypassing an existing policy intended to restrict egress; choosing this alternative would address the wrong failure mode.

Question 128

A production Azure security implementation shows this failure: An attacker overwrites a blob with incorrect content but its latest object still exists, and administrators have no prior version to restore. What should the engineer implement first to address the weakness?

  1. Enable blob soft delete with an appropriate retention period and verify the restore process.
  2. Enable supported blob versioning and define backup or lifecycle protection for critical objects.
  3. Configure the appropriate time-based immutability policy or legal hold for the protected container.
  4. Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage.

Explanation

Correct Answer

B:

The cause is: Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The appropriate change is: Enable supported blob versioning and define backup or lifecycle protection for critical objects. Verify it with this outcome: A test overwrite creates a retrievable previous version that administrators can restore.

Incorrect Answers

A:

This action concerns blob soft delete recovery window, where The storage account lacks blob soft delete retention to recover recently removed objects. The reported incident instead involves Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning.

C:

This action concerns blob immutable storage legal hold, where Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. The corrective response here is “Enable supported blob versioning and define backup or lifecycle protection for critical objects”; this alternative does not provide that response.

D:

This action concerns storage infrastructure double encryption, where The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. The stem reports an attacker overwrites a blob with incorrect content but its latest object still exists, and administrators have no prior version to restore; this control addresses a different failure condition.

Question 129

The cloud operations team reviews the following risk: A ransomware response plan assumes that ordinary backup retention settings prevent all privileged administrators from modifying recovery point protections. Which remediation best addresses the specific issue?

  1. Grant only the necessary deployment role to the assignment identity and run the authorized remediation task.
  2. Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing.
  3. Validate the configured policy baseline and separately test data-plane role assignments and storage access controls.
  4. Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control.

Explanation

Correct Answer

B:

The cause is: An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. The appropriate change is: Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing. Verify it with this outcome: Authorized operators can restore data while prohibited backup protection reduction operations are rejected.

Incorrect Answers

A:

This action concerns deployifnotexists diagnostic settings remediation, where A DeployIfNotExists assignment evaluates related resources but needs appropriate assignment identity permissions and remediation for existing assets. The reported incident instead involves An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection.

C:

This action concerns azure policy evaluation versus data plane checks, where Azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. The corrective response here is “Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing”; this alternative does not provide that response.

D:

This action concerns azure policy scope and notscopes exclusions, where An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. The stem reports a ransomware response plan assumes that ordinary backup retention settings prevent all privileged administrators from modifying recovery point protections; this control addresses a different failure condition.

Question 130

An Azure security engineer investigates the following incident: A Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants. Which safeguard would best prevent this issue from recurring?

  1. Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated.
  2. Review playbook connection identities and least-privilege rights before enabling automated containment.
  3. Retest analytic watchlist joins after source schema or naming normalization changes.
  4. Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators.

Explanation

Correct Answer

C:

This guardrail addresses sentinel watchlist match normalization: Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The prevention measure is: Retest analytic watchlist joins after source schema or naming normalization changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated” would address that alternative cause, not the condition in this question: watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.

B:

“Review playbook connection identities and least-privilege rights before enabling automated containment” responds to this separate finding: playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. This question instead needs “Retest analytic watchlist joins after source schema or naming normalization changes”, so the alternative does not meet the stated condition.

D:

Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators” applies to that separate problem. The observed case is a Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants; choosing this alternative would address the wrong failure mode.