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 61

Question 600

Following the issue — An application uses the shared storage account key for read-only file retrieval from one container. — the team takes this action: Replace shared key use with Microsoft Entra authorization or a narrowly scoped suitable SAS when appropriate. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Monitor shared key usage and progressively migrate compatible applications.
  2. Monitor key expiry and access for CMK-encrypted SQL services.
  3. Review container security coverage for transient deployments as well as AKS.
  4. Review AKS cluster roles and group mappings after organizational changes.

Explanation

Correct Answer

A:

The recurring safeguard is: Monitor shared key usage and progressively migrate compatible applications. This mitigates the control weakness because: Account keys authorize broad storage operations and exceed the requirements of a simple limited read. Keep the intervention, Replace shared key use with Microsoft Entra authorization or a narrowly scoped suitable SAS when appropriate., in the approved deployment, monitoring and change governance process.

Incorrect Answers

B:

“Monitor key expiry and access for CMK-encrypted SQL services” addresses a different recurring failure: Customer-managed TDE protectors must remain accessible for database encryption operations. For the condition in this question, maintain “Monitor shared key usage and progressively migrate compatible applications” because account keys authorize broad storage operations and exceed the requirements of a simple limited read.

C:

That review protects the control associated with: Ephemeral containers still create runtime and image exposure independent of short deployment lifetime. It does not directly prevent the stated recurrence, which concerns: Account keys authorize broad storage operations and exceed the requirements of a simple limited read. The appropriate guardrail is “Monitor shared key usage and progressively migrate compatible applications”.

D:

This safeguard is for the dependency described by: Identity-based cluster access can provide accountable and scoped permissions beyond shared local credentials. The continuing risk here is determined by: Account keys authorize broad storage operations and exceed the requirements of a simple limited read. The targeted safeguard is “Monitor shared key usage and progressively migrate compatible applications”.

Question 601

An Azure security engineer evaluates this fictional situation: A storage account access key is discovered in a source repository and rotating one key immediately breaks every workload. Which response BEST addresses the identified security requirement?

  1. Configure the supported customer-managed TDE protector and associated identity permissions.
  2. Use the supported SQL encryption key integration and narrowly scoped key vault permissions.
  3. Coordinate key rotation using the available key slots and update consuming clients safely.
  4. Sanitize headers in gateway logging or remove sensitive payload capture according to the approved policy.

Explanation

Correct Answer

C:

The most targeted response is: Coordinate key rotation using the available key slots and update consuming clients safely. The security basis is: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. Verification should show: All approved services use the new key and the exposed key no longer authenticates.

Incorrect Answers

A:

The alternative focuses on the technical control described by: TDE key ownership can be changed using supported customer-managed key integration. The present requirement is governed by: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. Apply “Coordinate key rotation using the available key slots and update consuming clients safely” to address that particular cause.

B:

“Use the supported SQL encryption key integration and narrowly scoped key vault permissions” can be suitable where encryption key access should use the platform-supported identity and network patterns rather than unbounded application egress. It does not resolve this question’s narrower failure, which follows: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. The relevant action is “Coordinate key rotation using the available key slots and update consuming clients safely”.

D:

The alternative focuses on the technical control described by: Gateway observability can become a credential exposure path if it records secrets. The present requirement is governed by: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. Apply “Coordinate key rotation using the available key slots and update consuming clients safely” to address that particular cause.

Question 602

In this retired AZ-500 educational case, A storage account access key is discovered in a source repository and rotating one key immediately breaks every workload. Which security principle BEST explains the appropriate response?

  1. Setting the Entra administrator does not require granting every directory user access to database contents.
  2. Server HTTPS encryption and client certificate authentication establish different trust properties.
  3. Dynamic data masking alters certain query results for nonprivileged users but does not encrypt underlying data.
  4. Shared access keys are powerful secrets and rotation requires inventory of dependent clients.

Explanation

Correct Answer

D:

The relevant security principle is: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. That is why the action is: Coordinate key rotation using the available key slots and update consuming clients safely. The directly relevant confirmation is: All approved services use the new key and the exposed key no longer authenticates.

Incorrect Answers

A:

“Setting the Entra administrator does not require granting every directory user access to database contents” reflects the mechanism: Setting the Entra administrator does not require granting every directory user access to database contents. The actual reported symptoms are better explained by: Shared access keys are powerful secrets and rotation requires inventory of dependent clients.

B:

The offered principle describes: Server HTTPS encryption and client certificate authentication establish different trust properties. The situation in this question instead depends on: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. These are different technical conditions.

