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 89

Question 880

The cloud operations team reviews the following risk: 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. What governance practice would best prevent the same failure?

  1. Validate ASG membership as part of VM deployment and automated network acceptance tests.
  2. Review route table association and next-hop validity during onboarding of new application subnets.
  3. Assess effective rules at subnet and interface levels before approving firewall exceptions.
  4. Test actual outbound reachability instead of relying on the presence of an NSG attachment alone.

Explanation

Correct Answer

A:

This guardrail addresses application security group membership scoping: An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. The prevention measure is: Validate ASG membership as part of VM deployment and automated network acceptance tests. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. “Review route table association and next-hop validity during onboarding of new application subnets” 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:

“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 “Validate ASG membership as part of VM deployment and automated network acceptance tests”, so the alternative does not meet the stated condition.

D:

Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. “Test actual outbound reachability instead of relying on the presence of an NSG attachment alone” 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 881

A platform security assessment reveals this issue: A storage account is limited to selected VNets but a newly created workload subnet reaches only the public service and fails its access restriction. Which recurring validation best protects against the observed problem?

  1. Test both private-resolution success and public-path denial whenever a new Private Endpoint is added.
  2. Verify DNS zone links and forwarders for all VNets consuming a private service.
  3. Inventory subnet service endpoint configuration and service firewall allowances together.
  4. Treat private transport and payload encryption as separate security controls in architecture reviews.

Explanation

Correct Answer

C:

This guardrail addresses vnet service endpoint network scope: The required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. The prevention measure is: Inventory subnet service endpoint configuration and service firewall allowances together. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A private endpoint has not been configured or public network access has not been restricted for the resource. “Test both private-resolution success and public-path denial whenever a new Private Endpoint is added” would address that alternative cause, not the condition in this question: the required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall.

B:

“Verify DNS zone links and forwarders for all VNets consuming a private service” responds to this separate finding: the private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. This question instead needs “Inventory subnet service endpoint configuration and service firewall allowances together”, so the alternative does not meet the stated condition.

D:

ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. “Treat private transport and payload encryption as separate security controls in architecture reviews” applies to that separate problem. The observed case is a storage account is limited to selected VNets but a newly created workload subnet reaches only the public service and fails its access restriction; choosing this alternative would address the wrong failure mode.

Question 882

While validating an Azure workload, the security team finds: A security team enables per-user MFA for administrators but a sensitive Azure app remains accessible in a way that does not consistently apply context-aware authentication requirements. Which condition most directly explains the failure?

  1. Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access.
  2. The group entitlement has no scheduled access review or defined decision maker to remove stale members.
  3. Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments.
  4. No properly protected emergency access account and tested exclusion exists to recover from policy or federation failures.

Explanation

Correct Answer

A:

The described technical condition is: Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. The appropriate corrective action is: Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app. Confirm with: Targeted users meet the required control under the specified access conditions, and excluded accounts follow documented exceptions.

Incorrect Answers

B:

The group entitlement has no scheduled access review or defined decision maker to remove stale members. “Configure Microsoft Entra access reviews for the relevant group with reviewers and automatic remediation as authorized” would address that alternative cause, not the condition in this question: per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access.

C:

“Review permanent assignments and configure PIM alerts, justification and eligible access where feasible” responds to this separate finding: standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. This question instead needs “Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app”, so the alternative does not meet the stated condition.

D:

No properly protected emergency access account and tested exclusion exists to recover from policy or federation failures. “Maintain tightly monitored cloud-only emergency access accounts excluded from the blocking control under approved procedures” applies to that separate problem. The observed case is a security team enables per-user MFA for administrators but a sensitive Azure app remains accessible in a way that does not consistently apply context-aware authentication requirements; choosing this alternative would address the wrong failure mode.

Question 883

A production Azure security implementation shows this failure: An auditor requests a bespoke compliance requirement absent from built-in regulatory mappings, and the governance team attempts to edit a built-in standard directly. What observation is the strongest validation evidence?

  1. Key metadata and approved validation demonstrate hardware-backed protection for the sensitive workload.
  2. The custom control produces explainable pass or fail evidence mapped to the institution's actual documented requirement.
  3. Approved services retrieve permitted secrets through the expected path while unauthorized public requests fail.
  4. A new prohibited public IP deployment is rejected while existing resources appear in policy compliance reporting.

Explanation

