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 74

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.

Question 731

An Azure security engineer investigates the following incident: A workload reaches approved web APIs but an administrator adds a network rule permitting every public IP in an ASN rather than the business service hostnames. Which configuration change most directly resolves this problem?

  1. Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy.
  2. Correct the group membership query or approved explicit membership and deploy the security configuration.
  3. Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints.
  4. Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow.

Explanation

Correct Answer

A:

The cause is: A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. The appropriate change is: Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy. Verify it with this outcome: Approved HTTPS hosts are reachable and unrelated hosts in the same IP ranges are rejected.

Incorrect Answers

B:

This action concerns virtual network manager dynamic network group, where The dynamic network group criteria do not include the intended VNet attributes or scope. The reported incident instead involves A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering.

C:

This action concerns gateway transit peering configuration, where Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The corrective response here is “Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy”; this alternative does not provide that response.

D:

This action concerns azure firewall network rule ip protocol, where An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. The stem reports a workload reaches approved web APIs but an administrator adds a network rule permitting every public IP in an ASN rather than the business service hostnames; this control addresses a different failure condition.

Question 732

While validating an Azure workload, the security team finds: Two site-to-site VPN peers disagree on encryption and integrity parameters, preventing IKE negotiation even though their public endpoints are reachable. Which condition most directly explains the failure?

  1. The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings.
  2. The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior.
  3. Azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions.
  4. The topology lacks the intended central security policy and routing intent in Azure Firewall Manager.

Explanation

Correct Answer

A:

The described technical condition is: The VPN gateway and customer edge have incompatible IKE or IPsec proposal settings. The appropriate corrective action is: Align supported IPsec/IKE policy, keys and proposal parameters between the two authorized peers. Confirm with: The tunnel establishes with the intended cryptographic suite and routes pass protected traffic.

Incorrect Answers

B:

The configured threat intelligence mode is alert-only rather than the approved alert-and-deny behavior. “Enable the authorized threat intelligence alert-and-deny mode with appropriate exceptions and validation” would address that alternative cause, not the condition in this question: the VPN gateway and customer edge have incompatible IKE or IPsec proposal settings.

C:

“Review inherited policy evaluation and adjust approved parent or child rule design with central authorization” responds to this separate finding: azure Firewall Policy hierarchy evaluates parent policy controls before child configuration and can prevent local exceptions. This question instead needs “Align supported IPsec/IKE policy, keys and proposal parameters between the two authorized peers”, so the alternative does not meet the stated condition.

D:

The topology lacks the intended central security policy and routing intent in Azure Firewall Manager. “Configure a supported secured virtual hub with firewall policy and routing intent for inspected traffic” applies to that separate problem. The observed case is two site-to-site VPN peers disagree on encryption and integrity parameters, preventing IKE negotiation even though their public endpoints are reachable; choosing this alternative would address the wrong failure mode.

Question 733

A Microsoft Azure administrator receives this requirement: An externally hosted user connects to a firewall public IP and port but never reaches the internal application service because no translation rule exists. Which underlying control gap is responsible for the issue?

  1. A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering.
  2. Saving network manager intent does not itself apply connectivity or security configuration to target regions.
  3. Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port.
  4. An enforced security admin deny rule has higher governance precedence than the workload NSG allow.

Explanation

Correct Answer

C:

The described technical condition is: Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. The appropriate corrective action is: Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service. Confirm with: The published external endpoint reaches only the approved internal listener and is logged.

Incorrect Answers

A:

A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. “Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy” would address that alternative cause, not the condition in this question: inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port.

B:

“Deploy the approved configuration to the correct regions and verify the deployed state” responds to this separate finding: saving network manager intent does not itself apply connectivity or security configuration to target regions. This question instead needs “Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service”, 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. “Change the governing security admin policy through approved central administration rather than widening local NSGs” applies to that separate problem. The observed case is an externally hosted user connects to a firewall public IP and port but never reaches the internal application service because no translation rule exists; choosing this alternative would address the wrong failure mode.

Question 734

An Azure security engineer investigates the following incident: A protected API receives requests with expired or incorrectly signed bearer tokens but the gateway forwards them unchecked. Which safeguard would best prevent this issue from recurring?

  1. Separate build-pipeline image publishing identity from runtime image-pull identity.
  2. Review ACR admin user state and rotate or remove unused registry credentials.
  3. Maintain owner-assigned storage key rotation plans and detect dependencies on old keys.
  4. Test negative token cases after identity provider and APIM policy changes.

