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 61

Question 600

A platform security assessment reveals this issue: An unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events. What technical cause best accounts for the described behavior?

  1. The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent.
  2. Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions.
  3. Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls.
  4. Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.

Explanation

Correct Answer

D:

The described technical condition is: Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The appropriate corrective action is: Inspect service principal sign-in logs and correlated credential or conditional policy results. Confirm with: The failing app identity, time and error reason are identified in the service principal log stream.

Incorrect Answers

A:

The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. “Have an authorized administrator evaluate and grant only the required application permission after review” would address that alternative cause, not the condition in this question: non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.

B:

“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 “Inspect service principal sign-in logs and correlated credential or conditional policy results”, so the alternative does not meet the stated condition.

C:

Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. “Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles” applies to that separate problem. The observed case is an unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events; choosing this alternative would address the wrong failure mode.

Question 601

A platform security assessment reveals this issue: An AKS public API endpoint remains reachable from any source address though administration should originate only from a controlled office IP range. What should the engineer implement first to address the weakness?

  1. Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings.
  2. Configure a secure Container Apps secret reference or managed identity for database access.
  3. Configure approved API server authorized IP ranges or move to private control-plane access.
  4. Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components.

Explanation

Correct Answer

C:

The cause is: The cluster's public API server authorized IP ranges were not configured for restricted administrative access. The appropriate change is: Configure approved API server authorized IP ranges or move to private control-plane access. Verify it with this outcome: An allowed management source can connect while test sources outside the ranges are blocked.

Incorrect Answers

A:

This action concerns aks legacy pod identity migration, where The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. The reported incident instead involves The cluster's public API server authorized IP ranges were not configured for restricted administrative access.

B:

This action concerns container apps secret references, where Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. The corrective response here is “Configure approved API server authorized IP ranges or move to private control-plane access”; 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 an AKS public API endpoint remains reachable from any source address though administration should originate only from a controlled office IP range; this control addresses a different failure condition.

Question 602

During a cloud security review, the operations team observes: A broad Conditional Access policy blocks all administrators including both recovery accounts, leaving no viable emergency access route after a policy misconfiguration. After remediation, which test result best proves the intended change?

  1. An SMS-only sign-in fails the privileged requirement while an authorized phishing-resistant method succeeds.
  2. Legitimate branch users match the correct location policy and unrelated public addresses are not trusted.
  3. A supervised break-glass validation succeeds while ordinary privileged users remain subject to strong controls.
  4. A test sign-in with only MFA fails, while one meeting both MFA and device compliance succeeds.

Explanation

Correct Answer

C:

This validates the specific control for emergency account conditional access exclusion: The policy targets protected emergency principals without the approved tightly controlled recovery exclusions. The associated corrective action is: Apply the documented emergency access exclusion and protect recovery identities with independent safeguards. Testing a different component would not establish this result.

Incorrect Answers

A:

The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. “Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods” would address that alternative cause, not the condition in this question: the policy targets protected emergency principals without the approved tightly controlled recovery exclusions.

B:

“Update the trusted named location with validated new egress ranges and test the affected policy conditions” 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 “Apply the documented emergency access exclusion and protect recovery identities with independent safeguards”, so the alternative does not meet the stated condition.

D:

The grant control operator allows any selected requirement rather than requiring all specified requirements. “Select the required combination of grant controls and confirm the intended AND behavior” applies to that separate problem. The observed case is a broad Conditional Access policy blocks all administrators including both recovery accounts, leaving no viable emergency access route after a policy misconfiguration; choosing this alternative would address the wrong failure mode.

Question 603

A platform security assessment reveals this issue: 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. What should the engineer implement first to address the weakness?

  1. Configure a secure Container Apps secret reference or managed identity for database access.
  2. Configure internal ingress and supported network isolation for the Container App environment.
  3. Attach a supported managed identity and grant the intended Key Vault secret-read role.
  4. Configure approved API server authorized IP ranges or move to private control-plane access.

Explanation

Correct Answer

C:

The cause is: The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The appropriate change is: Attach a supported managed identity and grant the intended Key Vault secret-read role. Verify it with this outcome: The app retrieves secrets via its identity and remains operational after the old client secret is revoked.

Incorrect Answers

A:

This action concerns container apps secret references, where Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. The reported incident instead involves The Container App does not use an attached managed identity with the correct Key Vault data-plane permission.

