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 58

Question 570

In this retired AZ-500 educational case, An API Management policy logs Authorization headers to diagnostics, leaking sensitive bearer tokens. Which security principle BEST explains the appropriate response?

  1. Dynamic data masking alters certain query results for nonprivileged users but does not encrypt underlying data.
  2. Always Encrypted can protect eligible sensitive column values from server-side plaintext exposure.
  3. Setting the Entra administrator does not require granting every directory user access to database contents.
  4. Gateway observability can become a credential exposure path if it records secrets.

Explanation

Correct Answer

D:

The relevant security principle is: Gateway observability can become a credential exposure path if it records secrets. That is why the action is: Sanitize headers in gateway logging or remove sensitive payload capture according to the approved policy. The directly relevant confirmation is: A diagnostic test captures operational metadata without the secret token value.

Incorrect Answers

A:

The offered principle describes: Dynamic data masking alters certain query results for nonprivileged users but does not encrypt underlying data. The situation in this question instead depends on: Gateway observability can become a credential exposure path if it records secrets. These are different technical conditions.

B:

This alternative is valid when always Encrypted can protect eligible sensitive column values from server-side plaintext exposure. The facts here establish a different controlling reason: Gateway observability can become a credential exposure path if it records secrets.

C:

“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: Gateway observability can become a credential exposure path if it records secrets.

Question 571

An Azure security team encounters: An API Management policy logs Authorization headers to diagnostics, leaking sensitive bearer tokens. The selected action is: Sanitize headers in gateway logging or remove sensitive payload capture according to the approved policy. Which evidence BEST confirms that the security requirement has been met?

  1. A diagnostic test captures operational metadata without the secret token value.
  2. An approved Entra identity connects and an unauthorized SQL principal is denied where configured.
  3. An unauthorized storage writer cannot alter the protected audit event file.
  4. The administrator manages server settings but table queries need an explicit suitable database principal.

Explanation

Correct Answer

A:

The most meaningful acceptance evidence is: A diagnostic test captures operational metadata without the secret token value. It confirms whether the selected response, Sanitize headers in gateway logging or remove sensitive payload capture according to the approved policy., addressed the scenario. The underlying mechanism is: Gateway observability can become a credential exposure path if it records secrets.

Incorrect Answers

B:

This checks a different technical dependency: Microsoft Entra authentication can centralize identity and avoid routine SQL password reliance. The case requires proof of “A diagnostic test captures operational metadata without the secret token value”, which establishes the relevant condition: Gateway observability can become a credential exposure path if it records secrets.

C:

That observation would verify a control associated with: Audit integrity depends on securing stored evidence as well as producing the events. It does not establish the needed acceptance outcome. The direct evidence is “A diagnostic test captures operational metadata without the secret token value”, testing: Gateway observability can become a credential exposure path if it records secrets.

D:

“The administrator manages server settings but table queries need an explicit suitable database principal” could occur while the stated failure remains unresolved. It tests: Azure resource management roles do not automatically grant relational data-plane permissions. The required validation instead is “A diagnostic test captures operational metadata without the secret token value”, because gateway observability can become a credential exposure path if it records secrets.

Question 572

Following the issue — An API Management policy logs Authorization headers to diagnostics, leaking sensitive bearer tokens. — the team takes this action: Sanitize headers in gateway logging or remove sensitive payload capture according to the approved policy. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Scan base images for storage credentials and rotate compromised secrets.
  2. Audit APIM diagnostic policies after troubleshooting changes.
  3. Monitor key expiry and access for CMK-encrypted SQL services.
  4. Audit immutability retention and legal hold governance before changing policies.

Explanation

Correct Answer

B:

The recurring safeguard is: Audit APIM diagnostic policies after troubleshooting changes. This mitigates the control weakness because: Gateway observability can become a credential exposure path if it records secrets. Keep the intervention, Sanitize headers in gateway logging or remove sensitive payload capture according to the approved policy., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: Distributing storage account secrets in machine images creates broad and persistent exposure. It does not directly prevent the stated recurrence, which concerns: Gateway observability can become a credential exposure path if it records secrets. The appropriate guardrail is “Audit APIM diagnostic policies after troubleshooting changes”.

C:

“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 “Audit APIM diagnostic policies after troubleshooting changes” because gateway observability can become a credential exposure path if it records secrets.

