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 68

Question 670

During a cloud security review, the operations team observes: A subscription team assigns an Azure Policy definition with Audit effect to prevent public IP deployment, yet the network group continues creating public IP resources. After remediation, which test result best proves the intended change?

  1. The dependent database resumes protected access after recovery and unauthorized permanent purge is blocked.
  2. A new prohibited public IP deployment is rejected while existing resources appear in policy compliance reporting.
  3. Approved services retrieve permitted secrets through the expected path while unauthorized public requests fail.
  4. After a controlled rotation the service remains encrypted and uses an appropriate authorized key version without downtime.

Explanation

Correct Answer

B:

This validates the specific control for azure policy audit versus deny effect: The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect. The associated corrective action is: Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type. Testing a different component would not establish this result.

Incorrect Answers

A:

Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period. “Recover the deleted key using the supported procedure and enable governed purge protection for critical encryption dependencies” would address that alternative cause, not the condition in this question: the Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect.

C:

“Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path” responds to this separate finding: key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. This question instead needs “Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type”, 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 subscription team assigns an Azure Policy definition with Audit effect to prevent public IP deployment, yet the network group continues creating public IP resources; choosing this alternative would address the wrong failure mode.

Question 671

A regulated Azure tenant has this security condition: A private endpoint connection is approved, but VMs keep resolving a storage hostname to the service's public IP from an unlinked VNet. Which condition most directly explains the failure?

  1. The provider has not published a supported Private Link Service behind an eligible standard internal load balancer.
  2. The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations.
  3. App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections.
  4. The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address.

Explanation

Correct Answer

D:

The described technical condition is: The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. The appropriate corrective action is: Configure the correct privatelink DNS zone record and link the client VNet to the zone. Confirm with: The storage service hostname resolves to the intended private endpoint IP from authorized clients.

Incorrect Answers

A:

The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval” would address that alternative cause, not the condition in this question: the private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address.

B:

“Apply an appropriate service endpoint policy restricting the subnet to approved storage resources” responds to this separate finding: the subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations. This question instead needs “Configure the correct privatelink DNS zone record and link the client VNet to the zone”, so the alternative does not meet the stated condition.

C:

App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. “Configure regional App Service VNet integration and the necessary subnet routing and DNS” applies to that separate problem. The observed case is a private endpoint connection is approved, but VMs keep resolving a storage hostname to the service's public IP from an unlinked VNet; choosing this alternative would address the wrong failure mode.

Question 672

A platform security assessment reveals this issue: A Kubernetes service crashes repeatedly but the security team collects only VM infrastructure metrics and lacks container and audit diagnostics. What is the most appropriate corrective step?

  1. Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels.
  2. Use secure value handling or managed identity based authentication for the containerized application.
  3. Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components.
  4. Schedule supported AKS node image updates and verify rollout health across node pools.

Explanation

Correct Answer

A:

The cause is: AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. The appropriate change is: Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels. Verify it with this outcome: Security analysts can correlate pod restart, audit and security signals for the affected workload.

Incorrect Answers

B:

This action concerns container instances environment secret handling, where Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. The reported incident instead involves AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health.

C:

This action concerns azure policy admission for aks, where Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. The corrective response here is “Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels”; this alternative does not provide that response.

D:

This action concerns aks node image upgrade hygiene, where Control-plane version compliance is distinct from node OS image and node pool security patch state. The stem reports a Kubernetes service crashes repeatedly but the security team collects only VM infrastructure metrics and lacks container and audit diagnostics; this control addresses a different failure condition.

Question 673

An Azure security engineer investigates the following incident: A team protects a resource through group-based RBAC but all members keep standing membership in the privileged group despite an on-demand access requirement. Which result confirms the relevant security control is effective?

  1. Security receives and investigates alerts for new permanent privileged assignments, reducing unnecessary standing admins.
  2. High-risk sign-ins receive the configured stronger response while ordinary travel follows approved policy.
  3. An engineer gains temporary group-derived resource access only during an approved activation.
  4. A controlled risky sign-in is blocked in enforced mode and appears with the applied policy result.

Explanation

Correct Answer

C:

This validates the specific control for pim for groups role elevation: Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. The associated corrective action is: Configure PIM for Groups with eligible membership and required activation controls where supported. Testing a different component would not establish this result.

Incorrect Answers

A:

Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. “Review permanent assignments and configure PIM alerts, justification and eligible access where feasible” would address that alternative cause, not the condition in this question: permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles.

B:

“Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed” responds to this separate finding: network location alone does not substitute for appropriate risk signals and risk-based access controls. This question instead needs “Configure PIM for Groups with eligible membership and required activation controls where supported”, so the alternative does not meet the stated condition.

D:

A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. “Review report-only results, correct exclusions and switch the approved policy to On for enforcement” applies to that separate problem. The observed case is a team protects a resource through group-based RBAC but all members keep standing membership in the privileged group despite an on-demand access requirement; choosing this alternative would address the wrong failure mode.

Question 674

A platform security assessment reveals this issue: An administrator enables the Key Vault Azure RBAC permission model but assumes previously configured vault access policies still grant secret read operations. What technical cause best accounts for the described behavior?

  1. Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active.
  2. The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect.
  3. Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry.
  4. An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration.

Explanation

Correct Answer

A:

The described technical condition is: Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active. The appropriate corrective action is: Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model. Confirm with: The approved identity retrieves only authorized secrets and a formerly permitted but unassigned identity is denied.

Incorrect Answers

B:

The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect. “Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type” would address that alternative cause, not the condition in this question: key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active.

C:

“Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications” responds to this separate finding: secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. This question instead needs “Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model”, so the alternative does not meet the stated condition.

D:

An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. “Set time-limited exemptions with accountable justification and remove or renew each only after security review” applies to that separate problem. The observed case is an administrator enables the Key Vault Azure RBAC permission model but assumes previously configured vault access policies still grant secret read operations; choosing this alternative would address the wrong failure mode.

Question 675

A platform security assessment reveals this issue: A global web service must block traffic from a prohibited geography, but the team configures only a regional backend NSG that lacks end-user geographic context. Which recurring validation best protects against the observed problem?

  1. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  2. Test regional edge WAF policies with representative client source conditions and observe false positives.
  3. Track custom domain certificate validity and binding renewal before expiration.
  4. Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services.

Explanation

Correct Answer

B:

This guardrail addresses front door waf geographic access controls: The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. The prevention measure is: Test regional edge WAF policies with representative client source conditions and observe false positives. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. “Test TLS protocol settings and certificate expiry after changes to public application endpoints” would address that alternative cause, not the condition in this question: the access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge.

C:

“Track custom domain certificate validity and binding renewal before expiration” responds to this separate finding: the custom domain has no correct TLS certificate binding for the expected host name. This question instead needs “Test regional edge WAF policies with representative client source conditions and observe false positives”, so the alternative does not meet the stated condition.

D:

The function hosting plan and network integration/DNS are not configured for the required private destination. “Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services” applies to that separate problem. The observed case is a global web service must block traffic from a prohibited geography, but the team configures only a regional backend NSG that lacks end-user geographic context; choosing this alternative would address the wrong failure mode.

Question 676

A platform security assessment reveals this issue: A spoke subnet unexpectedly learns routes from an attached virtual network gateway and uses an unwanted path despite a locally maintained route table. What is the most appropriate corrective step?

  1. Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls.
  2. Disable BGP route propagation on the relevant route table where the approved design requires static steering.
  3. Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria.
  4. Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path.

Explanation

Correct Answer

B:

The cause is: Gateway route propagation remains enabled for the route table and influences effective routing selections. The appropriate change is: Disable BGP route propagation on the relevant route table where the approved design requires static steering. Verify it with this outcome: Effective route inspection shows only intended propagated and explicit routes for the target subnet.

Incorrect Answers

A:

This action concerns default outbound network access control, where Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. The reported incident instead involves Gateway route propagation remains enabled for the route table and influences effective routing selections.

C:

This action concerns application security group membership scoping, where An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. The corrective response here is “Disable BGP route propagation on the relevant route table where the approved design requires static steering”; this alternative does not provide that response.

D:

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 stem reports a spoke subnet unexpectedly learns routes from an attached virtual network gateway and uses an unwanted path despite a locally maintained route table; this control addresses a different failure condition.

Question 677

While validating an Azure workload, the security team finds: A regulated storage account requires identity-based access, but data clients still authenticate using Shared Key and legacy SAS tokens. Which configuration change most directly resolves this problem?

  1. Configure customer-managed key encryption and grant the storage account identity the required key permissions.
  2. Configure the appropriate time-based immutability policy or legal hold for the protected container.
  3. Assign Storage Blob Data Reader to the application identity at the appropriate container scope.
  4. Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS.

Explanation

Correct Answer

D:

The cause is: The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. The appropriate change is: Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS. Verify it with this outcome: Shared Key requests are rejected while approved identity-based blob operations succeed.

Incorrect Answers

A:

This action concerns storage customer managed key in key vault, where Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. The reported incident instead involves The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control.

B:

This action concerns blob immutable storage legal hold, where Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. The corrective response here is “Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS”; this alternative does not provide that response.

C:

This action concerns blob storage data rbac, where Management-plane storage Contributor does not necessarily include blob data read DataActions. The stem reports a regulated storage account requires identity-based access, but data clients still authenticate using Shared Key and legacy SAS tokens; this control addresses a different failure condition.

Question 678

During a cloud security review, the operations team observes: A sensitive browser session persists for many days without a fresh sign-in despite a policy requiring shorter high-risk session exposure. What should the engineer implement first to address the weakness?

  1. Configure a justified sign-in frequency session control for the appropriate protected application.
  2. Extend the policy to the correct external-user categories and trust settings using supported B2B controls.
  3. Include the intended enterprise application or cloud resource in the Conditional Access assignment.
  4. Apply the documented emergency access exclusion and protect recovery identities with independent safeguards.

Explanation

Correct Answer

A:

The cause is: The relevant Conditional Access session control lacks the required sign-in frequency and session behavior. The appropriate change is: Configure a justified sign-in frequency session control for the appropriate protected application. Verify it with this outcome: A controlled session prompts for renewed authentication at the configured interval within product limitations.

Incorrect Answers

B:

This action concerns guest user conditional access coverage, where The targeted policy does not include the guest or external user population for the protected application. The reported incident instead involves The relevant Conditional Access session control lacks the required sign-in frequency and session behavior.

C:

This action concerns conditional access cloud app targeting, where The target cloud application selection is wrong and policy enforcement does not cover the actual resource. The corrective response here is “Configure a justified sign-in frequency session control for the appropriate protected application”; this alternative does not provide that response.

D:

This action concerns emergency account conditional access exclusion, where The policy targets protected emergency principals without the approved tightly controlled recovery exclusions. The stem reports a sensitive browser session persists for many days without a fresh sign-in despite a policy requiring shorter high-risk session exposure; this control addresses a different failure condition.

Question 679

A regulated Azure tenant has this security condition: A web service requires encryption to backend instances, but an Application Gateway listener terminates HTTPS and forwards plaintext HTTP downstream. Which outcome most clearly verifies that the issue is resolved?

  1. The managed instance deploys in the intended delegated subnet and responds only to permitted connections.
  2. Application Gateway reports healthy targets and completes an end-to-end request to the application.
  3. A test flow negotiates TLS to both gateway and backend without exposing plaintext on the internal leg.
  4. Only authorized internal clients reach hosted apps, and operations can verify the isolated hosting path.

Explanation

Correct Answer

C:

This validates the specific control for application gateway end to end tls: Backend HTTP settings do not enforce the required HTTPS connection to backend servers. The associated corrective action is: Configure backend HTTPS with appropriate certificate trust and listener/backend settings. Testing a different component would not establish this result.

Incorrect Answers

A:

SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. “Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls” would address that alternative cause, not the condition in this question: backend HTTP settings do not enforce the required HTTPS connection to backend servers.

B:

“Correct the custom health probe to match the actual service endpoint and backend settings” responds to this separate finding: the backend health probe is failing due to its configured request host, path or expected response rather than VM availability. This question instead needs “Configure backend HTTPS with appropriate certificate trust and listener/backend settings”, so the alternative does not meet the stated condition.

D:

The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. “Deploy a supported internal App Service Environment and configure ingress and outbound network controls” applies to that separate problem. The observed case is a web service requires encryption to backend instances, but an Application Gateway listener terminates HTTPS and forwards plaintext HTTP downstream; choosing this alternative would address the wrong failure mode.

Question 680

A Microsoft Azure administrator receives this requirement: A regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints. Which operating control most directly reduces this recurring risk?

  1. Require residual-risk signoff and evidence of compensating controls before closing high-severity posture exceptions.
  2. Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes.
  3. Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy.
  4. Continuously audit subscription plan coverage after creating or moving subscriptions.

Explanation

Correct Answer

C:

This guardrail addresses defender for cloud cloud security benchmark: A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. The prevention measure is: Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. “Require residual-risk signoff and evidence of compensating controls before closing high-severity posture exceptions” would address that alternative cause, not the condition in this question: a cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation.

B:

“Continuously reconcile external attack surface discovery with mergers, new domains and cloud service changes” responds to this separate finding: internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. This question instead needs “Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy”, so the alternative does not meet the stated condition.

D:

Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. “Continuously audit subscription plan coverage after creating or moving subscriptions” applies to that separate problem. The observed case is a regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints; choosing this alternative would address the wrong failure mode.