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 55

Question 540

Following the issue — A Container Apps environment permits privileged application secrets in plain configuration variables visible to routine operators. — the team takes this action: Move secrets into approved secret references or managed identity-controlled services with scoped access. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Test application driver support after dependency and database upgrades.
  2. Scan container deployment manifests for embedded credentials and unsafe role grants.
  3. Require versioning or equivalent recovery controls for mutable critical objects.
  4. Teach reviewers the limitations of masking versus encryption and role-based access.

Explanation

Correct Answer

B:

The recurring safeguard is: Scan container deployment manifests for embedded credentials and unsafe role grants. This mitigates the control weakness because: Container configuration and operator privileges affect exposure of sensitive runtime secrets. Keep the intervention, Move secrets into approved secret references or managed identity-controlled services with scoped access., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

This safeguard is for the dependency described by: Client-side column encryption depends on driver capabilities in addition to server schema. The continuing risk here is determined by: Container configuration and operator privileges affect exposure of sensitive runtime secrets. The targeted safeguard is “Scan container deployment manifests for embedded credentials and unsafe role grants”.

C:

That review protects the control associated with: Versioning preserves prior object versions according to configured service capabilities and retention. It does not directly prevent the stated recurrence, which concerns: Container configuration and operator privileges affect exposure of sensitive runtime secrets. The appropriate guardrail is “Scan container deployment manifests for embedded credentials and unsafe role grants”.

D:

This safeguard is for the dependency described by: Dynamic masking is not a comprehensive confidentiality boundary against arbitrary query inference. The continuing risk here is determined by: Container configuration and operator privileges affect exposure of sensitive runtime secrets. The targeted safeguard is “Scan container deployment manifests for embedded credentials and unsafe role grants”.

Question 541

An Azure security engineer evaluates this fictional situation: An Azure Container Registry accepts anonymous pulls from a private image repository not intended to be public. Which response BEST addresses the identified security requirement?

  1. Apply suitable Azure Files share-level permissions and compatible file ACLs where supported.
  2. Configure an appropriate masking rule on the sensitive column for eligible nonprivileged queries.
  3. Issue an appropriate scoped credential with operations limited to the application path.
  4. Disable inappropriate anonymous access and enforce authenticated scoped pull permissions.

Explanation

Correct Answer

D:

The most targeted response is: Disable inappropriate anonymous access and enforce authenticated scoped pull permissions. The security basis is: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. Verification should show: An anonymous pull fails while an assigned workload identity can retrieve the approved image.

Incorrect Answers

A:

The alternative focuses on the technical control described by: SMB authorization can combine share-level identity permissions with file-system ACL evaluation. The present requirement is governed by: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. Apply “Disable inappropriate anonymous access and enforce authenticated scoped pull permissions” to address that particular cause.

B:

“Configure an appropriate masking rule on the sensitive column for eligible nonprivileged queries” can be suitable where dynamic data masking alters certain query results for nonprivileged users but does not encrypt underlying data. It does not resolve this question’s narrower failure, which follows: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. The relevant action is “Disable inappropriate anonymous access and enforce authenticated scoped pull permissions”.

C:

The offered action, “Issue an appropriate scoped credential with operations limited to the application path”, addresses a different dependency: Data access should reflect precise blob type, resource path, and allowed operations. The failure reported here instead follows: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. The targeted response is “Disable inappropriate anonymous access and enforce authenticated scoped pull permissions”.

Question 542

In this retired AZ-500 educational case, An Azure Container Registry accepts anonymous pulls from a private image repository not intended to be public. Which security principle BEST explains the appropriate response?

  1. Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.
  2. Azure Storage uses encryption at rest even when an organization has not configured its own CMK.
  3. Client-side cryptography depends on coordinated keys, metadata and compatible application drivers.
  4. Data access should reflect precise blob type, resource path, and allowed operations.

Explanation

Correct Answer

A:

The relevant security principle is: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. That is why the action is: Disable inappropriate anonymous access and enforce authenticated scoped pull permissions. The directly relevant confirmation is: An anonymous pull fails while an assigned workload identity can retrieve the approved image.

Incorrect Answers

B:

The offered principle describes: Azure Storage uses encryption at rest even when an organization has not configured its own CMK. The situation in this question instead depends on: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. These are different technical conditions.

C:

This alternative is valid when client-side cryptography depends on coordinated keys, metadata and compatible application drivers. The facts here establish a different controlling reason: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.

D:

“Data access should reflect precise blob type, resource path, and allowed operations” reflects the mechanism: Data access should reflect precise blob type, resource path, and allowed operations. The actual reported symptoms are better explained by: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.

Question 543

An Azure security team encounters: An Azure Container Registry accepts anonymous pulls from a private image repository not intended to be public. The selected action is: Disable inappropriate anonymous access and enforce authenticated scoped pull permissions. Which evidence BEST confirms that the security requirement has been met?

  1. A test audited statement appears at the new authorized destination after the migration.
  2. An anonymous pull fails while an assigned workload identity can retrieve the approved image.
  3. All approved services use the new key and the exposed key no longer authenticates.
  4. The approved application transparently encrypts and decrypts the designated column.

Explanation

Correct Answer

B:

The most meaningful acceptance evidence is: An anonymous pull fails while an assigned workload identity can retrieve the approved image. It confirms whether the selected response, Disable inappropriate anonymous access and enforce authenticated scoped pull permissions., addressed the scenario. The underlying mechanism is: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.

Incorrect Answers

A:

That observation would verify a control associated with: Application database reachability does not guarantee every telemetry or audit egress path. It does not establish the needed acceptance outcome. The direct evidence is “An anonymous pull fails while an assigned workload identity can retrieve the approved image”, testing: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.

C:

This checks a different technical dependency: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. The case requires proof of “An anonymous pull fails while an assigned workload identity can retrieve the approved image”, which establishes the relevant condition: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.

D:

That observation would verify a control associated with: Client-side column encryption depends on driver capabilities in addition to server schema. It does not establish the needed acceptance outcome. The direct evidence is “An anonymous pull fails while an assigned workload identity can retrieve the approved image”, testing: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.

Question 544

Following the issue — An Azure Container Registry accepts anonymous pulls from a private image repository not intended to be public. — the team takes this action: Disable inappropriate anonymous access and enforce authenticated scoped pull permissions. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Run monitoring and audit end-to-end checks after SQL MI subnet changes.
  2. Test SQL auditing destinations after storage permission or network changes.
  3. Audit container registry public access and pull identities after pipeline changes.
  4. Review identity source and file ACL compatibility before server migrations.

Explanation

Correct Answer

C:

The recurring safeguard is: Audit container registry public access and pull identities after pipeline changes. This mitigates the control weakness because: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. Keep the intervention, Disable inappropriate anonymous access and enforce authenticated scoped pull permissions., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

“Run monitoring and audit end-to-end checks after SQL MI subnet changes” addresses a different recurring failure: Application database reachability does not guarantee every telemetry or audit egress path. For the condition in this question, maintain “Audit container registry public access and pull identities after pipeline changes” because container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.

B:

That review protects the control associated with: Audit policy presence does not prove that authorized log records are successfully stored. It does not directly prevent the stated recurrence, which concerns: Container registry endpoints may expose proprietary or sensitive build artifacts when access is broad. The appropriate guardrail is “Audit container registry public access and pull identities after pipeline changes”.

D:

“Review identity source and file ACL compatibility before server migrations” addresses a different recurring failure: Azure Files can use identity-based SMB access when its authentication prerequisites are met. For the condition in this question, maintain “Audit container registry public access and pull identities after pipeline changes” because container registry endpoints may expose proprietary or sensitive build artifacts when access is broad.

Question 545

An Azure security engineer evaluates this fictional situation: A deployment pipeline has ACR Push on an entire registry when it should only pull release images. Which response BEST addresses the identified security requirement?

  1. Replace broad registry write permission with an appropriate least-privileged pull role.
  2. Enable transport TLS for connections and document TDE as at-rest database protection.
  3. Remove sensitive values from logs and apply appropriate column protection and application data handling.
  4. Coordinate key rotation using the available key slots and update consuming clients safely.

Explanation

Correct Answer

A:

The most targeted response is: Replace broad registry write permission with an appropriate least-privileged pull role. The security basis is: ACR push and pull permissions allow different changes to supply-chain artifacts. Verification should show: The pipeline pulls the approved image but cannot push a modified production tag.

Incorrect Answers

B:

The offered action, “Enable transport TLS for connections and document TDE as at-rest database protection”, addresses a different dependency: TDE encrypts database storage whereas transport encryption protects traffic in motion. The failure reported here instead follows: ACR push and pull permissions allow different changes to supply-chain artifacts. The targeted response is “Replace broad registry write permission with an appropriate least-privileged pull role”.

C:

The alternative focuses on the technical control described by: Presentation masking alone does not prevent exposure through logging and diagnostics. The present requirement is governed by: ACR push and pull permissions allow different changes to supply-chain artifacts. Apply “Replace broad registry write permission with an appropriate least-privileged pull role” to address that particular cause.

D:

“Coordinate key rotation using the available key slots and update consuming clients safely” can be suitable where shared access keys are powerful secrets and rotation requires inventory of dependent clients. It does not resolve this question’s narrower failure, which follows: ACR push and pull permissions allow different changes to supply-chain artifacts. The relevant action is “Replace broad registry write permission with an appropriate least-privileged pull role”.

Question 546

In this retired AZ-500 educational case, A deployment pipeline has ACR Push on an entire registry when it should only pull release images. Which security principle BEST explains the appropriate response?

  1. Microsoft Entra authentication can centralize identity and avoid routine SQL password reliance.
  2. ACR push and pull permissions allow different changes to supply-chain artifacts.
  3. Restoring encrypted backups may depend on appropriate historical key material availability.
  4. Recovery mechanisms can fail if the same compromised identity can destroy both primary and backup data.

Explanation

Correct Answer

B:

The relevant security principle is: ACR push and pull permissions allow different changes to supply-chain artifacts. That is why the action is: Replace broad registry write permission with an appropriate least-privileged pull role. The directly relevant confirmation is: The pipeline pulls the approved image but cannot push a modified production tag.

Incorrect Answers

A:

The offered principle describes: Microsoft Entra authentication can centralize identity and avoid routine SQL password reliance. The situation in this question instead depends on: ACR push and pull permissions allow different changes to supply-chain artifacts. These are different technical conditions.

C:

“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: ACR push and pull permissions allow different changes to supply-chain artifacts.

D:

The offered principle describes: Recovery mechanisms can fail if the same compromised identity can destroy both primary and backup data. The situation in this question instead depends on: ACR push and pull permissions allow different changes to supply-chain artifacts. These are different technical conditions.

Question 547

An Azure security team encounters: A deployment pipeline has ACR Push on an entire registry when it should only pull release images. The selected action is: Replace broad registry write permission with an appropriate least-privileged pull role. Which evidence BEST confirms that the security requirement has been met?

  1. The account's encryption properties show default encryption while its key source is documented.
  2. A test audited statement appears at the new authorized destination after the migration.
  3. The pipeline pulls the approved image but cannot push a modified production tag.
  4. The auditor reads the expected blob during the window but cannot overwrite or delete it.

Explanation

Correct Answer

C:

The most meaningful acceptance evidence is: The pipeline pulls the approved image but cannot push a modified production tag. It confirms whether the selected response, Replace broad registry write permission with an appropriate least-privileged pull role., addressed the scenario. The underlying mechanism is: ACR push and pull permissions allow different changes to supply-chain artifacts.

Incorrect Answers

A:

“The account's encryption properties show default encryption while its key source is documented” could occur while the stated failure remains unresolved. It tests: Azure Storage uses encryption at rest even when an organization has not configured its own CMK. The required validation instead is “The pipeline pulls the approved image but cannot push a modified production tag”, because aCR push and pull permissions allow different changes to supply-chain artifacts.

B:

This checks a different technical dependency: Application database reachability does not guarantee every telemetry or audit egress path. The case requires proof of “The pipeline pulls the approved image but cannot push a modified production tag”, which establishes the relevant condition: ACR push and pull permissions allow different changes to supply-chain artifacts.

D:

“The auditor reads the expected blob during the window but cannot overwrite or delete it” could occur while the stated failure remains unresolved. It tests: Shared access signatures grant delegated storage access according to their scope, permissions and expiry. The required validation instead is “The pipeline pulls the approved image but cannot push a modified production tag”, because aCR push and pull permissions allow different changes to supply-chain artifacts.

Question 548

Following the issue — A deployment pipeline has ACR Push on an entire registry when it should only pull release images. — the team takes this action: Replace broad registry write permission with an appropriate least-privileged pull role. Which continuing safeguard BEST prevents the same control weakness from returning?

  1. Verify client source addresses during SAS access provisioning.
  2. Monitor key access, rotation and unavailability risk for CMK-backed accounts.
  3. Track storage key dependencies and test rotation processes on a routine schedule.
  4. Review registry permissions during CI/CD service principal rotation.

