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 42

Question 410

The cloud operations team reviews the following risk: A public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources. What governance practice would best prevent the same failure?

  1. Reassess API throttling limits and correlation identifiers following traffic-pattern changes.
  2. Review client certificate trust and renewal processes for all privileged API consumers.
  3. Test negative token cases after identity provider and APIM policy changes.
  4. Review APIM API and product access configuration when introducing new routes.

Explanation

Correct Answer

A:

This guardrail addresses apim throttling policy for abuse: The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. The prevention measure is: Reassess API throttling limits and correlation identifiers following traffic-pattern changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The API gateway has not enforced the required mutual TLS certificate validation for partner clients. “Review client certificate trust and renewal processes for all privileged API consumers” would address that alternative cause, not the condition in this question: the API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.

C:

“Test negative token cases after identity provider and APIM policy changes” responds to this separate finding: aPI Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. This question instead needs “Reassess API throttling limits and correlation identifiers following traffic-pattern changes”, so the alternative does not meet the stated condition.

D:

The API or product does not require the intended APIM subscription key or equivalent authentication control. “Review APIM API and product access configuration when introducing new routes” applies to that separate problem. The observed case is a public API permits one compromised client to issue thousands of expensive requests per second, exhausting shared backend resources; choosing this alternative would address the wrong failure mode.

Question 411

A Microsoft Azure administrator receives this requirement: An external partner receives a long-lived SAS token with unrestricted permissions and broad network access for a short upload job. Which underlying control gap is responsible for the issue?

  1. Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account.
  2. The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control.
  3. The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose.
  4. Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone.

Explanation

Correct Answer

C:

The described technical condition is: The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. The appropriate corrective action is: Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions. Confirm with: The partner uploads an authorized object before expiry and cannot delete unrelated blobs or reuse an expired token.

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: the SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose.

B:

“Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS” responds to this separate finding: the account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. This question instead needs “Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions”, so the alternative does not meet the stated condition.

D:

Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. “Configure the appropriate time-based immutability policy or legal hold for the protected container” applies to that separate problem. The observed case is an external partner receives a long-lived SAS token with unrestricted permissions and broad network access for a short upload job; choosing this alternative would address the wrong failure mode.

Question 412

During a cloud security review, the operations team observes: An attacker overwrites a blob with incorrect content but its latest object still exists, and administrators have no prior version to restore. Which underlying control gap is responsible for the issue?

  1. The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control.
  2. The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose.
  3. Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning.
  4. The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks.

Explanation

Correct Answer

C:

The described technical condition is: Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The appropriate corrective action is: Enable supported blob versioning and define backup or lifecycle protection for critical objects. Confirm with: A test overwrite creates a retrievable previous version that administrators can restore.

Incorrect Answers

A:

The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. “Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS” would address that alternative cause, not the condition in this question: blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning.

B:

“Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions” responds to this separate finding: the SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. This question instead needs “Enable supported blob versioning and define backup or lifecycle protection for critical objects”, so the alternative does not meet the stated condition.

D:

The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. “Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required” applies to that separate problem. The observed case is an attacker overwrites a blob with incorrect content but its latest object still exists, and administrators have no prior version to restore; choosing this alternative would address the wrong failure mode.

Question 413

An Azure security engineer investigates the following incident: An Azure Function accesses a private SQL backend but its outbound requests fail after the SQL resource is moved behind Private Link. What governance practice would best prevent the same failure?

  1. Review WAF mode, tuning and false-positive impact before promoting a policy to production.
  2. Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services.
  3. Test regional edge WAF policies with representative client source conditions and observe false positives.
  4. Test TLS protocol settings and certificate expiry after changes to public application endpoints.

Explanation

Correct Answer

B:

This guardrail addresses azure functions private service access: The function hosting plan and network integration/DNS are not configured for the required private destination. The prevention measure is: Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. “Review WAF mode, tuning and false-positive impact before promoting a policy to production” would address that alternative cause, not the condition in this question: the function hosting plan and network integration/DNS are not configured for the required private destination.

C:

“Test regional edge WAF policies with representative client source conditions and observe false positives” responds to this separate finding: the access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. This question instead needs “Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services”, 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. “Test TLS protocol settings and certificate expiry after changes to public application endpoints” applies to that separate problem. The observed case is an Azure Function accesses a private SQL backend but its outbound requests fail after the SQL resource is moved behind Private Link; choosing this alternative would address the wrong failure mode.

Question 414

