McAfee Secure

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

Microsoft AZ-500 Bundle $44.99

100% Microsoft AZ-500 Guaranteed Success With Testking Training Materials

Get Real AZ-500 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

  • Questions & Answers

    AZ-500 Questions & Answers

    523 Questions & Answers

    The ultimate exam preparation tool, Questions & Answers mirrors the actual AZ-500 exam while allowing you to hone and measure every aspect of your test-taking ability.

  • AZ-500 Video Course

    AZ-500 Training Course

    73 Video Lectures

    AZ-500 Video Course is developed by Microsoft Professionals to help you pass the AZ-500 exam.

    Description

    This course will improve your knowledge and skills required to pass Microsoft Azure Security Technologies exam.
  • Study Guide

    AZ-500 Study Guide

    635 PDF Pages

    Developed by industry experts, this 635-page guide spells out in painstaking detail all of the information you need to ace AZ-500 exam.

Microsoft Azure Security Technologies (AZ-500) Practice Tests

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • Questions & Answers

    Questions & Answers

    523 Questions

    $124.99
  • AZ-500 Video Course

    Training Course

    73 Video Lectures

    $39.99
  • Study Guide

    Study Guide

    635 PDF Pages

    $29.99

Microsoft AZ-500 Practice Test 75

Question 740

Following the issue — A managed instance uses public endpoints although all application clients are confined to a private network. — the team takes this action: Restrict database connectivity using supported private MI networking and approved firewall rules. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review identity source and file ACL compatibility before server migrations.
  2. Require versioning or equivalent recovery controls for mutable critical objects.
  3. Review VM public management exposure and Bastion placement after new subnet deployments.
  4. Check SQL endpoint exposure when introducing new application networks.

Explanation

Correct Answer

D:

The recurring safeguard is: Check SQL endpoint exposure when introducing new application networks. This mitigates the control weakness because: Database exposure should be consistent with private client traffic requirements and platform capabilities. Keep the intervention, Restrict database connectivity using supported private MI networking and approved firewall rules., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Azure Files can use identity-based SMB access when its authentication prerequisites are met. It does not directly prevent the stated recurrence, which concerns: Database exposure should be consistent with private client traffic requirements and platform capabilities. The appropriate guardrail is “Check SQL endpoint exposure when introducing new application networks”.

B:

This safeguard is for the dependency described by: Versioning preserves prior object versions according to configured service capabilities and retention. The continuing risk here is determined by: Database exposure should be consistent with private client traffic requirements and platform capabilities. The targeted safeguard is “Check SQL endpoint exposure when introducing new application networks”.

C:

“Review VM public management exposure and Bastion placement after new subnet deployments” addresses a different recurring failure: Azure Bastion offers controlled browser or client-based access to VMs over private network paths. For the condition in this question, maintain “Check SQL endpoint exposure when introducing new application networks” because database exposure should be consistent with private client traffic requirements and platform capabilities.

Question 741

An Azure security engineer evaluates this fictional situation: An Azure SQL database uses the default encryption protector but the policy mandates organization-owned Key Vault keys. Which response BEST addresses the identified security requirement?

  1. Evaluate a suitable stored access policy where the SAS type supports that mechanism.
  2. Configure the supported customer-managed TDE protector and associated identity permissions.
  3. Enable supported infrastructure encryption for eligible new storage accounts where mandated.
  4. Implement a supported network policy for required namespace and workload segmentation.

Explanation

Correct Answer

B:

The most targeted response is: Configure the supported customer-managed TDE protector and associated identity permissions. The security basis is: TDE key ownership can be changed using supported customer-managed key integration. Verification should show: The database encryption protector shows the approved key and the database remains available.

Incorrect Answers

A:

The offered action, “Evaluate a suitable stored access policy where the SAS type supports that mechanism”, addresses a different dependency: Stored access policies can centralize certain SAS authorization characteristics for revocation. The failure reported here instead follows: TDE key ownership can be changed using supported customer-managed key integration. The targeted response is “Configure the supported customer-managed TDE protector and associated identity permissions”.

