mcAfee Secure Website
23

Microsoft AZ-500 Bundle

Exam Code: AZ-500

Exam Name Microsoft Azure Security Technologies

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Azure Security Engineer Associate

AZ-500 Training Materials $44.99

Reliable & Actual Study Materials for AZ-500 Exam Success

The Latest AZ-500 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-500 Questions & Answers

    523 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-500 Video Course

    AZ-500 Training Course

    73 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

  • exam =30
    Study Guide

    AZ-500 Study Guide

    635 PDF Pages

    Study Guide developed by industry experts who have written exams in the past. They are technology-specific IT certification researchers with at least a decade of experience at Fortune 500 companies.

exam =32

Microsoft Azure Security Technologies (AZ-500) Practice Tests

Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Microsoft Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Total Cost: $194.97
Bundle Price: $149.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    523 Questions

    $124.99
    exam =35
  • exam =37
    AZ-500 Video Course

    Training Course

    73 Video Lectures

    $39.99
  • exam =36
    Study Guide

    Study Guide

    635 PDF Pages

    $29.99

Microsoft AZ-500 Practice Test 91

Question 900

While validating an Azure workload, the security team finds: A cloud security analyst concentrates on low-impact recommendations while a highly weighted open-management-port finding remains unresolved. Which safeguard would best prevent this issue from recurring?

  1. Version and retest custom standards whenever baseline policy definitions or service configurations change.
  2. Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks.
  3. Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts.
  4. Require attribution evidence and review of discovered assets before initiating high-impact external remediation.

Explanation

Correct Answer

C:

This guardrail addresses defender for cloud secure score priority: Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. The prevention measure is: Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions. “Version and retest custom standards whenever baseline policy definitions or service configurations change” would address that alternative cause, not the condition in this question: secure score is based on security-control recommendations and affected resources, not just a raw count of findings.

B:

“Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks” responds to this separate finding: a connector's project enrollment or organization-level integration scope may omit newly created GCP projects. This question instead needs “Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts”, so the alternative does not meet the stated condition.

D:

Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. “Require attribution evidence and review of discovered assets before initiating high-impact external remediation” applies to that separate problem. The observed case is a cloud security analyst concentrates on low-impact recommendations while a highly weighted open-management-port finding remains unresolved; choosing this alternative would address the wrong failure mode.

Question 901

During a cloud security review, the operations team observes: An administrator intends to require MFA and compliant devices but configures the policy to accept any one selected control. What observation is the strongest validation evidence?

  1. A supervised break-glass validation succeeds while ordinary privileged users remain subject to strong controls.
  2. A lost key can be revoked and replaced without allowing unverified MFA bypass.
  3. The targeted legacy authentication attempt is rejected while modern approved sign-in remains operational.
  4. A test sign-in with only MFA fails, while one meeting both MFA and device compliance succeeds.

Explanation

Correct Answer

D:

This validates the specific control for conditional access multiple grant controls: The grant control operator allows any selected requirement rather than requiring all specified requirements. The associated corrective action is: Select the required combination of grant controls and confirm the intended AND behavior. Testing a different component would not establish this result.

Incorrect Answers

A:

The policy targets protected emergency principals without the approved tightly controlled recovery exclusions. “Apply the documented emergency access exclusion and protect recovery identities with independent safeguards” would address that alternative cause, not the condition in this question: the grant control operator allows any selected requirement rather than requiring all specified requirements.

B:

“Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification” responds to this separate finding: strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. This question instead needs “Select the required combination of grant controls and confirm the intended AND behavior”, so the alternative does not meet the stated condition.

C:

The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. “Create a policy that blocks legacy client authentication for the necessary users and applications” applies to that separate problem. The observed case is an administrator intends to require MFA and compliant devices but configures the policy to accept any one selected control; choosing this alternative would address the wrong failure mode.

Question 902

