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 90

Question 890

An Azure security engineer investigates the following incident: A records container must resist deletion for a required retention period, but standard user write permissions allow documents to be overwritten. Which outcome most clearly verifies that the issue is resolved?

  1. Authorized reads continue while deletes or overwrites prohibited by retention are rejected.
  2. The storage account reports infrastructure encryption enabled in addition to regular service-side encryption.
  3. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.
  4. A test overwrite creates a retrievable previous version that administrators can restore.

Explanation

Correct Answer

A:

This validates the specific control for blob immutable storage legal hold: Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. The associated corrective action is: Configure the appropriate time-based immutability policy or legal hold for the protected container. Testing a different component would not establish this result.

Incorrect Answers

B:

The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. “Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage” would address that alternative cause, not the condition in this question: data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone.

C:

“Configure customer-managed key encryption and grant the storage account identity the required key permissions” responds to this separate finding: storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. This question instead needs “Configure the appropriate time-based immutability policy or legal hold for the protected container”, so the alternative does not meet the stated condition.

D:

Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. “Enable supported blob versioning and define backup or lifecycle protection for critical objects” applies to that separate problem. The observed case is a records container must resist deletion for a required retention period, but standard user write permissions allow documents to be overwritten; choosing this alternative would address the wrong failure mode.

Question 891

The cloud operations team reviews the following risk: An enterprise application requests a high-impact directory-wide application permission, and regular users try to grant the permission themselves. Which remediation best addresses the specific issue?

  1. Define application roles, assign them to approved users or groups and validate role claims in the app.
  2. Select approved application permissions with administrator consent and configure client-credentials access.
  3. Define and publish the intended API scope and update client permissions and authorization enforcement.
  4. Have an authorized administrator evaluate and grant only the required application permission after review.

Explanation

Correct Answer

D:

The cause is: The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. The appropriate change is: Have an authorized administrator evaluate and grant only the required application permission after review. Verify it with this outcome: Consent records show authorized approval and the application uses the narrower intended permission.

Incorrect Answers

A:

This action concerns application role assignment authorization, where Successful authentication does not establish application authorization; app roles and assignments are not enforced. The reported incident instead involves The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent.

B:

This action concerns delegated versus application api permissions, where Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. The corrective response here is “Have an authorized administrator evaluate and grant only the required application permission after review”; this alternative does not provide that response.

C:

This action concerns expose an api permission scope, where The protected application registration has not exposed an OAuth permission scope for the required delegated operation. The stem reports an enterprise application requests a high-impact directory-wide application permission, and regular users try to grant the permission themselves; this control addresses a different failure condition.

Question 892

A regulated Azure tenant has this security condition: An Azure subscription suddenly has a new Owner and the incident team inspects VM guest logs instead of Azure resource authorization events. Which configuration change most directly resolves this problem?

  1. Maintain tightly monitored cloud-only emergency access accounts excluded from the blocking control under approved procedures.
  2. Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context.
  3. Configure approval and valid approvers for activation of the sensitive Azure resource role.
  4. Review report-only results, correct exclusions and switch the approved policy to On for enforcement.

Explanation

Correct Answer

B:

The cause is: Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs. The appropriate change is: Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context. Verify it with this outcome: The investigation identifies the actual initiating principal and time of the privileged role change.

Incorrect Answers

A:

This action concerns emergency access account exclusion design, where No properly protected emergency access account and tested exclusion exists to recover from policy or federation failures. The reported incident instead involves Azure role assignment changes are management-plane events captured in Azure Activity Log rather than guest OS logs.

C:

This action concerns pim role activation approval, where The PIM activation workflow lacks the configured approver requirement for the targeted privileged resource role. The corrective response here is “Inspect Azure Activity Log for Microsoft.Authorization role assignment write and delete operations with caller context”; this alternative does not provide that response.

D:

This action concerns conditional access report only mode, where A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. The stem reports an Azure subscription suddenly has a new Owner and the incident team inspects VM guest logs instead of Azure resource authorization events; this control addresses a different failure condition.

Question 893