C:

“Enable supported infrastructure encryption for eligible new storage accounts where mandated” can be suitable where infrastructure encryption adds an independent layer to Azure Storage encryption at rest. It does not resolve this question’s narrower failure, which follows: TDE key ownership can be changed using supported customer-managed key integration. The relevant action is “Configure the supported customer-managed TDE protector and associated identity permissions”.

D:

The offered action, “Implement a supported network policy for required namespace and workload segmentation”, addresses a different dependency: AKS private control-plane access and pod data-plane policy are separate security boundaries. The failure reported here instead follows: TDE key ownership can be changed using supported customer-managed key integration. The targeted response is “Configure the supported customer-managed TDE protector and associated identity permissions”.

Question 742

In this retired AZ-500 educational case, An Azure SQL database uses the default encryption protector but the policy mandates organization-owned Key Vault keys. Which security principle BEST explains the appropriate response?

  1. A secure capable VM must have applicable firmware and security settings enabled for boot integrity checks.
  2. Blob deletion recovery and container deletion recovery are different storage protections.
  3. TDE key ownership can be changed using supported customer-managed key integration.
  4. Shared access signatures grant delegated storage access according to their scope, permissions and expiry.

Explanation

Correct Answer

C:

The relevant security principle is: TDE key ownership can be changed using supported customer-managed key integration. That is why the action is: Configure the supported customer-managed TDE protector and associated identity permissions. The directly relevant confirmation is: The database encryption protector shows the approved key and the database remains available.

Incorrect Answers

A:

This alternative is valid when a secure capable VM must have applicable firmware and security settings enabled for boot integrity checks. The facts here establish a different controlling reason: TDE key ownership can be changed using supported customer-managed key integration.

B:

“Blob deletion recovery and container deletion recovery are different storage protections” reflects the mechanism: Blob deletion recovery and container deletion recovery are different storage protections. The actual reported symptoms are better explained by: TDE key ownership can be changed using supported customer-managed key integration.

D:

This alternative is valid when shared access signatures grant delegated storage access according to their scope, permissions and expiry. The facts here establish a different controlling reason: TDE key ownership can be changed using supported customer-managed key integration.

Question 743

An Azure security team encounters: An Azure SQL database uses the default encryption protector but the policy mandates organization-owned Key Vault keys. The selected action is: Configure the supported customer-managed TDE protector and associated identity permissions. Which evidence BEST confirms that the security requirement has been met?

  1. A controlled suspicious container activity signal reaches the designated monitoring workflow.
  2. A denied unsolicited RDP attempt becomes permitted only during an approved JIT window.
  3. The storage account properties show infrastructure encryption enabled on the eligible resource.
  4. The database encryption protector shows the approved key and the database remains available.

Explanation

Correct Answer

D:

The most meaningful acceptance evidence is: The database encryption protector shows the approved key and the database remains available. It confirms whether the selected response, Configure the supported customer-managed TDE protector and associated identity permissions., addressed the scenario. The underlying mechanism is: TDE key ownership can be changed using supported customer-managed key integration.

Incorrect Answers

A:

This checks a different technical dependency: Ephemeral containers still create runtime and image exposure independent of short deployment lifetime. The case requires proof of “The database encryption protector shows the approved key and the database remains available”, which establishes the relevant condition: TDE key ownership can be changed using supported customer-managed key integration.

B:

That observation would verify a control associated with: JIT can open constrained management access only for approved requests and durations. It does not establish the needed acceptance outcome. The direct evidence is “The database encryption protector shows the approved key and the database remains available”, testing: TDE key ownership can be changed using supported customer-managed key integration.

C:

