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 11

Question 100

A platform security assessment reveals this issue: A deployment account has Contributor on a resource group but receives an explicit deny through a managed deployment, and an administrator keeps adding more Allow role assignments. What technical cause best accounts for the described behavior?

  1. NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule.
  2. PIM role settings have not required the intended multifactor or authentication-strength control at activation.
  3. A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.
  4. Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope.

Explanation

Correct Answer

D:

The described technical condition is: Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. The appropriate corrective action is: Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures. Confirm with: A test write succeeds only after the legitimate deny condition is resolved without adding unnecessary privilege.

Incorrect Answers

A:

NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. “Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment” would address that alternative cause, not the condition in this question: azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope.

B:

“Configure the PIM role activation requirements to demand the approved strong authentication method” responds to this separate finding: pIM role settings have not required the intended multifactor or authentication-strength control at activation. This question instead needs “Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures”, so the alternative does not meet the stated condition.

C:

A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” applies to that separate problem. The observed case is a deployment account has Contributor on a resource group but receives an explicit deny through a managed deployment, and an administrator keeps adding more Allow role assignments; choosing this alternative would address the wrong failure mode.

Question 101

A platform security assessment reveals this issue: An application registered in a software supplier tenant needs access to a customer's API, but the customer assumes the supplier's role grants automatically apply locally. Which underlying control gap is responsible for the issue?

  1. Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions.
  2. Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls.
  3. The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity.
  4. The user consent configuration permits risky OAuth grants without publisher and permission restrictions.

Explanation

Correct Answer

B:

The described technical condition is: Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The appropriate corrective action is: Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles. Confirm with: A customer tenant administrator can revoke the app's local access without altering the supplier registration.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls.

C:

“Configure a certificate credential or supported workload federation and remove the leaked text secret” responds to this separate finding: the confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. This question instead needs “Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles”, so the alternative does not meet the stated condition.

D:

The user consent configuration permits risky OAuth grants without publisher and permission restrictions. “Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow” applies to that separate problem. The observed case is an application registered in a software supplier tenant needs access to a customer's API, but the customer assumes the supplier's role grants automatically apply locally; choosing this alternative would address the wrong failure mode.

Question 102

The cloud operations team reviews the following risk: A Windows operations team wants SSH clients to reach private Linux VMs, but the deployment assumes every connection must expose the VM on a public IP. Which configuration change most directly resolves this problem?

  1. Choose supported confidential VM features and configure the correct security type and encryption settings.
  2. Use a supported Bastion native-client connection and required RBAC and network prerequisites.
  3. Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration.
  4. Configure the encryption set and supported Key Vault key permissions, then associate eligible disks.

Explanation

Correct Answer

B:

The cause is: Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. The appropriate change is: Use a supported Bastion native-client connection and required RBAC and network prerequisites. Verify it with this outcome: An approved SSH client reaches the private VM through Bastion without a VM public IP.

Incorrect Answers

A:

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

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 “Use a supported Bastion native-client connection and required RBAC and network prerequisites”; this alternative does not provide that response.

D:

This action concerns disk customer managed key disk encryption set, where Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The stem reports a Windows operations team wants SSH clients to reach private Linux VMs, but the deployment assumes every connection must expose the VM on a public IP; this control addresses a different failure condition.

Question 103

A Microsoft Azure administrator receives this requirement: A network team adds an outbound deny rule and assumes it will immediately terminate every existing TCP session previously allowed through the subnet NSG. Which recurring validation best protects against the observed problem?

  1. Validate both directions of protected flows after any UDR, peering or subnet address change.
  2. Include established-session and fresh-connection checks in NSG incident response validation.
  3. Assess effective rules at subnet and interface levels before approving firewall exceptions.
  4. Review effective NSG rule order with both positive and negative port reachability tests after changes.

Explanation

Correct Answer

B:

This guardrail addresses stateful nsg return traffic behavior: NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. The prevention measure is: Include established-session and fresh-connection checks in NSG incident response validation. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: nSGs are stateful and existing established flows can persist until their flow records expire despite rule changes.

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 “Include established-session and fresh-connection checks in NSG incident response validation”, so the alternative does not meet the stated condition.

