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 46

Question 450

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

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

Explanation

Correct Answer

D:

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

Incorrect Answers

A:

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

B:

“Validate secret refresh and authorization when rotating Key Vault credentials consumed by clusters” responds to this separate finding: application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. This question instead needs “Review snapshot export and managed disk permissions as part of sensitive VM data governance”, so the alternative does not meet the stated condition.

C:

Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. “Test backup restore and deletion resistance periodically under approved adversarial scenarios” applies to that separate problem. The observed case is a read-only VM operator can unexpectedly download managed disk snapshots because broad storage and compute role permissions expose sensitive snapshot artifacts; choosing this alternative would address the wrong failure mode.

Question 451

A Microsoft Azure administrator receives this requirement: An Azure Policy remediation task repeatedly fails with authorization errors although its definition and target resources are correct. Which underlying control gap is responsible for the issue?

  1. Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation.
  2. Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types.
  3. A connector's project enrollment or organization-level integration scope may omit newly created GCP projects.
  4. DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope.

Explanation

Correct Answer

D:

The described technical condition is: DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. The appropriate corrective action is: Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope. Confirm with: The remediation operation succeeds and creates or updates only the intended governed configuration.

Incorrect Answers

A:

Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. “Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution” would address that alternative cause, not the condition in this question: deployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope.

B:

“Clear or expand the inventory filter and verify the evaluated scope against resource ownership records” responds to this separate finding: inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. This question instead needs “Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope”, so the alternative does not meet the stated condition.

C:

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 Azure Policy remediation task repeatedly fails with authorization errors although its definition and target resources are correct; choosing this alternative would address the wrong failure mode.

Question 452

While validating an Azure workload, the security team finds: A calendar integration with no directory management duties has been granted broad Directory.ReadWrite.All application permission. Which condition most directly explains the failure?

  1. The user consent configuration permits risky OAuth grants without publisher and permission restrictions.
  2. The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact.
  3. Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra.
  4. Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.

Explanation

Correct Answer

B:

The described technical condition is: The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. The appropriate corrective action is: Revoke the excessive permission and grant only the narrowly required API scopes or app roles. Confirm with: The integration performs its approved workflow while directory write attempts from the principal are denied.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact.

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 “Revoke the excessive permission and grant only the narrowly required API scopes or app roles”, so the alternative does not meet the stated condition.

D:

Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. “Inspect service principal sign-in logs and correlated credential or conditional policy results” applies to that separate problem. The observed case is a calendar integration with no directory management duties has been granted broad Directory.ReadWrite.All application permission; choosing this alternative would address the wrong failure mode.

Question 453

A Microsoft Azure administrator receives this requirement: An organization grants access to a SaaS vendor app based on its global application registration ID but forgets to create and manage the local enterprise application. Which recurring validation best protects against the observed problem?

  1. Review third-party enterprise applications and granted permissions as part of tenant governance.
  2. Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes.
  3. Track enrollment, lost-device recovery and phishing-resistance outcomes before expanding passwordless adoption.
  4. Test vault data-plane access with the actual managed identity rather than relying on ARM role labels.

Explanation

Correct Answer

A:

This guardrail addresses enterprise application service principal: The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. The prevention measure is: Review third-party enterprise applications and granted permissions as part of tenant governance. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. “Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes” would address that alternative cause, not the condition in this question: the multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy.

C:

“Track enrollment, lost-device recovery and phishing-resistance outcomes before expanding passwordless adoption” responds to this separate finding: microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. This question instead needs “Review third-party enterprise applications and granted permissions as part of tenant governance”, so the alternative does not meet the stated condition.

D:

Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. “Test vault data-plane access with the actual managed identity rather than relying on ARM role labels” applies to that separate problem. The observed case is an organization grants access to a SaaS vendor app based on its global application registration ID but forgets to create and manage the local enterprise application; choosing this alternative would address the wrong failure mode.

Question 454