“The storage account properties show infrastructure encryption enabled on the eligible resource” could occur while the stated failure remains unresolved. It tests: Infrastructure encryption adds an independent layer to Azure Storage encryption at rest. The required validation instead is “The database encryption protector shows the approved key and the database remains available”, because tDE key ownership can be changed using supported customer-managed key integration.

Question 744

Following the issue — An Azure SQL database uses the default encryption protector but the policy mandates organization-owned Key Vault keys. — the team takes this action: Configure the supported customer-managed TDE protector and associated identity permissions. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review SQL encryption protector settings with cryptographic governance owners.
  2. Monitor key access, rotation and unavailability risk for CMK-backed accounts.
  3. Audit immutability retention and legal hold governance before changing policies.
  4. Test CMK fault scenarios and vault connectivity before enforcing network restrictions.

Explanation

Correct Answer

A:

The recurring safeguard is: Review SQL encryption protector settings with cryptographic governance owners. This mitigates the control weakness because: TDE key ownership can be changed using supported customer-managed key integration. Keep the intervention, Configure the supported customer-managed TDE protector and associated identity permissions., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

“Monitor key access, rotation and unavailability risk for CMK-backed accounts” addresses a different recurring failure: Customer-managed keys provide customer control over key access and lifecycle for supported storage services. For the condition in this question, maintain “Review SQL encryption protector settings with cryptographic governance owners” because tDE key ownership can be changed using supported customer-managed key integration.

C:

That review protects the control associated with: Immutable storage enforces write-once retention characteristics that ordinary backup access does not guarantee. It does not directly prevent the stated recurrence, which concerns: TDE key ownership can be changed using supported customer-managed key integration. The appropriate guardrail is “Review SQL encryption protector settings with cryptographic governance owners”.

D:

This safeguard is for the dependency described by: Storage encryption operations depend on continued authorized access to externally managed key material. The continuing risk here is determined by: TDE key ownership can be changed using supported customer-managed key integration. The targeted safeguard is “Review SQL encryption protector settings with cryptographic governance owners”.

Question 745

An Azure security engineer evaluates this fictional situation: A DBA rotates a customer-managed SQL encryption key without keeping required old key versions accessible for restores. Which response BEST addresses the identified security requirement?

  1. Configure a supported disk encryption set with the required customer-managed key when mandated.
  2. Evaluate a suitable stored access policy where the SAS type supports that mechanism.
  3. Manage key versions and retention according to supported TDE recovery requirements.
  4. Configure an appropriate immutable storage or legal hold policy for the required retention scope.

Explanation

Correct Answer

C:

The most targeted response is: Manage key versions and retention according to supported TDE recovery requirements. The security basis is: Restoring encrypted backups may depend on appropriate historical key material availability. Verification should show: A controlled backup restore succeeds using approved key lifecycle resources.

Incorrect Answers

A:

The alternative focuses on the technical control described by: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models. The present requirement is governed by: Restoring encrypted backups may depend on appropriate historical key material availability. Apply “Manage key versions and retention according to supported TDE recovery requirements” to address that particular cause.

B:

“Evaluate a suitable stored access policy where the SAS type supports that mechanism” can be suitable where stored access policies can centralize certain SAS authorization characteristics for revocation. It does not resolve this question’s narrower failure, which follows: Restoring encrypted backups may depend on appropriate historical key material availability. The relevant action is “Manage key versions and retention according to supported TDE recovery requirements”.

D:

The alternative focuses on the technical control described by: Immutable storage enforces write-once retention characteristics that ordinary backup access does not guarantee. The present requirement is governed by: Restoring encrypted backups may depend on appropriate historical key material availability. Apply “Manage key versions and retention according to supported TDE recovery requirements” to address that particular cause.

Question 746

In this retired AZ-500 educational case, A DBA rotates a customer-managed SQL encryption key without keeping required old key versions accessible for restores. Which security principle BEST explains the appropriate response?

  1. Anonymous blob exposure is controlled by service and container-level settings rather than Azure RBAC alone.
  2. Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.
  3. Container vulnerabilities can exist in workloads even when host nodes are up to date.
  4. Restoring encrypted backups may depend on appropriate historical key material availability.