D:

Network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny. “Review effective NSG rule order with both positive and negative port reachability tests after changes” applies to that separate problem. The observed case is a network team adds an outbound deny rule and assumes it will immediately terminate every existing TCP session previously allowed through the subnet NSG; choosing this alternative would address the wrong failure mode.

Question 104

An Azure security engineer investigates the following incident: A Sentinel incident includes high-risk authentication events from multiple hosts but the analyst reviews only its headline before dismissing the incident. Which condition most directly explains the failure?

  1. Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation.
  2. A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities.
  3. A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation.
  4. Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.

Explanation

Correct Answer

A:

The described technical condition is: Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The appropriate corrective action is: Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition. Confirm with: The case includes a clear event chronology and evidence-backed conclusion or documented containment steps.

Incorrect Answers

B:

A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. “Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content” would address that alternative cause, not the condition in this question: incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation.

C:

“Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay” responds to this separate finding: a rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. This question instead needs “Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition”, so the alternative does not meet the stated condition.

D:

Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” applies to that separate problem. The observed case is a Sentinel incident includes high-risk authentication events from multiple hosts but the analyst reviews only its headline before dismissing the incident; choosing this alternative would address the wrong failure mode.

Question 105

A platform security assessment reveals this issue: An NSG management rule was fixed minutes ago but Defender for Cloud still shows the prior security recommendation as open. After remediation, which test result best proves the intended change?

  1. The targeted risky configuration is remediated and the secure-score control reflects an appropriate improvement on reevaluation.
  2. The report includes the full resource inventory and separately highlights untagged or misclassified resources.
  3. Effective network tests confirm the fix and the recommendation transitions after the expected assessment cycle.
  4. The new GCP projects are present in Defender inventory and receive applicable posture findings.

Explanation

Correct Answer

C:

This validates the specific control for defender for cloud posture assessment freshness: Defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change. The associated corrective action is: Verify the live NSG rule and its effect, then review the supported assessment refresh and remediation state. Testing a different component would not establish this result.

Incorrect Answers

A:

Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. “Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap” would address that alternative cause, not the condition in this question: defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change.

B:

“Query all in-scope Azure resources first and then classify missing or unexpected tags for correction” responds to this separate finding: tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. This question instead needs “Verify the live NSG rule and its effect, then review the supported assessment refresh and remediation state”, so the alternative does not meet the stated condition.

D:

A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. “Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects” applies to that separate problem. The observed case is an NSG management rule was fixed minutes ago but Defender for Cloud still shows the prior security recommendation as open; choosing this alternative would address the wrong failure mode.

Question 106

A regulated Azure tenant has this security condition: A workload can reach one internal service but not another, and the incident team repeatedly edits a single NSG without checking inherited or parallel network controls. Which result confirms the relevant security control is effective?

  1. New prohibited connections fail and the team documents disposition of any previously established flows.
  2. Spoke-to-spoke traffic reaches its destination through the approved hub appliance and no unintended direct path exists.
  3. The newly assigned web VM receives authorized application traffic while non-member VMs remain excluded.
  4. The diagnostic result identifies the NSG rule responsible and the approved flow passes after targeted remediation.

Explanation

Correct Answer

D:

This validates the specific control for effective network security rules diagnosis: The active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view. The associated corrective action is: Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision. Testing a different component would not establish this result.

Incorrect Answers

A:

NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. “Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes” would address that alternative cause, not the condition in this question: the active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view.

B:

“Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs” responds to this separate finding: the necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. This question instead needs “Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision”, so the alternative does not meet the stated condition.

C:

An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. “Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria” applies to that separate problem. The observed case is a workload can reach one internal service but not another, and the incident team repeatedly edits a single NSG without checking inherited or parallel network controls; choosing this alternative would address the wrong failure mode.

Question 107

