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 10

Question 90

The cloud operations team reviews the following risk: An Azure Container App needs to read a protected secret but its outbound code uses an expired service principal secret rather than a platform credential. Which explanation fits the observed symptoms most closely?

  1. The Container App does not use an attached managed identity with the correct Key Vault data-plane permission.
  2. Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity.
  3. Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references.
  4. The cluster's public API server authorized IP ranges were not configured for restricted administrative access.

Explanation

Correct Answer

A:

The described technical condition is: The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The appropriate corrective action is: Attach a supported managed identity and grant the intended Key Vault secret-read role. Confirm with: The app retrieves secrets via its identity and remains operational after the old client secret is revoked.

Incorrect Answers

B:

Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. “Configure a secure Container Apps secret reference or managed identity for database access” would address that alternative cause, not the condition in this question: the Container App does not use an attached managed identity with the correct Key Vault data-plane permission.

C:

“Use secure value handling or managed identity based authentication for the containerized application” responds to this separate finding: sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. This question instead needs “Attach a supported managed identity and grant the intended Key Vault secret-read role”, so the alternative does not meet the stated condition.

D:

The cluster's public API server authorized IP ranges were not configured for restricted administrative access. “Configure approved API server authorized IP ranges or move to private control-plane access” applies to that separate problem. The observed case is an Azure Container App needs to read a protected secret but its outbound code uses an expired service principal secret rather than a platform credential; choosing this alternative would address the wrong failure mode.

Question 91

While validating an Azure workload, the security team finds: A container image with known vulnerable packages is pulled into production AKS because teams check only that the registry login succeeds. Which explanation fits the observed symptoms most closely?

  1. Authentication to a container registry does not establish that deployed images meet vulnerability security requirements.
  2. The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.
  3. Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules.
  4. Cluster authorization is not aligned with identity-based RBAC and separation of duties.

Explanation

Correct Answer

A:

The described technical condition is: Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. The appropriate corrective action is: Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation. Confirm with: The vulnerable image is detected and a patched replacement is deployed before production exposure.

Incorrect Answers

B:

The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. “Configure workload identity on the service account and scoped access to the target Key Vault” would address that alternative cause, not the condition in this question: authentication to a container registry does not establish that deployed images meet vulnerability security requirements.

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 “Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation”, so the alternative does not meet the stated condition.

D:

Cluster authorization is not aligned with identity-based RBAC and separation of duties. “Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope” applies to that separate problem. The observed case is a container image with known vulnerable packages is pulled into production AKS because teams check only that the registry login succeeds; choosing this alternative would address the wrong failure mode.

Question 92

During a cloud security review, the operations team observes: A legacy VM uses Azure Disk Encryption but a required Key Vault key or secret is disabled during rotation and the VM cannot unlock encrypted volumes. Which underlying control gap is responsible for the issue?

  1. Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk.
  2. Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement.
  3. Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access.
  4. The VM's NSG exposes a persistent management port rather than enforcing just-in-time access.

Explanation

Correct Answer

A:

The described technical condition is: Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. The appropriate corrective action is: Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies. Confirm with: The VM successfully mounts its protected volume after an approved recovery and retains encryption.

Incorrect Answers

B:

Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. “Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability” would address that alternative cause, not the condition in this question: azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk.

C:

“Configure the encryption set and supported Key Vault key permissions, then associate eligible disks” responds to this separate finding: azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. This question instead needs “Restore approved key or secret access using supported ADE recovery procedures and rotate without breaking dependencies”, so the alternative does not meet the stated condition.

D:

The VM's NSG exposes a persistent management port rather than enforcing just-in-time access. “Configure supported just-in-time VM access and remove persistent open management rules” applies to that separate problem. The observed case is a legacy VM uses Azure Disk Encryption but a required Key Vault key or secret is disabled during rotation and the VM cannot unlock encrypted volumes; choosing this alternative would address the wrong failure mode.

Question 93

While validating an Azure workload, the security team finds: Database administrators can see sensitive customer identifiers in plaintext despite a policy requiring only client applications to decrypt those values. What governance practice would best prevent the same failure?

  1. Review client-driver support, key custody and query limitations before Always Encrypted rollout.
  2. Audit file-share permissions at both Azure share level and file system ACL layers.
  3. Audit Kubernetes Secret permissions and encryption settings as part of cluster hardening.
  4. Audit TDE status and key rotation separately from transport TLS compliance.

