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 73

Question 720

A Microsoft Azure administrator receives this requirement: An enterprise application requests a high-impact directory-wide application permission, and regular users try to grant the permission themselves. Which operating control most directly reduces this recurring risk?

  1. Version and review exposed API scopes so newly added privileges require explicit consent.
  2. Require review and documented business purpose before granting tenant-wide application consent.
  3. Audit app role assignments and test default-deny authorization paths during release reviews.
  4. Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles.

Explanation

Correct Answer

B:

This guardrail addresses admin consent for sensitive application permission: The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. The prevention measure is: Require review and documented business purpose before granting tenant-wide application consent. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The protected application registration has not exposed an OAuth permission scope for the required delegated operation. “Version and review exposed API scopes so newly added privileges require explicit consent” would address that alternative cause, not the condition in this question: the requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent.

C:

“Audit app role assignments and test default-deny authorization paths during release reviews” responds to this separate finding: successful authentication does not establish application authorization; app roles and assignments are not enforced. This question instead needs “Require review and documented business purpose before granting tenant-wide application consent”, 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. “Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles” applies to that separate problem. The observed case is an enterprise application requests a high-impact directory-wide application permission, and regular users try to grant the permission themselves; choosing this alternative would address the wrong failure mode.

Question 721

During a cloud security review, the operations team observes: An external partner receives a long-lived SAS token with unrestricted permissions and broad network access for a short upload job. What is the most appropriate corrective step?

  1. Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions.
  2. Configure customer-managed key encryption and grant the storage account identity the required key permissions.
  3. Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS.
  4. Assign Storage Blob Data Reader to the application identity at the appropriate container scope.

Explanation

Correct Answer

A:

The cause is: The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. The appropriate change is: Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions. Verify it with this outcome: The partner uploads an authorized object before expiry and cannot delete unrelated blobs or reuse an expired token.

Incorrect Answers

B:

This action concerns storage customer managed key in key vault, where Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. The reported incident instead involves The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose.

C:

This action concerns storage shared key authorization disable, where The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. The corrective response here is “Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions”; this alternative does not provide that response.

D:

This action concerns blob storage data rbac, where Management-plane storage Contributor does not necessarily include blob data read DataActions. The stem reports an external partner receives a long-lived SAS token with unrestricted permissions and broad network access for a short upload job; this control addresses a different failure condition.

Question 722

A Microsoft Azure administrator receives this requirement: A container group deployment exposes an API password as an ordinary public environment variable in its template and diagnostic output. What technical cause best accounts for the described behavior?

  1. The Container App does not use an attached managed identity with the correct Key Vault data-plane permission.
  2. Control-plane version compliance is distinct from node OS image and node pool security patch state.
  3. Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references.
  4. The application's ingress configuration enables external exposure instead of internal-only routing.

Explanation

Correct Answer

C:

The described technical condition is: Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. The appropriate corrective action is: Use secure value handling or managed identity based authentication for the containerized application. Confirm with: Normal deployment reports do not reveal the secret, and approved workloads still authenticate to dependencies.

Incorrect Answers

A:

The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. “Attach a supported managed identity and grant the intended Key Vault secret-read role” would address that alternative cause, not the condition in this question: sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references.

B:

“Schedule supported AKS node image updates and verify rollout health across node pools” responds to this separate finding: control-plane version compliance is distinct from node OS image and node pool security patch state. This question instead needs “Use secure value handling or managed identity based authentication for the containerized application”, so the alternative does not meet the stated condition.

D:

The application's ingress configuration enables external exposure instead of internal-only routing. “Configure internal ingress and supported network isolation for the Container App environment” applies to that separate problem. The observed case is a container group deployment exposes an API password as an ordinary public environment variable in its template and diagnostic output; choosing this alternative would address the wrong failure mode.

Question 723

A production Azure security implementation shows this failure: A background daemon calls Microsoft Graph without a signed-in user but requests delegated permission scopes that rely on user context. What technical cause best accounts for the described behavior?

  1. The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity.
  2. Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions.
  3. Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.
  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: Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. The appropriate corrective action is: Select approved application permissions with administrator consent and configure client-credentials access. Confirm with: The daemon accesses only approved Graph resources without impersonating an absent signed-in user.

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: delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions.

C:

“Inspect service principal sign-in logs and correlated credential or conditional policy results” responds to this separate finding: non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. This question instead needs “Select approved application permissions with administrator consent and configure client-credentials access”, 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 background daemon calls Microsoft Graph without a signed-in user but requests delegated permission scopes that rely on user context; choosing this alternative would address the wrong failure mode.