An Azure security engineer investigates the following incident: A Front Door application must privately reach an Azure origin, yet its backend storage or app remains publicly accessible to any Internet client. What governance practice would best prevent the same failure?

  1. Review network flow telemetry retention and cost before deploying broad monitoring coverage.
  2. Maintain controlled packet capture procedures that protect sensitive payloads and access to stored traces.
  3. Retain source-to-destination connection test results for complex hybrid connectivity incidents.
  4. Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames.

Explanation

Correct Answer

D:

This guardrail addresses front door private link origin protection: The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. The prevention measure is: Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Network flow logging has not been configured for the relevant virtual network monitoring scope. “Review network flow telemetry retention and cost before deploying broad monitoring coverage” would address that alternative cause, not the condition in this question: the Front Door origin connection is not constrained through a supported private-link origin with public access restriction.

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 “Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames”, so the alternative does not meet the stated condition.

C:

A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. “Retain source-to-destination connection test results for complex hybrid connectivity incidents” applies to that separate problem. The observed case is a Front Door application must privately reach an Azure origin, yet its backend storage or app remains publicly accessible to any Internet client; choosing this alternative would address the wrong failure mode.

Question 108

A regulated Azure tenant has this security condition: Security analysts can query VM logs but cannot investigate anomalous Microsoft Entra sign-ins because identity logs are absent. Which configuration change most directly resolves this problem?

  1. Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition.
  2. Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content.
  3. Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition.
  4. Configure the supported Entra sign-in log integration into Sentinel and verify enabled categories and consent.

Explanation

Correct Answer

D:

The cause is: Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. The appropriate change is: Configure the supported Entra sign-in log integration into Sentinel and verify enabled categories and consent. Verify it with this outcome: A controlled test sign-in yields searchable identity event fields in the approved workspace.

Incorrect Answers

A:

This action concerns sentinel incident investigation timeline, where Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The reported incident instead involves Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions.

B:

This action concerns sentinel workspace onboarding, where A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. The corrective response here is “Configure the supported Entra sign-in log integration into Sentinel and verify enabled categories and consent”; this alternative does not provide that response.

C:

This action concerns sentinel automation rule order and stop processing, where Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. The stem reports security analysts can query VM logs but cannot investigate anomalous Microsoft Entra sign-ins because identity logs are absent; this control addresses a different failure condition.

Question 109

During a cloud security review, the operations team observes: An incident automation rule calls a Logic App but the playbook cannot isolate an identified malicious IP because the workflow identity has no access to its firewall. What observation is the strongest validation evidence?

  1. Expired indicators stop driving automatic actions and fresh verified indicators can be correlated with current events.
  2. An authorized six-month historical query retrieves the necessary security events or documents correctly archived data access.
  3. Known variants match relevant records while unrelated similar names do not produce unjustified cases.
  4. A controlled test incident causes the approved containment change and produces an auditable action record.

Explanation

Correct Answer

D:

This validates the specific control for sentinel playbook managed identity permissions: Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. The associated corrective action is: Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection. Testing a different component would not establish this result.

Incorrect Answers

A:

Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics” would address that alternative cause, not the condition in this question: playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents.

B:

“Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes” responds to this separate finding: security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. This question instead needs “Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is an incident automation rule calls a Logic App but the playbook cannot isolate an identified malicious IP because the workflow identity has no access to its firewall; choosing this alternative would address the wrong failure mode.

Question 110

A Microsoft Azure administrator receives this requirement: A SOC investigates role assignments but sees no Azure subscription management activity in Sentinel despite collecting VM system logs. What is the most appropriate corrective step?

  1. Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes.
  2. Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition.
  3. Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace.
  4. Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content.

Explanation

Correct Answer

C:

The cause is: Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. The appropriate change is: Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace. Verify it with this outcome: An authorized test role assignment creates a searchable subscription activity record in Sentinel.

Incorrect Answers

A:

This action concerns sentinel data retention investigation needs, where Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. The reported incident instead involves Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions.

B:

This action concerns sentinel incident investigation timeline, where Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The corrective response here is “Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace”; this alternative does not provide that response.

D:

This action concerns sentinel workspace onboarding, where A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. The stem reports a SOC investigates role assignments but sees no Azure subscription management activity in Sentinel despite collecting VM system logs; this control addresses a different failure condition.