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 58

Question 570

A platform security assessment reveals this issue: An AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current. What is the most appropriate corrective step?

  1. Configure a secure Container Apps secret reference or managed identity for database access.
  2. Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components.
  3. Attach a supported managed identity and grant the intended Key Vault secret-read role.
  4. Schedule supported AKS node image updates and verify rollout health across node pools.

Explanation

Correct Answer

D:

The cause is: Control-plane version compliance is distinct from node OS image and node pool security patch state. The appropriate change is: Schedule supported AKS node image updates and verify rollout health across node pools. Verify it with this outcome: The node pools report patched images and workloads continue meeting availability requirements.

Incorrect Answers

A:

This action concerns container apps secret references, where Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. The reported incident instead involves Control-plane version compliance is distinct from node OS image and node pool security patch state.

B:

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 “Schedule supported AKS node image updates and verify rollout health across node pools”; this alternative does not provide that response.

C:

This action concerns container apps managed identity auth, where The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The stem reports an AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current; this control addresses a different failure condition.

Question 571

While validating an Azure workload, the security team finds: A payment system uses an Azure SQL logical server over a public address although its design requires only approved workload subnets to reach database traffic. What governance practice would best prevent the same failure?

  1. Review masking policies alongside direct data export and privileged bypass paths.
  2. Audit Kubernetes Secret permissions and encryption settings as part of cluster hardening.
  3. Audit TDE status and key rotation separately from transport TLS compliance.
  4. Validate SQL private connectivity and public network restrictions during application onboarding.

Explanation

Correct Answer

D:

This guardrail addresses azure sql private endpoint dns and public disable: The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. The prevention measure is: Validate SQL private connectivity and public network restrictions during application onboarding. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. “Review masking policies alongside direct data export and privileged bypass paths” would address that alternative cause, not the condition in this question: the SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction.

B:

“Audit Kubernetes Secret permissions and encryption settings as part of cluster hardening” responds to this separate finding: kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. This question instead needs “Validate SQL private connectivity and public network restrictions during application onboarding”, so the alternative does not meet the stated condition.

C:

TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Audit TDE status and key rotation separately from transport TLS compliance” applies to that separate problem. The observed case is a payment system uses an Azure SQL logical server over a public address although its design requires only approved workload subnets to reach database traffic; choosing this alternative would address the wrong failure mode.

Question 572

While validating an Azure workload, the security team finds: A design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint. Which remediation best addresses the specific issue?

  1. Configure the correct privatelink DNS zone record and link the client VNet to the zone.
  2. Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval.
  3. Configure regional App Service VNet integration and the necessary subnet routing and DNS.
  4. Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service.

Explanation

Correct Answer

D:

The cause is: Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. The appropriate change is: Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service. Verify it with this outcome: The service resolves to a VNet private address and only permitted private clients connect.

Incorrect Answers

A:

This action concerns private dns zone linking for endpoint, where The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. The reported incident instead involves Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.

B:

This action concerns private link service provider design, where The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. The corrective response here is “Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service”; this alternative does not provide that response.

C:

This action concerns app service vnet integration outbound path, where App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. The stem reports a design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint; this control addresses a different failure condition.

Question 573

A platform security assessment reveals this issue: A high-risk portal role accepts SMS-based MFA even though policy explicitly requires phishing-resistant authentication for privileged operations. What should the engineer implement first to address the weakness?

  1. Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods.
  2. Add an appropriately scoped Conditional Access grant control requiring a compliant device, with emergency exceptions.
  3. Select the required combination of grant controls and confirm the intended AND behavior.
  4. Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification.

Explanation

Correct Answer

A:

The cause is: The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. The appropriate change is: Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods. Verify it with this outcome: An SMS-only sign-in fails the privileged requirement while an authorized phishing-resistant method succeeds.

Incorrect Answers

B:

This action concerns require compliant device condition, where The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. The reported incident instead involves The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength.

C:

This action concerns conditional access multiple grant controls, where The grant control operator allows any selected requirement rather than requiring all specified requirements. The corrective response here is “Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods”; this alternative does not provide that response.

D:

This action concerns fido2 passkey enrollment governance, where Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. The stem reports a high-risk portal role accepts SMS-based MFA even though policy explicitly requires phishing-resistant authentication for privileged operations; this control addresses a different failure condition.