Correct Answer

B:

This validates the specific control for azure policy custom regulatory rule mapping: Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. The associated corrective action is: Create and test a supported custom Azure Policy definition or initiative and attach it to the relevant regulatory assessment process. 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: built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment.

C:

“Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path” responds to this separate finding: key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. This question instead needs “Create and test a supported custom Azure Policy definition or initiative and attach it to the relevant regulatory assessment process”, so the alternative does not meet the stated condition.

D:

The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect. “Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type” applies to that separate problem. The observed case is an auditor requests a bespoke compliance requirement absent from built-in regulatory mappings, and the governance team attempts to edit a built-in standard directly; choosing this alternative would address the wrong failure mode.

Question 884

A production Azure security implementation shows this failure: An app team creates an NSG allow for a port that organizational policy denies through Virtual Network Manager security admin rules, but access still fails. After remediation, which test result best proves the intended change?

  1. The forbidden flow remains blocked until a reviewed policy exception is applied centrally.
  2. The published external endpoint reaches only the approved internal listener and is logged.
  3. Traffic between the two spokes uses the intended hub transit path and is subject to inspection.
  4. The new VNet appears in the proper network group and receives the intended security admin rules.

Explanation

Correct Answer

A:

This validates the specific control for azure virtual network manager security admin rules: An enforced security admin deny rule has higher governance precedence than the workload NSG allow. The associated corrective action is: Change the governing security admin policy through approved central administration rather than widening local NSGs. Testing a different component would not establish this result.

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: an enforced security admin deny rule has higher governance precedence than the workload NSG allow.

C:

“Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs” responds to this separate finding: vNet peering does not inherently create transitive routing between other independently peered VNets. This question instead needs “Change the governing security admin policy through approved central administration rather than widening local NSGs”, so the alternative does not meet the stated condition.

D:

The dynamic network group criteria do not include the intended VNet attributes or scope. “Correct the group membership query or approved explicit membership and deploy the security configuration” applies to that separate problem. The observed case is an app team creates an NSG allow for a port that organizational policy denies through Virtual Network Manager security admin rules, but access still fails; choosing this alternative would address the wrong failure mode.

Question 885

A production Azure security implementation shows this failure: A leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation. What is the most appropriate corrective step?

  1. Provision or consent the enterprise application service principal and configure appropriate access and controls.
  2. Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate.
  3. Register the exact approved redirect URI and update the app client flow accordingly.
  4. Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly.

Explanation

Correct Answer

B:

The cause is: No effective user-risk-based identity protection response has been configured for the relevant identities. The appropriate change is: Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate. Verify it with this outcome: High-risk users complete required recovery or are denied access while risk remediation is recorded.

Incorrect Answers

A:

This action concerns enterprise application service principal, where The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. The reported incident instead involves No effective user-risk-based identity protection response has been configured for the relevant identities.

C:

This action concerns app registration redirect uri validation, where The application's registered redirect URI does not match the callback URI used in the authorization request. The corrective response here is “Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate”; this alternative does not provide that response.

D:

This action concerns user assigned managed identity reuse, where Separate system-assigned identities do not provide the stable reusable principal desired across resources. The stem reports a leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation; this control addresses a different failure condition.

Question 886

A platform security assessment reveals this issue: A detection rule flags suspicious logins but incidents contain only free-text messages and cannot link the affected user or source IP. What observation is the strongest validation evidence?

  1. Known variants match relevant records while unrelated similar names do not produce unjustified cases.
  2. A controlled burst of related events creates the documented consolidated incident without merging unrelated users.
  3. The generated incident displays the correct user and IP entities and can correlate related events.
  4. Late-arriving simulated authentication events are detected once without producing excessive duplicate incidents.

Explanation

Correct Answer

C:

This validates the specific control for sentinel entity mapping accuracy: Useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers. The associated corrective action is: Map the rule output's user account and IP fields to the appropriate Sentinel entity types and identifiers. Testing a different component would not establish this result.

Incorrect Answers

A:

Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. “Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches” would address that alternative cause, not the condition in this question: useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers.

B:

“Configure the supported analytic-rule event or alert grouping window and matching fields for the intended incident unit” responds to this separate finding: alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit. This question instead needs “Map the rule output's user account and IP fields to the appropriate Sentinel entity types and identifiers”, so the alternative does not meet the stated condition.