Explanation

Correct Answer

D:

This guardrail addresses api management validate jwt policy: API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. The prevention measure is: Test negative token cases after identity provider and APIM policy changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The workload has an overly broad registry data role instead of the necessary pull-only authorization. “Separate build-pipeline image publishing identity from runtime image-pull identity” would address that alternative cause, not the condition in this question: aPI Management does not have the necessary JWT signature, issuer, audience and expiration validation policy.

B:

“Review ACR admin user state and rotate or remove unused registry credentials” responds to this separate finding: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. This question instead needs “Test negative token cases after identity provider and APIM policy changes”, so the alternative does not meet the stated condition.

C:

The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. “Maintain owner-assigned storage key rotation plans and detect dependencies on old keys” applies to that separate problem. The observed case is a protected API receives requests with expired or incorrectly signed bearer tokens but the gateway forwards them unchecked; choosing this alternative would address the wrong failure mode.

Question 735

A regulated Azure tenant has this security condition: A regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints. Which outcome most clearly verifies that the issue is resolved?

  1. Confirmed owned exposures enter the remediation queue while unrelated third-party assets are excluded with reasons.
  2. Selected connected AWS instances appear in the correct Defender plan with expected scanning and alert coverage.
  3. The assessment clearly distinguishes justified exceptions from technical fixes and tracks residual risk ownership.
  4. The compliance record distinguishes benchmark guidance from enforceable obligations and documents any controlled exceptions.

Explanation

Correct Answer

D:

This validates the specific control for defender for cloud cloud security benchmark: A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. The associated corrective action is: Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements. Testing a different component would not establish this result.

Incorrect Answers

A:

Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. “Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution” would address that alternative cause, not the condition in this question: a cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation.

B:

“Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances” responds to this separate finding: protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. This question instead needs “Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements”, so the alternative does not meet the stated condition.

C:

An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. “Validate exemption justification, owner, expiry and business controls or actually remediate the resource” applies to that separate problem. The observed case is a regulated team treats the Microsoft Cloud Security Benchmark as a binding statute and applies every recommended setting without considering service constraints; choosing this alternative would address the wrong failure mode.

Question 736

While validating an Azure workload, the security team finds: A private service is reachable from some VMs but times out from a specific subnet, and the team needs path-based evidence of the failure. Which safeguard would best prevent this issue from recurring?

  1. Verify firewall diagnostic export completeness after routing or workspace configuration changes.
  2. Test origin bypass routes as part of every public application security assessment.
  3. Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames.
  4. Retain source-to-destination connection test results for complex hybrid connectivity incidents.

Explanation

Correct Answer

D:

This guardrail addresses connection troubleshoot destination metrics: A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. The prevention measure is: Retain source-to-destination connection test results for complex hybrid connectivity incidents. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. “Verify firewall diagnostic export completeness after routing or workspace configuration changes” would address that alternative cause, not the condition in this question: a point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues.

B:

“Test origin bypass routes as part of every public application security assessment” responds to this separate finding: the origin accepts unauthenticated direct public traffic instead of restricting it to the approved Front Door path. This question instead needs “Retain source-to-destination connection test results for complex hybrid connectivity incidents”, so the alternative does not meet the stated condition.

C:

The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. “Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames” applies to that separate problem. The observed case is a private service is reachable from some VMs but times out from a specific subnet, and the team needs path-based evidence of the failure; choosing this alternative would address the wrong failure mode.

Question 737

While validating an Azure workload, the security team finds: A service experiences intermittent TCP resets, but operators have no packet-level evidence and rely only on Azure resource health statuses. Which result confirms the relevant security control is effective?

  1. A filtered packet trace identifies the reset sender and supports a targeted remediation decision.
  2. The security team queries the required firewall rule-match records for a controlled test flow.
  3. Front Door continues serving approved requests but direct Internet calls to the origin are blocked.
  4. The connection test identifies reachability and applicable hop failures before and after the repair.

Explanation

Correct Answer

A:

This validates the specific control for network watcher packet capture evidence: Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. The associated corrective action is: Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow. Testing a different component would not establish this result.

