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 70

Question 690

During a cloud security review, the operations team observes: A spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet. After remediation, which test result best proves the intended change?

  1. The two VNets establish valid connectivity only after address overlap is eliminated or appropriately translated.
  2. The VM reaches its approved Azure service while unrelated Internet destinations remain blocked.
  3. Approved HTTPS hosts are reachable and unrelated hosts in the same IP ranges are rejected.
  4. A spoke workload reaches the on-premises network via the shared hub gateway without deploying a second gateway.

Explanation

Correct Answer

D:

This validates the specific control for gateway transit peering configuration: Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. The associated corrective action is: Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints. Testing a different component would not establish this result.

Incorrect Answers

A:

Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. “Renumber or redesign the address space before establishing peering or use an approved translation architecture” would address that alternative cause, not the condition in this question: gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.

B:

“Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls” responds to this separate finding: a broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. This question instead needs “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is a spoke VNet is peered to a hub containing a VPN gateway but its VMs cannot use the hub gateway to reach an on-premises subnet; choosing this alternative would address the wrong failure mode.

Question 691

A Microsoft Azure administrator receives this requirement: A GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments. Which recurring validation best protects against the observed problem?

  1. Reconcile repository discovery and connector app permissions after organizational or repository changes.
  2. Link vulnerability closure to post-remediation evidence rather than administrative ticket state alone.
  3. Review supported scan coverage and inventory accuracy when adding agentless-protected compute resources.
  4. Test storage malware inspection and quarantine handling separately from encryption and access control checks.

Explanation

Correct Answer

A:

This guardrail addresses defender for cloud devops github connector scope: DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. The prevention measure is: Reconcile repository discovery and connector app permissions after organizational or repository changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. “Link vulnerability closure to post-remediation evidence rather than administrative ticket state alone” would address that alternative cause, not the condition in this question: devOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.

C:

“Review supported scan coverage and inventory accuracy when adding agentless-protected compute resources” responds to this separate finding: supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent. This question instead needs “Reconcile repository discovery and connector app permissions after organizational or repository changes”, so the alternative does not meet the stated condition.

D:

Storage encryption at rest does not inspect uploaded content for malware; appropriate Defender for Storage capabilities must be enabled where supported. “Test storage malware inspection and quarantine handling separately from encryption and access control checks” applies to that separate problem. The observed case is a GitHub organization is integrated into Defender for Cloud DevOps Security, but confidential repositories are omitted from code security assessments; choosing this alternative would address the wrong failure mode.

Question 692

A Microsoft Azure administrator receives this requirement: An application subnet can access many Azure Storage accounts even though governance permits only designated corporate storage resource IDs. What is the most appropriate corrective step?

  1. Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval.
  2. Implement supported IPsec over ExpressRoute or application-layer TLS encryption according to the threat model.
  3. Apply an appropriate service endpoint policy restricting the subnet to approved storage resources.
  4. Configure the correct privatelink DNS zone record and link the client VNet to the zone.

Explanation

Correct Answer

C:

The cause is: The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations. The appropriate change is: Apply an appropriate service endpoint policy restricting the subnet to approved storage resources. Verify it with this outcome: Approved corporate storage access succeeds and a test unapproved storage destination is denied.

Incorrect Answers

A:

This action concerns private link service provider design, where The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. The reported incident instead involves The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations.

B:

This action concerns expressroute encryption requirement, where ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. The corrective response here is “Apply an appropriate service endpoint policy restricting the subnet to approved storage resources”; this alternative does not provide that response.

D:

This action concerns private dns zone linking for endpoint, where The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. The stem reports an application subnet can access many Azure Storage accounts even though governance permits only designated corporate storage resource IDs; this control addresses a different failure condition.

Question 693

During a cloud security review, the operations team observes: A Defender for Cloud alert reports suspicious VM command execution, but analysts close it immediately because the VM currently appears healthy. What technical cause best accounts for the described behavior?

  1. Code security inventory and posture coverage depend on a supported connector for the actual source-control platform.
  2. Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue.
  3. Supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent.
  4. A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines.

Explanation

Correct Answer

D:

The described technical condition is: A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. The appropriate corrective action is: Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment. Confirm with: The case records corroborated benign activity or documented remediation of the suspicious command chain.

Incorrect Answers

A:

Code security inventory and posture coverage depend on a supported connector for the actual source-control platform. “Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories” would address that alternative cause, not the condition in this question: a single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines.

B:

“Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw” responds to this separate finding: patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. This question instead needs “Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment”, so the alternative does not meet the stated condition.

C:

Supported Defender for Cloud agentless machine scanning can assess certain VM properties and installed software without relying on a traditional guest agent. “Enable the supported agentless scanning capability and verify its resource scope, prerequisites and results” applies to that separate problem. The observed case is a Defender for Cloud alert reports suspicious VM command execution, but analysts close it immediately because the VM currently appears healthy; choosing this alternative would address the wrong failure mode.

Question 694

The cloud operations team reviews the following risk: A scheduled Sentinel rule runs every 15 minutes but looks back only two minutes, allowing delayed logs to fall into unobserved intervals. Which configuration change most directly resolves this problem?

  1. Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content.
  2. Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics.
  3. Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay.
  4. Enable the required syslog facility and severity in the Linux data collection rule and verify agent association.

Explanation

Correct Answer

C:

The cause is: A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. The appropriate change is: Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay. Verify it with this outcome: Late-arriving simulated authentication events are detected once without producing excessive duplicate incidents.

Incorrect Answers

A:

This action concerns sentinel workspace onboarding, where A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. The reported incident instead involves A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation.

B:

This action concerns sentinel threat intelligence indicator freshness, where Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. The corrective response here is “Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay”; this alternative does not provide that response.

D:

This action concerns azure monitor dcr linux syslog facility, where A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. The stem reports a scheduled Sentinel rule runs every 15 minutes but looks back only two minutes, allowing delayed logs to fall into unobserved intervals; this control addresses a different failure condition.

Question 695

A platform security assessment reveals this issue: A data team must control its own encryption key lifecycle, but storage uses only Microsoft-managed encryption keys and lacks access to the chosen vault. Which recurring validation best protects against the observed problem?

  1. Test customer-managed key rotation and access recovery before changing storage encryption configuration.
  2. Test storage account public network access and network rules after resource redeployment.
  3. Validate version history and lifecycle management for sensitive mutable blob data.
  4. Review SAS expiry, permission and network constraints during partner file exchange.

Explanation

Correct Answer

A:

This guardrail addresses storage customer managed key in key vault: Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. The prevention measure is: Test customer-managed key rotation and access recovery before changing storage encryption configuration. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. “Test storage account public network access and network rules after resource redeployment” would address that alternative cause, not the condition in this question: storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account.

C:

“Validate version history and lifecycle management for sensitive mutable blob data” responds to this separate finding: blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. This question instead needs “Test customer-managed key rotation and access recovery before changing storage encryption configuration”, so the alternative does not meet the stated condition.

D:

The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. “Review SAS expiry, permission and network constraints during partner file exchange” applies to that separate problem. The observed case is a data team must control its own encryption key lifecycle, but storage uses only Microsoft-managed encryption keys and lacks access to the chosen vault; choosing this alternative would address the wrong failure mode.

Question 696

The cloud operations team reviews the following risk: A VM scanner lists a high-severity operating system vulnerability and the operator closes the ticket without applying any patch. Which explanation fits the observed symptoms most closely?

  1. Node management alone does not provide full supported Defender for Containers security posture and workload protection.
  2. A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified.
  3. Storage encryption at rest does not inspect uploaded content for malware; appropriate Defender for Storage capabilities must be enabled where supported.
  4. Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy.

Explanation

Correct Answer

B:

The described technical condition is: A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The appropriate corrective action is: Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation. Confirm with: A subsequent scan no longer detects the affected vulnerable package or documents a justified protected exception.

Incorrect Answers

A:

Node management alone does not provide full supported Defender for Containers security posture and workload protection. “Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster” would address that alternative cause, not the condition in this question: a vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified.

C:

“Enable the approved Defender for Storage malware scanning on upload and configure the appropriate event handling” responds to this separate finding: storage encryption at rest does not inspect uploaded content for malware; appropriate Defender for Storage capabilities must be enabled where supported. This question instead needs “Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation”, so the alternative does not meet the stated condition.

D:

Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings” applies to that separate problem. The observed case is a VM scanner lists a high-severity operating system vulnerability and the operator closes the ticket without applying any patch; choosing this alternative would address the wrong failure mode.

Question 697

A platform security assessment reveals this issue: A team assigns the same Azure resource role individually to dozens of analysts, then former team members retain access when the department changes. Which recurring validation best protects against the observed problem?

  1. Investigate deny assignments as well as allow grants when diagnosing apparent RBAC permission anomalies.
  2. Review group ownership and membership periodically rather than accumulating direct role assignments.
  3. Test conditioned Azure RBAC access against both permitted and forbidden resource attributes.
  4. Validate custom-role definitions through effective permission tests before applying them widely.

Explanation

Correct Answer

B:

This guardrail addresses group based azure rbac: Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. The prevention measure is: Review group ownership and membership periodically rather than accumulating direct role assignments. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. “Investigate deny assignments as well as allow grants when diagnosing apparent RBAC permission anomalies” would address that alternative cause, not the condition in this question: direct per-user role assignments can persist after personnel changes without a managed membership lifecycle.

C:

“Test conditioned Azure RBAC access against both permitted and forbidden resource attributes” responds to this separate finding: a broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. This question instead needs “Review group ownership and membership periodically rather than accumulating direct role assignments”, so the alternative does not meet the stated condition.

D:

NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. “Validate custom-role definitions through effective permission tests before applying them widely” applies to that separate problem. The observed case is a team assigns the same Azure resource role individually to dozens of analysts, then former team members retain access when the department changes; choosing this alternative would address the wrong failure mode.

Question 698

A Microsoft Azure administrator receives this requirement: A branch app subnet sends outbound Internet traffic straight to its default system route despite an architecture requiring inspection by a central Azure Firewall. What is the most appropriate corrective step?

  1. Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes.
  2. Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP.
  3. Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs.
  4. Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision.

Explanation

Correct Answer

B:

The cause is: No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance. The appropriate change is: Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP. Verify it with this outcome: The app subnet's outbound flows traverse the central inspection appliance and are visible in policy logs.

Incorrect Answers

A:

This action concerns stateful nsg return traffic behavior, where NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. The reported incident instead involves No effective user-defined default route sends the workload subnet's outbound traffic to the intended virtual appliance.

C:

This action concerns vnet peering forwarded traffic setting, where The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. The corrective response here is “Associate a route table with the appropriate 0.0.0.0/0 next hop at the authorized firewall private IP”; this alternative does not provide that response.

D:

This action concerns effective network security rules diagnosis, where The active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view. The stem reports a branch app subnet sends outbound Internet traffic straight to its default system route despite an architecture requiring inspection by a central Azure Firewall; this control addresses a different failure condition.

Question 699

The cloud operations team reviews the following risk: A container app revision embeds a database password directly into plaintext application arguments, violating application secret-handling rules. Which condition most directly explains the failure?

  1. Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control.
  2. AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health.
  3. Control-plane version compliance is distinct from node OS image and node pool security patch state.
  4. Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity.

Explanation

Correct Answer

D:

The described technical condition is: Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. The appropriate corrective action is: Configure a secure Container Apps secret reference or managed identity for database access. Confirm with: The workload authenticates without printing or exposing the password in revision configuration.

Incorrect Answers

A:

Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. “Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components” would address that alternative cause, not the condition in this question: sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity.

B:

“Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels” responds to this separate finding: aKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. This question instead needs “Configure a secure Container Apps secret reference or managed identity for database access”, so the alternative does not meet the stated condition.

C:

Control-plane version compliance is distinct from node OS image and node pool security patch state. “Schedule supported AKS node image updates and verify rollout health across node pools” applies to that separate problem. The observed case is a container app revision embeds a database password directly into plaintext application arguments, violating application secret-handling rules; choosing this alternative would address the wrong failure mode.

Question 700

A Microsoft Azure administrator receives this requirement: A CISO compares an Azure posture dashboard with an AWS dashboard and claims missing AWS assessments prove that no AWS security risks exist. What observation is the strongest validation evidence?

  1. Confirmed owned exposures enter the remediation queue while unrelated third-party assets are excluded with reasons.
  2. The inventory includes the acquired subscriptions, identifies owners and reveals previously unreviewed internet-exposed machines.
  3. The report documents coverage gaps and provides comparable evidence for each supported cloud control.
  4. The new GCP projects are present in Defender inventory and receive applicable posture findings.

Explanation

Correct Answer

C:

This validates the specific control for microsoft defender for cloud aws security benchmark coverage: Control applicability and enabled cloud connectors differ across providers, so absent assessment coverage is not equivalent to a passing control. The associated corrective action is: Check supported AWS assessment coverage, connector health and applicable cloud-specific configuration rules before comparing results. 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: control applicability and enabled cloud connectors differ across providers, so absent assessment coverage is not equivalent to a passing control.

B:

“Build an authorized inventory from Defender for Cloud and Azure Resource Graph across governed subscriptions and management groups” responds to this separate finding: a security inventory that excludes child subscriptions and connected accounts cannot give complete exposure or asset ownership coverage. This question instead needs “Check supported AWS assessment coverage, connector health and applicable cloud-specific configuration rules before comparing results”, so the alternative does not meet the stated condition.

D:

A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. “Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects” applies to that separate problem. The observed case is a CISO compares an Azure posture dashboard with an AWS dashboard and claims missing AWS assessments prove that no AWS security risks exist; choosing this alternative would address the wrong failure mode.