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 20

Question 190

During a cloud security review, the operations team observes: A Terraform change introduces publicly reachable database configuration, but teams review only whether the deployment pipeline passed syntax validation. What should the engineer implement first to address the weakness?

  1. Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment.
  2. Enable the applicable App Service workload protection and route findings to the approved responder queue.
  3. Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook.
  4. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.

Explanation

Correct Answer

A:

The cause is: Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The appropriate change is: Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment. Verify it with this outcome: The updated template passes the security assessment and the deployed database is not unintentionally public.

Incorrect Answers

B:

This action concerns defender for app service protection plan, where Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. The reported incident instead involves Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls.

C:

This action concerns defender for cloud workflow automation trigger scope, where A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. The corrective response here is “Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment”; this alternative does not provide that response.

D:

This action concerns defender vulnerability management remediation validation, where A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The stem reports a Terraform change introduces publicly reachable database configuration, but teams review only whether the deployment pipeline passed syntax validation; this control addresses a different failure condition.

Question 191

The cloud operations team reviews the following risk: A regulated storage account requires identity-based access, but data clients still authenticate using Shared Key and legacy SAS tokens. Which safeguard would best prevent this issue from recurring?

  1. Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry.
  2. Test WORM retention enforcement and approved release procedures before storing regulated records.
  3. Review SAS expiry, permission and network constraints during partner file exchange.
  4. Check account Shared Key access settings after migration and monitor rejected legacy clients.

Explanation

Correct Answer

D:

This guardrail addresses storage shared key authorization disable: The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. The prevention measure is: Check account Shared Key access settings after migration and monitor rejected legacy clients. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. “Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry” 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:

“Test WORM retention enforcement and approved release procedures before storing regulated records” responds to this separate finding: data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. This question instead needs “Check account Shared Key access settings after migration and monitor rejected legacy clients”, so the alternative does not meet the stated condition.

C:

The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. “Review SAS expiry, permission and network constraints during partner file exchange” 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 192

A regulated Azure tenant has this security condition: A newly provisioned VNet fails to receive expected global security configuration because it does not meet the membership condition of the assigned Network Manager group. Which configuration change most directly resolves this problem?

  1. Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs.
  2. Correct the group membership query or approved explicit membership and deploy the security configuration.
  3. Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls.
  4. Deploy the approved configuration to the correct regions and verify the deployed state.

Explanation

Correct Answer

B:

The cause is: The dynamic network group criteria do not include the intended VNet attributes or scope. The appropriate change is: Correct the group membership query or approved explicit membership and deploy the security configuration. Verify it with this outcome: The new VNet appears in the proper network group and receives the intended security admin rules.

Incorrect Answers

A:

This action concerns vnet peering non transitivity, where VNet peering does not inherently create transitive routing between other independently peered VNets. The reported incident instead involves The dynamic network group criteria do not include the intended VNet attributes or scope.

C:

This action concerns service tag outbound allow scoping, where A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. The corrective response here is “Correct the group membership query or approved explicit membership and deploy the security configuration”; this alternative does not provide that response.

D:

This action concerns central network intent deployment region, where Saving network manager intent does not itself apply connectivity or security configuration to target regions. The stem reports a newly provisioned VNet fails to receive expected global security configuration because it does not meet the membership condition of the assigned Network Manager group; this control addresses a different failure condition.

Question 193

A regulated Azure tenant has this security condition: A VM cannot reach a backend on TCP 5432, and an operator keeps guessing which NSG is responsible without testing effective decisions. Which remediation best addresses the specific issue?

  1. Run Network Watcher IP flow verify with the test source, destination, direction and port.
  2. Configure relevant firewall diagnostic categories and secure retention for rule and threat events.
  3. Configure a supported Private Link origin and restrict direct public access to the origin service.
  4. Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources.

Explanation

Correct Answer

A:

The cause is: The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. The appropriate change is: Run Network Watcher IP flow verify with the test source, destination, direction and port. Verify it with this outcome: Diagnostics identify the exact applicable rule and the corrected flow matches approved connectivity.

