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 72

Question 710

A production Azure security implementation shows this failure: An unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events. What should the engineer implement first to address the weakness?

  1. Establish the approved multi-tenant consent and configure the consuming tenant's local service principal roles.
  2. Inspect service principal sign-in logs and correlated credential or conditional policy results.
  3. Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow.
  4. Define and publish the intended API scope and update client permissions and authorization enforcement.

Explanation

Correct Answer

B:

The cause is: Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. The appropriate change is: Inspect service principal sign-in logs and correlated credential or conditional policy results. Verify it with this outcome: The failing app identity, time and error reason are identified in the service principal log stream.

Incorrect Answers

A:

This action concerns cross tenant service principal consent, where Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The reported incident instead involves Non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views.

C:

This action concerns user consent policies for third party apps, where The user consent configuration permits risky OAuth grants without publisher and permission restrictions. The corrective response here is “Inspect service principal sign-in logs and correlated credential or conditional policy results”; this alternative does not provide that response.

D:

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 unattended application intermittently fails token requests, but the incident team searches only interactive user sign-in events; this control addresses a different failure condition.

Question 711

While validating an Azure workload, the security team finds: A SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation. Which configuration change most directly resolves this problem?

  1. Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls.
  2. Correct the custom health probe to match the actual service endpoint and backend settings.
  3. After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener.
  4. Create the approved Front Door WAF geographic match rule with a documented action and exclusions.

Explanation

Correct Answer

A:

The cause is: SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The appropriate change is: Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls. Verify it with this outcome: The managed instance deploys in the intended delegated subnet and responds only to permitted connections.

Incorrect Answers

B:

This action concerns application gateway backend health probes, where The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. The reported incident instead involves SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.

C:

This action concerns application gateway waf detection versus prevention, where The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. The corrective response here is “Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls”; this alternative does not provide that response.

D:

This action concerns front door waf geographic access controls, where The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. The stem reports a SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation; this control addresses a different failure condition.

Question 712

The cloud operations team reviews the following risk: A VM scanner lists a high-severity operating system vulnerability and the operator closes the ticket without applying any patch. What governance practice would best prevent the same failure?

  1. Link vulnerability closure to post-remediation evidence rather than administrative ticket state alone.
  2. Check DevOps project onboarding, repository scanning and governance assignments before each release.
  3. Include App Service protection in onboarding checks for Internet-exposed web applications.
  4. Revalidate security connector coverage as repositories move between GitHub, Azure DevOps and GitLab.

Explanation

Correct Answer

A:

This guardrail addresses defender vulnerability management remediation validation: A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The prevention measure is: Link vulnerability closure to post-remediation evidence rather than administrative ticket state alone. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. “Check DevOps project onboarding, repository scanning and governance assignments before each release” would address that alternative cause, not the condition in this question: a vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified.

C:

“Include App Service protection in onboarding checks for Internet-exposed web applications” responds to this separate finding: inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. This question instead needs “Link vulnerability closure to post-remediation evidence rather than administrative ticket state alone”, so the alternative does not meet the stated condition.

D:

Code security inventory and posture coverage depend on a supported connector for the actual source-control platform. “Revalidate security connector coverage as repositories move between GitHub, Azure DevOps and GitLab” applies to that separate problem. The observed case is a VM scanner lists a high-severity operating system vulnerability and the operator closes the ticket without applying any patch; choosing this alternative would address the wrong failure mode.

Question 713

The cloud operations team reviews the following risk: A Kubernetes control-plane API endpoint is reachable from the public Internet even though the application platform requires private administration. Which safeguard would best prevent this issue from recurring?

  1. Use private API endpoint requirements during AKS cluster provisioning and access reviews.
  2. Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates.
  3. Test backup restore and deletion resistance periodically under approved adversarial scenarios.
  4. Audit service accounts and federated identity subjects when deploying workload identities.

Explanation

Correct Answer

A:

This guardrail addresses aks private cluster control plane: The cluster uses a public API server endpoint rather than a supported private AKS cluster design. The prevention measure is: Use private API endpoint requirements during AKS cluster provisioning and access reviews. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. “Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates” would address that alternative cause, not the condition in this question: the cluster uses a public API server endpoint rather than a supported private AKS cluster design.

