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 67

Question 660

A Microsoft Azure administrator receives this requirement: A business-critical public IP in an Azure VNet is exposed to volumetric attacks but the organization relies only on application WAF rules. What is the most appropriate corrective step?

  1. Use Network Watcher packet capture or an equivalent approved network trace for the affected VM flow.
  2. Inspect effective routes and run Network Watcher next hop against the intended destination IP.
  3. Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources.
  4. Enable the supported Virtual Network flow logs and associated analytics or storage retention.

Explanation

Correct Answer

C:

The cause is: An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs. The appropriate change is: Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources. Verify it with this outcome: A controlled policy review confirms protection coverage and attack telemetry for the targeted public endpoint.

Incorrect Answers

A:

This action concerns network watcher packet capture evidence, where Control-plane resource health does not show the wire-level sequence or endpoint generating TCP resets. The reported incident instead involves An application WAF targets HTTP-layer threats and does not replace supported Azure DDoS network protection for eligible public IPs.

B:

This action concerns network watcher next hop diagnosis, where A user-defined or propagated route controls the next hop independently of NSG allow decisions. The corrective response here is “Enable the appropriate Azure DDoS protection option for the VNet's eligible public IP resources”; this alternative does not provide that response.

D:

This action concerns virtual network flow logs monitoring, where Network flow logging has not been configured for the relevant virtual network monitoring scope. The stem reports a business-critical public IP in an Azure VNet is exposed to volumetric attacks but the organization relies only on application WAF rules; this control addresses a different failure condition.

Question 661

While validating an Azure workload, the security team finds: An administrator opens a public RDP endpoint on every production VM even though security rules prohibit direct Internet-facing management ports. What governance practice would best prevent the same failure?

  1. Audit VM management ports and prefer controlled bastion connectivity with MFA and access logging.
  2. Test Bastion SKU and client feature support before designing remote-administration access.
  3. Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts.
  4. Schedule OS-level update compliance checks independent of ARM deployment status.

Explanation

Correct Answer

A:

This guardrail addresses azure bastion without public vm ip: Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. The prevention measure is: Audit VM management ports and prefer controlled bastion connectivity with MFA and access logging. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. “Test Bastion SKU and client feature support before designing remote-administration access” 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:

“Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts” responds to this separate finding: azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. This question instead needs “Audit VM management ports and prefer controlled bastion connectivity with MFA and access logging”, so the alternative does not meet the stated condition.

D:

Azure resource deployment health does not automatically establish guest operating system patch compliance. “Schedule OS-level update compliance checks independent of ARM deployment status” 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 662

A Microsoft Azure administrator receives this requirement: A GCP organization is connected to Defender for Cloud, but new projects do not appear in security inventory or compliance assessments. What is the most appropriate corrective step?

  1. Map benchmark recommendations to actual business risk, supported architecture and binding governance requirements.
  2. Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects.
  3. Enable the relevant supported regulatory standard and verify its assessment mappings for the intended environment.
  4. Onboard the supported on-premises servers through Azure Arc and configure the relevant Defender for Cloud protection.

Explanation

Correct Answer

B:

The cause is: A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. The appropriate change is: Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects. Verify it with this outcome: The new GCP projects are present in Defender inventory and receive applicable posture findings.

Incorrect Answers

A:

This action concerns defender for cloud cloud security benchmark, where A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. The reported incident instead involves A connector's project enrollment or organization-level integration scope may omit newly created GCP projects.

C:

This action concerns defender for cloud regulatory standard assignment, where Additional regulatory compliance standards require supported selection, assessment availability and assignment at the appropriate management scope. The corrective response here is “Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects”; this alternative does not provide that response.

D:

This action concerns azure arc hybrid server posture, where Defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans. The stem reports a GCP organization is connected to Defender for Cloud, but new projects do not appear in security inventory or compliance assessments; this control addresses a different failure condition.

Question 663

The cloud operations team reviews the following risk: A development subscription has a temporary exception to deny public network access, but the exception remains active long after the approved change window. Which remediation best addresses the specific issue?

  1. Provision supported HSM-protected keys in the appropriate vault tier and migrate applications according to key-dependency rules.
  2. Enable and verify the applicable vault soft delete protections and restrict backup-deletion privileges.
  3. Set time-limited exemptions with accountable justification and remove or renew each only after security review.
  4. Recover the deleted key using the supported procedure and enable governed purge protection for critical encryption dependencies.

Explanation

Correct Answer

C:

The cause is: An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration. The appropriate change is: Set time-limited exemptions with accountable justification and remove or renew each only after security review. Verify it with this outcome: The expired exemption no longer suppresses enforcement and any remaining public access is reported under the intended policy.

Incorrect Answers

A:

This action concerns key vault hsm keys versus software keys, where Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. The reported incident instead involves An exemption can legitimately alter policy evaluation for a scope and should have bounded governance and reviewed expiration.

B:

This action concerns azure backup soft delete retention protection, where Soft delete protects eligible backups from immediate irreversible deletion, subject to the configured protection features and retention rules. The corrective response here is “Set time-limited exemptions with accountable justification and remove or renew each only after security review”; this alternative does not provide that response.

D:

This action concerns key vault soft delete and purge protection, where Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period. The stem reports a development subscription has a temporary exception to deny public network access, but the exception remains active long after the approved change window; this control addresses a different failure condition.

Question 664

While validating an Azure workload, the security team finds: An organization requires isolated multi-app hosting with restricted inbound access, but deployments use a public App Service plan and broad access restrictions. Which outcome most clearly verifies that the issue is resolved?

  1. Controlled malicious request patterns are blocked while normal requests pass and logs record rule decisions.
  2. A test flow negotiates TLS to both gateway and backend without exposing plaintext on the internal leg.
  3. The managed instance deploys in the intended delegated subnet and responds only to permitted connections.
  4. Only authorized internal clients reach hosted apps, and operations can verify the isolated hosting path.

Explanation

Correct Answer

D:

This validates the specific control for internal app service environment isolation: The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. The associated corrective action is: Deploy a supported internal App Service Environment and configure ingress and outbound network controls. Testing a different component would not establish this result.

Incorrect Answers

A:

The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. “After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener” would address that alternative cause, not the condition in this question: the design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary.

B:

“Configure backend HTTPS with appropriate certificate trust and listener/backend settings” responds to this separate finding: backend HTTP settings do not enforce the required HTTPS connection to backend servers. This question instead needs “Deploy a supported internal App Service Environment and configure ingress and outbound network controls”, so the alternative does not meet the stated condition.

C:

SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. “Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls” applies to that separate problem. The observed case is an organization requires isolated multi-app hosting with restricted inbound access, but deployments use a public App Service plan and broad access restrictions; choosing this alternative would address the wrong failure mode.

Question 665

A regulated Azure tenant has this security condition: An application issues shared-key SAS tokens to end users while security requires tokens to derive from Microsoft Entra authorization. Which safeguard would best prevent this issue from recurring?

  1. Review data-plane RBAC separately from account administration roles for every application.
  2. Review SAS expiry, permission and network constraints during partner file exchange.
  3. Test WORM retention enforcement and approved release procedures before storing regulated records.
  4. Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry.

Explanation

Correct Answer

D:

This guardrail addresses user delegation sas for blob storage: Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. The prevention measure is: Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Management-plane storage Contributor does not necessarily include blob data read DataActions. “Review data-plane RBAC separately from account administration roles for every application” 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:

“Review SAS expiry, permission and network constraints during partner file exchange” responds to this separate finding: the SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. This question instead needs “Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry”, so the alternative does not meet the stated condition.

C:

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” 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 666

A platform security assessment reveals this issue: A security team creates a Logic App response workflow but expects Defender for Cloud to invoke it automatically without configuring any workflow automation trigger. Which operating control most directly reduces this recurring risk?

  1. Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly.
  2. Require security scan gates and scoped exceptions for infrastructure-as-code pull requests.
  3. Assess database threat protection plan coverage separately from firewall and SQL audit configuration.
  4. Review cloud storage protection coverage and alert destinations whenever sensitive data accounts are created.

Explanation

Correct Answer

A:

This guardrail addresses defender for cloud workflow automation trigger scope: A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. The prevention measure is: Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. “Require security scan gates and scoped exceptions for infrastructure-as-code pull requests” would address that alternative cause, not the condition in this question: a Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions.

C:

“Assess database threat protection plan coverage separately from firewall and SQL audit configuration” responds to this separate finding: database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. This question instead needs “Test workflow filters, identity permissions and duplicate handling before enabling security automation broadly”, so the alternative does not meet the stated condition.

D:

Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. “Review cloud storage protection coverage and alert destinations whenever sensitive data accounts are created” applies to that separate problem. The observed case is a security team creates a Logic App response workflow but expects Defender for Cloud to invoke it automatically without configuring any workflow automation trigger; choosing this alternative would address the wrong failure mode.

Question 667

A regulated Azure tenant has this security condition: A recently acquired corporate domain hosts forgotten Internet-exposed services that are absent from internal Azure subscription inventory. Which outcome most clearly verifies that the issue is resolved?

  1. The report documents coverage gaps and provides comparable evidence for each supported cloud control.
  2. The report includes the full resource inventory and separately highlights untagged or misclassified resources.
  3. Previously unknown externally reachable assets are identified, attributed to an owner and queued for risk assessment.
  4. Selected connected AWS instances appear in the correct Defender plan with expected scanning and alert coverage.