Incorrect Answers

B:

This action concerns firewall diagnostic settings and retention, where Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The reported incident instead involves The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template.

C:

This action concerns front door private link origin protection, where The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. The corrective response here is “Run Network Watcher IP flow verify with the test source, destination, direction and port”; this alternative does not provide that response.

D:

This action concerns ddos protection virtual network coverage, where An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. The stem reports a VM cannot reach a backend on TCP 5432, and an operator keeps guessing which NSG is responsible without testing effective decisions; this control addresses a different failure condition.

Question 194

During a cloud security review, the operations team observes: A web application redirects OAuth sign-in callbacks to an address different from its registered URI and receives a redirect mismatch error. Which underlying control gap is responsible for the issue?

  1. A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal.
  2. The application's registered redirect URI does not match the callback URI used in the authorization request.
  3. The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy.
  4. The app registration client credential has expired and the workload has no safe rotation mechanism.

Explanation

Correct Answer

B:

The described technical condition is: The application's registered redirect URI does not match the callback URI used in the authorization request. The appropriate corrective action is: Register the exact approved redirect URI and update the app client flow accordingly. Confirm with: The authorized browser sign-in returns only to the registered callback, rejecting unlisted redirect targets.

Incorrect Answers

A:

A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. “Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal” would address that alternative cause, not the condition in this question: the application's registered redirect URI does not match the callback URI used in the authorization request.

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 “Register the exact approved redirect URI and update the app client flow accordingly”, so the alternative does not meet the stated condition.

D:

The app registration client credential has expired and the workload has no safe rotation mechanism. “Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation” applies to that separate problem. The observed case is a web application redirects OAuth sign-in callbacks to an address different from its registered URI and receives a redirect mismatch error; choosing this alternative would address the wrong failure mode.

Question 195

A Microsoft Azure administrator receives this requirement: A GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments. After remediation, which test result best proves the intended change?

  1. A subsequent scan no longer detects the affected vulnerable package or documents a justified protected exception.
  2. A matching test alert triggers the intended notification or ticket while unrelated findings do not invoke it.
  3. The previously omitted repositories appear in DevOps Security findings and receive appropriate code scanning coverage.
  4. A controlled suspicious management-plane action produces the expected Defender alert and activity context.

Explanation

Correct Answer

C:

This validates the specific control for defender for cloud devops github connector scope: DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. The associated corrective action is: Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories. Testing a different component would not establish this result.

Incorrect Answers

A:

A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. “Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation” would address that alternative cause, not the condition in this question: devOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.

B:

“Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook” responds to this separate finding: a Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. This question instead needs “Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments; choosing this alternative would address the wrong failure mode.

Question 196

During a cloud security review, the operations team observes: An Azure App Service managed identity has Contributor on its resource group but fails to read a secret from an RBAC-enabled Key Vault. After remediation, which test result best proves the intended change?

  1. The application resolves the required secret without receiving broad Key Vault management permission.
  2. The managed identity writes only approved blobs after role propagation and cannot access excluded storage.
  3. The consuming tenant lists the app service principal and can enforce authorized user assignment.
  4. The function uses token-based access without a stored application client secret and writes only permitted blobs.

Explanation

Correct Answer

A:

This validates the specific control for 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 associated corrective action is: Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity. Testing a different component would not establish this result.

Incorrect Answers

B:

Creating a managed identity alone does not grant the target resource's required data-plane role. “Grant the appropriate storage blob data role to the VM identity at the least necessary scope” 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:

“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 “Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity”, so the alternative does not meet the stated condition.

D:

The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. “Enable an appropriate managed identity and grant narrowly scoped storage data authorization to that identity” 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 197

During a cloud security review, the operations team observes: An attacker with backup administrative rights tries to delete backup items permanently to defeat future recovery after ransomware deployment. What is the most appropriate corrective step?

  1. Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation.
  2. Use controlled SSH public-key authentication and restrict access through Bastion or approved private management.
  3. Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible.
  4. Enable supported vault soft delete and enhanced protection settings including immutable backup where required.