Question 724

While validating an Azure workload, the security team finds: A daemon app cannot obtain access tokens after a certificate of service availability window because its application client secret has expired. Which outcome most clearly verifies that the issue is resolved?

  1. The daemon acquires tokens again without logging or exposing client credentials.
  2. Activation is rejected until the applicant satisfies the configured challenge and succeeds only for authorized operators.
  3. The managed identity writes only approved blobs after role propagation and cannot access excluded storage.
  4. The consuming tenant lists the app service principal and can enforce authorized user assignment.

Explanation

Correct Answer

A:

This validates the specific control for application client secret expiration: The app registration client credential has expired and the workload has no safe rotation mechanism. The associated corrective action is: Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation. Testing a different component would not establish this result.

Incorrect Answers

B:

PIM role settings have not required the intended multifactor or authentication-strength control at activation. “Configure the PIM role activation requirements to demand the approved strong authentication method” would address that alternative cause, not the condition in this question: the app registration client credential has expired and the workload has no safe rotation mechanism.

C:

“Grant the appropriate storage blob data role to the VM identity at the least necessary scope” responds to this separate finding: creating a managed identity alone does not grant the target resource's required data-plane role. This question instead needs “Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation”, so the alternative does not meet the stated condition.

D:

The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. “Provision or consent the enterprise application service principal and configure appropriate access and controls” applies to that separate problem. The observed case is a daemon app cannot obtain access tokens after a certificate of service availability window because its application client secret has expired; choosing this alternative would address the wrong failure mode.

Question 725

During a cloud security review, the operations team observes: A global web service must block traffic from a prohibited geography, but the team configures only a regional backend NSG that lacks end-user geographic context. What observation is the strongest validation evidence?

  1. Requests from the test blocked geography receive the intended WAF response at the edge.
  2. Application Gateway reports healthy targets and completes an end-to-end request to the application.
  3. TLS clients validate the intended hostname and chain without accepting certificate warnings.
  4. Deprecated TLS clients fail negotiation while approved modern clients connect securely.

Explanation

Correct Answer

A:

This validates the specific control for front door waf geographic access controls: The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. The associated corrective action is: Create the approved Front Door WAF geographic match rule with a documented action and exclusions. Testing a different component would not establish this result.

Incorrect Answers

B:

The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. “Correct the custom health probe to match the actual service endpoint and backend settings” would address that alternative cause, not the condition in this question: the access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge.

C:

“Bind a valid certificate to the custom hostname using an approved App Service certificate mechanism” responds to this separate finding: the custom domain has no correct TLS certificate binding for the expected host name. This question instead needs “Create the approved Front Door WAF geographic match rule with a documented action and exclusions”, so the alternative does not meet the stated condition.

D:

The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. “Set the supported minimum TLS version to an approved modern value and verify certificate configuration” applies to that separate problem. The observed case is a global web service must block traffic from a prohibited geography, but the team configures only a regional backend NSG that lacks end-user geographic context; choosing this alternative would address the wrong failure mode.

Question 726

The cloud operations team reviews the following risk: A cloud security analyst concentrates on low-impact recommendations while a highly weighted open-management-port finding remains unresolved. Which explanation fits the observed symptoms most closely?

  1. Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet.
  2. Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types.
  3. Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path.
  4. Secure score is based on security-control recommendations and affected resources, not just a raw count of findings.

Explanation

Correct Answer

D:

The described technical condition is: Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. The appropriate corrective action is: Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap. Confirm with: The targeted risky configuration is remediated and the secure-score control reflects an appropriate improvement on reevaluation.

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: secure score is based on security-control recommendations and affected resources, not just a raw count of findings.

B:

“Clear or expand the inventory filter and verify the evaluated scope against resource ownership records” responds to this separate finding: inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. This question instead needs “Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap”, so the alternative does not meet the stated condition.

C:

Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. “Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls” 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 727

A platform security assessment reveals this issue: A scheduled Sentinel rule runs every 15 minutes but looks back only two minutes, allowing delayed logs to fall into unobserved intervals. After remediation, which test result best proves the intended change?

  1. Late-arriving simulated authentication events are detected once without producing excessive duplicate incidents.
  2. A fresh qualifying incident invokes the authorized workflow, while unrelated new incidents are unaffected.
  3. The workspace exposes Sentinel analytics, incident management and authorized security content appropriately.
  4. An authorized test role assignment creates a searchable subscription activity record in Sentinel.

