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 99

Question 980

A regulated Azure tenant has this security condition: Azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week. Which configuration change most directly resolves this problem?

  1. Inspect effective routes and run Network Watcher next hop against the intended destination IP.
  2. Associate intended eligible VNets with the correct plan and validate protection settings.
  3. Configure relevant firewall diagnostic categories and secure retention for rule and threat events.
  4. Run Network Watcher IP flow verify with the test source, destination, direction and port.

Explanation

Correct Answer

C:

The cause is: Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The appropriate change is: Configure relevant firewall diagnostic categories and secure retention for rule and threat events. Verify it with this outcome: The security team queries the required firewall rule-match records for a controlled test flow.

Incorrect Answers

A:

This action concerns network watcher next hop diagnosis, where A user-defined or propagated route controls the next hop independently of NSG allow decisions. The reported incident instead involves Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination.

B:

This action concerns ddos plan coverage and ownership, where Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. The corrective response here is “Configure relevant firewall diagnostic categories and secure retention for rule and threat events”; this alternative does not provide that response.

D:

This action concerns network watcher ip flow verification, where The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. The stem reports azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week; this control addresses a different failure condition.

Question 981

A regulated Azure tenant has this security condition: An Azure Policy assignment with Modify effect adds a cost-center tag to new storage accounts, but hundreds of earlier accounts remain untagged. Which safeguard would best prevent this issue from recurring?

  1. Review immutability settings and approval gates before changing backup security or recovery policies.
  2. Include existing-resource remediation and identity permissions in Azure Policy deployment acceptance criteria.
  3. Audit Key Vault public exposure and the exact network dependencies of each application after changes.
  4. Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan.

Explanation

Correct Answer

B:

This guardrail addresses 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 prevention measure is: Include existing-resource remediation and identity permissions in Azure Policy deployment acceptance criteria. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. “Review immutability settings and approval gates before changing backup security or recovery policies” 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.

C:

“Audit Key Vault public exposure and the exact network dependencies of each application after changes” 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 “Include existing-resource remediation and identity permissions in Azure Policy deployment acceptance criteria”, so the alternative does not meet the stated condition.

D:

Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. “Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan” 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 982

A platform security assessment reveals this issue: Several workloads show a recommendation to close Internet-exposed management ports, but the security team wants to suppress the recommendation rather than inspect actual reachable paths. What observation is the strongest validation evidence?

  1. The assessment clearly distinguishes justified exceptions from technical fixes and tracks residual risk ownership.
  2. Public SSH and RDP access is denied from unauthorized networks and the security assessment updates accordingly.
  3. The new GCP projects are present in Defender inventory and receive applicable posture findings.
  4. Selected connected AWS instances appear in the correct Defender plan with expected scanning and alert coverage.

Explanation

Correct Answer

B:

This validates the specific control for defender for cloud recommendation root-cause assessment: A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. The associated corrective action is: Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives. Testing a different component would not establish this result.

Incorrect Answers

A:

An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. “Validate exemption justification, owner, expiry and business controls or actually remediate the resource” would address that alternative cause, not the condition in this question: a recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration.

C:

“Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects” responds to this separate finding: a connector's project enrollment or organization-level integration scope may omit newly created GCP projects. This question instead needs “Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives”, so the alternative does not meet the stated condition.

D:

Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. “Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances” applies to that separate problem. The observed case is several workloads show a recommendation to close Internet-exposed management ports, but the security team wants to suppress the recommendation rather than inspect actual reachable paths; choosing this alternative would address the wrong failure mode.

Question 983

A platform security assessment reveals this issue: A cloud security analyst concentrates on low-impact recommendations while a highly weighted open-management-port finding remains unresolved. After remediation, which test result best proves the intended change?

  1. Every governed subscription reports the expected Defender workload plan state and billed resource scope.
  2. Previously hidden resources are included and their vulnerability or configuration status can be assessed.
  3. The new GCP projects are present in Defender inventory and receive applicable posture findings.
  4. The targeted risky configuration is remediated and the secure-score control reflects an appropriate improvement on reevaluation.

Explanation

Correct Answer

D:

This validates the specific control for defender for cloud secure score priority: Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. The associated corrective action is: Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: secure score is based on security-control recommendations and affected resources, not just a raw count of findings.

B:

“Clear or expand the inventory filter and verify the evaluated scope against resource ownership records” responds to this separate finding: inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. This question instead needs “Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap”, so the alternative does not meet the stated condition.

C:

A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. “Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects” applies to that separate problem. The observed case is a cloud security analyst concentrates on low-impact recommendations while a highly weighted open-management-port finding remains unresolved; choosing this alternative would address the wrong failure mode.