C:

This alternative is valid when dynamic data masking alters certain query results for nonprivileged users but does not encrypt underlying data. The facts here establish a different controlling reason: Shared access keys are powerful secrets and rotation requires inventory of dependent clients.

Question 603

An Azure security team encounters: A storage account access key is discovered in a source repository and rotating one key immediately breaks every workload. The selected action is: Coordinate key rotation using the available key slots and update consuming clients safely. Which evidence BEST confirms that the security requirement has been met?

  1. All approved services use the new key and the exposed key no longer authenticates.
  2. A low-privilege reader cannot retrieve the secret and the application still authenticates.
  3. An authorized operator reaches the test VM via Bastion and external SSH scans fail.
  4. Old and updated clients are tested appropriately and designated data remains decryptable.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: All approved services use the new key and the exposed key no longer authenticates. It confirms whether the selected response, Coordinate key rotation using the available key slots and update consuming clients safely., addressed the scenario. The underlying mechanism is: Shared access keys are powerful secrets and rotation requires inventory of dependent clients.

Incorrect Answers

B:

“A low-privilege reader cannot retrieve the secret and the application still authenticates” could occur while the stated failure remains unresolved. It tests: Container configuration and operator privileges affect exposure of sensitive runtime secrets. The required validation instead is “All approved services use the new key and the exposed key no longer authenticates”, because shared access keys are powerful secrets and rotation requires inventory of dependent clients.

C:

This checks a different technical dependency: Azure Bastion offers controlled browser or client-based access to VMs over private network paths. The case requires proof of “All approved services use the new key and the exposed key no longer authenticates”, which establishes the relevant condition: Shared access keys are powerful secrets and rotation requires inventory of dependent clients.

D:

That observation would verify a control associated with: Client-side cryptography depends on coordinated keys, metadata and compatible application drivers. It does not establish the needed acceptance outcome. The direct evidence is “All approved services use the new key and the exposed key no longer authenticates”, testing: Shared access keys are powerful secrets and rotation requires inventory of dependent clients.

Question 604

Following the issue — A storage account access key is discovered in a source repository and rotating one key immediately breaks every workload. — the team takes this action: Coordinate key rotation using the available key slots and update consuming clients safely. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Inventory cluster API exposure after network and identity changes.
  2. Track storage key dependencies and test rotation processes on a routine schedule.
  3. Test encrypted-column key rotations in staging before changing production.
  4. Monitor SQL audit collection health and retention coverage.

Explanation

Correct Answer

B:

The recurring safeguard is: Track storage key dependencies and test rotation processes on a routine schedule. This mitigates the control weakness because: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. Keep the intervention, Coordinate key rotation using the available key slots and update consuming clients safely., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Inventory cluster API exposure after network and identity changes” addresses a different recurring failure: Cluster API exposure controls administrative access separately from hosted application traffic. For the condition in this question, maintain “Track storage key dependencies and test rotation processes on a routine schedule” because shared access keys are powerful secrets and rotation requires inventory of dependent clients.

C:

This safeguard is for the dependency described by: Client-side cryptography depends on coordinated keys, metadata and compatible application drivers. The continuing risk here is determined by: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. The targeted safeguard is “Track storage key dependencies and test rotation processes on a routine schedule”.

D:

“Monitor SQL audit collection health and retention coverage” addresses a different recurring failure: Database audit logs support investigation and compliance independently from performance monitoring. For the condition in this question, maintain “Track storage key dependencies and test rotation processes on a routine schedule” because shared access keys are powerful secrets and rotation requires inventory of dependent clients.

Question 605

An Azure security engineer evaluates this fictional situation: A blob SAS URL is valid for a year and permits list, write and delete even though an external auditor only needs one-day read access. Which response BEST addresses the identified security requirement?

  1. Add proper database authorization and avoid treating masking as a substitute for access restrictions.
  2. Configure an appropriate masking rule on the sensitive column for eligible nonprivileged queries.
  3. Restrict privileged membership and choose encryption or appropriate application access controls for the true confidentiality requirement.
  4. Issue a narrowly scoped, short-lived SAS with only the required permissions.

Explanation

Correct Answer

D:

The most targeted response is: Issue a narrowly scoped, short-lived SAS with only the required permissions. The security basis is: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. Verification should show: The auditor reads the expected blob during the window but cannot overwrite or delete it.

Incorrect Answers

A:

