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 7

Question 60

A Microsoft Azure administrator receives this requirement: An AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured. What technical cause best accounts for the described behavior?

  1. The API gateway has not enforced the required mutual TLS certificate validation for partner clients.
  2. The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes.
  3. Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access.
  4. API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy.

Explanation

Correct Answer

C:

The described technical condition is: Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. The appropriate corrective action is: Configure eligible ACR private endpoints and DNS paths for all required registry endpoints. Confirm with: The cluster retrieves approved images using private addresses while public registry access stays disabled.

Incorrect Answers

A:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Configure supported APIM client certificate validation and trusted certificate criteria” would address that alternative cause, not the condition in this question: private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access.

B:

“Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys” responds to this separate finding: the client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. This question instead needs “Configure eligible ACR private endpoints and DNS paths for all required registry endpoints”, so the alternative does not meet the stated condition.

D:

API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. “Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims” applies to that separate problem. The observed case is an AKS cluster cannot pull images after ACR public network access is disabled because registry private DNS and endpoints were not configured; choosing this alternative would address the wrong failure mode.

Question 61

A Microsoft Azure administrator receives this requirement: A corporate branch receives a new public IP range but a Conditional Access policy still trusts the old named location, leading to unexpected access failures. After remediation, which test result best proves the intended change?

  1. A test sign-in with only MFA fails, while one meeting both MFA and device compliance succeeds.
  2. Legitimate branch users match the correct location policy and unrelated public addresses are not trusted.
  3. A controlled session prompts for renewed authentication at the configured interval within product limitations.
  4. A compliant managed workstation can access the app while an unenrolled device is rejected as designed.

Explanation

Correct Answer

B:

This validates the specific control for named location ipv4 range update: The named location definition is stale and no longer reflects current verified branch egress address ranges. The associated corrective action is: Update the trusted named location with validated new egress ranges and test the affected policy conditions. Testing a different component would not establish this result.

Incorrect Answers

A:

The grant control operator allows any selected requirement rather than requiring all specified requirements. “Select the required combination of grant controls and confirm the intended AND behavior” would address that alternative cause, not the condition in this question: the named location definition is stale and no longer reflects current verified branch egress address ranges.

C:

“Configure a justified sign-in frequency session control for the appropriate protected application” responds to this separate finding: the relevant Conditional Access session control lacks the required sign-in frequency and session behavior. This question instead needs “Update the trusted named location with validated new egress ranges and test the affected policy conditions”, so the alternative does not meet the stated condition.

D:

The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. “Add an appropriately scoped Conditional Access grant control requiring a compliant device, with emergency exceptions” applies to that separate problem. The observed case is a corporate branch receives a new public IP range but a Conditional Access policy still trusts the old named location, leading to unexpected access failures; choosing this alternative would address the wrong failure mode.

Question 62

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. Which recurring validation best protects against the observed problem?

  1. Require security scan gates and scoped exceptions for infrastructure-as-code pull requests.
  2. Assess database threat protection plan coverage separately from firewall and SQL audit configuration.
  3. Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly.
  4. Check connector health and ingestion mappings whenever the SOC changes its primary Sentinel workspace.

Explanation

Correct Answer

A:

This guardrail addresses defender for cloud devops iac misconfiguration: Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The prevention measure is: Require security scan gates and scoped exceptions for infrastructure-as-code pull requests. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. “Assess database threat protection plan coverage separately from firewall and SQL audit configuration” 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.

C:

“Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly” 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 “Require security scan gates and scoped exceptions for infrastructure-as-code pull requests”, so the alternative does not meet the stated condition.

D:

Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. “Check connector health and ingestion mappings whenever the SOC changes its primary Sentinel workspace” 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 63

A platform security assessment reveals this issue: A team monitors database firewall access but has no alerting for anomalous SQL injection or suspicious database sign-ins. Which recurring validation best protects against the observed problem?

  1. Assess database threat protection plan coverage separately from firewall and SQL audit configuration.
  2. Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly.
  3. Include App Service protection in onboarding checks for Internet-exposed web applications.
  4. Reconcile repository discovery and connector app permissions after organizational or repository changes.