Incorrect Answers

B:

Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. “Configure relevant firewall diagnostic categories and secure retention for rule and threat events” would address that alternative cause, not the condition in this question: control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets.

C:

“Configure a supported Private Link origin and restrict direct public access to the origin service” responds to this separate finding: the Front Door origin connection is not constrained through a supported private-link origin with public access restriction. This question instead needs “Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow”, so the alternative does not meet the stated condition.

D:

A point-to-point reachability test with hop and latency data is needed to distinguish routing from remote service issues. “Use Network Watcher connection troubleshoot for the source VM and intended destination and inspect diagnostic results” applies to that separate problem. The observed case is a service experiences intermittent TCP resets, but operators have no packet-level evidence and rely only on Azure resource health statuses; choosing this alternative would address the wrong failure mode.

Question 738

A Microsoft Azure administrator receives this requirement: A GitHub Actions deployment stores a long-lived Azure service principal secret as a repository variable and leaked logs risk credential compromise. What observation is the strongest validation evidence?

  1. Consent records show authorized approval and the application uses the narrower intended permission.
  2. A test unverified high-risk application cannot gain requested scopes through ordinary user consent.
  3. Only the approved workflow obtains short-lived Azure tokens without transmitting a static client secret.
  4. The failing app identity, time and error reason are identified in the service principal log stream.

Explanation

Correct Answer

C:

This validates the specific control for workload identity federation in ci pipeline: Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. The associated corrective action is: Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret. Testing a different component would not establish this result.

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: secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra.

B:

“Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow” responds to this separate finding: the user consent configuration permits risky OAuth grants without publisher and permission restrictions. This question instead needs “Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a GitHub Actions deployment stores a long-lived Azure service principal secret as a repository variable and leaked logs risk credential compromise; choosing this alternative would address the wrong failure mode.

Question 739

An Azure security engineer investigates the following incident: A SOC investigates role assignments but sees no Azure subscription management activity in Sentinel despite collecting VM system logs. What governance practice would best prevent the same failure?

  1. Test create and update automation triggers independently after SOC workflow changes.
  2. Include evidence that logs are arriving when implementing new high-impact network policies.
  3. Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated.
  4. Review management-plane telemetry source coverage separately from endpoint and operating-system logs.

Explanation

Correct Answer

D:

This guardrail addresses sentinel azure activity data connector: Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. The prevention measure is: Review management-plane telemetry source coverage separately from endpoint and operating-system logs. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Test create and update automation triggers independently after SOC workflow changes” would address that alternative cause, not the condition in this question: guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions.

B:

“Include evidence that logs are arriving when implementing new high-impact network policies” responds to this separate finding: network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. This question instead needs “Review management-plane telemetry source coverage separately from endpoint and operating-system logs”, so the alternative does not meet the stated condition.

C:

A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated” applies to that separate problem. The observed case is a SOC investigates role assignments but sees no Azure subscription management activity in Sentinel despite collecting VM system logs; choosing this alternative would address the wrong failure mode.

Question 740

A production Azure security implementation shows this failure: A payment system uses an Azure SQL logical server over a public address although its design requires only approved workload subnets to reach database traffic. After remediation, which test result best proves the intended change?

  1. An eligible client mounts the share securely while outdated unencrypted access fails.
  2. Approved users mount the file share with identities and cannot read restricted directories.
  3. Sensitive columns remain encrypted to the database engine while authorized clients decrypt needed values.
  4. The application resolves its SQL host to the private endpoint and Internet SQL connection attempts fail.

Explanation

Correct Answer

D:

This validates the specific control for azure sql private endpoint dns and public disable: The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. The associated corrective action is: Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access. Testing a different component would not establish this result.

Incorrect Answers

A:

The file access path needs compatible secure SMB protocol and supported encrypted transport settings. “Use supported modern SMB client configuration and private connectivity or TLS where applicable” would address that alternative cause, not the condition in this question: the SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction.

B:

“Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs” responds to this separate finding: shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. This question instead needs “Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access”, so the alternative does not meet the stated condition.

C:

TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. “Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients” applies to that separate problem. The observed case is a payment system uses an Azure SQL logical server over a public address although its design requires only approved workload subnets to reach database traffic; choosing this alternative would address the wrong failure mode.