“Add proper database authorization and avoid treating masking as a substitute for access restrictions” can be suitable where dynamic masking is not a comprehensive confidentiality boundary against arbitrary query inference. It does not resolve this question’s narrower failure, which follows: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. The relevant action is “Issue a narrowly scoped, short-lived SAS with only the required permissions”.

B:

The offered action, “Configure an appropriate masking rule on the sensitive column for eligible nonprivileged queries”, addresses a different dependency: Dynamic data masking alters certain query results for nonprivileged users but does not encrypt underlying data. The failure reported here instead follows: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. The targeted response is “Issue a narrowly scoped, short-lived SAS with only the required permissions”.

C:

The alternative focuses on the technical control described by: Masking rules typically do not protect data from users with relevant elevated SQL privileges. The present requirement is governed by: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. Apply “Issue a narrowly scoped, short-lived SAS with only the required permissions” to address that particular cause.

Question 606

In this retired AZ-500 educational case, A blob SAS URL is valid for a year and permits list, write and delete even though an external auditor only needs one-day read access. Which security principle BEST explains the appropriate response?

  1. Shared access signatures grant delegated storage access according to their scope, permissions and expiry.
  2. Database audit logs support investigation and compliance independently from performance monitoring.
  3. Kubernetes workload egress can create risk even when the API server is not publicly exposed.
  4. Azure resource management roles do not automatically grant relational data-plane permissions.

Explanation

Correct Answer

A:

The relevant security principle is: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. That is why the action is: Issue a narrowly scoped, short-lived SAS with only the required permissions. The directly relevant confirmation is: The auditor reads the expected blob during the window but cannot overwrite or delete it.

Incorrect Answers

B:

This alternative is valid when database audit logs support investigation and compliance independently from performance monitoring. The facts here establish a different controlling reason: Shared access signatures grant delegated storage access according to their scope, permissions and expiry.

C:

“Kubernetes workload egress can create risk even when the API server is not publicly exposed” reflects the mechanism: Kubernetes workload egress can create risk even when the API server is not publicly exposed. The actual reported symptoms are better explained by: Shared access signatures grant delegated storage access according to their scope, permissions and expiry.

D:

The offered principle describes: Azure resource management roles do not automatically grant relational data-plane permissions. The situation in this question instead depends on: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. These are different technical conditions.

Question 607

An Azure security team encounters: A blob SAS URL is valid for a year and permits list, write and delete even though an external auditor only needs one-day read access. The selected action is: Issue a narrowly scoped, short-lived SAS with only the required permissions. Which evidence BEST confirms that the security requirement has been met?

  1. A low-privilege user sees the masked value while designated authorized operations remain functional.
  2. The auditor reads the expected blob during the window but cannot overwrite or delete it.
  3. The developer reads selected logs but cannot edit a different namespace.
  4. An unauthorized API request is rejected while an approved caller passes the gateway checks.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: The auditor reads the expected blob during the window but cannot overwrite or delete it. It confirms whether the selected response, Issue a narrowly scoped, short-lived SAS with only the required permissions., addressed the scenario. The underlying mechanism is: Shared access signatures grant delegated storage access according to their scope, permissions and expiry.

Incorrect Answers

A:

“A low-privilege user sees the masked value while designated authorized operations remain functional” could occur while the stated failure remains unresolved. It tests: Dynamic data masking alters certain query results for nonprivileged users but does not encrypt underlying data. The required validation instead is “The auditor reads the expected blob during the window but cannot overwrite or delete it”, because shared access signatures grant delegated storage access according to their scope, permissions and expiry.

C:

That observation would verify a control associated with: Kubernetes management authorization should align with namespace boundaries and operational job needs. It does not establish the needed acceptance outcome. The direct evidence is “The auditor reads the expected blob during the window but cannot overwrite or delete it”, testing: Shared access signatures grant delegated storage access according to their scope, permissions and expiry.

D:

“An unauthorized API request is rejected while an approved caller passes the gateway checks” could occur while the stated failure remains unresolved. It tests: A gateway can enforce consumer controls independently from the API's internal application code. The required validation instead is “The auditor reads the expected blob during the window but cannot overwrite or delete it”, because shared access signatures grant delegated storage access according to their scope, permissions and expiry.

Question 608

Following the issue — A blob SAS URL is valid for a year and permits list, write and delete even though an external auditor only needs one-day read access. — the team takes this action: Issue a narrowly scoped, short-lived SAS with only the required permissions. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Review confidential compute compatibility whenever altering security type or disk images.
  2. Review privileged database role members after periodic security policy changes.
  3. Review SAS expiration and permission breadth before sharing storage links.
  4. Review AKS cluster roles and group mappings after organizational changes.