Explanation

Correct Answer

A:

This guardrail addresses microsoft defender for databases sql coverage: Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. The prevention measure is: Assess database threat protection plan coverage separately from firewall and SQL audit configuration. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. “Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly” would address that alternative cause, not the condition in this question: database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan.

C:

“Include App Service protection in onboarding checks for Internet-exposed web applications” responds to this separate finding: inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. This question instead needs “Assess database threat protection plan coverage separately from firewall and SQL audit configuration”, so the alternative does not meet the stated condition.

D:

DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. “Reconcile repository discovery and connector app permissions after organizational or repository changes” applies to that separate problem. The observed case is a team monitors database firewall access but has no alerting for anomalous SQL injection or suspicious database sign-ins; choosing this alternative would address the wrong failure mode.

Question 64

A production Azure security implementation shows this failure: Two incident automation rules are meant to route high-severity cases to the SOC, but a broad earlier rule marks every incident closed first. After remediation, which test result best proves the intended change?

  1. An authorized six-month historical query retrieves the necessary security events or documents correctly archived data access.
  2. High-severity test incidents reach the correct responder without being prematurely closed.
  3. A controlled test incident causes the approved containment change and produces an auditable action record.
  4. The expected records appear only in approved production destinations and analysts can query them within the retention policy.

Explanation

Correct Answer

B:

This validates the specific control for sentinel automation rule order and stop processing: Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. The associated corrective action is: Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition. Testing a different component would not establish this result.

Incorrect Answers

A:

Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. “Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes” would address that alternative cause, not the condition in this question: automation rule ordering and stopping behavior can prevent more specific rules from executing as intended.

C:

“Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection” responds to this separate finding: playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. This question instead needs “Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition”, so the alternative does not meet the stated condition.

D:

A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters” applies to that separate problem. The observed case is two incident automation rules are meant to route high-severity cases to the SOC, but a broad earlier rule marks every incident closed first; choosing this alternative would address the wrong failure mode.

Question 65

A production Azure security implementation shows this failure: A hub appliance receives packets from a spoke VNet, but forwarding to another spoke fails because peerings were configured only for ordinary direct VNet traffic. What is the most appropriate corrective step?

  1. Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs.
  2. Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope.
  3. Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria.
  4. Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls.

Explanation

Correct Answer

A:

The cause is: The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. The appropriate change is: Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs. Verify it with this outcome: Spoke-to-spoke traffic reaches its destination through the approved hub appliance and no unintended direct path exists.

Incorrect Answers

B:

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 reported incident instead involves The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.

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 “Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs”; this alternative does not provide that response.

D:

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 stem reports a hub appliance receives packets from a spoke VNet, but forwarding to another spoke fails because peerings were configured only for ordinary direct VNet traffic; this control addresses a different failure condition.

Question 66

During a cloud security review, the operations team observes: A security program expects passwordless sign-in but permits only password-and-SMS methods in the authentication methods policy. Which underlying control gap is responsible for the issue?

  1. Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model.
  2. Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.
  3. The app registration client credential has expired and the workload has no safe rotation mechanism.
  4. The workload is not using its platform-managed identity and therefore depends on long-lived application secrets.

Explanation

Correct Answer

B:

The described technical condition is: Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. The appropriate corrective action is: Enable the approved passwordless method and complete secure user registration. Confirm with: A pilot user signs in with the intended passwordless credential under Conditional Access enforcement.

Incorrect Answers

A:

Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. “Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity” would address that alternative cause, not the condition in this question: microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.

C:

“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 “Enable the approved passwordless method and complete secure user registration”, 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 a security program expects passwordless sign-in but permits only password-and-SMS methods in the authentication methods policy; choosing this alternative would address the wrong failure mode.

Question 67

An Azure security engineer investigates the following incident: A GCP organization is connected to Defender for Cloud, but new projects do not appear in security inventory or compliance assessments. Which explanation fits the observed symptoms most closely?

  1. DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope.
  2. Defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans.
  3. A connector's project enrollment or organization-level integration scope may omit newly created GCP projects.
  4. Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption.