The cloud operations team reviews the following risk: A highly sensitive VM workload requires protecting guest memory and boot state, but the design uses only ordinary managed disk encryption. Which result confirms the relevant security control is effective?

  1. A test request from the approved address succeeds temporarily while arbitrary Internet sources remain denied.
  2. A test VM reports the intended confidential security posture and protected boot chain.
  3. The VM successfully mounts its protected volume after an approved recovery and retains encryption.
  4. An approved SSH client reaches the private VM through Bastion without a VM public IP.

Explanation

Correct Answer

B:

This validates the specific control for confidential vm protected boot and encryption: Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory. The associated corrective action is: Choose supported confidential VM features and configure the correct security type and encryption settings. Testing a different component would not establish this result.

Incorrect Answers

A:

JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. “Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration” would address that alternative cause, not the condition in this question: disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory.

C:

“Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies” responds to this separate finding: azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. This question instead needs “Choose supported confidential VM features and configure the correct security type and encryption settings”, so the alternative does not meet the stated condition.

D:

Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. “Use a supported Bastion native-client connection and required RBAC and network prerequisites” applies to that separate problem. The observed case is a highly sensitive VM workload requires protecting guest memory and boot state, but the design uses only ordinary managed disk encryption; choosing this alternative would address the wrong failure mode.

Question 903

During a cloud security review, the operations team observes: An application registered in a software supplier tenant needs access to a customer's API, but the customer assumes the supplier's role grants automatically apply locally. What observation is the strongest validation evidence?

  1. The application authenticates with its secured credential while the old secret is revoked and unusable.
  2. A test unverified high-risk application cannot gain requested scopes through ordinary user consent.
  3. A customer tenant administrator can revoke the app's local access without altering the supplier registration.
  4. Only the approved workflow obtains short-lived Azure tokens without transmitting a static client secret.

Explanation

Correct Answer

C:

This validates the specific control for cross tenant service principal consent: Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The associated corrective action is: Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles. Testing a different component would not establish this result.

Incorrect Answers

A:

The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. “Configure a certificate credential or supported workload federation and remove the leaked text secret” would address that alternative cause, not the condition in this question: cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls.

B:

“Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow” responds to this separate finding: the user consent configuration permits risky OAuth grants without publisher and permission restrictions. This question instead needs “Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles”, so the alternative does not meet the stated condition.

D:

Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. “Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret” applies to that separate problem. The observed case is an application registered in a software supplier tenant needs access to a customer's API, but the customer assumes the supplier's role grants automatically apply locally; choosing this alternative would address the wrong failure mode.

Question 904

A Microsoft Azure administrator receives this requirement: A container app revision embeds a database password directly into plaintext application arguments, violating application secret-handling rules. Which operating control most directly reduces this recurring risk?

  1. Track identity integration feature lifecycle before Kubernetes version upgrades.
  2. Review app revision changes for insecure arguments and secret-reference drift.
  3. Prefer identity-based secret retrieval and recertify permissions for each container revision.
  4. Test AKS diagnostic collection coverage after cluster upgrades and namespace changes.

Explanation

Correct Answer

B:

This guardrail addresses container apps secret references: Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. The prevention measure is: Review app revision changes for insecure arguments and secret-reference drift. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. “Track identity integration feature lifecycle before Kubernetes version upgrades” would address that alternative cause, not the condition in this question: sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity.

C:

“Prefer identity-based secret retrieval and recertify permissions for each container revision” responds to this separate finding: the Container App does not use an attached managed identity with the correct Key Vault data-plane permission. This question instead needs “Review app revision changes for insecure arguments and secret-reference drift”, so the alternative does not meet the stated condition.

D:

AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. “Test AKS diagnostic collection coverage after cluster upgrades and namespace changes” applies to that separate problem. The observed case is a container app revision embeds a database password directly into plaintext application arguments, violating application secret-handling rules; choosing this alternative would address the wrong failure mode.

Question 905