Explanation

Correct Answer

D:

The recurring safeguard is: Review registry permissions during CI/CD service principal rotation. This mitigates the control weakness because: ACR push and pull permissions allow different changes to supply-chain artifacts. Keep the intervention, Replace broad registry write permission with an appropriate least-privileged pull role., in the approved deployment, monitoring and change governance process.

Incorrect Answers

A:

That review protects the control associated with: SAS IP constraints can limit where otherwise valid signed access requests are accepted. It does not directly prevent the stated recurrence, which concerns: ACR push and pull permissions allow different changes to supply-chain artifacts. The appropriate guardrail is “Review registry permissions during CI/CD service principal rotation”.

B:

This safeguard is for the dependency described by: Customer-managed keys provide customer control over key access and lifecycle for supported storage services. The continuing risk here is determined by: ACR push and pull permissions allow different changes to supply-chain artifacts. The targeted safeguard is “Review registry permissions during CI/CD service principal rotation”.

C:

“Track storage key dependencies and test rotation processes on a routine schedule” addresses a different recurring failure: Shared access keys are powerful secrets and rotation requires inventory of dependent clients. For the condition in this question, maintain “Review registry permissions during CI/CD service principal rotation” because aCR push and pull permissions allow different changes to supply-chain artifacts.

Question 549

An Azure security engineer evaluates this fictional situation: A VM uses a managed disk, but security staff assume that default encryption always satisfies a customer-managed-key requirement. Which response BEST addresses the identified security requirement?

  1. Restrict database connectivity using supported private MI networking and approved firewall rules.
  2. Configure a supported disk encryption set with the required customer-managed key when mandated.
  3. Disable shared key authorization when supported and migrate clients to Microsoft Entra tokens.
  4. Configure an appropriate immutable storage or legal hold policy for the required retention scope.

Explanation

Correct Answer

B:

The most targeted response is: Configure a supported disk encryption set with the required customer-managed key when mandated. The security basis is: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models. Verification should show: Disk configuration references the approved encryption set and key availability is validated.

Incorrect Answers

A:

The offered action, “Restrict database connectivity using supported private MI networking and approved firewall rules”, addresses a different dependency: Database exposure should be consistent with private client traffic requirements and platform capabilities. The failure reported here instead follows: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models. The targeted response is “Configure a supported disk encryption set with the required customer-managed key when mandated”.

C:

“Disable shared key authorization when supported and migrate clients to Microsoft Entra tokens” can be suitable where encryption at rest does not replace strong access control for storage data. It does not resolve this question’s narrower failure, which follows: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models. The relevant action is “Configure a supported disk encryption set with the required customer-managed key when mandated”.

D:

The offered action, “Configure an appropriate immutable storage or legal hold policy for the required retention scope”, addresses a different dependency: Immutable storage enforces write-once retention characteristics that ordinary backup access does not guarantee. The failure reported here instead follows: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models. The targeted response is “Configure a supported disk encryption set with the required customer-managed key when mandated”.

Question 550

In this retired AZ-500 educational case, A VM uses a managed disk, but security staff assume that default encryption always satisfies a customer-managed-key requirement. 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. Retention locks can make storage records undeletable for the configured duration.
  3. Platform-managed at-rest encryption and customer-managed key policies provide different key-control models.
  4. Audit policy presence does not prove that authorized log records are successfully stored.

Explanation

Correct Answer

C:

The relevant security principle is: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models. That is why the action is: Configure a supported disk encryption set with the required customer-managed key when mandated. The directly relevant confirmation is: Disk configuration references the approved encryption set and key availability is validated.

Incorrect Answers

A:

This alternative is valid when setting the Entra administrator does not require granting every directory user access to database contents. The facts here establish a different controlling reason: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models.

B:

“Retention locks can make storage records undeletable for the configured duration” reflects the mechanism: Retention locks can make storage records undeletable for the configured duration. The actual reported symptoms are better explained by: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models.

D:

This alternative is valid when audit policy presence does not prove that authorized log records are successfully stored. The facts here establish a different controlling reason: Platform-managed at-rest encryption and customer-managed key policies provide different key-control models.