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 35

Question 340

While validating an Azure workload, the security team finds: An app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption. Which safeguard would best prevent this issue from recurring?

  1. Test secure SQL client driver configurations during application and certificate renewals.
  2. Review Entra SQL administrator assignments and database access periodically.
  3. Audit file-share permissions at both Azure share level and file system ACL layers.
  4. Audit TDE status and key rotation separately from transport TLS compliance.

Explanation

Correct Answer

A:

This guardrail addresses azure sql network tls encryption: Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. The prevention measure is: Test secure SQL client driver configurations during application and certificate renewals. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. “Review Entra SQL administrator assignments and database access periodically” would address that alternative cause, not the condition in this question: encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.

C:

“Audit file-share permissions at both Azure share level and file system ACL layers” responds to this separate finding: shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. This question instead needs “Test secure SQL client driver configurations during application and certificate renewals”, so the alternative does not meet the stated condition.

D:

TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Audit TDE status and key rotation separately from transport TLS compliance” applies to that separate problem. The observed case is an app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption; choosing this alternative would address the wrong failure mode.

Question 341

A platform security assessment reveals this issue: A disaster recovery team exports a Key Vault key backup and assumes it can always be restored to any Azure region regardless of supported requirements. Which recurring validation best protects against the observed problem?

  1. Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan.
  2. Test secret ownership, rotation cadence and notification delivery during periodic credential reviews.
  3. Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards.
  4. Audit exclusions whenever subscriptions move between management groups or baseline assignments change.

Explanation

Correct Answer

A:

This guardrail addresses key vault backup restore regional limitation: Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. The prevention measure is: Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. “Test secret ownership, rotation cadence and notification delivery during periodic credential reviews” would address that alternative cause, not the condition in this question: key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules.

C:

“Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards” responds to this separate finding: critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. This question instead needs “Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan”, so the alternative does not meet the stated condition.

D:

An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. “Audit exclusions whenever subscriptions move between management groups or baseline assignments change” applies to that separate problem. The observed case is a disaster recovery team exports a Key Vault key backup and assumes it can always be restored to any Azure region regardless of supported requirements; choosing this alternative would address the wrong failure mode.

Question 342

During a cloud security review, the operations team observes: 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 should the engineer implement first to address the weakness?

  1. Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change.
  2. Assign Storage Blob Data Reader or another appropriate data role at the least required scope.
  3. Assign the approved read-only role at a suitable management group with the intended child subscription coverage.
  4. Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures.

Explanation

Correct Answer

D:

The cause 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 change is: Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures. Verify it with this outcome: A test write succeeds only after the legitimate deny condition is resolved without adding unnecessary privilege.

Incorrect Answers

A:

This action concerns pim eligible versus active role, where A PIM eligible assignment is not an active role grant until the user completes the configured activation process. The reported incident instead involves Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope.

B:

This action concerns dataactions for azure data plane, where Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. The corrective response here is “Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures”; this alternative does not provide that response.

C:

This action concerns management group security assignment, where Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The stem reports 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; this control addresses a different failure condition.

Question 343

An Azure security engineer investigates the following incident: An audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions. What governance practice would best prevent the same failure?

  1. Investigate deny assignments as well as allow grants when diagnosing apparent RBAC permission anomalies.
  2. Audit effective inherited role assignments whenever management groups or subscription hierarchy changes.
  3. Review role definitions against actual job tasks and prefer a narrowly scoped write role over broad access.
  4. Validate custom-role definitions through effective permission tests before applying them widely.

Explanation

Correct Answer

C:

This guardrail addresses reader role versus resource modification: The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. The prevention measure is: Review role definitions against actual job tasks and prefer a narrowly scoped write role over broad access. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. “Investigate deny assignments as well as allow grants when diagnosing apparent RBAC permission anomalies” would address that alternative cause, not the condition in this question: the Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.

B:

“Audit effective inherited role assignments whenever management groups or subscription hierarchy changes” responds to this separate finding: azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. This question instead needs “Review role definitions against actual job tasks and prefer a narrowly scoped write role over broad access”, so the alternative does not meet the stated condition.

D:

NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. “Validate custom-role definitions through effective permission tests before applying them widely” applies to that separate problem. The observed case is an audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions; choosing this alternative would address the wrong failure mode.

Question 344

