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 80

Question 790

While validating an Azure workload, the security team finds: On-premises Windows servers lack cloud security recommendations because the organization monitors only native Azure virtual machines. Which remediation best addresses the specific issue?

  1. Validate registration, DNS, certificate and business ownership evidence before accepting or rejecting EASM asset attribution.
  2. Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances.
  3. Onboard the supported on-premises servers through Azure Arc and configure the relevant Defender for Cloud protection.
  4. Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives.

Explanation

Correct Answer

C:

The cause is: Defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans. The appropriate change is: Onboard the supported on-premises servers through Azure Arc and configure the relevant Defender for Cloud protection. Verify it with this outcome: Hybrid servers show recognized inventory, security recommendations and the expected threat-protection status.

Incorrect Answers

A:

This action concerns easm asset attribution false positives, where Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. The reported incident instead involves Defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans.

B:

This action concerns defender for cloud cross-account connected aws plans, where Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. The corrective response here is “Onboard the supported on-premises servers through Azure Arc and configure the relevant Defender for Cloud protection”; this alternative does not provide that response.

D:

This action concerns defender for cloud recommendation root-cause assessment, where A recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. The stem reports on-premises Windows servers lack cloud security recommendations because the organization monitors only native Azure virtual machines; this control addresses a different failure condition.

Question 791

During a cloud security review, the operations team observes: An automated report job has Storage Account Contributor but HTTP blob reads fail with authorization errors under Microsoft Entra tokens. What observation is the strongest validation evidence?

  1. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.
  2. The report job retrieves allowed blobs via Entra tokens and cannot change unrelated storage settings.
  3. A controlled deletion can be reversed within retention without rebuilding the entire account.
  4. Approved clients access data and unauthorized public source IPs receive network access denial.

Explanation

Correct Answer

B:

This validates the specific control for blob storage data rbac: Management-plane storage Contributor does not necessarily include blob data read DataActions. The associated corrective action is: Assign Storage Blob Data Reader to the application identity at the appropriate container scope. Testing a different component would not establish this result.

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: management-plane storage Contributor does not necessarily include blob data read DataActions.

C:

“Enable blob soft delete with an appropriate retention period and verify the restore process” responds to this separate finding: the storage account lacks blob soft delete retention to recover recently removed objects. This question instead needs “Assign Storage Blob Data Reader to the application identity at the appropriate container scope”, 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 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.

Question 792

An Azure security engineer investigates the following incident: An application uses a custom hostname but presents an unrelated default certificate, causing client hostname validation failures. Which safeguard would best prevent this issue from recurring?

  1. Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services.
  2. Review WAF mode, tuning and false-positive impact before promoting a policy to production.
  3. Track custom domain certificate validity and binding renewal before expiration.
  4. Include listener-to-backend encryption checks in application gateway security reviews.

Explanation

Correct Answer

C:

This guardrail addresses custom domain tls certificate binding: The custom domain has no correct TLS certificate binding for the expected host name. The prevention measure is: Track custom domain certificate validity and binding renewal before expiration. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The function hosting plan and network integration/DNS are not configured for the required private destination. “Verify Functions plan capabilities and effective outbound DNS/routing before enforcing private-only services” would address that alternative cause, not the condition in this question: the custom domain has no correct TLS certificate binding for the expected host name.

B:

“Review WAF mode, tuning and false-positive impact before promoting a policy to production” responds to this separate finding: the Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. This question instead needs “Track custom domain certificate validity and binding renewal before expiration”, so the alternative does not meet the stated condition.

D:

Backend HTTP settings do not enforce the required HTTPS connection to backend servers. “Include listener-to-backend encryption checks in application gateway security reviews” applies to that separate problem. The observed case is an application uses a custom hostname but presents an unrelated default certificate, causing client hostname validation failures; choosing this alternative would address the wrong failure mode.

Question 793

A regulated Azure tenant has this security condition: A web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured. Which remediation best addresses the specific issue?

  1. Configure regional App Service VNet integration and the necessary subnet routing and DNS.
  2. Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service.
  3. Create an approved Private Endpoint in the workload VNet and disable or restrict the service's public access.
  4. Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage.

Explanation

Correct Answer

A:

The cause is: App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. The appropriate change is: Configure regional App Service VNet integration and the necessary subnet routing and DNS. Verify it with this outcome: The web app reaches the internal backend over the intended outbound integrated network path.

Incorrect Answers

B:

This action concerns private endpoint versus service endpoint isolation, where Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. The reported incident instead involves App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections.

C:

This action concerns private endpoint public exposure reduction, where A private endpoint has not been configured or public network access has not been restricted for the resource. The corrective response here is “Configure regional App Service VNet integration and the necessary subnet routing and DNS”; this alternative does not provide that response.

D:

This action concerns vnet service endpoint network scope, where The required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. The stem reports a web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured; this control addresses a different failure condition.

Question 794

While validating an Azure workload, the security team finds: A central security owner enables a protection plan in one subscription and expects all subscriptions in the tenant to receive paid workload protection automatically. Which condition most directly explains the failure?

  1. Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption.
  2. Custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions.
  3. Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth.
  4. A multicloud connector can exist while its required permissions, services or security plan settings are incomplete.

Explanation

Correct Answer

A:

The described technical condition is: Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. The appropriate corrective action is: Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope. Confirm with: Every governed subscription reports the expected Defender workload plan state and billed resource scope.

Incorrect Answers

B:

Custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions. “Build the supported custom standard from approved Azure Policy content and map its controls to the organization's documented obligations” would address that alternative cause, not the condition in this question: defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption.

C:

“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 “Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope”, so the alternative does not meet the stated condition.

D:

A multicloud connector can exist while its required permissions, services or security plan settings are incomplete. “Review and repair the AWS connector's authorized access and enable applicable posture assessment capabilities” applies to that separate problem. The observed case is a central security owner enables a protection plan in one subscription and expects all subscriptions in the tenant to receive paid workload protection automatically; choosing this alternative would address the wrong failure mode.

Question 795

While validating an Azure workload, the security team finds: An Azure API Management product accepts anonymous calls to a sensitive paid API because subscription enforcement is disabled. Which explanation fits the observed symptoms most closely?

  1. The API or product does not require the intended APIM subscription key or equivalent authentication control.
  2. The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes.
  3. Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation.
  4. The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers.

Explanation

Correct Answer

A:

The described technical condition is: The API or product does not require the intended APIM subscription key or equivalent authentication control. The appropriate corrective action is: Enable appropriate APIM subscription requirements and validate product/API associations. Confirm with: A request without authorized API credentials is rejected and approved subscribers receive normal responses.

Incorrect Answers

B:

The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. “Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys” would address that alternative cause, not the condition in this question: the API or product does not require the intended APIM subscription key or equivalent authentication control.

C:

“Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys” responds to this separate finding: disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. This question instead needs “Enable appropriate APIM subscription requirements and validate product/API associations”, so the alternative does not meet the stated condition.

D:

The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. “Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions” applies to that separate problem. The observed case is an Azure API Management product accepts anonymous calls to a sensitive paid API because subscription enforcement is disabled; choosing this alternative would address the wrong failure mode.

Question 796

A production Azure security implementation shows this failure: A public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application. Which recurring validation best protects against the observed problem?

  1. Include listener-to-backend encryption checks in application gateway security reviews.
  2. Validate probe host/path behavior whenever application URLs or certificates change.
  3. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  4. Review WAF mode, tuning and false-positive impact before promoting a policy to production.

Explanation

Correct Answer

D:

This guardrail addresses application gateway waf detection versus prevention: The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. The prevention measure is: Review WAF mode, tuning and false-positive impact before promoting a policy to production. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Backend HTTP settings do not enforce the required HTTPS connection to backend servers. “Include listener-to-backend encryption checks in application gateway security reviews” would address that alternative cause, not the condition in this question: the Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode.

B:

“Validate probe host/path behavior whenever application URLs or certificates change” responds to this separate finding: the backend health probe is failing due to its configured request host, path or expected response rather than VM availability. This question instead needs “Review WAF mode, tuning and false-positive impact before promoting a policy to production”, so the alternative does not meet the stated condition.

C:

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 a public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application; choosing this alternative would address the wrong failure mode.

Question 797

A platform security assessment reveals this issue: An App Service must accept application requests only through private network connectivity, but the team uses outbound VNet integration alone. After remediation, which test result best proves the intended change?

  1. Clients inside authorized networks reach the app over the private endpoint while public requests fail.
  2. A capture or configuration review confirms sensitive payloads are cryptographically protected over the private circuit.
  3. Approved corporate storage access succeeds and a test unapproved storage destination is denied.
  4. The web app reaches the internal backend over the intended outbound integrated network path.

Explanation

Correct Answer

A:

This validates the specific control for app service private endpoint inbound path: Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. The associated corrective action is: Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required. Testing a different component would not establish this result.

Incorrect Answers

B:

ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. “Implement supported IPsec over ExpressRoute or application-layer TLS encryption according to the threat model” would address that alternative cause, not the condition in this question: regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint.

C:

“Apply an appropriate service endpoint policy restricting the subnet to approved storage resources” responds to this separate finding: the subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations. This question instead needs “Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required”, so the alternative does not meet the stated condition.

D:

App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. “Configure regional App Service VNet integration and the necessary subnet routing and DNS” applies to that separate problem. The observed case is an App Service must accept application requests only through private network connectivity, but the team uses outbound VNet integration alone; choosing this alternative would address the wrong failure mode.

Question 798

While validating an Azure workload, the security team finds: Two Kubernetes namespaces in AKS exchange traffic freely although finance workloads must not be reachable from untrusted pods. Which safeguard would best prevent this issue from recurring?

  1. Review snapshot export and managed disk permissions as part of sensitive VM data governance.
  2. Use private API endpoint requirements during AKS cluster provisioning and access reviews.
  3. Rotate administrator keys on staff changes and prohibit shared SSH passwords in templates.
  4. Test both ingress and egress network policies with real pods after label changes.

Explanation

Correct Answer

D:

This guardrail addresses aks pod network policy isolation: Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. The prevention measure is: Test both ingress and egress network policies with real pods after label changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. “Review snapshot export and managed disk permissions as part of sensitive VM data governance” would address that alternative cause, not the condition in this question: namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules.

B:

“Use private API endpoint requirements during AKS cluster provisioning and access reviews” responds to this separate finding: the cluster uses a public API server endpoint rather than a supported private AKS cluster design. This question instead needs “Test both ingress and egress network policies with real pods after label changes”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is two Kubernetes namespaces in AKS exchange traffic freely although finance workloads must not be reachable from untrusted pods; choosing this alternative would address the wrong failure mode.

Question 799

A regulated Azure tenant has this security condition: A spoke subnet unexpectedly learns routes from an attached virtual network gateway and uses an unwanted path despite a locally maintained route table. Which condition most directly explains the failure?

  1. Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg.
  2. No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance.
  3. Gateway route propagation remains enabled for the route table and influences effective routing selections.
  4. NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes.

Explanation

Correct Answer

C:

The described technical condition is: Gateway route propagation remains enabled for the route table and influences effective routing selections. The appropriate corrective action is: Disable BGP route propagation on the relevant route table where the approved design requires static steering. Confirm with: Effective route inspection shows only intended propagated and explicit routes for the target subnet.

Incorrect Answers

A:

Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. “Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path” would address that alternative cause, not the condition in this question: gateway route propagation remains enabled for the route table and influences effective routing selections.

B:

“Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP” responds to this separate finding: no effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. This question instead needs “Disable BGP route propagation on the relevant route table where the approved design requires static steering”, so the alternative does not meet the stated condition.

D:

NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. “Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes” applies to that separate problem. The observed case is a spoke subnet unexpectedly learns routes from an attached virtual network gateway and uses an unwanted path despite a locally maintained route table; choosing this alternative would address the wrong failure mode.

Question 800

The cloud operations team reviews the following risk: A production application silently continues using a legacy connection secret near its expiration date because nobody owns renewal procedures. Which result confirms the relevant security control is effective?

  1. A protected backup deletion request fails until a separate authorized security approver grants the required permission.
  2. Authorized operators can restore data while prohibited backup protection reduction operations are rejected.
  3. Each child subscription reports consistent compliance results and the documented initiative parameters match approved standards.
  4. The application authenticates using the current secret and monitoring alerts before the next scheduled expiration.

Explanation

Correct Answer

D:

This validates the specific control for key vault secret expiry lifecycle: Secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry. The associated corrective action is: Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications. Testing a different component would not establish this result.

Incorrect Answers

A:

Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. “Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers” would address that alternative cause, not the condition in this question: secret rotation and expiration notifications require assigned ownership and supported alert or event handling before expiry.

B:

“Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing” responds to this separate finding: an immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. This question instead needs “Establish a governed rotation schedule and notification process and deploy the new secret to dependent applications”, so the alternative does not meet the stated condition.

C:

Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. “Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope” applies to that separate problem. The observed case is a production application silently continues using a legacy connection secret near its expiration date because nobody owns renewal procedures; choosing this alternative would address the wrong failure mode.