A production Azure security implementation shows this failure: A VM successfully obtains a token for Azure Storage through managed identity, but blob writes return 403 even though its system identity exists. What technical cause best accounts for the described behavior?

  1. The app registration client credential has expired and the workload has no safe rotation mechanism.
  2. Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.
  3. Creating a managed identity alone does not grant the target resource's required data-plane role.
  4. No effective user-risk-based identity protection response has been configured for the relevant identities.

Explanation

Correct Answer

C:

The described technical condition is: Creating a managed identity alone does not grant the target resource's required data-plane role. The appropriate corrective action is: Grant the appropriate storage blob data role to the VM identity at the least necessary scope. Confirm with: The managed identity writes only approved blobs after role propagation and cannot access excluded storage.

Incorrect Answers

A:

The app registration client credential has expired and the workload has no safe rotation mechanism. “Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation” would address that alternative cause, not the condition in this question: creating a managed identity alone does not grant the target resource's required data-plane role.

B:

“Enable the approved passwordless method and complete secure user registration” responds to this separate finding: microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. This question instead needs “Grant the appropriate storage blob data role to the VM identity at the least necessary scope”, so the alternative does not meet the stated condition.

D:

No effective user-risk-based identity protection response has been configured for the relevant identities. “Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate” applies to that separate problem. The observed case is a VM successfully obtains a token for Azure Storage through managed identity, but blob writes return 403 even though its system identity exists; choosing this alternative would address the wrong failure mode.

Question 906

While validating an Azure workload, the security team finds: A team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged. Which condition most directly explains the failure?

  1. Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories.
  2. The cluster uses a public API server endpoint rather than a supported private AKS cluster design.
  3. Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules.
  4. Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization.

Explanation

Correct Answer

A:

The described technical condition is: Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. The appropriate corrective action is: Move credentials into a managed secrets service and use approved persistent data storage where needed. Confirm with: Recreated instances retrieve approved secrets securely without relying on local ephemeral disk recovery.

Incorrect Answers

B:

The cluster uses a public API server endpoint rather than a supported private AKS cluster design. “Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths” would address that alternative cause, not the condition in this question: ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories.

C:

“Enable the supported network policy option and enforce namespace/pod label based allowlists” responds to this separate finding: namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. This question instead needs “Move credentials into a managed secrets service and use approved persistent data storage where needed”, so the alternative does not meet the stated condition.

D:

Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. “Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals” applies to that separate problem. The observed case is a team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged; choosing this alternative would address the wrong failure mode.

Question 907

A Microsoft Azure administrator receives this requirement: A team enables Azure Firewall Premium TLS inspection without distributing the enterprise trust chain, causing browser certificate errors for inspected applications. What should the engineer implement first to address the weakness?

  1. Enable firewall DNS proxy where required and set spoke resolvers to the authorized firewall private address.
  2. Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies.
  3. Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic.
  4. Adjust Azure Firewall private IP ranges and route design to preserve source addresses for approved private traffic.

Explanation

Correct Answer

B:

The cause is: TLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients. The appropriate change is: Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies. Verify it with this outcome: Authorized inspected HTTPS sessions validate the expected certificate chain and security events are visible.

Incorrect Answers

A:

This action concerns firewall dns proxy routing, where Spoke DNS server settings do not use the intended firewall DNS proxy endpoint consistently. The reported incident instead involves TLS interception requires a supported firewall certificate configuration and trusted enterprise CA distribution to clients.

C:

This action concerns firewall manager secured virtual hub, where The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. The corrective response here is “Configure the appropriate intermediate CA and client trust deployment with supported TLS inspection policies”; this alternative does not provide that response.

D:

This action concerns azure firewall snat private range design, where The firewall's configured private address space for SNAT exemption omits the datacenter destination range. The stem reports a team enables Azure Firewall Premium TLS inspection without distributing the enterprise trust chain, causing browser certificate errors for inspected applications; this control addresses a different failure condition.