C:

“Test backup restore and deletion resistance periodically under approved adversarial scenarios” responds to this separate finding: backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. This question instead needs “Use private API endpoint requirements during AKS cluster provisioning and access reviews”, so the alternative does not meet the stated condition.

D:

The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. “Audit service accounts and federated identity subjects when deploying workload identities” applies to that separate problem. The observed case is a Kubernetes control-plane API endpoint is reachable from the public Internet even though the application platform requires private administration; choosing this alternative would address the wrong failure mode.

Question 714

A Microsoft Azure administrator receives this requirement: An application issues shared-key SAS tokens to end users while security requires tokens to derive from Microsoft Entra authorization. What technical cause best accounts for the described behavior?

  1. Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account.
  2. The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks.
  3. Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model.
  4. Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning.

Explanation

Correct Answer

C:

The described technical condition is: Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. The appropriate corrective action is: Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege. Confirm with: A delegated client accesses only intended blobs without possession of the storage account key.

Incorrect Answers

A:

Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. “Configure customer-managed key encryption and grant the storage account identity the required key permissions” would address that alternative cause, not the condition in this question: account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model.

B:

“Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required” responds to this separate finding: the storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. This question instead needs “Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege”, 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 an application issues shared-key SAS tokens to end users while security requires tokens to derive from Microsoft Entra authorization; choosing this alternative would address the wrong failure mode.

Question 715

While validating an Azure workload, the security team finds: A VM cannot reach a backend on TCP 5432, and an operator keeps guessing which NSG is responsible without testing effective decisions. Which result confirms the relevant security control is effective?

  1. The identified next hop matches the approved routing design after changes, with no unintended appliance loop.
  2. The security team queries the required firewall rule-match records for a controlled test flow.
  3. Diagnostics identify the exact applicable rule and the corrected flow matches approved connectivity.
  4. Security inventory shows production VNets under the required DDoS protection configuration.

Explanation

Correct Answer

C:

This validates the specific control for network watcher ip flow verification: The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. The associated corrective action is: Run Network Watcher IP flow verify with the test source, destination, direction and port. Testing a different component would not establish this result.

Incorrect Answers

A:

A user-defined or propagated route controls the next hop independently of NSG allow decisions. “Inspect effective routes and run Network Watcher next hop against the intended destination IP” would address that alternative cause, not the condition in this question: the blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template.

B:

“Configure relevant firewall diagnostic categories and secure retention for rule and threat events” responds to this separate finding: required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. This question instead needs “Run Network Watcher IP flow verify with the test source, destination, direction and port”, so the alternative does not meet the stated condition.

D:

Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. “Associate intended eligible VNets with the correct plan and validate protection settings” applies to that separate problem. The observed case is a VM cannot reach a backend on TCP 5432, and an operator keeps guessing which NSG is responsible without testing effective decisions; choosing this alternative would address the wrong failure mode.

Question 716

A Microsoft Azure administrator receives this requirement: An administrator opens a public RDP endpoint on every production VM even though security rules prohibit direct Internet-facing management ports. What observation is the strongest validation evidence?

  1. Approved administrators reach private VMs using Bastion while direct Internet RDP and SSH attempts fail.
  2. A test request from the approved address succeeds temporarily while arbitrary Internet sources remain denied.
  3. The disk references the approved encryption set and retains correct key-access connectivity.
  4. A test VM reports the intended confidential security posture and protected boot chain.

Explanation

Correct Answer

A:

This validates the specific control for azure bastion without public vm ip: Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. The associated corrective action is: Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules. Testing a different component would not establish this result.

Incorrect Answers

B:

JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. “Require authorized per-user JIT requests with the narrowest permitted source IP range and short duration” would address that alternative cause, not the condition in this question: direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections.

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 “Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules”, so the alternative does not meet the stated condition.

D:

Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory. “Choose supported confidential VM features and configure the correct security type and encryption settings” applies to that separate problem. The observed case is an administrator opens a public RDP endpoint on every production VM even though security rules prohibit direct Internet-facing management ports; choosing this alternative would address the wrong failure mode.