Question 984

During a cloud security review, the operations team observes: An Azure Function calls a storage account using a client secret embedded in configuration, and secret rotation regularly breaks the application. Which underlying control gap is responsible for the issue?

  1. The application's registered redirect URI does not match the callback URI used in the authorization request.
  2. A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal.
  3. The workload is not using its platform-managed identity and therefore depends on long-lived application secrets.
  4. The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy.

Explanation

Correct Answer

C:

The described technical condition is: The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. The appropriate corrective action is: Enable an appropriate managed identity and grant narrowly scoped storage data authorization to that identity. Confirm with: The function uses token-based access without a stored application client secret and writes only permitted blobs.

Incorrect Answers

A:

The application's registered redirect URI does not match the callback URI used in the authorization request. “Register the exact approved redirect URI and update the app client flow accordingly” would address that alternative cause, not the condition in this question: the workload is not using its platform-managed identity and therefore depends on long-lived application secrets.

B:

“Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal” responds to this separate finding: a system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. This question instead needs “Enable an appropriate managed identity and grant narrowly scoped storage data authorization to that identity”, so the alternative does not meet the stated condition.

D:

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 an Azure Function calls a storage account using a client secret embedded in configuration, and secret rotation regularly breaks the application; choosing this alternative would address the wrong failure mode.

Question 985

While validating an Azure workload, the security team finds: An administrator enables password-based SSH for Internet reachable Linux VMs and never rotates the shared password after personnel departures. Which result confirms the relevant security control is effective?

  1. Only approved private keys authenticate to the private Linux VM and shared password login is unavailable.
  2. The pod obtains a short-lived token and reads only the approved secret without stored client secrets.
  3. A deletion attempt cannot immediately eradicate protected backup recovery points and recovery remains possible.
  4. An unauthorized operator cannot generate snapshot access while recovery administrators retain documented access.

Explanation

Correct Answer

A:

This validates the specific control for linux ssh key management: Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. The associated corrective action is: Use controlled SSH public-key authentication and restrict access through Bastion or approved private management. Testing a different component would not establish this result.

Incorrect Answers

B:

The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. “Configure workload identity on the service account and scoped access to the target Key Vault” would address that alternative cause, not the condition in this question: shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management.

C:

“Enable supported vault soft delete and enhanced protection settings including immutable backup where required” responds to this separate finding: backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. This question instead needs “Use controlled SSH public-key authentication and restrict access through Bastion or approved private management”, so the alternative does not meet the stated condition.

D:

Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. “Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals” applies to that separate problem. The observed case is an administrator enables password-based SSH for Internet reachable Linux VMs and never rotates the shared password after personnel departures; choosing this alternative would address the wrong failure mode.

Question 986

An Azure security engineer investigates the following incident: A regulated Azure SQL database must encrypt database files and backups at rest, but administrators focus only on the client TLS connection. Which outcome most clearly verifies that the issue is resolved?

  1. Secrets are protected in the intended storage path and only approved workload identities can retrieve values.
  2. The database reports TDE enabled and encrypted at-rest backups while client connections remain supported.
  3. Sensitive columns remain encrypted to the database engine while authorized clients decrypt needed values.
  4. The client connects only to the legitimate database endpoint and rejects an untrusted test certificate.

Explanation

Correct Answer

B:

This validates the specific control for transparent data encryption at rest: TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. The associated corrective action is: Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration. Testing a different component would not establish this result.

Incorrect Answers

A:

Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. “Enable supported secret encryption and external secret management using Key Vault where required” would address that alternative cause, not the condition in this question: tLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.

C:

“Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients” responds to this separate finding: tDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. This question instead needs “Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration”, so the alternative does not meet the stated condition.

D:

Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. “Configure supported SQL driver encryption with certificate chain and hostname validation enabled” applies to that separate problem. The observed case is a regulated Azure SQL database must encrypt database files and backups at rest, but administrators focus only on the client TLS connection; choosing this alternative would address the wrong failure mode.

Question 987

An Azure security engineer investigates the following incident: An AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current. What governance practice would best prevent the same failure?

  1. Test AKS diagnostic collection coverage after cluster upgrades and namespace changes.
  2. Review environment variables and container logging for unintended credential exposure.
  3. Include node operating system image lifecycle in AKS maintenance plans.
  4. Prefer identity-based secret retrieval and recertify permissions for each container revision.

Explanation

Correct Answer

C:

This guardrail addresses aks node image upgrade hygiene: Control-plane version compliance is distinct from node OS image and node pool security patch state. The prevention measure is: Include node operating system image lifecycle in AKS maintenance plans. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. “Test AKS diagnostic collection coverage after cluster upgrades and namespace changes” would address that alternative cause, not the condition in this question: control-plane version compliance is distinct from node OS image and node pool security patch state.