Explanation

Correct Answer

A:

This validates the specific control for sentinel analytics frequency lookback mismatch: A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. The associated corrective action is: Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay. Testing a different component would not establish this result.

Incorrect Answers

B:

Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Change the automation rule to the correct incident-created trigger with the intended scoped conditions” would address that alternative cause, not the condition in this question: a rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation.

C:

“Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content” responds to this separate finding: a Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. This question instead needs “Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay”, so the alternative does not meet the stated condition.

D:

Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. “Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace” applies to that separate problem. The observed case is a scheduled Sentinel rule runs every 15 minutes but looks back only two minutes, allowing delayed logs to fall into unobserved intervals; choosing this alternative would address the wrong failure mode.

Question 728

A regulated Azure tenant has this security condition: An AKS team stores production credentials in Kubernetes Secrets and assumes base64 encoding alone provides strong confidentiality of stored secret values. What governance practice would best prevent the same failure?

  1. Test client OS support, outbound port requirements and SMB security before migrations.
  2. Review masking policies alongside direct data export and privileged bypass paths.
  3. Audit Kubernetes Secret permissions and encryption settings as part of cluster hardening.
  4. Review client-driver support, key custody and query limitations before Always Encrypted rollout.

Explanation

Correct Answer

C:

This guardrail addresses aks secrets encryption at rest governance: Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. The prevention measure is: Audit Kubernetes Secret permissions and encryption settings as part of cluster hardening. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The file access path needs compatible secure SMB protocol and supported encrypted transport settings. “Test client OS support, outbound port requirements and SMB security before migrations” would address that alternative cause, not the condition in this question: kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls.

B:

“Review masking policies alongside direct data export and privileged bypass paths” responds to this separate finding: sQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. This question instead needs “Audit Kubernetes Secret permissions and encryption settings as part of cluster hardening”, so the alternative does not meet the stated condition.

D:

TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. “Review client-driver support, key custody and query limitations before Always Encrypted rollout” applies to that separate problem. The observed case is an AKS team stores production credentials in Kubernetes Secrets and assumes base64 encoding alone provides strong confidentiality of stored secret values; choosing this alternative would address the wrong failure mode.

Question 729

A regulated Azure tenant has this security condition: An Azure Function calls a storage account using a client secret embedded in configuration, and secret rotation regularly breaks the application. Which safeguard would best prevent this issue from recurring?

  1. Review third-party enterprise applications and granted permissions as part of tenant governance.
  2. Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents.
  3. Verify both identity issuance and resource-side permissions during managed identity onboarding.
  4. Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes.

Explanation

Correct Answer

D:

This guardrail addresses managed identity replaces embedded secret: The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. The prevention measure is: Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. “Review third-party enterprise applications and granted permissions as part of tenant governance” would address that alternative cause, not the condition in this question: the workload is not using its platform-managed identity and therefore depends on long-lived application secrets.

B:

“Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents” responds to this separate finding: no effective user-risk-based identity protection response has been configured for the relevant identities. This question instead needs “Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes”, so the alternative does not meet the stated condition.

C:

Creating a managed identity alone does not grant the target resource's required data-plane role. “Verify both identity issuance and resource-side permissions during managed identity onboarding” applies to that separate problem. The observed case is an Azure Function calls a storage account using a client secret embedded in configuration, and secret rotation regularly breaks the application; choosing this alternative would address the wrong failure mode.

Question 730

The cloud operations team reviews the following risk: A developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off. Which configuration change most directly resolves this problem?

  1. Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege.
  2. Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS.
  3. Configure customer-managed key encryption and grant the storage account identity the required key permissions.
  4. Enable blob soft delete with an appropriate retention period and verify the restore process.

Explanation

Correct Answer

D:

The cause is: The storage account lacks blob soft delete retention to recover recently removed objects. The appropriate change is: Enable blob soft delete with an appropriate retention period and verify the restore process. Verify it with this outcome: A controlled deletion can be reversed within retention without rebuilding the entire account.

Incorrect Answers

A:

This action concerns user delegation sas for blob storage, where Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. The reported incident instead involves The storage account lacks blob soft delete retention to recover recently removed objects.

B:

This action concerns storage shared key authorization disable, where The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. The corrective response here is “Enable blob soft delete with an appropriate retention period and verify the restore process”; this alternative does not provide that response.

C:

This action concerns storage customer managed key in key vault, where Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. The stem reports a developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off; this control addresses a different failure condition.