An Azure security engineer investigates the following incident: A storage engineer has Storage Blob Data Reader at a management group while security expects access limited to one storage container, resulting in read access across child subscriptions. Which outcome most clearly verifies that the issue is resolved?

  1. Removing a user from the group removes inherited resource access after propagation, without changing role assignments.
  2. The protected operation succeeds during the approved activation window and fails after activation expires.
  3. The operator reads the approved container but is denied access to an unrelated descendant subscription.
  4. A test write succeeds only after the legitimate deny condition is resolved without adding unnecessary privilege.

Explanation

Correct Answer

C:

This validates the specific control for inherited azure rbac scope: Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. The associated corrective action is: Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope. Testing a different component would not establish this result.

Incorrect Answers

A:

Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. “Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls” would address that alternative cause, not the condition in this question: azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted.

B:

“Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change” responds to this separate finding: a PIM eligible assignment is not an active role grant until the user completes the configured activation process. This question instead needs “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope”, so the alternative does not meet the stated condition.

D:

Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. “Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures” applies to that separate problem. The observed case is a storage engineer has Storage Blob Data Reader at a management group while security expects access limited to one storage container, resulting in read access across child subscriptions; choosing this alternative would address the wrong failure mode.

Question 455

A platform security assessment reveals this issue: A team enables Azure Firewall Premium TLS inspection without distributing the enterprise trust chain, causing browser certificate errors for inspected applications. After remediation, which test result best proves the intended change?

  1. The tunnel establishes with the intended cryptographic suite and routes pass protected traffic.
  2. Spoke queries traverse the DNS proxy and the service's allowed FQDN policy operates consistently.
  3. BGP sessions establish and only approved prefixes appear on both sides of the encrypted connection.
  4. Authorized inspected HTTPS sessions validate the expected certificate chain and security events are visible.

Explanation

Correct Answer

D:

This validates the specific control for firewall premium tls inspection trust: TLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients. The associated corrective action is: Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies. Testing a different component would not establish this result.

Incorrect Answers

A:

The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings. “Align supported IPsec/IKE policy, keys and proposal parameters between the two authorized peers” would address that alternative cause, not the condition in this question: tLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients.

B:

“Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address” responds to this separate finding: spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. This question instead needs “Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies”, so the alternative does not meet the stated condition.

C:

The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. “Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state” applies to that separate problem. The observed case is a team enables Azure Firewall Premium TLS inspection without distributing the enterprise trust chain, causing browser certificate errors for inspected applications; choosing this alternative would address the wrong failure mode.

Question 456

A platform security assessment reveals this issue: An application subnet can access many Azure Storage accounts even though governance permits only designated corporate storage resource IDs. What technical cause best accounts for the described behavior?

  1. Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.
  2. App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections.
  3. The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations.
  4. The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address.

Explanation

Correct Answer

C:

The described technical condition is: The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations. The appropriate corrective action is: Apply an appropriate service endpoint policy restricting the subnet to approved storage resources. Confirm with: Approved corporate storage access succeeds and a test unapproved storage destination is denied.

Incorrect Answers

A:

Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. “Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service” would address that alternative cause, not the condition in this question: the subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations.

B:

“Configure regional App Service VNet integration and the necessary subnet routing and DNS” responds to this separate finding: app Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. This question instead needs “Apply an appropriate service endpoint policy restricting the subnet to approved storage resources”, so the alternative does not meet the stated condition.

D:

The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Configure the correct privatelink DNS zone record and link the client VNet to the zone” applies to that separate problem. The observed case is an application subnet can access many Azure Storage accounts even though governance permits only designated corporate storage resource IDs; choosing this alternative would address the wrong failure mode.

Question 457

A production Azure security implementation shows this failure: An application owner marks a critical Defender for Cloud finding as accepted without a compensating control, and management assumes the security risk has disappeared. What is the most appropriate corrective step?

  1. Verify the live NSG rule and its effect, then review the supported assessment refresh and remediation state.
  2. Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls.
  3. Review and repair the AWS connector's authorized access and enable applicable posture assessment capabilities.
  4. Clear or expand the inventory filter and verify the evaluated scope against resource ownership records.