Explanation

Correct Answer

A:

This guardrail addresses sql always encrypted client column isolation: TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. The prevention measure is: Review client-driver support, key custody and query limitations before Always Encrypted rollout. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. “Audit file-share permissions at both Azure share level and file system ACL layers” would address that alternative cause, not the condition in this question: tDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing.

C:

“Audit Kubernetes Secret permissions and encryption settings as part of cluster hardening” responds to this separate finding: kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. This question instead needs “Review client-driver support, key custody and query limitations before Always Encrypted rollout”, so the alternative does not meet the stated condition.

D:

TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Audit TDE status and key rotation separately from transport TLS compliance” applies to that separate problem. The observed case is database administrators can see sensitive customer identifiers in plaintext despite a policy requiring only client applications to decrypt those values; choosing this alternative would address the wrong failure mode.

Question 94

A platform security assessment reveals this issue: An application issues shared-key SAS tokens to end users while security requires tokens to derive from Microsoft Entra authorization. What is the most appropriate corrective step?

  1. Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage.
  2. Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions.
  3. Enable supported blob versioning and define backup or lifecycle protection for critical objects.
  4. Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege.

Explanation

Correct Answer

D:

The cause is: Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. The appropriate change is: Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege. Verify it with this outcome: A delegated client accesses only intended blobs without possession of the storage account key.

Incorrect Answers

A:

This action concerns storage infrastructure double encryption, where The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. The reported incident instead involves Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model.

B:

This action concerns service sas expiry and ip restrictions, where The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. The corrective response here is “Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege”; this alternative does not provide that response.

C:

This action concerns blob versioning prior content recovery, where Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The stem reports an application issues shared-key SAS tokens to end users while security requires tokens to derive from Microsoft Entra authorization; this control addresses a different failure condition.

Question 95

A platform security assessment reveals this issue: A security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions. After remediation, which test result best proves the intended change?

  1. The analyst lists authorized blobs with Entra authentication but cannot change account-level configuration.
  2. The operator views security inventory in both existing and newly attached eligible subscriptions.
  3. Activation is rejected until the applicant satisfies the configured challenge and succeeds only for authorized operators.
  4. An authorized test modifies the intended tags while the operator retains no additional administration privileges.

Explanation

Correct Answer

B:

This validates the specific control for management group security assignment: Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The associated corrective action is: Assign the approved read-only role at a suitable management group with the intended child subscription coverage. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” would address that alternative cause, not the condition in this question: per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.

C:

“Configure the PIM role activation requirements to demand the approved strong authentication method” responds to this separate finding: pIM role settings have not required the intended multifactor or authentication-strength control at activation. This question instead needs “Assign the approved read-only role at a suitable management group with the intended child subscription coverage”, so the alternative does not meet the stated condition.

D:

The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. “Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized” applies to that separate problem. The observed case is a security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions; choosing this alternative would address the wrong failure mode.

Question 96

An Azure security engineer investigates the following incident: An app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption. Which remediation best addresses the specific issue?

  1. Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients.
  2. Configure the Microsoft Entra administrator and create appropriate contained database users and roles.
  3. Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access.
  4. Configure supported SQL driver encryption with certificate chain and hostname validation enabled.

Explanation

Correct Answer

D:

The cause is: Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. The appropriate change is: Configure supported SQL driver encryption with certificate chain and hostname validation enabled. Verify it with this outcome: The client connects only to the legitimate database endpoint and rejects an untrusted test certificate.

Incorrect Answers

A:

This action concerns sql always encrypted client column isolation, where TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. The reported incident instead involves Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.

B:

This action concerns azure sql microsoft entra administrator auth, where The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. The corrective response here is “Configure supported SQL driver encryption with certificate chain and hostname validation enabled”; this alternative does not provide that response.

C:

This action concerns azure sql private endpoint dns and public disable, where The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. The stem reports an app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption; this control addresses a different failure condition.

Question 97

The cloud operations team reviews the following risk: A security team creates a Logic App response workflow but expects Defender for Cloud to invoke it automatically without configuring any workflow automation trigger. Which remediation best addresses the specific issue?

  1. Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts.
  2. Compare required features to current Defender for Servers plans and enable the appropriate supported tier for governed machines.
  3. Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook.
  4. Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment.

Explanation

Correct Answer

C:

