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 76

Question 750

The cloud operations team reviews the following risk: A highly sensitive VM workload requires protecting guest memory and boot state, but the design uses only ordinary managed disk encryption. Which configuration change most directly resolves this problem?

  1. Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies.
  2. Choose supported confidential VM features and configure the correct security type and encryption settings.
  3. Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules.
  4. Configure the encryption set and supported Key Vault key permissions, then associate eligible disks.

Explanation

Correct Answer

B:

The cause is: Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory. The appropriate change is: Choose supported confidential VM features and configure the correct security type and encryption settings. Verify it with this outcome: A test VM reports the intended confidential security posture and protected boot chain.

Incorrect Answers

A:

This action concerns azure disk encryption key vault dependency, where Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. The reported incident instead involves Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory.

C:

This action concerns azure bastion without public vm ip, where Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. The corrective response here is “Choose supported confidential VM features and configure the correct security type and encryption settings”; this alternative does not provide that response.

D:

This action concerns disk customer managed key disk encryption set, where Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The stem reports a highly sensitive VM workload requires protecting guest memory and boot state, but the design uses only ordinary managed disk encryption; this control addresses a different failure condition.

Question 751

While validating an Azure workload, the security team finds: A shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs. What governance practice would best prevent the same failure?

  1. Test negative token cases after identity provider and APIM policy changes.
  2. Separate build-pipeline image publishing identity from runtime image-pull identity.
  3. Review client certificate trust and renewal processes for all privileged API consumers.
  4. Review ACR admin user state and rotate or remove unused registry credentials.

Explanation

Correct Answer

D:

This guardrail addresses acr administrator account disablement: The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The prevention measure is: Review ACR admin user state and rotate or remove unused registry credentials. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. “Test negative token cases after identity provider and APIM policy changes” would address that alternative cause, not the condition in this question: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.

B:

“Separate build-pipeline image publishing identity from runtime image-pull identity” responds to this separate finding: the workload has an overly broad registry data role instead of the necessary pull-only authorization. This question instead needs “Review ACR admin user state and rotate or remove unused registry credentials”, so the alternative does not meet the stated condition.

C:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Review client certificate trust and renewal processes for all privileged API consumers” applies to that separate problem. The observed case is a shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs; choosing this alternative would address the wrong failure mode.

Question 752

A Microsoft Azure administrator receives this requirement: A Terraform change introduces publicly reachable database configuration, but teams review only whether the deployment pipeline passed syntax validation. What technical cause best accounts for the described behavior?

  1. Control-plane Resource Manager activity can require dedicated detection separate from guest server security events.
  2. A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified.
  3. DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.
  4. Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls.

Explanation

Correct Answer

D:

The described technical condition is: Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The appropriate corrective action is: Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment. Confirm with: The updated template passes the security assessment and the deployed database is not unintentionally public.

Incorrect Answers

A:

Control-plane Resource Manager activity can require dedicated detection separate from guest server security events. “Enable supported Defender for Resource Manager protection and route control-plane anomalies to investigators” would address that alternative cause, not the condition in this question: infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls.

B:

“Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation” responds to this separate finding: a vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. This question instead needs “Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment”, so the alternative does not meet the stated condition.

C:

DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. “Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories” applies to that separate problem. The observed case is a Terraform change introduces publicly reachable database configuration, but teams review only whether the deployment pipeline passed syntax validation; choosing this alternative would address the wrong failure mode.

Question 753

A platform security assessment reveals this issue: A production cluster identity can push or delete container images in ACR even though it only needs to retrieve signed deployment images. What should the engineer implement first to address the weakness?

  1. Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims.
  2. Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys.
  3. Grant the appropriate ACR pull permission and remove excess push or management roles.
  4. Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys.

Explanation

Correct Answer

C:

The cause is: The workload has an overly broad registry data role instead of the necessary pull-only authorization. The appropriate change is: Grant the appropriate ACR pull permission and remove excess push or management roles. Verify it with this outcome: The cluster pulls approved images but cannot push replacement artifacts or modify registry settings.

Incorrect Answers

A:

This action concerns api management validate jwt policy, where API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. The reported incident instead involves The workload has an overly broad registry data role instead of the necessary pull-only authorization.

B:

This action concerns storage shared key versus sas distinction, where Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. The corrective response here is “Grant the appropriate ACR pull permission and remove excess push or management roles”; this alternative does not provide that response.

D:

This action concerns storage account key rotation continuity, where The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. The stem reports a production cluster identity can push or delete container images in ACR even though it only needs to retrieve signed deployment images; this control addresses a different failure condition.

Question 754

During a cloud security review, the operations team observes: Storage encryption depends on a Key Vault key URI that names a fixed old key version, and an administrator expects automatic key rotation to update consumers. Which underlying control gap is responsible for the issue?

  1. Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads.
  2. Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active.
  3. A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design.
  4. Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions.

Explanation

Correct Answer

C:

The described technical condition is: A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. The appropriate corrective action is: Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported. Confirm with: After a controlled rotation the service remains encrypted and uses an appropriate authorized key version without downtime.

Incorrect Answers

A:

Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. “Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path” would address that alternative cause, not the condition in this question: a service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design.

B:

“Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model” responds to this separate finding: key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active. This question instead needs “Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported”, so the alternative does not meet the stated condition.

D:

Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. “Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition” applies to that separate problem. The observed case is storage encryption depends on a Key Vault key URI that names a fixed old key version, and an administrator expects automatic key rotation to update consumers; choosing this alternative would address the wrong failure mode.

Question 755

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. Which configuration change most directly resolves this problem?

  1. Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity.
  2. Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly.
  3. Enable the approved passwordless method and complete secure user registration.
  4. Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate.

Explanation

Correct Answer

A:

The cause is: Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. The appropriate change is: Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity. Verify it with this outcome: The application resolves the required secret without receiving broad Key Vault management permission.

Incorrect Answers

B:

This action concerns user assigned managed identity reuse, where Separate system-assigned identities do not provide the stable reusable principal desired across resources. The reported incident instead involves Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model.

C:

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 corrective response here is “Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity”; this alternative does not provide that response.

D:

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 stem reports an Azure App Service managed identity has Contributor on its resource group but fails to read a secret from an RBAC-enabled Key Vault; this control addresses a different failure condition.

Question 756

While validating an Azure workload, the security team finds: A multi-subscription organization buys a DDoS protection plan but forgets to associate eligible production VNets containing exposed public services. Which outcome most clearly verifies that the issue is resolved?

  1. The identified next hop matches the approved routing design after changes, with no unintended appliance loop.
  2. Security inventory shows production VNets under the required DDoS protection configuration.
  3. Front Door continues serving approved requests but direct Internet calls to the origin are blocked.
  4. The connection test identifies reachability and applicable hop failures before and after the repair.

Explanation

Correct Answer

B:

This validates the specific control for ddos plan coverage and ownership: Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The associated corrective action is: Associate intended eligible VNets with the correct plan and validate protection settings. Testing a different component would not establish this result.

Incorrect Answers

A:

A user-defined or propagated route controls the next hop independently of NSG allow decisions. “Inspect effective routes and run Network Watcher next hop against the intended destination IP” would address that alternative cause, not the condition in this question: purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet.

C:

“Configure a supported Private Link origin and restrict direct public access to the origin service” responds to this separate finding: the Front Door origin connection is not constrained through a supported private-link origin with public access restriction. This question instead needs “Associate intended eligible VNets with the correct plan and validate protection settings”, so the alternative does not meet the stated condition.

D:

A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. “Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results” applies to that separate problem. The observed case is a multi-subscription organization buys a DDoS protection plan but forgets to associate eligible production VNets containing exposed public services; choosing this alternative would address the wrong failure mode.

Question 757

During a cloud security review, the operations team observes: A tenant permits employees to consent to any third-party application, resulting in a rogue app receiving broad mailbox-related scopes. What technical cause best accounts for the described behavior?

  1. The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact.
  2. Successful authentication does not establish application authorization; app roles and assignments are not enforced.
  3. The user consent configuration permits risky OAuth grants without publisher and permission restrictions.
  4. Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.

Explanation

Correct Answer

C:

The described technical condition is: The user consent configuration permits risky OAuth grants without publisher and permission restrictions. The appropriate corrective action is: Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow. Confirm with: A test unverified high-risk application cannot gain requested scopes through ordinary user consent.

Incorrect Answers

A:

The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. “Revoke the excessive permission and grant only the narrowly required API scopes or app roles” would address that alternative cause, not the condition in this question: the user consent configuration permits risky OAuth grants without publisher and permission restrictions.

B:

“Define application roles, assign them to approved users or groups and validate role claims in the app” responds to this separate finding: successful authentication does not establish application authorization; app roles and assignments are not enforced. This question instead needs “Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow”, so the alternative does not meet the stated condition.

D:

Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. “Inspect service principal sign-in logs and correlated credential or conditional policy results” applies to that separate problem. The observed case is a tenant permits employees to consent to any third-party application, resulting in a rogue app receiving broad mailbox-related scopes; choosing this alternative would address the wrong failure mode.

Question 758

An Azure security engineer investigates the following incident: 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 condition most directly explains the failure?

  1. A DeployIfNotExists assignment evaluates related resources but needs appropriate assignment identity permissions and remediation for existing assets.
  2. Soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules.
  3. Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules.
  4. Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry.

Explanation

Correct Answer

C:

The described technical condition is: Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. The appropriate corrective action is: Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault. Confirm with: A restored test key operates in the approved recovery location with its expected identity and cryptographic properties.

Incorrect Answers

A:

A DeployIfNotExists assignment evaluates related resources but needs appropriate assignment identity permissions and remediation for existing assets. “Grant only the necessary deployment role to the assignment identity and run the authorized remediation task” 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.

B:

“Enable and verify the applicable vault soft delete protections and restrict backup-deletion privileges” responds to this separate finding: soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules. This question instead needs “Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault”, so the alternative does not meet the stated condition.

D:

Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. “Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications” 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 759

A regulated Azure tenant has this security condition: A subscription Owner role can be activated by any eligible member immediately even though security policy requires peer approval for high-risk changes. Which remediation best addresses the specific issue?

  1. Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context.
  2. Maintain tightly monitored cloud-only emergency access accounts excluded from the blocking control under approved procedures.
  3. Configure approval and valid approvers for activation of the sensitive Azure resource role.
  4. Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed.

Explanation

Correct Answer

C:

The cause is: The PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. The appropriate change is: Configure approval and valid approvers for activation of the sensitive Azure resource role. Verify it with this outcome: A pending activation cannot be used before an authorized approver reviews and approves it.

Incorrect Answers

A:

This action concerns role assignment audit history, where Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. The reported incident instead involves The PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role.

B:

This action concerns emergency access account exclusion design, where No properly protected emergency access account and tested exclusion exists to recover from policy or federation failures. The corrective response here is “Configure approval and valid approvers for activation of the sensitive Azure resource role”; this alternative does not provide that response.

D:

This action concerns risk based conditional access policy, where Network location alone does not substitute for appropriate risk signals and risk-based access controls. The stem reports a subscription Owner role can be activated by any eligible member immediately even though security policy requires peer approval for high-risk changes; this control addresses a different failure condition.

Question 760

A regulated Azure tenant has this security condition: An application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress. Which result confirms the relevant security control is effective?

  1. Direct origin requests are rejected while requests passing the edge WAF are served.
  2. The identified next hop matches the approved routing design after changes, with no unintended appliance loop.
  3. Front Door continues serving approved requests but direct Internet calls to the origin are blocked.
  4. The security team queries the required firewall rule-match records for a controlled test flow.

Explanation

Correct Answer

B:

This validates the specific control for network watcher next hop diagnosis: A user-defined or propagated route controls the next hop independently of NSG allow decisions. The associated corrective action is: Inspect effective routes and run Network Watcher next hop against the intended destination IP. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: a user-defined or propagated route controls the next hop independently of NSG allow decisions.

C:

“Configure a supported Private Link origin and restrict direct public access to the origin service” responds to this separate finding: the Front Door origin connection is not constrained through a supported private-link origin with public access restriction. This question instead needs “Inspect effective routes and run Network Watcher next hop against the intended destination IP”, so the alternative does not meet the stated condition.

D:

Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. “Configure relevant firewall diagnostic categories and secure retention for rule and threat events” applies to that separate problem. The observed case is an application packet uses an unexpected virtual appliance instead of an Internet path even though the VM's subnet NSG allows egress; choosing this alternative would address the wrong failure mode.