Question 717

A Microsoft Azure administrator receives this requirement: Azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week. Which recurring validation best protects against the observed problem?

  1. Audit DDoS resource coverage whenever a public service or subscription is added.
  2. Separate route next-hop verification from access-control rule checks in network troubleshooting.
  3. Verify firewall diagnostic export completeness after routing or workspace configuration changes.
  4. Test origin bypass routes as part of every public application security assessment.

Explanation

Correct Answer

C:

This guardrail addresses firewall diagnostic settings and retention: Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. The prevention measure is: Verify firewall diagnostic export completeness after routing or workspace configuration changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Purchasing a DDoS protection plan does not automatically enable the intended plan-based coverage on every relevant VNet. “Audit DDoS resource coverage whenever a public service or subscription is added” would address that alternative cause, not the condition in this question: required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination.

B:

“Separate route next-hop verification from access-control rule checks in network troubleshooting” responds to this separate finding: a user-defined or propagated route controls the next hop independently of NSG allow decisions. This question instead needs “Verify firewall diagnostic export completeness after routing or workspace configuration changes”, so the alternative does not meet the stated condition.

D:

The origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. “Test origin bypass routes as part of every public application security assessment” applies to that separate problem. The observed case is azure Firewall policies enforce outbound access but the security team cannot reconstruct which rule allowed a suspicious transfer last week; choosing this alternative would address the wrong failure mode.

Question 718

A regulated Azure tenant has this security condition: A Virtual WAN deployment relies on branch-created firewall rules at every spoke despite a requirement to manage inspection centrally in secured virtual hubs. What governance practice would best prevent the same failure?

  1. Review point-to-site authentication configuration and certificate or client profile lifecycle regularly.
  2. Audit VPN peer cryptographic settings and key rotation after device upgrades.
  3. Review secured hub routing and policy coverage during each new Virtual WAN attachment.
  4. Periodically validate threat intelligence enforcement mode and false-positive handling.

Explanation

Correct Answer

C:

This guardrail addresses firewall manager secured virtual hub: The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. The prevention measure is: Review secured hub routing and policy coverage during each new Virtual WAN attachment. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The point-to-site VPN design lacks supported per-user Microsoft Entra authentication and controlled client configuration. “Review point-to-site authentication configuration and certificate or client profile lifecycle regularly” would address that alternative cause, not the condition in this question: the topology lacks the intended central security policy and routing intent in Azure Firewall Manager.

B:

“Audit VPN peer cryptographic settings and key rotation after device upgrades” responds to this separate finding: the VPN gateway and customer edge have incompatible IKE or IPsec proposal settings. This question instead needs “Review secured hub routing and policy coverage during each new Virtual WAN attachment”, so the alternative does not meet the stated condition.

D:

The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. “Periodically validate threat intelligence enforcement mode and false-positive handling” applies to that separate problem. The observed case is a Virtual WAN deployment relies on branch-created firewall rules at every spoke despite a requirement to manage inspection centrally in secured virtual hubs; choosing this alternative would address the wrong failure mode.

Question 719

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. Which recurring validation best protects against the observed problem?

  1. Validate custom-role definitions through effective permission tests before applying them widely.
  2. Review management group hierarchy and inherited read-only roles whenever tenant organization changes.
  3. Require just-in-time activation for high-impact Azure roles rather than granting persistent standing access.
  4. Test conditioned Azure RBAC access against both permitted and forbidden resource attributes.

Explanation

Correct Answer

B:

This guardrail addresses management group security assignment: Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The prevention measure is: Review management group hierarchy and inherited read-only roles whenever tenant organization changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. “Validate custom-role definitions through effective permission tests before applying them widely” 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:

“Require just-in-time activation for high-impact Azure roles rather than granting persistent standing access” responds to this separate finding: a PIM eligible assignment is not an active role grant until the user completes the configured activation process. This question instead needs “Review management group hierarchy and inherited read-only roles whenever tenant organization changes”, so the alternative does not meet the stated condition.

D:

A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Test conditioned Azure RBAC access against both permitted and forbidden resource attributes” 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 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.