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 16

Question 150

The cloud operations team reviews the following risk: A pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure. Which configuration change most directly resolves this problem?

  1. Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope.
  2. Configure workload identity on the service account and scoped access to the target Key Vault.
  3. Enable the supported network policy option and enforce namespace/pod label based allowlists.
  4. Move credentials into a managed secrets service and use approved persistent data storage where needed.

Explanation

Correct Answer

B:

The cause is: The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. The appropriate change is: Configure workload identity on the service account and scoped access to the target Key Vault. Verify it with this outcome: The pod obtains a short-lived token and reads only the approved secret without stored client secrets.

Incorrect Answers

A:

This action concerns aks microsoft entra and kubernetes rbac, where Cluster authorization is not aligned with identity-based RBAC and separation of duties. The reported incident instead involves The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.

C:

This action concerns aks pod network policy isolation, where Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. The corrective response here is “Configure workload identity on the service account and scoped access to the target Key Vault”; this alternative does not provide that response.

D:

This action concerns ephemeral disk data handling, where Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. The stem reports a pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure; this control addresses a different failure condition.

Question 151

During a cloud security review, the operations team observes: A VM is deleted and recreated with the same name, but its prior system-assigned managed identity's role assignments are assumed to transfer unchanged. What technical cause best accounts for the described behavior?

  1. The application's registered redirect URI does not match the callback URI used in the authorization request.
  2. A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal.
  3. The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy.
  4. Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.

Explanation

Correct Answer

B:

The described technical condition is: A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. The appropriate corrective action is: Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal. Confirm with: The recreated VM authenticates to its approved resource using the newly granted managed identity.

Incorrect Answers

A:

The application's registered redirect URI does not match the callback URI used in the authorization request. “Register the exact approved redirect URI and update the app client flow accordingly” would address that alternative cause, not the condition in this question: a system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal.

C:

“Provision or consent the enterprise application service principal and configure appropriate access and controls” responds to this separate finding: the multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. This question instead needs “Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal”, 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. “Enable the approved passwordless method and complete secure user registration” applies to that separate problem. The observed case is a VM is deleted and recreated with the same name, but its prior system-assigned managed identity's role assignments are assumed to transfer unchanged; choosing this alternative would address the wrong failure mode.

Question 152

The cloud operations team reviews the following risk: A production application silently continues using a legacy connection secret near its expiration date because nobody owns renewal procedures. Which explanation fits the observed symptoms most closely?

  1. Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions.
  2. An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration.
  3. A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design.
  4. Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry.

Explanation

Correct Answer

D:

The described technical condition is: Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. The appropriate corrective action is: Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications. Confirm with: The application authenticates using the current secret and monitoring alerts before the next scheduled expiration.

Incorrect Answers

A:

Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. “Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope” would address that alternative cause, not the condition in this question: secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry.

B:

“Set time-limited exemptions with accountable justification and remove or renew each only after security review” responds to this separate finding: an exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. This question instead needs “Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications”, so the alternative does not meet the stated condition.

C:

A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. “Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported” applies to that separate problem. The observed case is a production application silently continues using a legacy connection secret near its expiration date because nobody owns renewal procedures; choosing this alternative would address the wrong failure mode.

Question 153

A regulated Azure tenant has this security condition: An administrator builds a valid data collection rule but points it at a test workspace while the SOC searches only its production workspace. Which remediation best addresses the specific issue?

  1. Map the rule output's user account and IP fields to the appropriate Sentinel entity types and identifiers.
  2. Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters.
  3. Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema.
  4. Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition.

Explanation

Correct Answer

B:

The cause is: A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. The appropriate change is: Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters. Verify it with this outcome: The expected records appear only in approved production destinations and analysts can query them within the retention policy.

Incorrect Answers

A:

This action concerns sentinel entity mapping accuracy, where Useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers. The reported incident instead involves A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace.

C:

This action concerns azure monitor transformation for sensitive fields, where Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. The corrective response here is “Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters”; this alternative does not provide that response.

D:

This action concerns sentinel automation rule order and stop processing, where Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. The stem reports an administrator builds a valid data collection rule but points it at a test workspace while the SOC searches only its production workspace; this control addresses a different failure condition.

Question 154

A platform security assessment reveals this issue: A SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation. Which operating control most directly reduces this recurring risk?

  1. Track custom domain certificate validity and binding renewal before expiration.
  2. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  3. Review WAF mode, tuning and false-positive impact before promoting a policy to production.
  4. Validate SQL MI subnet delegation and NSG/UDR constraints before submitting deployments.

Explanation

Correct Answer

D:

This guardrail addresses azure sql managed instance subnet requirements: SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The prevention measure is: Validate SQL MI subnet delegation and NSG/UDR constraints before submitting deployments. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The custom domain has no correct TLS certificate binding for the expected host name. “Track custom domain certificate validity and binding renewal before expiration” would address that alternative cause, not the condition in this question: sQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.

B:

“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 SQL MI subnet delegation and NSG/UDR constraints before submitting deployments”, so the alternative does not meet the stated condition.

C:

The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. “Review WAF mode, tuning and false-positive impact before promoting a policy to production” applies to that separate problem. The observed case is a SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation; choosing this alternative would address the wrong failure mode.

Question 155

