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 25

Question 240

During a cloud security review, the operations team observes: A web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured. Which recurring validation best protects against the observed problem?

  1. Test both private-resolution success and public-path denial whenever a new Private Endpoint is added.
  2. Verify DNS zone links and forwarders for all VNets consuming a private service.
  3. Validate App Service inbound and outbound network controls independently in deployment testing.
  4. Check supported private endpoint network policy settings before relying on subnet inspection rules.

Explanation

Correct Answer

C:

This guardrail addresses app service vnet integration outbound path: App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. The prevention measure is: Validate App Service inbound and outbound network controls independently in deployment testing. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A private endpoint has not been configured or public network access has not been restricted for the resource. “Test both private-resolution success and public-path denial whenever a new Private Endpoint is added” would address that alternative cause, not the condition in this question: app Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections.

B:

“Verify DNS zone links and forwarders for all VNets consuming a private service” responds to this separate finding: the private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. This question instead needs “Validate App Service inbound and outbound network controls independently in deployment testing”, so the alternative does not meet the stated condition.

D:

Private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. “Check supported private endpoint network policy settings before relying on subnet inspection rules” applies to that separate problem. The observed case is a web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured; choosing this alternative would address the wrong failure mode.

Question 241

An Azure security engineer investigates the following incident: A site-to-site Azure VPN tunnel reports connected, but on-premises routes are absent because the expected BGP peers do not establish. Which configuration change most directly resolves this problem?

  1. Configure the supported Virtual WAN routing intent and policy for the required traffic categories.
  2. Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state.
  3. Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation.
  4. Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address.

Explanation

Correct Answer

B:

The cause is: The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. The appropriate change is: Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state. Verify it with this outcome: BGP sessions establish and only approved prefixes appear on both sides of the encrypted connection.

Incorrect Answers

A:

This action concerns virtual wan routing intent security, where The secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured. The reported incident instead involves The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect.

C:

This action concerns firewall threat intelligence mode, where The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. The corrective response here is “Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state”; this alternative does not provide that response.

D:

This action concerns firewall dns proxy routing, where Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. The stem reports a site-to-site Azure VPN tunnel reports connected, but on-premises routes are absent because the expected BGP peers do not establish; this control addresses a different failure condition.

Question 242

A platform security assessment reveals this issue: Users access a sensitive administration application from ungoverned personal devices because the tenant only checks successful password authentication. Which operating control most directly reduces this recurring risk?

  1. Test permitted authentication methods against the actual role threat model after policy changes.
  2. Revalidate device compliance policy and Conditional Access coverage after device enrollment changes.
  3. Monitor legacy sign-in activity and resolve legitimate dependencies before enforcing global legacy blocking.
  4. Reconcile trusted named locations with network change records and periodically retest ranges.

Explanation

Correct Answer

B:

This guardrail addresses require compliant device condition: The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. The prevention measure is: Revalidate device compliance policy and Conditional Access coverage after device enrollment changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. “Test permitted authentication methods against the actual role threat model after policy changes” would address that alternative cause, not the condition in this question: the Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow.

C:

“Monitor legacy sign-in activity and resolve legitimate dependencies before enforcing global legacy blocking” responds to this separate finding: the tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. This question instead needs “Revalidate device compliance policy and Conditional Access coverage after device enrollment changes”, so the alternative does not meet the stated condition.

D:

The named location definition is stale and no longer reflects current verified branch egress address ranges. “Reconcile trusted named locations with network change records and periodically retest ranges” applies to that separate problem. The observed case is users access a sensitive administration application from ungoverned personal devices because the tenant only checks successful password authentication; choosing this alternative would address the wrong failure mode.

Question 243

During a cloud security review, the operations team observes: Security operators see important Defender for Cloud findings but they never arrive in their central Microsoft Sentinel investigation queue. What observation is the strongest validation evidence?

  1. The migrated GitLab infrastructure-as-code repositories become visible with supported security findings.
  2. The new VM has a completed supported agentless assessment with software vulnerability recommendations visible to security owners.
  3. An eligible Defender alert appears in Sentinel with its workload context and appropriate incident correlation.
  4. A safe simulated anomalous database activity test generates the expected protection alert without changing legitimate data.

Explanation

Correct Answer

C:

This validates the specific control for defender for cloud alert to sentinel ingestion: Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. The associated corrective action is: Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion. Testing a different component would not establish this result.

Incorrect Answers

A:

Code security inventory and posture coverage depend on a supported connector for the actual source-control platform. “Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories” would address that alternative cause, not the condition in this question: defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace.