The cause is: A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. The appropriate change is: Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook. Verify it with this outcome: A matching test alert triggers the intended notification or ticket while unrelated findings do not invoke it.

Incorrect Answers

A:

This action concerns defender for storage sensitive data threat detection, where Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. The reported incident instead involves A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions.

B:

This action concerns microsoft defender for servers plan 2 eligibility, where Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. The corrective response here is “Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook”; this alternative does not provide that response.

D:

This action concerns defender for cloud devops iac misconfiguration, where Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The stem reports a security team creates a Logic App response workflow but expects Defender for Cloud to invoke it automatically without configuring any workflow automation trigger; this control addresses a different failure condition.

Question 98

A production Azure security implementation shows this failure: A sensitive browser session persists for many days without a fresh sign-in despite a policy requiring shorter high-risk session exposure. Which recurring validation best protects against the observed problem?

  1. Monitor legacy sign-in activity and resolve legitimate dependencies before enforcing global legacy blocking.
  2. Reconcile trusted named locations with network change records and periodically retest ranges.
  3. Audit authenticator registration changes and enforce identity-proofing during account recovery.
  4. Review session control settings together with application token behavior and user impact.

Explanation

Correct Answer

D:

This guardrail addresses conditional access sign in frequency: The relevant Conditional Access session control lacks the required sign-in frequency and session behavior. The prevention measure is: Review session control settings together with application token behavior and user impact. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. “Monitor legacy sign-in activity and resolve legitimate dependencies before enforcing global legacy blocking” would address that alternative cause, not the condition in this question: the relevant Conditional Access session control lacks the required sign-in frequency and session behavior.

B:

“Reconcile trusted named locations with network change records and periodically retest ranges” responds to this separate finding: the named location definition is stale and no longer reflects current verified branch egress address ranges. This question instead needs “Review session control settings together with application token behavior and user impact”, so the alternative does not meet the stated condition.

C:

Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. “Audit authenticator registration changes and enforce identity-proofing during account recovery” applies to that separate problem. The observed case is a sensitive browser session persists for many days without a fresh sign-in despite a policy requiring shorter high-risk session exposure; choosing this alternative would address the wrong failure mode.

Question 99

A Microsoft Azure administrator receives this requirement: An App Service certificate stored in Key Vault renews through a provider but the application still serves an expired certificate chain. What should the engineer implement first to address the weakness?

  1. Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint.
  2. Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition.
  3. Set time-limited exemptions with accountable justification and remove or renew each only after security review.
  4. Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path.

Explanation

Correct Answer

A:

The cause is: Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. The appropriate change is: Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint. Verify it with this outcome: A TLS test of the service displays the new valid leaf certificate and trusted chain before the old one expires.

Incorrect Answers

B:

This action concerns azure policy modify remediation for existing tags, where Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. The reported incident instead involves Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version.

C:

This action concerns azure policy exemption expiration, where An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. The corrective response here is “Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint”; this alternative does not provide that response.

D:

This action concerns key vault firewall trusted bypass scope, where Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. The stem reports an App Service certificate stored in Key Vault renews through a provider but the application still serves an expired certificate chain; this control addresses a different failure condition.

Question 100

A platform security assessment reveals this issue: A deployment account has Contributor on a resource group but receives an explicit deny through a managed deployment, and an administrator keeps adding more Allow role assignments. What technical cause best accounts for the described behavior?

  1. NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule.
  2. PIM role settings have not required the intended multifactor or authentication-strength control at activation.
  3. A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.
  4. Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope.

Explanation

Correct Answer

D:

The described technical condition is: Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. The appropriate corrective action is: Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures. Confirm with: A test write succeeds only after the legitimate deny condition is resolved without adding unnecessary privilege.

Incorrect Answers

A:

NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. “Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment” would address that alternative cause, not the condition in this question: azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope.

B:

“Configure the PIM role activation requirements to demand the approved strong authentication method” responds to this separate finding: pIM role settings have not required the intended multifactor or authentication-strength control at activation. This question instead needs “Identify the effective deny assignment and change the controlling managed deployment or governance mechanism through supported procedures”, so the alternative does not meet the stated condition.

C:

A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” applies to that separate problem. The observed case is a deployment account has Contributor on a resource group but receives an explicit deny through a managed deployment, and an administrator keeps adding more Allow role assignments; choosing this alternative would address the wrong failure mode.