B:

“Review environment variables and container logging for unintended credential exposure” responds to this separate finding: the container group relies on a long-lived shared credential rather than supported managed identity authorization. This question instead needs “Include node operating system image lifecycle in AKS maintenance plans”, so the alternative does not meet the stated condition.

D:

The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. “Prefer identity-based secret retrieval and recertify permissions for each container revision” applies to that separate problem. The observed case is an AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current; choosing this alternative would address the wrong failure mode.

Question 988

The cloud operations team reviews the following risk: A spoke sends DNS to an external resolver directly although a central Azure Firewall DNS proxy was required for reliable FQDN policy evaluation. Which result confirms the relevant security control is effective?

  1. Effective route inspection confirms protected traffic reaches the firewall and Internet breakout follows intent.
  2. Spoke queries traverse the DNS proxy and the service's allowed FQDN policy operates consistently.
  3. The application matches its intended permitted rule without weakening the inherited organizational baseline.
  4. BGP sessions establish and only approved prefixes appear on both sides of the encrypted connection.

Explanation

Correct Answer

B:

This validates the specific control for firewall dns proxy routing: Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. The associated corrective action is: Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address. Testing a different component would not establish this result.

Incorrect Answers

A:

The secured virtual hub's routing intent for private and Internet traffic is missing or misconfigured. “Configure the supported Virtual WAN routing intent and policy for the required traffic categories” would address that alternative cause, not the condition in this question: spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently.

C:

“Review inherited policy evaluation and adjust approved parent or child rule design with central authorization” responds to this separate finding: azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. This question instead needs “Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address”, so the alternative does not meet the stated condition.

D:

The encrypted tunnel is operational while BGP neighbor addresses, ASN settings or routing sessions remain incorrect. “Correct the approved BGP settings on the VPN gateway and on-premises peer and inspect neighbor state” applies to that separate problem. The observed case is a spoke sends DNS to an external resolver directly although a central Azure Firewall DNS proxy was required for reliable FQDN policy evaluation; choosing this alternative would address the wrong failure mode.

Question 989

A production Azure security implementation shows this failure: A data team must control its own encryption key lifecycle, but storage uses only Microsoft-managed encryption keys and lacks access to the chosen vault. What observation is the strongest validation evidence?

  1. A controlled deletion can be reversed within retention without rebuilding the entire account.
  2. The report job retrieves allowed blobs via Entra tokens and cannot change unrelated storage settings.
  3. The storage account reports infrastructure encryption enabled in addition to regular service-side encryption.
  4. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.

Explanation

Correct Answer

D:

This validates the specific control for storage customer managed key in key vault: Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. The associated corrective action is: Configure customer-managed key encryption and grant the storage account identity the required key permissions. Testing a different component would not establish this result.

Incorrect Answers

A:

The storage account lacks blob soft delete retention to recover recently removed objects. “Enable blob soft delete with an appropriate retention period and verify the restore process” would address that alternative cause, not the condition in this question: storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account.

B:

“Assign Storage Blob Data Reader to the application identity at the appropriate container scope” responds to this separate finding: management-plane storage Contributor does not necessarily include blob data read DataActions. This question instead needs “Configure customer-managed key encryption and grant the storage account identity the required key permissions”, so the alternative does not meet the stated condition.

C:

The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. “Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage” applies to that separate problem. The observed case is a data team must control its own encryption key lifecycle, but storage uses only Microsoft-managed encryption keys and lacks access to the chosen vault; choosing this alternative would address the wrong failure mode.

Question 990

An Azure security engineer investigates the following incident: An auditor requests a bespoke compliance requirement absent from built-in regulatory mappings, and the governance team attempts to edit a built-in standard directly. Which condition most directly explains the failure?

  1. Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version.
  2. Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry.
  3. Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment.
  4. Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period.

Explanation

Correct Answer

C:

The described technical condition is: Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. The appropriate corrective action is: Create and test a supported custom Azure Policy definition or initiative and attach it to the relevant regulatory assessment process. Confirm with: The custom control produces explainable pass or fail evidence mapped to the institution's actual documented requirement.

Incorrect Answers

A:

Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. “Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint” would address that alternative cause, not the condition in this question: built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment.

B:

“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 “Create and test a supported custom Azure Policy definition or initiative and attach it to the relevant regulatory assessment process”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an auditor requests a bespoke compliance requirement absent from built-in regulatory mappings, and the governance team attempts to edit a built-in standard directly; choosing this alternative would address the wrong failure mode.