The cloud operations team reviews the following risk: An application uses a custom hostname but presents an unrelated default certificate, causing client hostname validation failures. Which configuration change most directly resolves this problem?

  1. Bind a valid certificate to the custom hostname using an approved App Service certificate mechanism.
  2. Configure backend HTTPS with appropriate certificate trust and listener/backend settings.
  3. Configure a supported APIM private networking option and restrict public gateway exposure as required.
  4. Set the supported minimum TLS version to an approved modern value and verify certificate configuration.

Explanation

Correct Answer

A:

The cause is: The custom domain has no correct TLS certificate binding for the expected host name. The appropriate change is: Bind a valid certificate to the custom hostname using an approved App Service certificate mechanism. Verify it with this outcome: TLS clients validate the intended hostname and chain without accepting certificate warnings.

Incorrect Answers

B:

This action concerns application gateway end to end tls, where Backend HTTP settings do not enforce the required HTTPS connection to backend servers. The reported incident instead involves The custom domain has no correct TLS certificate binding for the expected host name.

C:

This action concerns api management private network access, where The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. The corrective response here is “Bind a valid certificate to the custom hostname using an approved App Service certificate mechanism”; this alternative does not provide that response.

D:

This action concerns minimum tls protocol enforcement, where The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. The stem reports an application uses a custom hostname but presents an unrelated default certificate, causing client hostname validation failures; this control addresses a different failure condition.

Question 415

An Azure security engineer investigates the following incident: File-share users access Azure Files with a shared storage account key even though access must follow corporate user identities and ACLs. Which explanation fits the observed symptoms most closely?

  1. Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model.
  2. SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege.
  3. Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.
  4. TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.

Explanation

Correct Answer

A:

The described technical condition is: Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. The appropriate corrective action is: Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs. Confirm with: Approved users mount the file share with identities and cannot read restricted directories.

Incorrect Answers

B:

SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. “Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers” would address that alternative cause, not the condition in this question: shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model.

C:

“Configure supported SQL driver encryption with certificate chain and hostname validation enabled” responds to this separate finding: encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. This question instead needs “Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs”, so the alternative does not meet the stated condition.

D:

TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration” applies to that separate problem. The observed case is file-share users access Azure Files with a shared storage account key even though access must follow corporate user identities and ACLs; choosing this alternative would address the wrong failure mode.

Question 416

An Azure security engineer investigates the following incident: A security team allows all Internet outbound destinations because a VM must access Azure Storage, bypassing an existing policy intended to restrict egress. Which safeguard would best prevent this issue from recurring?

  1. Review FQDN-based application rules for wildcard overreach and domain ownership changes.
  2. Audit shared gateway peering settings whenever a new spoke joins the hub.
  3. Review exposed DNAT entries against asset owners and remove obsolete Internet listeners.
  4. Review service tag selection, platform limitations and least-privilege egress regularly.

Explanation

Correct Answer

D:

This guardrail addresses service tag outbound allow scoping: A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. The prevention measure is: Review service tag selection, platform limitations and least-privilege egress regularly. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. “Review FQDN-based application rules for wildcard overreach and domain ownership changes” would address that alternative cause, not the condition in this question: a broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges.

B:

“Audit shared gateway peering settings whenever a new spoke joins the hub” responds to this separate finding: gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. This question instead needs “Review service tag selection, platform limitations and least-privilege egress regularly”, so the alternative does not meet the stated condition.

C:

Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. “Review exposed DNAT entries against asset owners and remove obsolete Internet listeners” applies to that separate problem. The observed case is a security team allows all Internet outbound destinations because a VM must access Azure Storage, bypassing an existing policy intended to restrict egress; choosing this alternative would address the wrong failure mode.

Question 417

A Microsoft Azure administrator receives this requirement: A newly provisioned VNet fails to receive expected global security configuration because it does not meet the membership condition of the assigned Network Manager group. Which recurring validation best protects against the observed problem?

  1. Review network group membership drift after subscription and resource tagging changes.
  2. Audit shared gateway peering settings whenever a new spoke joins the hub.
  3. Document and test non-transitive peerings before granting inter-spoke network access.
  4. Track central security admin policy impacts before granting application network exceptions.

Explanation

Correct Answer

A:

This guardrail addresses virtual network manager dynamic network group: The dynamic network group criteria do not include the intended VNet attributes or scope. The prevention measure is: Review network group membership drift after subscription and resource tagging changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. “Audit shared gateway peering settings whenever a new spoke joins the hub” would address that alternative cause, not the condition in this question: the dynamic network group criteria do not include the intended VNet attributes or scope.

C:

“Document and test non-transitive peerings before granting inter-spoke network access” responds to this separate finding: vNet peering does not inherently create transitive routing between other independently peered VNets. This question instead needs “Review network group membership drift after subscription and resource tagging changes”, so the alternative does not meet the stated condition.