Question 908

A regulated Azure tenant has this security condition: An NSG management rule was fixed minutes ago but Defender for Cloud still shows the prior security recommendation as open. What governance practice would best prevent the same failure?

  1. Validate effective network reachability and owner approval when dismissing or exempting cloud posture findings.
  2. Use independent configuration verification and record assessment timestamps when validating urgent posture remediations.
  3. Revalidate exemption evidence and age periodically so exceptions do not mask ongoing exposure.
  4. Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy.

Explanation

Correct Answer

B:

This guardrail addresses defender for cloud posture assessment freshness: Defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change. The prevention measure is: Use independent configuration verification and record assessment timestamps when validating urgent posture remediations. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. “Validate effective network reachability and owner approval when dismissing or exempting cloud posture findings” would address that alternative cause, not the condition in this question: defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change.

C:

“Revalidate exemption evidence and age periodically so exceptions do not mask ongoing exposure” responds to this separate finding: an exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. This question instead needs “Use independent configuration verification and record assessment timestamps when validating urgent posture remediations”, so the alternative does not meet the stated condition.

D:

A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. “Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy” applies to that separate problem. The observed case is an NSG management rule was fixed minutes ago but Defender for Cloud still shows the prior security recommendation as open; choosing this alternative would address the wrong failure mode.

Question 909

A regulated Azure tenant has this security condition: An attacker overwrites a blob with incorrect content but its latest object still exists, and administrators have no prior version to restore. Which outcome most clearly verifies that the issue is resolved?

  1. A test overwrite creates a retrievable previous version that administrators can restore.
  2. The partner uploads an authorized object before expiry and cannot delete unrelated blobs or reuse an expired token.
  3. Approved clients access data and unauthorized public source IPs receive network access denial.
  4. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.

Explanation

Correct Answer

A:

This validates the specific control for blob versioning prior content recovery: Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The associated corrective action is: Enable supported blob versioning and define backup or lifecycle protection for critical objects. Testing a different component would not establish this result.

Incorrect Answers

B:

The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. “Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions” would address that alternative cause, not the condition in this question: blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning.

C:

“Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required” responds to this separate finding: the storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. This question instead needs “Enable supported blob versioning and define backup or lifecycle protection for critical objects”, so the alternative does not meet the stated condition.

D:

Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. “Configure customer-managed key encryption and grant the storage account identity the required key permissions” applies to that separate problem. The observed case is an attacker overwrites a blob with incorrect content but its latest object still exists, and administrators have no prior version to restore; choosing this alternative would address the wrong failure mode.

Question 910

An Azure security engineer investigates the following incident: A Container Apps environment publishes an administrative endpoint to everyone although it should accept only private application traffic. Which remediation best addresses the specific issue?

  1. Attach a supported managed identity and grant the intended Key Vault secret-read role.
  2. Schedule supported AKS node image updates and verify rollout health across node pools.
  3. Configure internal ingress and supported network isolation for the Container App environment.
  4. Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components.

Explanation

Correct Answer

C:

The cause is: The application's ingress configuration enables external exposure instead of internal-only routing. The appropriate change is: Configure internal ingress and supported network isolation for the Container App environment. Verify it with this outcome: Authorized internal clients reach the service while public Internet attempts are denied.

Incorrect Answers

A:

This action concerns container apps managed identity auth, where The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The reported incident instead involves The application's ingress configuration enables external exposure instead of internal-only routing.

B:

This action concerns aks node image upgrade hygiene, where Control-plane version compliance is distinct from node OS image and node pool security patch state. The corrective response here is “Configure internal ingress and supported network isolation for the Container App environment”; this alternative does not provide that response.

D:

This action concerns azure policy admission for aks, where Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. The stem reports a Container Apps environment publishes an administrative endpoint to everyone although it should accept only private application traffic; this control addresses a different failure condition.