Explanation

Correct Answer

C:

The recurring safeguard is: Review SAS expiration and permission breadth before sharing storage links. This mitigates the control weakness because: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. Keep the intervention, Issue a narrowly scoped, short-lived SAS with only the required permissions., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Confidential computing offers specialized guest and disk protections beyond generic encryption modes. It does not directly prevent the stated recurrence, which concerns: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. The appropriate guardrail is “Review SAS expiration and permission breadth before sharing storage links”.

B:

This safeguard is for the dependency described by: Masking rules typically do not protect data from users with relevant elevated SQL privileges. The continuing risk here is determined by: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. The targeted safeguard is “Review SAS expiration and permission breadth before sharing storage links”.

D:

That review protects the control associated with: Identity-based cluster access can provide accountable and scoped permissions beyond shared local credentials. It does not directly prevent the stated recurrence, which concerns: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. The appropriate guardrail is “Review SAS expiration and permission breadth before sharing storage links”.

Question 609

An Azure security engineer evaluates this fictional situation: An application team needs to revoke shared blob access without regenerating all storage account keys. Which response BEST addresses the identified security requirement?

  1. Evaluate a suitable stored access policy where the SAS type supports that mechanism.
  2. Manage key versions and retention according to supported TDE recovery requirements.
  3. Deploy an appropriately secured Azure Bastion path and remove unnecessary direct public management access.
  4. Enable suitable SQL audit events and protected monitoring for authentication failures.

Explanation

Correct Answer

A:

The most targeted response is: Evaluate a suitable stored access policy where the SAS type supports that mechanism. The security basis is: Stored access policies can centralize certain SAS authorization characteristics for revocation. Verification should show: A test SAS tied to the changed policy stops working while unrelated authorized access survives.

Incorrect Answers

B:

The alternative focuses on the technical control described by: Restoring encrypted backups may depend on appropriate historical key material availability. The present requirement is governed by: Stored access policies can centralize certain SAS authorization characteristics for revocation. Apply “Evaluate a suitable stored access policy where the SAS type supports that mechanism” to address that particular cause.

C:

“Deploy an appropriately secured Azure Bastion path and remove unnecessary direct public management access” can be suitable where azure Bastion offers controlled browser or client-based access to VMs over private network paths. It does not resolve this question’s narrower failure, which follows: Stored access policies can centralize certain SAS authorization characteristics for revocation. The relevant action is “Evaluate a suitable stored access policy where the SAS type supports that mechanism”.

D:

The offered action, “Enable suitable SQL audit events and protected monitoring for authentication failures”, addresses a different dependency: Performance diagnostics do not necessarily capture the authentication evidence required for investigations. The failure reported here instead follows: Stored access policies can centralize certain SAS authorization characteristics for revocation. The targeted response is “Evaluate a suitable stored access policy where the SAS type supports that mechanism”.

Question 610

In this retired AZ-500 educational case, An application team needs to revoke shared blob access without regenerating all storage account keys. Which security principle BEST explains the appropriate response?

  1. Database exposure should be consistent with private client traffic requirements and platform capabilities.
  2. Stored access policies can centralize certain SAS authorization characteristics for revocation.
  3. Dynamic masking is not a comprehensive confidentiality boundary against arbitrary query inference.
  4. Azure resource management roles do not automatically grant relational data-plane permissions.

Explanation

Correct Answer

B:

The relevant security principle is: Stored access policies can centralize certain SAS authorization characteristics for revocation. That is why the action is: Evaluate a suitable stored access policy where the SAS type supports that mechanism. The directly relevant confirmation is: A test SAS tied to the changed policy stops working while unrelated authorized access survives.

Incorrect Answers

A:

This alternative is valid when database exposure should be consistent with private client traffic requirements and platform capabilities. The facts here establish a different controlling reason: Stored access policies can centralize certain SAS authorization characteristics for revocation.

C:

The offered principle describes: Dynamic masking is not a comprehensive confidentiality boundary against arbitrary query inference. The situation in this question instead depends on: Stored access policies can centralize certain SAS authorization characteristics for revocation. These are different technical conditions.

D:

This alternative is valid when azure resource management roles do not automatically grant relational data-plane permissions. The facts here establish a different controlling reason: Stored access policies can centralize certain SAS authorization characteristics for revocation.