B:

“Enable the supported agentless scanning capability and verify its resource scope, prerequisites and results” responds to this separate finding: supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent. This question instead needs “Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion”, so the alternative does not meet the stated condition.

D:

Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. “Enable the appropriate Defender for SQL or Databases protection plan and configure supported alert routing” applies to that separate problem. The observed case is security operators see important Defender for Cloud findings but they never arrive in their central Microsoft Sentinel investigation queue; choosing this alternative would address the wrong failure mode.

Question 244

A platform security assessment reveals this issue: An organization creates a strict Conditional Access block for risky Azure portal sessions but users continue signing in because administrators never enable the policy. Which operating control most directly reduces this recurring risk?

  1. Schedule periodic owner-driven reviews for groups granting sensitive Azure resource permissions.
  2. Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective.
  3. Audit PIM approval configuration and backup approvers after organizational changes.
  4. Audit, alert on, and periodically test emergency account use without treating it as a routine administrator.

Explanation

Correct Answer

B:

This guardrail addresses conditional access report only mode: A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. The prevention measure is: Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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: a Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block.

C:

“Audit PIM approval configuration and backup approvers after organizational changes” responds to this separate finding: the PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. This question instead needs “Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective”, so the alternative does not meet the stated condition.

D:

No properly protected emergency access account and tested exclusion exists to recover from policy or federation failures. “Audit, alert on, and periodically test emergency account use without treating it as a routine administrator” applies to that separate problem. The observed case is an organization creates a strict Conditional Access block for risky Azure portal sessions but users continue signing in because administrators never enable the policy; choosing this alternative would address the wrong failure mode.

Question 245

During a cloud security review, the operations team observes: A regulated organization needs to apply a coordinated security baseline to ten subscriptions, but administrators assign isolated definitions with inconsistent parameters. What is the most appropriate corrective step?

  1. Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition.
  2. Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported.
  3. Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope.
  4. Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications.

Explanation

Correct Answer

C:

The cause is: Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. The appropriate change is: Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope. Verify it with this outcome: Each child subscription reports consistent compliance results and the documented initiative parameters match approved standards.

Incorrect Answers

A:

This action concerns azure policy modify remediation for existing tags, where Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. The reported incident instead involves Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions.

B:

This action concerns key vault key rotation version pinning, where A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. The corrective response here is “Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope”; this alternative does not provide that response.

D:

This action concerns key vault secret expiry lifecycle, where Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. The stem reports a regulated organization needs to apply a coordinated security baseline to ten subscriptions, but administrators assign isolated definitions with inconsistent parameters; this control addresses a different failure condition.

Question 246

A platform security assessment reveals this issue: A GitHub Actions deployment stores a long-lived Azure service principal secret as a repository variable and leaked logs risk credential compromise. What is the most appropriate corrective step?

  1. Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret.
  2. Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles.
  3. Revoke the excessive permission and grant only the narrowly required API scopes or app roles.
  4. Inspect service principal sign-in logs and correlated credential or conditional policy results.

Explanation

Correct Answer

A:

The cause is: Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. The appropriate change is: Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret. Verify it with this outcome: Only the approved workflow obtains short-lived Azure tokens without transmitting a static client secret.

Incorrect Answers

B:

This action concerns cross tenant service principal consent, where Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The reported incident instead involves Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra.

C:

This action concerns overprivileged oauth permission grant, where The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. The corrective response here is “Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret”; this alternative does not provide that response.

D:

This action concerns service principal sign in diagnostics, where Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The stem reports a GitHub Actions deployment stores a long-lived Azure service principal secret as a repository variable and leaked logs risk credential compromise; this control addresses a different failure condition.

Question 247

A regulated Azure tenant has this security condition: An Azure SQL database is administered only by a shared SQL login, contrary to corporate requirements for named Entra identity lifecycle management. Which outcome most clearly verifies that the issue is resolved?

  1. A low-privilege test user sees masked values while approved privileged users follow their allowed data access.
  2. Sensitive columns remain encrypted to the database engine while authorized clients decrypt needed values.
  3. The database reports TDE enabled and encrypted at-rest backups while client connections remain supported.
  4. Authorized Entra principals connect and act within granted database roles without using the shared SQL account.

Explanation

Correct Answer

D:

This validates the specific control for azure sql microsoft entra administrator auth: The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. The associated corrective action is: Configure the Microsoft Entra administrator and create appropriate contained database users and roles. Testing a different component would not establish this result.