Explanation

Correct Answer

C:

The described technical condition is: A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. The appropriate corrective action is: Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects. Confirm with: The new GCP projects are present in Defender inventory and receive applicable posture findings.

Incorrect Answers

A:

DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. “Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope” would address that alternative cause, not the condition in this question: a connector's project enrollment or organization-level integration scope may omit newly created GCP projects.

B:

“Onboard the supported on-premises servers through Azure Arc and configure the relevant Defender for Cloud protection” responds to this separate finding: defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans. This question instead needs “Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects”, 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. “Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope” applies to that separate problem. The observed case is a GCP organization is connected to Defender for Cloud, but new projects do not appear in security inventory or compliance assessments; choosing this alternative would address the wrong failure mode.

Question 68

While validating an Azure workload, the security team finds: A daemon app cannot obtain access tokens after a certificate of service availability window because its application client secret has expired. Which condition most directly explains the failure?

  1. A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal.
  2. No effective user-risk-based identity protection response has been configured for the relevant identities.
  3. The app registration client credential has expired and the workload has no safe rotation mechanism.
  4. Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.

Explanation

Correct Answer

C:

The described technical condition is: The app registration client credential has expired and the workload has no safe rotation mechanism. The appropriate corrective action is: Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation. Confirm with: The daemon acquires tokens again without logging or exposing client credentials.

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 app registration client credential has expired and the workload has no safe rotation mechanism.

B:

“Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate” responds to this separate finding: no effective user-risk-based identity protection response has been configured for the relevant identities. This question instead needs “Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation”, so the alternative does not meet the stated condition.

D:

Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. “Enable the approved passwordless method and complete secure user registration” applies to that separate problem. The observed case is a daemon app cannot obtain access tokens after a certificate of service availability window because its application client secret has expired; choosing this alternative would address the wrong failure mode.

Question 69

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. Which operating control most directly reduces this recurring risk?

  1. Review image digest and vulnerability assessment status in continuous delivery pipelines.
  2. Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates.
  3. Test backup restore and deletion resistance periodically under approved adversarial scenarios.
  4. Use private API endpoint requirements during AKS cluster provisioning and access reviews.

Explanation

Correct Answer

C:

This guardrail addresses recovery services vault soft delete: Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. The prevention measure is: Test backup restore and deletion resistance periodically under approved adversarial scenarios. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. “Review image digest and vulnerability assessment status in continuous delivery pipelines” would address that alternative cause, not the condition in this question: backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault.

B:

“Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates” responds to this separate finding: shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. This question instead needs “Test backup restore and deletion resistance periodically under approved adversarial scenarios”, so the alternative does not meet the stated condition.

D:

The cluster uses a public API server endpoint rather than a supported private AKS cluster design. “Use private API endpoint requirements during AKS cluster provisioning and access reviews” applies to that separate problem. The observed case is an attacker with backup administrative rights tries to delete backup items permanently to defeat future recovery after ransomware deployment; choosing this alternative would address the wrong failure mode.

Question 70

A Microsoft Azure administrator receives this requirement: A SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation. What technical cause best accounts for the described behavior?

  1. The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline.
  2. The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge.
  3. Backend HTTP settings do not enforce the required HTTPS connection to backend servers.
  4. SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.

Explanation

Correct Answer

D:

The described technical condition is: SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The appropriate corrective action is: Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls. Confirm with: The managed instance deploys in the intended delegated subnet and responds only to permitted connections.

Incorrect Answers

A:

The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. “Set the supported minimum TLS version to an approved modern value and verify certificate configuration” would address that alternative cause, not the condition in this question: sQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.

B:

“Create the approved Front Door WAF geographic match rule with a documented action and exclusions” responds to this separate finding: the access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. This question instead needs “Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls”, so the alternative does not meet the stated condition.

C:

Backend HTTP settings do not enforce the required HTTPS connection to backend servers. “Configure backend HTTPS with appropriate certificate trust and listener/backend settings” applies to that separate problem. The observed case is a SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation; choosing this alternative would address the wrong failure mode.