A regulated Azure tenant has this security condition: A Kubernetes control-plane API endpoint is reachable from the public Internet even though the application platform requires private administration. Which remediation best addresses the specific issue?

  1. Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths.
  2. Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible.
  3. Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope.
  4. Enable the supported network policy option and enforce namespace/pod label based allowlists.

Explanation

Correct Answer

A:

The cause is: The cluster uses a public API server endpoint rather than a supported private AKS cluster design. The appropriate change is: Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths. Verify it with this outcome: Authorized in-network management clients reach the API while external Internet probes cannot.

Incorrect Answers

B:

This action concerns aks key vault csi secret retrieval, where Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. The reported incident instead involves The cluster uses a public API server endpoint rather than a supported private AKS cluster design.

C:

This action concerns aks microsoft entra and kubernetes rbac, where Cluster authorization is not aligned with identity-based RBAC and separation of duties. The corrective response here is “Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths”; this alternative does not provide that response.

D:

This action concerns aks pod network policy isolation, where Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. The stem reports a Kubernetes control-plane API endpoint is reachable from the public Internet even though the application platform requires private administration; this control addresses a different failure condition.

Question 894

A platform security assessment reveals this issue: Several workloads show a recommendation to close Internet-exposed management ports, but the security team wants to suppress the recommendation rather than inspect actual reachable paths. What technical cause best accounts for the described behavior?

  1. Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet.
  2. Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption.
  3. A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration.
  4. A multicloud connector can exist while its required permissions, services or security plan settings are incomplete.

Explanation

Correct Answer

C:

The described technical condition is: A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. The appropriate corrective action is: Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives. Confirm with: Public SSH and RDP access is denied from unauthorized networks and the security assessment updates accordingly.

Incorrect Answers

A:

Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. “Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains” would address that alternative cause, not the condition in this question: a recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration.

B:

“Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope” responds to this separate finding: defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. This question instead needs “Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives”, so the alternative does not meet the stated condition.

D:

A multicloud connector can exist while its required permissions, services or security plan settings are incomplete. “Review and repair the AWS connector's authorized access and enable applicable posture assessment capabilities” applies to that separate problem. The observed case is several workloads show a recommendation to close Internet-exposed management ports, but the security team wants to suppress the recommendation rather than inspect actual reachable paths; choosing this alternative would address the wrong failure mode.

Question 895

A production Azure security implementation shows this failure: An API gateway exposes internal APIs using a publicly accessible endpoint even though clients and backends are expected to remain on private networks. Which operating control most directly reduces this recurring risk?

  1. Test regional edge WAF policies with representative client source conditions and observe false positives.
  2. Review the APIM tier's supported private networking features before selecting gateway architecture.
  3. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  4. Track custom domain certificate validity and binding renewal before expiration.

Explanation

Correct Answer

B:

This guardrail addresses api management private network access: The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. The prevention measure is: Review the APIM tier's supported private networking features before selecting gateway architecture. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. “Test regional edge WAF policies with representative client source conditions and observe false positives” would address that alternative cause, not the condition in this question: the chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary.

C:

“Test TLS protocol settings and certificate expiry after changes to public application endpoints” responds to this separate finding: the app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. This question instead needs “Review the APIM tier's supported private networking features before selecting gateway architecture”, so the alternative does not meet the stated condition.

D:

The custom domain has no correct TLS certificate binding for the expected host name. “Track custom domain certificate validity and binding renewal before expiration” applies to that separate problem. The observed case is an API gateway exposes internal APIs using a publicly accessible endpoint even though clients and backends are expected to remain on private networks; choosing this alternative would address the wrong failure mode.

Question 896

A regulated Azure tenant has this security condition: A company migrates infrastructure templates to GitLab and assumes an existing GitHub-only cloud security connector will analyze them. Which result confirms the relevant security control is effective?

  1. The migrated GitLab infrastructure-as-code repositories become visible with supported security findings.
  2. A safe supported test activity can be correlated with a relevant App Service threat alert and workload identity.
  3. The new VM has a completed supported agentless assessment with software vulnerability recommendations visible to security owners.
  4. A matching test alert triggers the intended notification or ticket while unrelated findings do not invoke it.

Explanation

Correct Answer

A:

This validates the specific control for defender for cloud devops gitlab integration: Code security inventory and posture coverage depend on a supported connector for the actual source-control platform. The associated corrective action is: Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories. Testing a different component would not establish this result.

Incorrect Answers

B:

Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. “Enable the applicable App Service workload protection and route findings to the approved responder queue” would address that alternative cause, not the condition in this question: code security inventory and posture coverage depend on a supported connector for the actual source-control platform.

C:

“Enable the supported agentless scanning capability and verify its resource scope, prerequisites and results” responds to this separate finding: supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent. This question instead needs “Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories”, so the alternative does not meet the stated condition.

D:

A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. “Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook” applies to that separate problem. The observed case is a company migrates infrastructure templates to GitLab and assumes an existing GitHub-only cloud security connector will analyze them; choosing this alternative would address the wrong failure mode.

Question 897

A regulated Azure tenant has this security condition: A privileged engineer is eligible for Owner through Microsoft Entra PIM but attempts to change subscription access without activating the assignment. Which condition most directly explains the failure?

  1. Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.
  2. A PIM eligible assignment is not an active role grant until the user completes the configured activation process.
  3. The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.
  4. Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted.

Explanation

Correct Answer

B:

The described technical condition is: A PIM eligible assignment is not an active role grant until the user completes the configured activation process. The appropriate corrective action is: Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change. Confirm with: The protected operation succeeds during the approved activation window and fails after activation expires.

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: a PIM eligible assignment is not an active role grant until the user completes the configured activation process.

C:

“Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized” responds to this separate finding: the Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. This question instead needs “Activate the eligible Azure resource role using the required MFA, justification and approval steps before making the change”, so the alternative does not meet the stated condition.

D:

Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope” applies to that separate problem. The observed case is a privileged engineer is eligible for Owner through Microsoft Entra PIM but attempts to change subscription access without activating the assignment; choosing this alternative would address the wrong failure mode.

Question 898

While validating an Azure workload, the security team finds: Just-in-time access has been enabled on a VM, but emergency users request an unrestricted source-address exception rather than their current approved workstation IP. Which outcome most clearly verifies that the issue is resolved?

  1. The targeted VM reports the required security updates installed with service continuity preserved.
  2. A test request from the approved address succeeds temporarily while arbitrary Internet sources remain denied.
  3. The VM configuration shows host encryption enabled and temporary data is protected as required.
  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 jit request ip restriction: JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. The associated corrective action is: Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure resource deployment health does not automatically establish guest operating system patch compliance. “Apply approved Azure Update Manager or supported guest patch orchestration and verify patch installation” would address that alternative cause, not the condition in this question: jIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly.

C:

“Enable supported encryption at host for eligible VMs and disks, validating prerequisites and availability” responds to this separate finding: guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. This question instead needs “Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration”, 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 just-in-time access has been enabled on a VM, but emergency users request an unrestricted source-address exception rather than their current approved workstation IP; choosing this alternative would address the wrong failure mode.

Question 899

While validating an Azure workload, the security team finds: A GitHub Actions deployment stores a long-lived Azure service principal secret as a repository variable and leaked logs risk credential compromise. Which explanation fits the observed symptoms most closely?

  1. The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact.
  2. Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra.
  3. Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions.
  4. The protected application registration has not exposed an OAuth permission scope for the required delegated operation.

Explanation

Correct Answer

B:

The described technical condition is: Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. The appropriate corrective action is: Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret. Confirm with: Only the approved workflow obtains short-lived Azure tokens without transmitting a static client secret.

Incorrect Answers

A:

The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. “Revoke the excessive permission and grant only the narrowly required API scopes or app roles” would address that alternative cause, not the condition in this question: secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra.

C:

“Select approved application permissions with administrator consent and configure client-credentials access” responds to this separate finding: delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. This question instead needs “Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret”, so the alternative does not meet the stated condition.

D:

The protected application registration has not exposed an OAuth permission scope for the required delegated operation. “Define and publish the intended API scope and update client permissions and authorization enforcement” applies to that separate problem. The observed case is a GitHub Actions deployment stores a long-lived Azure service principal secret as a repository variable and leaked logs risk credential compromise; choosing this alternative would address the wrong failure mode.

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.