Incorrect Answers

A:

SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. “Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers” would address that alternative cause, not the condition in this question: the SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication.

B:

“Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients” responds to this separate finding: tDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. This question instead needs “Configure the Microsoft Entra administrator and create appropriate contained database users and roles”, so the alternative does not meet the stated condition.

C:

TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration” applies to that separate problem. The observed case is an Azure SQL database is administered only by a shared SQL login, contrary to corporate requirements for named Entra identity lifecycle management; choosing this alternative would address the wrong failure mode.

Question 248

A platform security assessment reveals this issue: A regulated storage account requires identity-based access, but data clients still authenticate using Shared Key and legacy SAS tokens. What observation is the strongest validation evidence?

  1. Approved clients access data and unauthorized public source IPs receive network access denial.
  2. The storage account reports infrastructure encryption enabled in addition to regular service-side encryption.
  3. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.
  4. Shared Key requests are rejected while approved identity-based blob operations succeed.

Explanation

Correct Answer

D:

This validates the specific control for storage shared key authorization disable: The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. The associated corrective action is: Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS. Testing a different component would not establish this result.

Incorrect Answers

A:

The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. “Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required” would address that alternative cause, not the condition in this question: the account has not disabled Shared Key authorization where the application's supported operations permit identity-based control.

B:

“Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage” responds to this separate finding: the specified infrastructure encryption requirement needs the supported additional service-side encryption layer. This question instead needs “Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS”, so the alternative does not meet the stated condition.

C:

Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. “Configure customer-managed key encryption and grant the storage account identity the required key permissions” applies to that separate problem. The observed case is a regulated storage account requires identity-based access, but data clients still authenticate using Shared Key and legacy SAS tokens; choosing this alternative would address the wrong failure mode.

Question 249

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 observation is the strongest validation evidence?

  1. Both functions obtain tokens for the approved user-assigned identity without duplicating secrets.
  2. The managed identity writes only approved blobs after role propagation and cannot access excluded storage.
  3. The application resolves the required secret without receiving broad Key Vault management permission.
  4. High-risk users complete required recovery or are denied access while risk remediation is recorded.

Explanation

Correct Answer

B:

This validates the specific control for managed identity data authorization: Creating a managed identity alone does not grant the target resource's required data-plane role. The associated corrective action is: Grant the appropriate storage blob data role to the VM identity at the least necessary scope. Testing a different component would not establish this result.

Incorrect Answers

A:

Separate system-assigned identities do not provide the stable reusable principal desired across resources. “Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly” would address that alternative cause, not the condition in this question: creating a managed identity alone does not grant the target resource's required data-plane role.

C:

“Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity” responds to this separate finding: resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. This question instead needs “Grant the appropriate storage blob data role to the VM identity at the least necessary scope”, so the alternative does not meet the stated condition.

D:

No effective user-risk-based identity protection response has been configured for the relevant identities. “Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate” applies to that separate problem. The observed case is a VM successfully obtains a token for Azure Storage through managed identity, but blob writes return 403 even though its system identity exists; choosing this alternative would address the wrong failure mode.

Question 250

A platform security assessment reveals this issue: A security analyst concludes there are no vulnerable resources because the Defender inventory is filtered to a single region rather than the global workload footprint. What is the most appropriate corrective step?

  1. Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives.
  2. Check supported AWS assessment coverage, connector health and applicable cloud-specific configuration rules before comparing results.
  3. Query all in-scope Azure resources first and then classify missing or unexpected tags for correction.
  4. Clear or expand the inventory filter and verify the evaluated scope against resource ownership records.

Explanation

Correct Answer

D:

The cause is: Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. The appropriate change is: Clear or expand the inventory filter and verify the evaluated scope against resource ownership records. Verify it with this outcome: Previously hidden resources are included and their vulnerability or configuration status can be assessed.

Incorrect Answers

A:

This action concerns defender for cloud recommendation root-cause assessment, where A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. The reported incident instead involves Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types.

B:

This action concerns microsoft defender for cloud aws security benchmark coverage, where Control applicability and enabled cloud connectors differ across providers, so absent assessment coverage is not equivalent to a passing control. The corrective response here is “Clear or expand the inventory filter and verify the evaluated scope against resource ownership records”; this alternative does not provide that response.

C:

This action concerns defender for cloud azure resource graph query validation, where Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. The stem reports a security analyst concludes there are no vulnerable resources because the Defender inventory is filtered to a single region rather than the global workload footprint; this control addresses a different failure condition.