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 34

Question 330

A Microsoft Azure administrator receives this requirement: A public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application. What is the most appropriate corrective step?

  1. After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener.
  2. Deploy a supported internal App Service Environment and configure ingress and outbound network controls.
  3. Configure a supported APIM private networking option and restrict public gateway exposure as required.
  4. Correct the custom health probe to match the actual service endpoint and backend settings.

Explanation

Correct Answer

A:

The cause is: The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. The appropriate change is: After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener. Verify it with this outcome: Controlled malicious request patterns are blocked while normal requests pass and logs record rule decisions.

Incorrect Answers

B:

This action concerns internal app service environment isolation, where The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. The reported incident instead involves The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode.

C:

This action concerns api management private network access, where The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. The corrective response here is “After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener”; this alternative does not provide that response.

D:

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 stem reports a public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application; this control addresses a different failure condition.

Question 331

An Azure security engineer investigates the following incident: An Azure App Service managed identity has Contributor on its resource group but fails to read a secret from an RBAC-enabled Key Vault. What governance practice would best prevent the same failure?

  1. Test vault data-plane access with the actual managed identity rather than relying on ARM role labels.
  2. Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents.
  3. Include identity recreation and RBAC reauthorization checks in infrastructure rebuild runbooks.
  4. Track enrollment, lost-device recovery and phishing-resistance outcomes before expanding passwordless adoption.

Explanation

Correct Answer

A:

This guardrail addresses key vault data role for workload identity: Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. The prevention measure is: Test vault data-plane access with the actual managed identity rather than relying on ARM role labels. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

No effective user-risk-based identity protection response has been configured for the relevant identities. “Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents” would address that alternative cause, not the condition in this question: resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model.

C:

“Include identity recreation and RBAC reauthorization checks in infrastructure rebuild runbooks” responds to this separate finding: a system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. This question instead needs “Test vault data-plane access with the actual managed identity rather than relying on ARM role labels”, so the alternative does not meet the stated condition.

D:

Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. “Track enrollment, lost-device recovery and phishing-resistance outcomes before expanding passwordless adoption” applies to that separate problem. The observed case is an Azure App Service managed identity has Contributor on its resource group but fails to read a secret from an RBAC-enabled Key Vault; choosing this alternative would address the wrong failure mode.

Question 332

A regulated Azure tenant has this security condition: A regulated Azure SQL database must encrypt database files and backups at rest, but administrators focus only on the client TLS connection. What governance practice would best prevent the same failure?

  1. Review Entra SQL administrator assignments and database access periodically.
  2. Audit TDE status and key rotation separately from transport TLS compliance.
  3. Test audit data delivery and access controls after SQL platform and diagnostic changes.
  4. Audit file-share permissions at both Azure share level and file system ACL layers.

Explanation

Correct Answer

B:

This guardrail addresses transparent data encryption at rest: TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. The prevention measure is: Audit TDE status and key rotation separately from transport TLS compliance. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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: tLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.

C:

“Test audit data delivery and access controls after SQL platform and diagnostic changes” responds to this separate finding: azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. This question instead needs “Audit TDE status and key rotation separately from transport TLS compliance”, so the alternative does not meet the stated condition.

D:

Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. “Audit file-share permissions at both Azure share level and file system ACL layers” applies to that separate problem. The observed case is a regulated Azure SQL database must encrypt database files and backups at rest, but administrators focus only on the client TLS connection; choosing this alternative would address the wrong failure mode.

Question 333

While validating an Azure workload, the security team finds: An App Service allows deprecated TLS versions for an API that handles sensitive data although newer clients support TLS 1.2 or later. Which configuration change most directly resolves this problem?

  1. Configure backend HTTPS with appropriate certificate trust and listener/backend settings.
  2. Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls.
  3. Set the supported minimum TLS version to an approved modern value and verify certificate configuration.
  4. After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener.

Explanation

Correct Answer

C:

The cause is: The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. The appropriate change is: Set the supported minimum TLS version to an approved modern value and verify certificate configuration. Verify it with this outcome: Deprecated TLS clients fail negotiation while approved modern clients connect securely.

Incorrect Answers

A:

This action concerns application gateway end to end tls, where Backend HTTP settings do not enforce the required HTTPS connection to backend servers. The reported incident instead involves The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline.

B:

This action concerns azure sql managed instance subnet requirements, where SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The corrective response here is “Set the supported minimum TLS version to an approved modern value and verify certificate configuration”; 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 App Service allows deprecated TLS versions for an API that handles sensitive data although newer clients support TLS 1.2 or later; this control addresses a different failure condition.

Question 334

During a cloud security review, the operations team observes: An Azure Function accesses a private SQL backend but its outbound requests fail after the SQL resource is moved behind Private Link. What should the engineer implement first to address the weakness?

  1. Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls.
  2. Configure a supported Functions hosting plan with VNet integration and correct private DNS resolution.
  3. Deploy a supported internal App Service Environment and configure ingress and outbound network controls.
  4. Correct the custom health probe to match the actual service endpoint and backend settings.

Explanation

Correct Answer

B:

The cause is: The function hosting plan and network integration/DNS are not configured for the required private destination. The appropriate change is: Configure a supported Functions hosting plan with VNet integration and correct private DNS resolution. Verify it with this outcome: The function reaches the private SQL endpoint with no public database network dependency.

Incorrect Answers

A:

This action concerns azure sql managed instance subnet requirements, where SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The reported incident instead involves The function hosting plan and network integration/DNS are not configured for the required private destination.

C:

This action concerns internal app service environment isolation, where The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. The corrective response here is “Configure a supported Functions hosting plan with VNet integration and correct private DNS resolution”; this alternative does not provide that response.

D:

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 stem reports an Azure Function accesses a private SQL backend but its outbound requests fail after the SQL resource is moved behind Private Link; this control addresses a different failure condition.

Question 335

A production Azure security implementation shows this failure: Employees register phishing-resistant security keys without a documented lost-key replacement process, creating risky manual bypasses when devices are lost. What technical cause best accounts for the described behavior?

  1. The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength.
  2. The named location definition is stale and no longer reflects current verified branch egress address ranges.
  3. Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle.
  4. The targeted policy does not include the guest or external user population for the protected application.

Explanation

Correct Answer

C:

The described technical condition is: Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. The appropriate corrective action is: Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification. Confirm with: A lost key can be revoked and replaced without allowing unverified MFA bypass.

Incorrect Answers

A:

The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. “Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods” would address that alternative cause, not the condition in this question: strong authentication adoption lacks an approved registration, recovery and revocation lifecycle.

B:

“Update the trusted named location with validated new egress ranges and test the affected policy conditions” responds to this separate finding: the named location definition is stale and no longer reflects current verified branch egress address ranges. This question instead needs “Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification”, so the alternative does not meet the stated condition.

D:

The targeted policy does not include the guest or external user population for the protected application. “Extend the policy to the correct external-user categories and trust settings using supported B2B controls” applies to that separate problem. The observed case is employees register phishing-resistant security keys without a documented lost-key replacement process, creating risky manual bypasses when devices are lost; choosing this alternative would address the wrong failure mode.

Question 336

An Azure security engineer investigates the following incident: A security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions. Which remediation best addresses the specific issue?

  1. Assign Storage Blob Data Reader or another appropriate data role at the least required scope.
  2. Configure the PIM role activation requirements to demand the approved strong authentication method.
  3. Assign the approved read-only role at a suitable management group with the intended child subscription coverage.
  4. Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change.

Explanation

Correct Answer

C:

The cause is: Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The appropriate change is: Assign the approved read-only role at a suitable management group with the intended child subscription coverage. Verify it with this outcome: The operator views security inventory in both existing and newly attached eligible subscriptions.

Incorrect Answers

A:

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 reported incident instead involves Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.

B:

This action concerns pim activation mfa prerequisite, where PIM role settings have not required the intended multifactor or authentication-strength control at activation. The corrective response here is “Assign the approved read-only role at a suitable management group with the intended child subscription coverage”; this alternative does not provide that response.

D:

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 stem reports a security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions; this control addresses a different failure condition.

Question 337

A production Azure security implementation shows this failure: 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 technical cause best accounts for the described behavior?

  1. Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions.
  2. A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace.
  3. Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents.
  4. Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events.

Explanation

Correct Answer

C:

The described technical condition is: Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. The appropriate corrective action is: Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection. Confirm with: A controlled test incident causes the approved containment change and produces an auditable action record.

Incorrect Answers

A:

Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. “Configure the supported Entra sign-in log integration into Sentinel and verify enabled categories and consent” 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:

“Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters” responds to this separate finding: a DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. 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.

D:

Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Change the automation rule to the correct incident-created trigger with the intended scoped conditions” 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 338

A platform security assessment reveals this issue: A Front Door application must privately reach an Azure origin, yet its backend storage or app remains publicly accessible to any Internet client. What technical cause best accounts for the described behavior?

  1. The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template.
  2. A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues.
  3. The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path.
  4. The Front Door origin connection is not constrained through a supported private-link origin with public access restriction.

Explanation

Correct Answer

D:

The described technical condition is: The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. The appropriate corrective action is: Configure a supported Private Link origin and restrict direct public access to the origin service. Confirm with: Front Door continues serving approved requests but direct Internet calls to the origin are blocked.

Incorrect Answers

A:

The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. “Run Network Watcher IP flow verify with the test source, destination, direction and port” 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:

“Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results” responds to this separate finding: a point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. This question instead needs “Configure a supported Private Link origin and restrict direct public access to the origin service”, so the alternative does not meet the stated condition.

C:

The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. “Use supported origin access restrictions such as Private Link or validated Front Door identity headers where applicable” 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 339

An Azure security engineer investigates the following incident: A security engineer deploys a new Azure VM with no endpoint agent and assumes the VM cannot be assessed for known software vulnerabilities. Which result confirms the relevant security control is effective?

  1. The server protection dashboard reports the selected plan and expected supported security features for enrolled machines.
  2. An eligible Defender alert appears in Sentinel with its workload context and appropriate incident correlation.
  3. Release evidence includes a current image scan report and a documented decision for any outstanding high-risk packages.
  4. The new VM has a completed supported agentless assessment with software vulnerability recommendations visible to security owners.

Explanation

Correct Answer

D:

This validates the specific control for defender for servers agentless vulnerability scanning: Supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent. The associated corrective action is: Enable the supported agentless scanning capability and verify its resource scope, prerequisites and results. Testing a different component would not establish this result.

Incorrect Answers

A:

Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. “Compare required features to current Defender for Servers plans and enable the appropriate supported tier for governed machines” would address that alternative cause, not the condition in this question: supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent.

B:

“Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion” responds to this separate finding: defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. This question instead needs “Enable the supported agentless scanning capability and verify its resource scope, prerequisites and results”, so the alternative does not meet the stated condition.

C:

Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings” applies to that separate problem. The observed case is a security engineer deploys a new Azure VM with no endpoint agent and assumes the VM cannot be assessed for known software vulnerabilities; choosing this alternative would address the wrong failure mode.

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.