D:

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: Gateway observability can become a credential exposure path if it records secrets. The appropriate guardrail is “Audit APIM diagnostic policies after troubleshooting changes”.

Question 573

An Azure security engineer evaluates this fictional situation: A secured API requires mutual TLS between clients and API Management but only server TLS is configured. Which response BEST addresses the identified security requirement?

  1. Protect audit access and set retention under the applicable regulatory and operational requirements.
  2. Disable public blob access in line with the intended account and container configuration.
  3. Use the supported SQL encryption key integration and narrowly scoped key vault permissions.
  4. Configure supported client-certificate validation at APIM and manage certificate lifecycle.

Explanation

Correct Answer

D:

The most targeted response is: Configure supported client-certificate validation at APIM and manage certificate lifecycle. The security basis is: Server HTTPS encryption and client certificate authentication establish different trust properties. Verification should show: A client with the approved certificate succeeds while an unknown client is denied.

Incorrect Answers

A:

The offered action, “Protect audit access and set retention under the applicable regulatory and operational requirements”, addresses a different dependency: Security logs can themselves contain private information and require governed access and lifecycle. The failure reported here instead follows: Server HTTPS encryption and client certificate authentication establish different trust properties. The targeted response is “Configure supported client-certificate validation at APIM and manage certificate lifecycle”.

B:

The alternative focuses on the technical control described by: Anonymous blob exposure is controlled by service and container-level settings rather than Azure RBAC alone. The present requirement is governed by: Server HTTPS encryption and client certificate authentication establish different trust properties. Apply “Configure supported client-certificate validation at APIM and manage certificate lifecycle” to address that particular cause.

C:

“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: Server HTTPS encryption and client certificate authentication establish different trust properties. The relevant action is “Configure supported client-certificate validation at APIM and manage certificate lifecycle”.

Question 574

In this retired AZ-500 educational case, A secured API requires mutual TLS between clients and API Management but only server TLS is configured. Which security principle BEST explains the appropriate response?

  1. Server HTTPS encryption and client certificate authentication establish different trust properties.
  2. Presentation masking alone does not prevent exposure through logging and diagnostics.
  3. Deterministic and randomized encryption modes offer different equality and confidentiality properties.
  4. Shared access keys are powerful secrets and rotation requires inventory of dependent clients.

Explanation

Correct Answer

A:

The relevant security principle is: Server HTTPS encryption and client certificate authentication establish different trust properties. That is why the action is: Configure supported client-certificate validation at APIM and manage certificate lifecycle. The directly relevant confirmation is: A client with the approved certificate succeeds while an unknown client is denied.

Incorrect Answers

B:

“Presentation masking alone does not prevent exposure through logging and diagnostics” reflects the mechanism: Presentation masking alone does not prevent exposure through logging and diagnostics. The actual reported symptoms are better explained by: Server HTTPS encryption and client certificate authentication establish different trust properties.

C:

The offered principle describes: Deterministic and randomized encryption modes offer different equality and confidentiality properties. The situation in this question instead depends on: Server HTTPS encryption and client certificate authentication establish different trust properties. These are different technical conditions.

D:

This alternative is valid when shared access keys are powerful secrets and rotation requires inventory of dependent clients. The facts here establish a different controlling reason: Server HTTPS encryption and client certificate authentication establish different trust properties.

Question 575

An Azure security team encounters: A secured API requires mutual TLS between clients and API Management but only server TLS is configured. The selected action is: Configure supported client-certificate validation at APIM and manage certificate lifecycle. Which evidence BEST confirms that the security requirement has been met?

  1. A controlled backup restore succeeds using approved key lifecycle resources.
  2. A client with the approved certificate succeeds while an unknown client is denied.
  3. All approved services use the new key and the exposed key no longer authenticates.
  4. Only approved investigators can query retained events and expired data follows policy.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: A client with the approved certificate succeeds while an unknown client is denied. It confirms whether the selected response, Configure supported client-certificate validation at APIM and manage certificate lifecycle., addressed the scenario. The underlying mechanism is: Server HTTPS encryption and client certificate authentication establish different trust properties.

Incorrect Answers

A:

This checks a different technical dependency: Restoring encrypted backups may depend on appropriate historical key material availability. The case requires proof of “A client with the approved certificate succeeds while an unknown client is denied”, which establishes the relevant condition: Server HTTPS encryption and client certificate authentication establish different trust properties.