D:

An enforced security admin deny rule has higher governance precedence than the workload NSG allow. “Track central security admin policy impacts before granting application network exceptions” applies to that separate problem. The observed case is a newly provisioned VNet fails to receive expected global security configuration because it does not meet the membership condition of the assigned Network Manager group; choosing this alternative would address the wrong failure mode.

Question 418

During a cloud security review, the operations team observes: A regulated VM disk must use organization-controlled encryption keys but a team assumes a Key Vault secret access policy alone attaches the key to a disk. After remediation, which test result best proves the intended change?

  1. The disk references the approved encryption set and retains correct key-access connectivity.
  2. The port opens only for an approved source and limited interval, then closes automatically.
  3. Approved administrators reach private VMs using Bastion while direct Internet RDP and SSH attempts fail.
  4. A test request from the approved address succeeds temporarily while arbitrary Internet sources remain denied.

Explanation

Correct Answer

A:

This validates the specific control for disk customer managed key disk encryption set: Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The associated corrective action is: Configure the encryption set and supported Key Vault key permissions, then associate eligible disks. Testing a different component would not establish this result.

Incorrect Answers

B:

The VM's NSG exposes a persistent management port rather than enforcing just-in-time access. “Configure supported just-in-time VM access and remove persistent open management rules” would address that alternative cause, not the condition in this question: azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access.

C:

“Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules” responds to this separate finding: direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. This question instead needs “Configure the encryption set and supported Key Vault key permissions, then associate eligible disks”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a regulated VM disk must use organization-controlled encryption keys but a team assumes a Key Vault secret access policy alone attaches the key to a disk; choosing this alternative would address the wrong failure mode.

Question 419

A Microsoft Azure administrator receives this requirement: A team monitors database firewall access but has no alerting for anomalous SQL injection or suspicious database sign-ins. After remediation, which test result best proves the intended change?

  1. The server protection dashboard reports the selected plan and expected supported security features for enrolled machines.
  2. A safe simulated anomalous database activity test generates the expected protection alert without changing legitimate data.
  3. The cluster reports supported posture assessments and security alerts for its monitored Kubernetes workloads.
  4. An eligible Defender alert appears in Sentinel with its workload context and appropriate incident correlation.

Explanation

Correct Answer

B:

This validates the specific control for microsoft defender for databases sql coverage: Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. The associated corrective action is: Enable the appropriate Defender for SQL or Databases protection plan and configure supported alert routing. Testing a different component would not establish this result.

Incorrect Answers

A:

Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. “Compare required features to current Defender for Servers plans and enable the appropriate supported tier for governed machines” would address that alternative cause, not the condition in this question: database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan.

C:

“Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster” responds to this separate finding: node management alone does not provide full supported Defender for Containers security posture and workload protection. This question instead needs “Enable the appropriate Defender for SQL or Databases protection plan and configure supported alert routing”, so the alternative does not meet the stated condition.

D:

Defender protection alerts need the supported connector or integration to reach the chosen Sentinel workspace. “Enable the relevant Defender for Cloud or Microsoft Defender connector and verify authorized workspace ingestion” applies to that separate problem. The observed case is a team monitors database firewall access but has no alerting for anomalous SQL injection or suspicious database sign-ins; choosing this alternative would address the wrong failure mode.

Question 420

The cloud operations team reviews the following risk: An automated report job has Storage Account Contributor but HTTP blob reads fail with authorization errors under Microsoft Entra tokens. What governance practice would best prevent the same failure?

  1. Test WORM retention enforcement and approved release procedures before storing regulated records.
  2. Test customer-managed key rotation and access recovery before changing storage encryption configuration.
  3. Review data-plane RBAC separately from account administration roles for every application.
  4. Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry.

Explanation

Correct Answer

C:

This guardrail addresses blob storage data rbac: Management-plane storage Contributor does not necessarily include blob data read DataActions. The prevention measure is: Review data-plane RBAC separately from account administration roles for every application. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. “Test WORM retention enforcement and approved release procedures before storing regulated records” would address that alternative cause, not the condition in this question: management-plane storage Contributor does not necessarily include blob data read DataActions.

B:

“Test customer-managed key rotation and access recovery before changing storage encryption configuration” 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 “Review data-plane RBAC separately from account administration roles for every application”, so the alternative does not meet the stated condition.

D:

Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. “Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry” applies to that separate problem. The observed case is an automated report job has Storage Account Contributor but HTTP blob reads fail with authorization errors under Microsoft Entra tokens; choosing this alternative would address the wrong failure mode.