B:

This action concerns azure container apps ingress restriction, where The application's ingress configuration enables external exposure instead of internal-only routing. The corrective response here is “Attach a supported managed identity and grant the intended Key Vault secret-read role”; this alternative does not provide that response.

D:

This action concerns aks api server authorized ip ranges, where The cluster's public API server authorized IP ranges were not configured for restricted administrative access. The stem reports 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; this control addresses a different failure condition.

Question 604

The cloud operations team reviews the following risk: A background daemon calls Microsoft Graph without a signed-in user but requests delegated permission scopes that rely on user context. Which result confirms the relevant security control is effective?

  1. The failing app identity, time and error reason are identified in the service principal log stream.
  2. A customer tenant administrator can revoke the app's local access without altering the supplier registration.
  3. Consent records show authorized approval and the application uses the narrower intended permission.
  4. The daemon accesses only approved Graph resources without impersonating an absent signed-in user.

Explanation

Correct Answer

D:

This validates the specific control for delegated versus application api permissions: Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. The associated corrective action is: Select approved application permissions with administrator consent and configure client-credentials access. Testing a different component would not establish this result.

Incorrect Answers

A:

Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. “Inspect service principal sign-in logs and correlated credential or conditional policy results” 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.

B:

“Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles” responds to this separate finding: cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. 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.

C:

The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. “Have an authorized administrator evaluate and grant only the required application permission after review” 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 605

A Microsoft Azure administrator receives this requirement: Employees register phishing-resistant security keys without a documented lost-key replacement process, creating risky manual bypasses when devices are lost. What should the engineer implement first to address the weakness?

  1. Include the intended enterprise application or cloud resource in the Conditional Access assignment.
  2. Add an appropriately scoped Conditional Access grant control requiring a compliant device, with emergency exceptions.
  3. Update the trusted named location with validated new egress ranges and test the affected policy conditions.
  4. Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification.

Explanation

Correct Answer

D:

The cause is: Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. The appropriate change is: Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification. Verify it with this outcome: A lost key can be revoked and replaced without allowing unverified MFA bypass.

Incorrect Answers

A:

This action concerns conditional access cloud app targeting, where The target cloud application selection is wrong and policy enforcement does not cover the actual resource. The reported incident instead involves Strong authentication adoption lacks an approved registration, recovery and revocation lifecycle.

B:

This action concerns require compliant device condition, where The Conditional Access policy does not require a compliant or otherwise approved managed device for this privileged workflow. The corrective response here is “Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification”; this alternative does not provide that response.

C:

This action concerns named location ipv4 range update, where The named location definition is stale and no longer reflects current verified branch egress address ranges. The stem reports employees register phishing-resistant security keys without a documented lost-key replacement process, creating risky manual bypasses when devices are lost; this control addresses a different failure condition.

Question 606

An Azure security engineer investigates the following incident: A client attempts to mount Azure Files using an obsolete insecure SMB configuration and cannot meet company encryption and authentication requirements. Which remediation best addresses the specific issue?

  1. Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration.
  2. Use supported modern SMB client configuration and private connectivity or TLS where applicable.
  3. Configure supported SQL driver encryption with certificate chain and hostname validation enabled.
  4. Enable supported SQL auditing with the necessary categories and protected retention settings.

Explanation

Correct Answer

B:

The cause is: The file access path needs compatible secure SMB protocol and supported encrypted transport settings. The appropriate change is: Use supported modern SMB client configuration and private connectivity or TLS where applicable. Verify it with this outcome: An eligible client mounts the share securely while outdated unencrypted access fails.

Incorrect Answers

A:

This action concerns transparent data encryption at rest, where TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. The reported incident instead involves The file access path needs compatible secure SMB protocol and supported encrypted transport settings.

C:

This action concerns azure sql network tls encryption, where Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. The corrective response here is “Use supported modern SMB client configuration and private connectivity or TLS where applicable”; this alternative does not provide that response.

D:

This action concerns azure sql auditing destination configuration, where Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. The stem reports a client attempts to mount Azure Files using an obsolete insecure SMB configuration and cannot meet company encryption and authentication requirements; this control addresses a different failure condition.

Question 607

While validating an Azure workload, the security team finds: An Azure App Service managed identity has Contributor on its resource group but fails to read a secret from an RBAC-enabled Key Vault. Which explanation fits the observed symptoms most closely?

  1. A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal.
  2. No effective user-risk-based identity protection response has been configured for the relevant identities.
  3. Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model.
  4. The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy.