C:

“All approved services use the new key and the exposed key no longer authenticates” could occur while the stated failure remains unresolved. It tests: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. The required validation instead is “A client with the approved certificate succeeds while an unknown client is denied”, because server HTTPS encryption and client certificate authentication establish different trust properties.

D:

This checks a different technical dependency: Security logs can themselves contain private information and require governed access and lifecycle. The case requires proof of “A client with the approved certificate succeeds while an unknown client is denied”, which establishes the relevant condition: Server HTTPS encryption and client certificate authentication establish different trust properties.

Question 576

Following the issue — A secured API requires mutual TLS between clients and API Management but only server TLS is configured. — the team takes this action: Configure supported client-certificate validation at APIM and manage certificate lifecycle. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Teach reviewers to separate encryption state from key ownership model.
  2. Make double-encryption requirements part of provisioning templates.
  3. Monitor accepted client certificate issuers and expiry for sensitive APIs.
  4. Audit immutability retention and legal hold governance before changing policies.

Explanation

Correct Answer

C:

The recurring safeguard is: Monitor accepted client certificate issuers and expiry for sensitive APIs. This mitigates the control weakness because: Server HTTPS encryption and client certificate authentication establish different trust properties. Keep the intervention, Configure supported client-certificate validation at APIM and manage certificate lifecycle., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Azure Storage uses encryption at rest even when an organization has not configured its own CMK. The continuing risk here is determined by: Server HTTPS encryption and client certificate authentication establish different trust properties. The targeted safeguard is “Monitor accepted client certificate issuers and expiry for sensitive APIs”.

B:

“Make double-encryption requirements part of provisioning templates” addresses a different recurring failure: Infrastructure encryption adds an independent layer to Azure Storage encryption at rest. For the condition in this question, maintain “Monitor accepted client certificate issuers and expiry for sensitive APIs” because server HTTPS encryption and client certificate authentication establish different trust properties.

D:

This safeguard is for the dependency described by: Immutable storage enforces write-once retention characteristics that ordinary backup access does not guarantee. The continuing risk here is determined by: Server HTTPS encryption and client certificate authentication establish different trust properties. The targeted safeguard is “Monitor accepted client certificate issuers and expiry for sensitive APIs”.

Question 577

An Azure security engineer evaluates this fictional situation: A containerized service runs with an unnecessarily privileged Kubernetes service account. Which response BEST addresses the identified security requirement?

  1. Bind the pod to a suitably scoped Kubernetes service account with required permissions only.
  2. Issue an appropriate scoped credential with operations limited to the application path.
  3. Configure the supported customer-managed TDE protector and associated identity permissions.
  4. Configure the appropriate supported container soft delete setting and restore testing.

Explanation

Correct Answer

A:

The most targeted response is: Bind the pod to a suitably scoped Kubernetes service account with required permissions only. The security basis is: Container workload identities should not inherit broad cluster privileges unnecessarily. Verification should show: The service performs its approved API read while a cluster-wide secret list fails.

Incorrect Answers

B:

“Issue an appropriate scoped credential with operations limited to the application path” can be suitable where data access should reflect precise blob type, resource path, and allowed operations. It does not resolve this question’s narrower failure, which follows: Container workload identities should not inherit broad cluster privileges unnecessarily. The relevant action is “Bind the pod to a suitably scoped Kubernetes service account with required permissions only”.

C:

The offered action, “Configure the supported customer-managed TDE protector and associated identity permissions”, addresses a different dependency: TDE key ownership can be changed using supported customer-managed key integration. The failure reported here instead follows: Container workload identities should not inherit broad cluster privileges unnecessarily. The targeted response is “Bind the pod to a suitably scoped Kubernetes service account with required permissions only”.

D:

The alternative focuses on the technical control described by: Blob deletion recovery and container deletion recovery are different storage protections. The present requirement is governed by: Container workload identities should not inherit broad cluster privileges unnecessarily. Apply “Bind the pod to a suitably scoped Kubernetes service account with required permissions only” to address that particular cause.

Question 578

In this retired AZ-500 educational case, A containerized service runs with an unnecessarily privileged Kubernetes service account. Which security principle BEST explains the appropriate response?

  1. Restoring encrypted backups may depend on appropriate historical key material availability.
  2. Container workload identities should not inherit broad cluster privileges unnecessarily.
  3. Azure Files can use identity-based SMB access when its authentication prerequisites are met.
  4. TDE encrypts database storage whereas transport encryption protects traffic in motion.