Question 574

A regulated Azure tenant has this security condition: A network team adds an outbound deny rule and assumes it will immediately terminate every existing TCP session previously allowed through the subnet NSG. Which configuration change most directly resolves this problem?

  1. Disable BGP route propagation on the relevant route table where the approved design requires static steering.
  2. Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria.
  3. Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope.
  4. Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes.

Explanation

Correct Answer

D:

The cause is: NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. The appropriate change is: Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes. Verify it with this outcome: New prohibited connections fail and the team documents disposition of any previously established flows.

Incorrect Answers

A:

This action concerns BGP gateway route propagation control, where Gateway route propagation remains enabled for the route table and influences effective routing selections. The reported incident instead involves NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes.

B:

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 “Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes”; this alternative does not provide that response.

C:

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 network team adds an outbound deny rule and assumes it will immediately terminate every existing TCP session previously allowed through the subnet NSG; this control addresses a different failure condition.

Question 575

During a cloud security review, the operations team observes: A storage account must be accessed only from an approved subnet, but its public endpoint remains open and traffic uses public IP connectivity. Which operating control most directly reduces this recurring risk?

  1. Treat private transport and payload encryption as separate security controls in architecture reviews.
  2. Inventory subnet service endpoint configuration and service firewall allowances together.
  3. Test both private-resolution success and public-path denial whenever a new Private Endpoint is added.
  4. Check supported private endpoint network policy settings before relying on subnet inspection rules.

Explanation

Correct Answer

C:

This guardrail addresses private endpoint public exposure reduction: A private endpoint has not been configured or public network access has not been restricted for the resource. The prevention measure is: Test both private-resolution success and public-path denial whenever a new Private Endpoint is added. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. “Treat private transport and payload encryption as separate security controls in architecture reviews” would address that alternative cause, not the condition in this question: a private endpoint has not been configured or public network access has not been restricted for the resource.

B:

“Inventory subnet service endpoint configuration and service firewall allowances together” responds to this separate finding: the required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. This question instead needs “Test both private-resolution success and public-path denial whenever a new Private Endpoint is added”, so the alternative does not meet the stated condition.

D:

Private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. “Check supported private endpoint network policy settings before relying on subnet inspection rules” applies to that separate problem. The observed case is a storage account must be accessed only from an approved subnet, but its public endpoint remains open and traffic uses public IP connectivity; choosing this alternative would address the wrong failure mode.

Question 576

During a cloud security review, the operations team observes: An audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions. What should the engineer implement first to address the weakness?

  1. Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized.
  2. Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment.
  3. Assign the approved read-only role at a suitable management group with the intended child subscription coverage.
  4. Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures.

Explanation

Correct Answer

A:

The cause is: The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. The appropriate change is: Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized. Verify it with this outcome: An authorized test modifies the intended tags while the operator retains no additional administration privileges.

Incorrect Answers

B:

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 reported incident instead involves The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.

C:

This action concerns management group security assignment, where Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The corrective response here is “Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized”; this alternative does not provide that response.

D:

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 stem reports an audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions; this control addresses a different failure condition.

Question 577

The cloud operations team reviews the following risk: An Azure Policy assignment with Modify effect adds a cost-center tag to new storage accounts, but hundreds of earlier accounts remain untagged. Which outcome most clearly verifies that the issue is resolved?

  1. After a controlled rotation the service remains encrypted and uses an appropriate authorized key version without downtime.
  2. The resource is compliant and unauthorized blob reads are independently denied by the appropriate storage permissions.
  3. The custom control produces explainable pass or fail evidence mapped to the institution's actual documented requirement.
  4. Previously untagged storage accounts receive the approved tag and are reevaluated as compliant.

Explanation

Correct Answer

D:

This validates the specific control for azure policy modify remediation for existing tags: Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. The associated corrective action is: Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions.

B:

“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 “Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition”, so the alternative does not meet the stated condition.

C:

Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. “Create and test a supported custom Azure Policy definition or initiative and attach it to the relevant regulatory assessment process” applies to that separate problem. The observed case is an Azure Policy assignment with Modify effect adds a cost-center tag to new storage accounts, but hundreds of earlier accounts remain untagged; choosing this alternative would address the wrong failure mode.