While validating an Azure workload, the security team finds: A Conditional Access policy requires all administrators to use a device that depends on an outage-prone identity service, risking total tenant lockout when that service fails. What governance practice would best prevent the same failure?

  1. Use Conditional Access policy reviews and sign-in logs to confirm enforcement for protected applications.
  2. Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective.
  3. Set activation duration according to risk and monitor unusually long privilege activations.
  4. Audit, alert on, and periodically test emergency account use without treating it as a routine administrator.

Explanation

Correct Answer

D:

This guardrail addresses emergency access account exclusion design: No properly protected emergency access account and tested exclusion exists to recover from policy or federation failures. The prevention measure is: Audit, alert on, and periodically test emergency account use without treating it as a routine administrator. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: no properly protected emergency access account and tested exclusion exists to recover from policy or federation failures.

B:

“Validate Conditional Access mode and actual sign-in outcomes before declaring a new rule effective” responds to this separate finding: a Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. This question instead needs “Audit, alert on, and periodically test emergency account use without treating it as a routine administrator”, so the alternative does not meet the stated condition.

C:

The PIM activation duration permits unnecessarily long elevated privileges relative to the approved task window. “Set activation duration according to risk and monitor unusually long privilege activations” applies to that separate problem. The observed case is a Conditional Access policy requires all administrators to use a device that depends on an outage-prone identity service, risking total tenant lockout when that service fails; choosing this alternative would address the wrong failure mode.

Question 156

While validating an Azure workload, the security team finds: A public scan associates a similarly named third-party domain with the enterprise and analysts attempt to shut it down as their own asset. Which remediation best addresses the specific issue?

  1. Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution.
  2. Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope.
  3. Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls.
  4. Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains.

Explanation

Correct Answer

A:

The cause is: Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. The appropriate change is: Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution. Verify it with this outcome: Confirmed owned exposures enter the remediation queue while unrelated third-party assets are excluded with reasons.

Incorrect Answers

B:

This action concerns azure policy remediation managed identity permissions, where DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. The reported incident instead involves Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation.

C:

This action concerns risk acceptance versus secure score remediation, where Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. The corrective response here is “Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution”; this alternative does not provide that response.

D:

This action concerns defender easm externally visible asset discovery, where Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. The stem reports a public scan associates a similarly named third-party domain with the enterprise and analysts attempt to shut it down as their own asset; this control addresses a different failure condition.

Question 157

A Microsoft Azure administrator receives this requirement: A single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements. Which underlying control gap is responsible for the issue?

  1. Soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules.
  2. The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect.
  3. Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary.
  4. A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design.

Explanation

Correct Answer

C:

The described technical condition is: Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. The appropriate corrective action is: Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers. Confirm with: A protected backup deletion request fails until a separate authorized security approver grants the required permission.

Incorrect Answers

A:

Soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules. “Enable and verify the applicable vault soft delete protections and restrict backup-deletion privileges” would address that alternative cause, not the condition in this question: critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary.

B:

“Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type” responds to this separate finding: the Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect. This question instead needs “Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers”, so the alternative does not meet the stated condition.

D:

A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. “Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported” applies to that separate problem. The observed case is a single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements; choosing this alternative would address the wrong failure mode.

Question 158

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

  1. Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope.
  2. Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures.
  3. Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations.
  4. Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment.

Explanation

Correct Answer

A:

The cause is: Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. The appropriate change is: Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope. Verify it with this outcome: The operator reads the approved container but is denied access to an unrelated descendant subscription.

Incorrect Answers

B:

This action concerns deny assignment precedence, where Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. The reported incident instead involves Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted.

C:

This action concerns storage blob rbac conditions, where A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. The corrective response here is “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope”; this alternative does not provide that response.

D:

This action concerns custom role actions and notactions, where NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. The stem reports 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; this control addresses a different failure condition.

Question 159

An Azure security engineer investigates the following incident: An operator mistakenly deletes a cryptographic key used by Azure SQL encryption and plans to purge it to clean the vault. Which explanation fits the observed symptoms most closely?

  1. Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period.
  2. Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version.
  3. Azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing.
  4. Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active.

Explanation

Correct Answer

A:

The described technical condition is: Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period. The appropriate corrective action is: Recover the deleted key using the supported procedure and enable governed purge protection for critical encryption dependencies. Confirm with: The dependent database resumes protected access after recovery and unauthorized permanent purge is blocked.

Incorrect Answers

B:

Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. “Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint” would address that alternative cause, not the condition in this question: purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period.

C:

“Validate the configured policy baseline and separately test data-plane role assignments and storage access controls” responds to this separate finding: azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. This question instead needs “Recover the deleted key using the supported procedure and enable governed purge protection for critical encryption dependencies”, so the alternative does not meet the stated condition.

D:

Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active. “Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model” applies to that separate problem. The observed case is an operator mistakenly deletes a cryptographic key used by Azure SQL encryption and plans to purge it to clean the vault; choosing this alternative would address the wrong failure mode.

Question 160

A production Azure security implementation shows this failure: A subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet. What should the engineer implement first to address the weakness?

  1. Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls.
  2. Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path.
  3. Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes.
  4. Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope.

Explanation

Correct Answer

A:

The cause is: Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. The appropriate change is: Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls. Verify it with this outcome: Unauthorized Internet egress fails while approved endpoints remain reachable through logged channels.

Incorrect Answers

B:

This action concerns asymmetric routing around network virtual appliance, where Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. The reported incident instead involves Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply.

C:

This action concerns stateful nsg return traffic behavior, where NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. The corrective response here is “Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls”; this alternative does not provide that response.

D:

This action concerns subnet versus nic nsg evaluation, where Both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. The stem reports a subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet; this control addresses a different failure condition.