Explanation

Correct Answer

D:

The relevant security principle is: Restoring encrypted backups may depend on appropriate historical key material availability. That is why the action is: Manage key versions and retention according to supported TDE recovery requirements. The directly relevant confirmation is: A controlled backup restore succeeds using approved key lifecycle resources.

Incorrect Answers

A:

“Anonymous blob exposure is controlled by service and container-level settings rather than Azure RBAC alone” reflects the mechanism: Anonymous blob exposure is controlled by service and container-level settings rather than Azure RBAC alone. The actual reported symptoms are better explained by: Restoring encrypted backups may depend on appropriate historical key material availability.

B:

The offered principle describes: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. The situation in this question instead depends on: Restoring encrypted backups may depend on appropriate historical key material availability. These are different technical conditions.

C:

This alternative is valid when container vulnerabilities can exist in workloads even when host nodes are up to date. The facts here establish a different controlling reason: Restoring encrypted backups may depend on appropriate historical key material availability.

Question 747

An Azure security team encounters: A DBA rotates a customer-managed SQL encryption key without keeping required old key versions accessible for restores. The selected action is: Manage key versions and retention according to supported TDE recovery requirements. Which evidence BEST confirms that the security requirement has been met?

  1. A controlled backup restore succeeds using approved key lifecycle resources.
  2. Key-signed requests fail while properly authorized Entra-based data requests succeed.
  3. A denied unsolicited RDP attempt becomes permitted only during an approved JIT window.
  4. A test SAS tied to the changed policy stops working while unrelated authorized access survives.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: A controlled backup restore succeeds using approved key lifecycle resources. It confirms whether the selected response, Manage key versions and retention according to supported TDE recovery requirements., addressed the scenario. The underlying mechanism is: Restoring encrypted backups may depend on appropriate historical key material availability.

Incorrect Answers

B:

“Key-signed requests fail while properly authorized Entra-based data requests succeed” could occur while the stated failure remains unresolved. It tests: Encryption at rest does not replace strong access control for storage data. The required validation instead is “A controlled backup restore succeeds using approved key lifecycle resources”, because restoring encrypted backups may depend on appropriate historical key material availability.

C:

This checks a different technical dependency: JIT can open constrained management access only for approved requests and durations. The case requires proof of “A controlled backup restore succeeds using approved key lifecycle resources”, which establishes the relevant condition: Restoring encrypted backups may depend on appropriate historical key material availability.

D:

That observation would verify a control associated with: Stored access policies can centralize certain SAS authorization characteristics for revocation. It does not establish the needed acceptance outcome. The direct evidence is “A controlled backup restore succeeds using approved key lifecycle resources”, testing: Restoring encrypted backups may depend on appropriate historical key material availability.

Question 748

Following the issue — A DBA rotates a customer-managed SQL encryption key without keeping required old key versions accessible for restores. — the team takes this action: Manage key versions and retention according to supported TDE recovery requirements. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Test blob data permissions explicitly during access requests.
  2. Include historical encryption keys in SQL backup and restore procedures.
  3. Review confidential compute compatibility whenever altering security type or disk images.
  4. Require versioning or equivalent recovery controls for mutable critical objects.

Explanation

Correct Answer

B:

The recurring safeguard is: Include historical encryption keys in SQL backup and restore procedures. This mitigates the control weakness because: Restoring encrypted backups may depend on appropriate historical key material availability. Keep the intervention, Manage key versions and retention according to supported TDE recovery requirements., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Test blob data permissions explicitly during access requests” addresses a different recurring failure: Azure RBAC Reader does not inherently grant storage blob content read permission. For the condition in this question, maintain “Include historical encryption keys in SQL backup and restore procedures” because restoring encrypted backups may depend on appropriate historical key material availability.