Question 578

An Azure security engineer investigates the following incident: Security requires resource diagnostic logs in Log Analytics, and an assigned DeployIfNotExists policy reports noncompliance without creating settings on existing resources. Which remediation best addresses the specific issue?

  1. Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition.
  2. Grant only the necessary deployment role to the assignment identity and run the authorized remediation task.
  3. Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers.
  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 DeployIfNotExists assignment evaluates related resources but needs appropriate assignment identity permissions and remediation for existing assets. The appropriate change is: Grant only the necessary deployment role to the assignment identity and run the authorized remediation task. Verify it with this outcome: The target resources have the expected diagnostic settings and logs begin arriving in the approved workspace.

Incorrect Answers

A:

This action concerns azure policy modify remediation for existing tags, where Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. The reported incident instead involves A DeployIfNotExists assignment evaluates related resources but needs appropriate assignment identity permissions and remediation for existing assets.

C:

This action concerns backup multiuser authorization resource guard, where Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. The corrective response here is “Grant only the necessary deployment role to the assignment identity and run the authorized remediation task”; 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 security requires resource diagnostic logs in Log Analytics, and an assigned DeployIfNotExists policy reports noncompliance without creating settings on existing resources; this control addresses a different failure condition.

Question 579

A production Azure security implementation shows this failure: A security team enables per-user MFA for administrators but a sensitive Azure app remains accessible in a way that does not consistently apply context-aware authentication requirements. What is the most appropriate corrective step?

  1. Configure approval and valid approvers for activation of the sensitive Azure resource role.
  2. Use supported Microsoft Entra sign-in risk conditions with justified MFA or blocking actions where licensed.
  3. Review permanent assignments and configure PIM alerts, justification and eligible access where feasible.
  4. Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app.

Explanation

Correct Answer

D:

The cause is: Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access. The appropriate change is: Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app. Verify it with this outcome: Targeted users meet the required control under the specified access conditions, and excluded accounts follow documented exceptions.

Incorrect Answers

A:

This action concerns pim role activation approval, where The PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. The reported incident instead involves Per-user MFA alone does not express all resource, location, sign-in risk and device conditions available in Conditional Access.

B:

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 corrective response here is “Create an appropriately scoped Conditional Access policy requiring MFA or authentication strength for the sensitive app”; this alternative does not provide that response.

C:

This action concerns pim permanent global administrator alert, where Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. The stem reports a security team enables per-user MFA for administrators but a sensitive Azure app remains accessible in a way that does not consistently apply context-aware authentication requirements; this control addresses a different failure condition.

Question 580

A platform security assessment reveals this issue: A security team enabled only the basic server plan but expects file integrity monitoring and advanced vulnerability capabilities available in a different plan tier. Which operating control most directly reduces this recurring risk?

  1. Require evidence-based alert closure with escalation for unresolved high-severity cloud threats.
  2. Check Arc connectivity and protection plan deployment independently for each non-Azure server group.
  3. Review plan feature availability and licensing before writing server threat protection acceptance criteria.
  4. Continuously combine vulnerability severity with external reachability and asset importance in remediation planning.

Explanation

Correct Answer

C:

This guardrail addresses microsoft defender for servers plan 2 eligibility: Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. The prevention measure is: Review plan feature availability and licensing before writing server threat protection acceptance criteria. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. “Require evidence-based alert closure with escalation for unresolved high-severity cloud threats” would address that alternative cause, not the condition in this question: defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements.

B:

“Check Arc connectivity and protection plan deployment independently for each non-Azure server group” responds to this separate finding: azure Arc inventory presence alone does not guarantee that applicable Defender for Servers protection and monitoring dependencies are enabled. This question instead needs “Review plan feature availability and licensing before writing server threat protection acceptance criteria”, so the alternative does not meet the stated condition.

D:

Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. “Continuously combine vulnerability severity with external reachability and asset importance in remediation planning” applies to that separate problem. The observed case is a security team enabled only the basic server plan but expects file integrity monitoring and advanced vulnerability capabilities available in a different plan tier; choosing this alternative would address the wrong failure mode.