Explanation

Correct Answer

D:

The cause is: Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. The appropriate change is: Enable supported vault soft delete and enhanced protection settings including immutable backup where required. Verify it with this outcome: A deletion attempt cannot immediately eradicate protected backup recovery points and recovery remains possible.

Incorrect Answers

A:

This action concerns aks workload image scanning, where Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. The reported incident instead involves Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault.

B:

This action concerns linux ssh key management, where Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. The corrective response here is “Enable supported vault soft delete and enhanced protection settings including immutable backup where required”; this alternative does not provide that response.

C:

This action concerns aks key vault csi secret retrieval, where Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. The stem reports an attacker with backup administrative rights tries to delete backup items permanently to defeat future recovery after ransomware deployment; this control addresses a different failure condition.

Question 198

While validating an Azure workload, the security team finds: Security operators see important Defender for Cloud findings but they never arrive in their central Microsoft Sentinel investigation queue. Which remediation best addresses the specific issue?

  1. Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion.
  2. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.
  3. Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings.
  4. Review project and repository connector coverage and enable the supported assessment pipeline for the missing project.

Explanation

Correct Answer

A:

The cause is: Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. The appropriate change is: Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion. Verify it with this outcome: An eligible Defender alert appears in Sentinel with its workload context and appropriate incident correlation.

Incorrect Answers

B:

This action concerns defender vulnerability management remediation validation, where A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The reported incident instead involves Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace.

C:

This action concerns defender for containers container registry vulnerabilities, where Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. The corrective response here is “Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion”; this alternative does not provide that response.

D:

This action concerns defender for cloud devops azure devops project coverage, where A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. The stem reports security operators see important Defender for Cloud findings but they never arrive in their central Microsoft Sentinel investigation queue; this control addresses a different failure condition.

Question 199

The cloud operations team reviews the following risk: 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 remediation best addresses the specific issue?

  1. Validate the configured policy baseline and separately test data-plane role assignments and storage access controls.
  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. Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing.

Explanation

Correct Answer

B:

The cause is: A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. The appropriate change is: Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported. Verify it with this outcome: After a controlled rotation the service remains encrypted and uses an appropriate authorized key version without downtime.

Incorrect Answers

A:

This action concerns azure policy evaluation versus data plane checks, where Azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. The reported incident instead involves A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design.

C:

This action concerns azure policy initiative and parameter assignments, where Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. The corrective response here is “Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported”; this alternative does not provide that response.

D:

This action concerns azure backup immutable vault controls, where An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. The stem reports 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; this control addresses a different failure condition.

Question 200

An Azure security engineer investigates the following incident: A leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation. Which outcome most clearly verifies that the issue is resolved?

  1. The managed identity writes only approved blobs after role propagation and cannot access excluded storage.
  2. The daemon acquires tokens again without logging or exposing client credentials.
  3. The consuming tenant lists the app service principal and can enforce authorized user assignment.
  4. High-risk users complete required recovery or are denied access while risk remediation is recorded.

Explanation

Correct Answer

D:

This validates the specific control for identity protection user risk response: No effective user-risk-based identity protection response has been configured for the relevant identities. The associated corrective action is: Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate. Testing a different component would not establish this result.

Incorrect Answers

A:

Creating a managed identity alone does not grant the target resource's required data-plane role. “Grant the appropriate storage blob data role to the VM identity at the least necessary scope” would address that alternative cause, not the condition in this question: no effective user-risk-based identity protection response has been configured for the relevant identities.

B:

“Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation” responds to this separate finding: the app registration client credential has expired and the workload has no safe rotation mechanism. This question instead needs “Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate”, so the alternative does not meet the stated condition.

C:

The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. “Provision or consent the enterprise application service principal and configure appropriate access and controls” applies to that separate problem. The observed case is a leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation; choosing this alternative would address the wrong failure mode.