Explanation

Correct Answer

B:

The cause is: Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. The appropriate change is: Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls. Verify it with this outcome: The owner can demonstrate a mitigated exposure or a formally governed residual risk with appropriate expiration.

Incorrect Answers

A:

This action concerns defender for cloud posture assessment freshness, where Defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change. The reported incident instead involves Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path.

C:

This action concerns multicloud aws connector permissions, where A multicloud connector can exist while its required permissions, services or security plan settings are incomplete. The corrective response here is “Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls”; this alternative does not provide that response.

D:

This action concerns defender for cloud inventory filters multi-region, where Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. The stem reports an application owner marks a critical Defender for Cloud finding as accepted without a compensating control, and management assumes the security risk has disappeared; this control addresses a different failure condition.

Question 458

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 remediation best addresses the specific issue?

  1. Enable the required syslog facility and severity in the Linux data collection rule and verify agent association.
  2. Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters.
  3. Review the incident timeline, related entities, triggering analytics and available supporting logs before final disposition.
  4. Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches.

Explanation

Correct Answer

D:

The cause is: Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. The appropriate change is: Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches. Verify it with this outcome: Known variants match relevant records while unrelated similar names do not produce unjustified cases.

Incorrect Answers

A:

This action concerns azure monitor dcr linux syslog facility, where A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. The reported incident instead involves Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.

B:

This action concerns dcr workspace destination configuration, where A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. The corrective response here is “Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches”; this alternative does not provide that response.

C:

This action concerns sentinel incident investigation timeline, where Incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. The stem reports a Sentinel query compares raw account aliases against a watchlist using exact case-sensitive strings and misses known risky user variants; this control addresses a different failure condition.

Question 459

During a cloud security review, the operations team observes: An API gateway exposes internal APIs using a publicly accessible endpoint even though clients and backends are expected to remain on private networks. What is the most appropriate corrective step?

  1. Bind a valid certificate to the custom hostname using an approved App Service certificate mechanism.
  2. Configure a supported APIM private networking option and restrict public gateway exposure as required.
  3. Correct the custom health probe to match the actual service endpoint and backend settings.
  4. After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener.

Explanation

Correct Answer

B:

The cause is: The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. The appropriate change is: Configure a supported APIM private networking option and restrict public gateway exposure as required. Verify it with this outcome: Authorized internal clients call the API through a permitted private path and public probes fail.

Incorrect Answers

A:

This action concerns custom domain tls certificate binding, where The custom domain has no correct TLS certificate binding for the expected host name. The reported incident instead involves The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary.

C:

This action concerns application gateway backend health probes, where The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. The corrective response here is “Configure a supported APIM private networking option and restrict public gateway exposure as required”; this alternative does not provide that response.

D:

This action concerns application gateway waf detection versus prevention, where The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. The stem reports an API gateway exposes internal APIs using a publicly accessible endpoint even though clients and backends are expected to remain on private networks; this control addresses a different failure condition.

Question 460

A Microsoft Azure administrator receives this requirement: A security program expects passwordless sign-in but permits only password-and-SMS methods in the authentication methods policy. What is the most appropriate corrective step?

  1. Enable the approved passwordless method and complete secure user registration.
  2. Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate.
  3. Provision or consent the enterprise application service principal and configure appropriate access and controls.
  4. Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly.

Explanation

Correct Answer

A:

The cause is: Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. The appropriate change is: Enable the approved passwordless method and complete secure user registration. Verify it with this outcome: A pilot user signs in with the intended passwordless credential under Conditional Access enforcement.

Incorrect Answers

B:

This action concerns identity protection user risk response, where No effective user-risk-based identity protection response has been configured for the relevant identities. The reported incident instead involves Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.

C:

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 corrective response here is “Enable the approved passwordless method and complete secure user registration”; 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 security program expects passwordless sign-in but permits only password-and-SMS methods in the authentication methods policy; this control addresses a different failure condition.