While validating an Azure workload, the security team finds: An Arc-enabled Linux server appears in Azure inventory but receives no Defender for Servers workload alerts after a controlled test. Which remediation best addresses the specific issue?

  1. Enable the appropriate Defender for Servers plan and verify supported hybrid machine monitoring prerequisites.
  2. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.
  3. Enable the approved Defender for Storage malware scanning on upload and configure the appropriate event handling.
  4. Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment.

Explanation

Correct Answer

A:

The cause is: Azure Arc inventory presence alone does not guarantee that applicable Defender for Servers protection and monitoring dependencies are enabled. The appropriate change is: Enable the appropriate Defender for Servers plan and verify supported hybrid machine monitoring prerequisites. Verify it with this outcome: The hybrid server reports covered status and expected security telemetry reaches the authorized investigation view.

Incorrect Answers

B:

This action concerns defender vulnerability management remediation validation, where A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The reported incident instead involves Azure Arc inventory presence alone does not guarantee that applicable Defender for Servers protection and monitoring dependencies are enabled.

C:

This action concerns defender for storage malware scanning on upload, where Storage encryption at rest does not inspect uploaded content for malware; appropriate Defender for Storage capabilities must be enabled where supported. The corrective response here is “Enable the appropriate Defender for Servers plan and verify supported hybrid machine monitoring prerequisites”; this alternative does not provide that response.

D:

This action concerns defender for cloud alert investigation evidence, where A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. The stem reports an Arc-enabled Linux server appears in Azure inventory but receives no Defender for Servers workload alerts after a controlled test; this control addresses a different failure condition.

Question 345

A production Azure security implementation shows this failure: A VM successfully obtains a token for Azure Storage through managed identity, but blob writes return 403 even though its system identity exists. What is the most appropriate corrective step?

  1. Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate.
  2. Grant the appropriate storage blob data role to the VM identity at the least necessary scope.
  3. Register the exact approved redirect URI and update the app client flow accordingly.
  4. Enable the approved passwordless method and complete secure user registration.

Explanation

Correct Answer

B:

The cause is: Creating a managed identity alone does not grant the target resource's required data-plane role. The appropriate change is: Grant the appropriate storage blob data role to the VM identity at the least necessary scope. Verify it with this outcome: The managed identity writes only approved blobs after role propagation and cannot access excluded storage.

Incorrect Answers

A:

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 Creating a managed identity alone does not grant the target resource's required data-plane role.

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 “Grant the appropriate storage blob data role to the VM identity at the least necessary scope”; this alternative does not provide that response.

D:

This action concerns passwordless authentication method policy, where Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. The stem reports a VM successfully obtains a token for Azure Storage through managed identity, but blob writes return 403 even though its system identity exists; this control addresses a different failure condition.

Question 346

A production Azure security implementation shows this failure: A partner-facing API requires client certificates but accepts arbitrary TLS connections without checking the presented identity. After remediation, which test result best proves the intended change?

  1. An eligible client mounts the share securely while outdated unencrypted access fails.
  2. An abusive test caller is throttled while independent legitimate clients retain service availability.
  3. Applications remain available through rotation and old leaked keys cease to authorize access.
  4. Approved client certificates are accepted and unknown or expired certificates are rejected.

Explanation

Correct Answer

D:

This validates the specific control for apim mutual tls client certificate control: The API gateway has not enforced the required mutual TLS certificate validation for partner clients. The associated corrective action is: Configure supported APIM client certificate validation and trusted certificate criteria. Testing a different component would not establish this result.

Incorrect Answers

A:

The file access path needs compatible secure SMB protocol and supported encrypted transport settings. “Use supported modern SMB client configuration and private connectivity or TLS where applicable” would address that alternative cause, not the condition in this question: the API gateway has not enforced the required mutual TLS certificate validation for partner clients.

B:

“Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions” responds to this separate finding: the API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. This question instead needs “Configure supported APIM client certificate validation and trusted certificate criteria”, so the alternative does not meet the stated condition.

C:

The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. “Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys” applies to that separate problem. The observed case is a partner-facing API requires client certificates but accepts arbitrary TLS connections without checking the presented identity; choosing this alternative would address the wrong failure mode.

Question 347

An Azure security engineer investigates the following incident: An organization wants just-in-time privileged access but several permanent Global Administrator assignments are created without review or notification. What governance practice would best prevent the same failure?

  1. Review privileged role assignments and alert response records monthly with designated accountable owners.
  2. Schedule periodic owner-driven reviews for groups granting sensitive Azure resource permissions.
  3. Set activation duration according to risk and monitor unusually long privilege activations.
  4. Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications.