Explanation

Correct Answer

C:

This validates the specific control for defender easm externally visible asset discovery: Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. The associated corrective action is: Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains. Testing a different component would not establish this result.

Incorrect Answers

A:

Control applicability and enabled cloud connectors differ across providers, so absent assessment coverage is not equivalent to a passing control. “Check supported AWS assessment coverage, connector health and applicable cloud-specific configuration rules before comparing results” would address that alternative cause, not the condition in this question: internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet.

B:

“Query all in-scope Azure resources first and then classify missing or unexpected tags for correction” responds to this separate finding: tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. This question instead needs “Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains”, so the alternative does not meet the stated condition.

D:

Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. “Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances” applies to that separate problem. The observed case is a recently acquired corporate domain hosts forgotten Internet-exposed services that are absent from internal Azure subscription inventory; choosing this alternative would address the wrong failure mode.

Question 668

A production Azure security implementation shows this failure: A VM cannot reach a backend on TCP 5432, and an operator keeps guessing which NSG is responsible without testing effective decisions. Which recurring validation best protects against the observed problem?

  1. Periodically validate that origins cannot be bypassed through leaked or guessed public hostnames.
  2. Use standardized IP flow verify evidence before altering high-impact NSG policies.
  3. Test origin bypass routes as part of every public application security assessment.
  4. Audit DDoS resource coverage whenever a public service or subscription is added.

Explanation

Correct Answer

B:

This guardrail addresses 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 prevention measure is: Use standardized IP flow verify evidence before altering high-impact NSG policies. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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” 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.

C:

“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 “Use standardized IP flow verify evidence before altering high-impact NSG policies”, 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. “Audit DDoS resource coverage whenever a public service or subscription is added” 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 669

During a cloud security review, the operations team observes: A hub appliance receives packets from a spoke VNet, but forwarding to another spoke fails because peerings were configured only for ordinary direct VNet traffic. What technical cause best accounts for the described behavior?

  1. Gateway route propagation remains enabled for the route table and influences effective routing selections.
  2. NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes.
  3. The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.
  4. Network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny.

Explanation

Correct Answer

C:

The described technical condition is: The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. The appropriate corrective action is: Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs. Confirm with: Spoke-to-spoke traffic reaches its destination through the approved hub appliance and no unintended direct path exists.

Incorrect Answers

A:

Gateway route propagation remains enabled for the route table and influences effective routing selections. “Disable BGP route propagation on the relevant route table where the approved design requires static steering” would address that alternative cause, not the condition in this question: the necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.

B:

“Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes” responds to this separate finding: nSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. This question instead needs “Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs”, so the alternative does not meet the stated condition.

D:

Network Security Groups process inbound and outbound rules by ascending priority; a first matching allow can shadow a later deny. “Remove or narrow the broad allow rule and position the applicable deny ahead of competing permissive rules” applies to that separate problem. The observed case is a hub appliance receives packets from a spoke VNet, but forwarding to another spoke fails because peerings were configured only for ordinary direct VNet traffic; choosing this alternative would address the wrong failure mode.

Question 670

During a cloud security review, the operations team observes: A subscription team assigns an Azure Policy definition with Audit effect to prevent public IP deployment, yet the network group continues creating public IP resources. After remediation, which test result best proves the intended change?

  1. The dependent database resumes protected access after recovery and unauthorized permanent purge is blocked.
  2. A new prohibited public IP deployment is rejected while existing resources appear in policy compliance reporting.
  3. Approved services retrieve permitted secrets through the expected path while unauthorized public requests fail.
  4. After a controlled rotation the service remains encrypted and uses an appropriate authorized key version without downtime.

Explanation

Correct Answer

B:

This validates the specific control for azure policy audit versus deny effect: The Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect. The associated corrective action is: Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type. Testing a different component would not establish this result.

Incorrect Answers

A:

Purge protection and soft delete allow controlled recovery of deleted keys and prevent premature permanent removal during their retention period. “Recover the deleted key using the supported procedure and enable governed purge protection for critical encryption dependencies” would address that alternative cause, not the condition in this question: the Audit effect evaluates and reports noncompliance but does not prevent creation, unlike a correctly scoped Deny effect.

C:

“Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path” responds to this separate finding: key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. This question instead needs “Assign an appropriately tested Deny policy with suitable exemptions and confirm that it applies to the targeted resource type”, so the alternative does not meet the stated condition.

D:

A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. “Review the consuming service's automatic rotation support and configure the intended versionless key reference where supported” applies to that separate problem. The observed case is a subscription team assigns an Azure Policy definition with Audit effect to prevent public IP deployment, yet the network group continues creating public IP resources; choosing this alternative would address the wrong failure mode.