C:

This safeguard is for the dependency described by: Confidential computing offers specialized guest and disk protections beyond generic encryption modes. The continuing risk here is determined by: Restoring encrypted backups may depend on appropriate historical key material availability. The targeted safeguard is “Include historical encryption keys in SQL backup and restore procedures”.

D:

“Require versioning or equivalent recovery controls for mutable critical objects” addresses a different recurring failure: Versioning preserves prior object versions according to configured service capabilities and retention. For the condition in this question, maintain “Include historical encryption keys in SQL backup and restore procedures” because restoring encrypted backups may depend on appropriate historical key material availability.

Question 749

An Azure security engineer evaluates this fictional situation: SQL auditing logs are written to an ordinary blob container where unrelated engineers can modify or delete events. Which response BEST addresses the identified security requirement?

  1. Disable inappropriate anonymous access and enforce authenticated scoped pull permissions.
  2. Replace broad registry write permission with an appropriate least-privileged pull role.
  3. Bind the pod to a suitably scoped Kubernetes service account with required permissions only.
  4. Protect the audit destination with restricted access and appropriate retention or immutable controls.

Explanation

Correct Answer

D:

The most targeted response is: Protect the audit destination with restricted access and appropriate retention or immutable controls. The security basis is: Audit integrity depends on securing stored evidence as well as producing the events. Verification should show: An unauthorized storage writer cannot alter the protected audit event file.

Incorrect Answers

A:

“Disable inappropriate anonymous access and enforce authenticated scoped pull permissions” can be suitable where container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. It does not resolve this question’s narrower failure, which follows: Audit integrity depends on securing stored evidence as well as producing the events. The relevant action is “Protect the audit destination with restricted access and appropriate retention or immutable controls”.

B:

The offered action, “Replace broad registry write permission with an appropriate least-privileged pull role”, addresses a different dependency: ACR push and pull permissions allow different changes to supply-chain artifacts. The failure reported here instead follows: Audit integrity depends on securing stored evidence as well as producing the events. The targeted response is “Protect the audit destination with restricted access and appropriate retention or immutable controls”.

C:

The alternative focuses on the technical control described by: Container workload identities should not inherit broad cluster privileges unnecessarily. The present requirement is governed by: Audit integrity depends on securing stored evidence as well as producing the events. Apply “Protect the audit destination with restricted access and appropriate retention or immutable controls” to address that particular cause.

Question 750

In this retired AZ-500 educational case, SQL auditing logs are written to an ordinary blob container where unrelated engineers can modify or delete events. Which security principle BEST explains the appropriate response?

  1. Audit integrity depends on securing stored evidence as well as producing the events.
  2. A secure capable VM must have applicable firmware and security settings enabled for boot integrity checks.
  3. Cluster API exposure controls administrative access separately from hosted application traffic.
  4. Shared access signatures grant delegated storage access according to their scope, permissions and expiry.

Explanation

Correct Answer

A:

The relevant security principle is: Audit integrity depends on securing stored evidence as well as producing the events. That is why the action is: Protect the audit destination with restricted access and appropriate retention or immutable controls. The directly relevant confirmation is: An unauthorized storage writer cannot alter the protected audit event file.

Incorrect Answers

B:

This alternative is valid when a secure capable VM must have applicable firmware and security settings enabled for boot integrity checks. The facts here establish a different controlling reason: Audit integrity depends on securing stored evidence as well as producing the events.

C:

“Cluster API exposure controls administrative access separately from hosted application traffic” reflects the mechanism: Cluster API exposure controls administrative access separately from hosted application traffic. The actual reported symptoms are better explained by: Audit integrity depends on securing stored evidence as well as producing the events.

D:

The offered principle describes: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. The situation in this question instead depends on: Audit integrity depends on securing stored evidence as well as producing the events. These are different technical conditions.