Explanation

Correct Answer

A:

This guardrail addresses pim permanent global administrator alert: Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. The prevention measure is: Review privileged role assignments and alert response records monthly with designated accountable owners. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The group entitlement has no scheduled access review or defined decision maker to remove stale members. “Schedule periodic owner-driven reviews for groups granting sensitive Azure resource permissions” would address that alternative cause, not the condition in this question: standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments.

C:

“Set activation duration according to risk and monitor unusually long privilege activations” responds to this separate finding: the PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. This question instead needs “Review privileged role assignments and alert response records monthly with designated accountable owners”, so the alternative does not meet the stated condition.

D:

Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. “Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications” applies to that separate problem. The observed case is an organization wants just-in-time privileged access but several permanent Global Administrator assignments are created without review or notification; choosing this alternative would address the wrong failure mode.

Question 348

An Azure security engineer investigates the following incident: An application needs to send DNS queries to a custom resolver over UDP, but Azure Firewall has only an HTTPS application rule for the resolver host. Which condition most directly explains the failure?

  1. Saving network manager intent does not itself apply connectivity or security configuration to target regions.
  2. Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.
  3. Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.
  4. An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.

Explanation

Correct Answer

D:

The described technical condition is: An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. The appropriate corrective action is: Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow. Confirm with: Only the authorized DNS queries succeed and firewall logs show the intended rule match.

Incorrect Answers

A:

Saving network manager intent does not itself apply connectivity or security configuration to target regions. “Deploy the approved configuration to the correct regions and verify the deployed state” would address that alternative cause, not the condition in this question: an HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.

B:

“Renumber or redesign the address space before establishing peering or use an approved translation architecture” responds to this separate finding: azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. This question instead needs “Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow”, so the alternative does not meet the stated condition.

C:

Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints” applies to that separate problem. The observed case is an application needs to send DNS queries to a custom resolver over UDP, but Azure Firewall has only an HTTPS application rule for the resolver host; choosing this alternative would address the wrong failure mode.

Question 349

The cloud operations team reviews the following risk: 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. Which safeguard would best prevent this issue from recurring?

  1. Review exposed DNAT entries against asset owners and remove obsolete Internet listeners.
  2. Review FQDN-based application rules for wildcard overreach and domain ownership changes.
  3. Track central security admin policy impacts before granting application network exceptions.
  4. Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy.

Explanation

Correct Answer

C:

This guardrail addresses azure virtual network manager security admin rules: An enforced security admin deny rule has higher governance precedence than the workload NSG allow. The prevention measure is: Track central security admin policy impacts before granting application network exceptions. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. “Review exposed DNAT entries against asset owners and remove obsolete Internet listeners” 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.

B:

“Review FQDN-based application rules for wildcard overreach and domain ownership changes” responds to this separate finding: a broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. This question instead needs “Track central security admin policy impacts before granting application network exceptions”, so the alternative does not meet the stated condition.

D:

An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. “Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy” 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 350

An Azure security engineer investigates the following incident: An Application Gateway intermittently returns 502 even though backend VMs are up because the health probe checks an incorrect hostname and path. Which safeguard would best prevent this issue from recurring?

  1. Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services.
  2. Validate probe host/path behavior whenever application URLs or certificates change.
  3. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  4. Review the APIM tier's supported private networking features before selecting gateway architecture.

Explanation

Correct Answer

B:

This guardrail addresses application gateway backend health probes: The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. The prevention measure is: Validate probe host/path behavior whenever application URLs or certificates change. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The function hosting plan and network integration/DNS are not configured for the required private destination. “Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services” would address that alternative cause, not the condition in this question: the backend health probe is failing due to its configured request host, path or expected response rather than VM availability.

C:

“Test TLS protocol settings and certificate expiry after changes to public application endpoints” responds to this separate finding: the app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. This question instead needs “Validate probe host/path behavior whenever application URLs or certificates change”, so the alternative does not meet the stated condition.

D:

The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. “Review the APIM tier's supported private networking features before selecting gateway architecture” applies to that separate problem. The observed case is an Application Gateway intermittently returns 502 even though backend VMs are up because the health probe checks an incorrect hostname and path; choosing this alternative would address the wrong failure mode.