D:

A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. “Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay” applies to that separate problem. The observed case is a detection rule flags suspicious logins but incidents contain only free-text messages and cannot link the affected user or source IP; choosing this alternative would address the wrong failure mode.

Question 887

A regulated Azure tenant has this security condition: A subscription team assigns an Azure Policy definition with Audit effect to prevent public IP deployment, yet the network group continues creating public IP resources. Which remediation best addresses the specific issue?

  1. Enable and verify the applicable vault soft delete protections and restrict backup-deletion privileges.
  2. Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault.
  3. Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control.
  4. Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type.

Explanation

Correct Answer

D:

The cause is: The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect. The appropriate change is: Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type. Verify it with this outcome: A new prohibited public IP deployment is rejected while existing resources appear in policy compliance reporting.

Incorrect Answers

A:

This action concerns azure backup soft delete retention protection, where Soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules. The reported incident instead involves The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect.

B:

This action concerns key vault backup restore regional limitation, where Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. The corrective response here is “Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type”; this alternative does not provide that response.

C:

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 subscription team assigns an Azure Policy definition with Audit effect to prevent public IP deployment, yet the network group continues creating public IP resources; this control addresses a different failure condition.

Question 888

During a cloud security review, the operations team observes: A read-only VM operator can unexpectedly download managed disk snapshots because broad storage and compute role permissions expose sensitive snapshot artifacts. Which underlying control gap is responsible for the issue?

  1. Cluster authorization is not aligned with identity-based RBAC and separation of duties.
  2. Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization.
  3. Authentication to a container registry does not establish that deployed images meet vulnerability security requirements.
  4. Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules.

Explanation

Correct Answer

B:

The described technical condition is: Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. The appropriate corrective action is: Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals. Confirm with: An unauthorized operator cannot generate snapshot access while recovery administrators retain documented access.

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: snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization.

C:

“Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation” responds to this separate finding: authentication to a container registry does not establish that deployed images meet vulnerability security requirements. This question instead needs “Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals”, so the alternative does not meet the stated condition.

D:

Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. “Enable the supported network policy option and enforce namespace/pod label based allowlists” 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.

Question 889

A regulated Azure tenant has this security condition: A production confidential client uses a shared text secret in CI logs despite a security requirement for stronger app authentication. Which condition most directly explains the failure?

  1. Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra.
  2. The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity.
  3. Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.
  4. Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls.

Explanation

Correct Answer

B:

The described technical condition is: The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. The appropriate corrective action is: Configure a certificate credential or supported workload federation and remove the leaked text secret. Confirm with: The application authenticates with its secured credential while the old secret is revoked and unusable.

Incorrect Answers

A:

Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. “Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret” would address that alternative cause, not the condition in this question: the confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity.

C:

“Inspect service principal sign-in logs and correlated credential or conditional policy results” responds to this separate finding: non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. This question instead needs “Configure a certificate credential or supported workload federation and remove the leaked text secret”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a production confidential client uses a shared text secret in CI logs despite a security requirement for stronger app authentication; choosing this alternative would address the wrong failure mode.

Question 890

An Azure security engineer investigates the following incident: A records container must resist deletion for a required retention period, but standard user write permissions allow documents to be overwritten. Which outcome most clearly verifies that the issue is resolved?

  1. Authorized reads continue while deletes or overwrites prohibited by retention are rejected.
  2. The storage account reports infrastructure encryption enabled in addition to regular service-side encryption.
  3. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.
  4. A test overwrite creates a retrievable previous version that administrators can restore.

Explanation

Correct Answer

A:

This validates the specific control for blob immutable storage legal hold: Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. The associated corrective action is: Configure the appropriate time-based immutability policy or legal hold for the protected container. Testing a different component would not establish this result.

Incorrect Answers

B:

The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. “Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage” would address that alternative cause, not the condition in this question: data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone.

C:

“Configure customer-managed key encryption and grant the storage account identity the required key permissions” responds to this separate finding: storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. This question instead needs “Configure the appropriate time-based immutability policy or legal hold for the protected container”, so the alternative does not meet the stated condition.

D:

Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. “Enable supported blob versioning and define backup or lifecycle protection for critical objects” applies to that separate problem. The observed case is a records container must resist deletion for a required retention period, but standard user write permissions allow documents to be overwritten; choosing this alternative would address the wrong failure mode.