Explanation

Correct Answer

B:

The relevant security principle is: Container workload identities should not inherit broad cluster privileges unnecessarily. That is why the action is: Bind the pod to a suitably scoped Kubernetes service account with required permissions only. The directly relevant confirmation is: The service performs its approved API read while a cluster-wide secret list fails.

Incorrect Answers

A:

“Restoring encrypted backups may depend on appropriate historical key material availability” reflects the mechanism: Restoring encrypted backups may depend on appropriate historical key material availability. The actual reported symptoms are better explained by: Container workload identities should not inherit broad cluster privileges unnecessarily.

C:

This alternative is valid when azure Files can use identity-based SMB access when its authentication prerequisites are met. The facts here establish a different controlling reason: Container workload identities should not inherit broad cluster privileges unnecessarily.

D:

“TDE encrypts database storage whereas transport encryption protects traffic in motion” reflects the mechanism: TDE encrypts database storage whereas transport encryption protects traffic in motion. The actual reported symptoms are better explained by: Container workload identities should not inherit broad cluster privileges unnecessarily.

Question 579

An Azure security team encounters: A containerized service runs with an unnecessarily privileged Kubernetes service account. The selected action is: Bind the pod to a suitably scoped Kubernetes service account with required permissions only. Which evidence BEST confirms that the security requirement has been met?

  1. A test SAS tied to the changed policy stops working while unrelated authorized access survives.
  2. The storage encryption configuration references the approved active key and data operations succeed.
  3. The service performs its approved API read while a cluster-wide secret list fails.
  4. All approved services use the new key and the exposed key no longer authenticates.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: The service performs its approved API read while a cluster-wide secret list fails. It confirms whether the selected response, Bind the pod to a suitably scoped Kubernetes service account with required permissions only., addressed the scenario. The underlying mechanism is: Container workload identities should not inherit broad cluster privileges unnecessarily.

Incorrect Answers

A:

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 “The service performs its approved API read while a cluster-wide secret list fails”, testing: Container workload identities should not inherit broad cluster privileges unnecessarily.

B:

“The storage encryption configuration references the approved active key and data operations succeed” could occur while the stated failure remains unresolved. It tests: Customer-managed keys provide customer control over key access and lifecycle for supported storage services. The required validation instead is “The service performs its approved API read while a cluster-wide secret list fails”, because container workload identities should not inherit broad cluster privileges unnecessarily.

D:

That observation would verify a control associated with: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. It does not establish the needed acceptance outcome. The direct evidence is “The service performs its approved API read while a cluster-wide secret list fails”, testing: Container workload identities should not inherit broad cluster privileges unnecessarily.

Question 580

Following the issue — A containerized service runs with an unnecessarily privileged Kubernetes service account. — the team takes this action: Bind the pod to a suitably scoped Kubernetes service account with required permissions only. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Monitor key expiry and access for CMK-encrypted SQL services.
  2. Audit storage access authentication modes alongside encryption posture.
  3. Run monitoring and audit end-to-end checks after SQL MI subnet changes.
  4. Inspect Kubernetes service account permissions during every workload rollout.

Explanation

Correct Answer

D:

The recurring safeguard is: Inspect Kubernetes service account permissions during every workload rollout. This mitigates the control weakness because: Container workload identities should not inherit broad cluster privileges unnecessarily. Keep the intervention, Bind the pod to a suitably scoped Kubernetes service account with required permissions only., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“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 “Inspect Kubernetes service account permissions during every workload rollout” because container workload identities should not inherit broad cluster privileges unnecessarily.

B:

That review protects the control associated with: Encryption at rest does not replace strong access control for storage data. It does not directly prevent the stated recurrence, which concerns: Container workload identities should not inherit broad cluster privileges unnecessarily. The appropriate guardrail is “Inspect Kubernetes service account permissions during every workload rollout”.

C:

This safeguard is for the dependency described by: Application database reachability does not guarantee every telemetry or audit egress path. The continuing risk here is determined by: Container workload identities should not inherit broad cluster privileges unnecessarily. The targeted safeguard is “Inspect Kubernetes service account permissions during every workload rollout”.