Explanation

Correct Answer

C:

The described technical condition is: Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. The appropriate corrective action is: Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity. Confirm with: The application resolves the required secret without receiving broad Key Vault management permission.

Incorrect Answers

A:

A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. “Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal” would address that alternative cause, not the condition in this question: resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model.

B:

“Configure a supported user risk remediation policy that invokes secure password change or blocking as appropriate” responds to this separate finding: no effective user-risk-based identity protection response has been configured for the relevant identities. This question instead needs “Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity”, 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 an Azure App Service managed identity has Contributor on its resource group but fails to read a secret from an RBAC-enabled Key Vault; choosing this alternative would address the wrong failure mode.

Question 608

A regulated Azure tenant has this security condition: A network security monitoring pipeline forwards full raw payload fields into an analytics workspace even though policy permits only necessary metadata. Which explanation fits the observed symptoms most closely?

  1. Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained.
  2. Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions.
  3. Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation.
  4. Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality.

Explanation

Correct Answer

A:

The described technical condition is: Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. The appropriate corrective action is: Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema. Confirm with: Representative security events remain analyzable without exposing the prohibited personal payload fields.

Incorrect Answers

B:

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” would address that alternative cause, not the condition in this question: unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained.

C:

“Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics” responds to this separate finding: threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. This question instead needs “Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema”, so the alternative does not meet the stated condition.

D:

Watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. “Normalize and join supported account identifiers and watchlist keys, then test expected variants and false matches” applies to that separate problem. The observed case is a network security monitoring pipeline forwards full raw payload fields into an analytics workspace even though policy permits only necessary metadata; choosing this alternative would address the wrong failure mode.

Question 609

The cloud operations team reviews the following risk: A security analyst concludes there are no vulnerable resources because the Defender inventory is filtered to a single region rather than the global workload footprint. Which safeguard would best prevent this issue from recurring?

  1. Use independent configuration verification and record assessment timestamps when validating urgent posture remediations.
  2. Document inventory filter parameters alongside every exported compliance or exposure report.
  3. Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts.
  4. Revalidate exemption evidence and age periodically so exceptions do not mask ongoing exposure.

Explanation

Correct Answer

B:

This guardrail addresses defender for cloud inventory filters multi-region: Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. The prevention measure is: Document inventory filter parameters alongside every exported compliance or exposure report. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Defender posture assessments may reevaluate asynchronously, so a stale dashboard can lag the actual configuration change. “Use independent configuration verification and record assessment timestamps when validating urgent posture remediations” would address that alternative cause, not the condition in this question: inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types.

C:

“Review remediation priorities using both exposure severity and secure-score recommendations rather than only total finding counts” responds to this separate finding: secure score is based on security-control recommendations and affected resources, not just a raw count of findings. This question instead needs “Document inventory filter parameters alongside every exported compliance or exposure report”, so the alternative does not meet the stated condition.

D:

An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. “Revalidate exemption evidence and age periodically so exceptions do not mask ongoing exposure” applies to that separate problem. The observed case is a security analyst concludes there are no vulnerable resources because the Defender inventory is filtered to a single region rather than the global workload footprint; choosing this alternative would address the wrong failure mode.

Question 610

A regulated Azure tenant has this security condition: A workload can reach one internal service but not another, and the incident team repeatedly edits a single NSG without checking inherited or parallel network controls. Which configuration change most directly resolves this problem?

  1. Remove or narrow the broad allow rule and position the applicable deny ahead of competing permissive rules.
  2. Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision.
  3. Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs.
  4. Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP.

Explanation

Correct Answer

B:

The cause is: The active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view. The appropriate change is: Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision. Verify it with this outcome: The diagnostic result identifies the NSG rule responsible and the approved flow passes after targeted remediation.

Incorrect Answers

A:

This action concerns nsg rule priority and first matching decision, where Network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny. The reported incident instead involves The active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view.

C:

This action concerns vnet peering forwarded traffic setting, where The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. The corrective response here is “Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision”; this alternative does not provide that response.

D:

This action concerns user defined default route to inspection, where No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. The stem reports a workload can reach one internal service but not another, and the incident team repeatedly edits a single NSG without checking inherited or parallel network controls; this control addresses a different failure condition.