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 64

Question 630

A Microsoft Azure administrator receives this requirement: A shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs. What observation is the strongest validation evidence?

  1. An abusive test caller is throttled while independent legitimate clients retain service availability.
  2. A request without authorized API credentials is rejected and approved subscribers receive normal responses.
  3. Approved CI pipelines push or pull with attributable identities and the shared admin login fails.
  4. A test deployment uses the reviewed digest and obsolete unapproved images are no longer deployable.

Explanation

Correct Answer

C:

This validates the specific control for acr administrator account disablement: The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The associated corrective action is: Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access.

B:

“Enable appropriate APIM subscription requirements and validate product/API associations” responds to this separate finding: the API or product does not require the intended APIM subscription key or equivalent authentication control. This question instead needs “Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles”, so the alternative does not meet the stated condition.

D:

Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. “Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks” applies to that separate problem. The observed case is a shared Azure Container Registry admin username and password is stored in multiple build pipelines and cannot be attributed to individual jobs; choosing this alternative would address the wrong failure mode.

Question 631

A production Azure security implementation shows this failure: A front-end subnet rule references an Application Security Group intended for web VMs, but a newly deployed VM is missing from the ASG and cannot receive traffic. What observation is the strongest validation evidence?

  1. Effective route inspection shows only intended propagated and explicit routes for the target subnet.
  2. HTTPS reaches the approved VM only when both applicable NSG layers permit the connection.
  3. New prohibited connections fail and the team documents disposition of any previously established flows.
  4. The newly assigned web VM receives authorized application traffic while non-member VMs remain excluded.

Explanation

Correct Answer

D:

This validates the specific control for application security group membership scoping: An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. The associated corrective action is: Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria. Testing a different component would not establish this result.

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: an ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group.

B:

“Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope” responds to this separate finding: both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. This question instead needs “Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria”, so the alternative does not meet the stated condition.

C:

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 front-end subnet rule references an Application Security Group intended for web VMs, but a newly deployed VM is missing from the ASG and cannot receive traffic; choosing this alternative would address the wrong failure mode.

Question 632

A regulated Azure tenant has this security condition: An App Service must accept application requests only through private network connectivity, but the team uses outbound VNet integration alone. What governance practice would best prevent the same failure?

  1. Verify DNS zone links and forwarders for all VNets consuming a private service.
  2. Review storage resource ID allowlists whenever approved service endpoint destinations change.
  3. Treat private transport and payload encryption as separate security controls in architecture reviews.
  4. Review separate inbound private endpoint and outbound integration settings for each App Service.

Explanation

Correct Answer

D:

This guardrail addresses app service private endpoint inbound path: Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. The prevention measure is: Review separate inbound private endpoint and outbound integration settings for each App Service. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Verify DNS zone links and forwarders for all VNets consuming a private service” 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.

B:

“Review storage resource ID allowlists whenever approved service endpoint destinations change” 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 “Review separate inbound private endpoint and outbound integration settings for each App Service”, so the alternative does not meet the stated condition.

C:

ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. “Treat private transport and payload encryption as separate security controls in architecture reviews” 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 633

A production Azure security implementation shows this failure: A developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off. Which operating control most directly reduces this recurring risk?

  1. Test storage account public network access and network rules after resource redeployment.
  2. Review deleted-object recovery tests and retention duration for critical storage containers.
  3. Review SAS expiry, permission and network constraints during partner file exchange.
  4. Confirm infrastructure encryption eligibility and immutability of settings before account creation.

Explanation

Correct Answer

B:

This guardrail addresses blob soft delete recovery window: The storage account lacks blob soft delete retention to recover recently removed objects. The prevention measure is: Review deleted-object recovery tests and retention duration for critical storage containers. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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: the storage account lacks blob soft delete retention to recover recently removed objects.

C:

“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 “Review deleted-object recovery tests and retention duration for critical storage containers”, so the alternative does not meet the stated condition.

D:

The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. “Confirm infrastructure encryption eligibility and immutability of settings before account creation” applies to that separate problem. The observed case is a developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off; choosing this alternative would address the wrong failure mode.

Question 634

A regulated Azure tenant has this security condition: A security initiative is assigned at a management group, but one production subscription does not appear in its compliance dashboard because it was excluded by notScopes. Which configuration change most directly resolves this problem?

  1. Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control.
  2. Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition.
  3. Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault.
  4. Configure the supported private endpoint or narrowly authorized network rule while validating the automation's actual network path.

Explanation

Correct Answer

A:

The cause is: An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. The appropriate change is: Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control. Verify it with this outcome: The production subscription enters the relevant compliance assessment and its resources receive the expected enforcement.

Incorrect Answers

B:

This action concerns azure policy modify remediation for existing tags, where Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. The reported incident instead involves An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended.

C:

This action concerns key vault backup restore regional limitation, where Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. The corrective response here is “Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control”; this alternative does not provide that response.

D:

This action concerns key vault firewall trusted bypass scope, where Key Vault networking restrictions require approved connectivity, and broad public exposure is not necessary for private workloads. The stem reports a security initiative is assigned at a management group, but one production subscription does not appear in its compliance dashboard because it was excluded by notScopes; this control addresses a different failure condition.

Question 635

A production Azure security implementation shows this failure: A central security owner enables a protection plan in one subscription and expects all subscriptions in the tenant to receive paid workload protection automatically. What is the most appropriate corrective step?

  1. Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope.
  2. Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap.
  3. Review AWS connector settings, workload protection plan scope and supported scanning capabilities for those instances.
  4. Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains.

Explanation

Correct Answer

A:

The cause is: Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. The appropriate change is: Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope. Verify it with this outcome: Every governed subscription reports the expected Defender workload plan state and billed resource scope.

Incorrect Answers

B:

This action concerns defender for cloud secure score priority, where Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. The reported incident instead involves Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption.

C:

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 “Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope”; this alternative does not provide that response.

D:

This action concerns defender easm externally visible asset discovery, where Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. The stem reports a central security owner enables a protection plan in one subscription and expects all subscriptions in the tenant to receive paid workload protection automatically; this control addresses a different failure condition.

Question 636

A platform security assessment reveals this issue: A financial services team needs internal cryptographic-key controls shown alongside standard assessments, but no built-in assessment matches their policy. What observation is the strongest validation evidence?

  1. The new GCP projects are present in Defender inventory and receive applicable posture findings.
  2. Public SSH and RDP access is denied from unauthorized networks and the security assessment updates accordingly.
  3. Selected connected AWS instances appear in the correct Defender plan with expected scanning and alert coverage.
  4. The custom standard displays measurable compliance results for relevant encrypted resources rather than unsupported manual declarations.

Explanation

Correct Answer

D:

This validates the specific control for defender for cloud custom standards mapping: Custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions. The associated corrective action is: Build the supported custom standard from approved Azure Policy content and map its controls to the organization's documented obligations. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions.

B:

“Inspect each affected VM exposure and remove unnecessary public administration routes or apply approved alternatives” responds to this separate finding: a recommendation reflects potential attack exposure that must be evaluated against effective network and resource configuration. This question instead needs “Build the supported custom standard from approved Azure Policy content and map its controls to the organization's documented obligations”, so the alternative does not meet the stated condition.

C:

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 financial services team needs internal cryptographic-key controls shown alongside standard assessments, but no built-in assessment matches their policy; choosing this alternative would address the wrong failure mode.

Question 637

A regulated Azure tenant has this security condition: Two applications are moved into VNets with overlapping private address ranges, and administrators attempt to establish a direct VNet peering between them. Which condition most directly explains the failure?

  1. Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings.
  2. Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.
  3. An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.
  4. An enforced security admin deny rule has higher governance precedence than the workload NSG allow.

Explanation

Correct Answer

B:

The described technical condition is: Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. The appropriate corrective action is: Renumber or redesign the address space before establishing peering or use an approved translation architecture. Confirm with: The two VNets establish valid connectivity only after address overlap is eliminated or appropriately translated.

Incorrect Answers

A:

Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints” would address that alternative cause, not the condition in this question: azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.

C:

“Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow” responds to this separate finding: an HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. This question instead needs “Renumber or redesign the address space before establishing peering or use an approved translation architecture”, 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 two applications are moved into VNets with overlapping private address ranges, and administrators attempt to establish a direct VNet peering between them; choosing this alternative would address the wrong failure mode.

Question 638

An Azure security engineer investigates the following incident: An AKS team stores production credentials in Kubernetes Secrets and assumes base64 encoding alone provides strong confidentiality of stored secret values. Which condition most directly explains the failure?

  1. Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls.
  2. The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication.
  3. Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model.
  4. Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination.

Explanation

Correct Answer

A:

The described technical condition is: Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. The appropriate corrective action is: Enable supported secret encryption and external secret management using Key Vault where required. Confirm with: Secrets are protected in the intended storage path and only approved workload identities can retrieve values.

Incorrect Answers

B:

The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. “Configure the Microsoft Entra administrator and create appropriate contained database users and roles” would address that alternative cause, not the condition in this question: kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls.

C:

“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 “Enable supported secret encryption and external secret management using Key Vault where required”, so the alternative does not meet the stated condition.

D:

Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. “Enable supported SQL auditing with the necessary categories and protected retention settings” applies to that separate problem. The observed case is an AKS team stores production credentials in Kubernetes Secrets and assumes base64 encoding alone provides strong confidentiality of stored secret values; choosing this alternative would address the wrong failure mode.

Question 639

An Azure security engineer investigates the following incident: An administrator builds a valid data collection rule but points it at a test workspace while the SOC searches only its production workspace. What governance practice would best prevent the same failure?

  1. Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy.
  2. Validate Sentinel workspace identity, role permissions and content configuration during SOC onboarding.
  3. Test create and update automation triggers independently after SOC workflow changes.
  4. Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated.

Explanation

Correct Answer

D:

This guardrail addresses dcr workspace destination configuration: A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. The prevention measure is: Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A cloud security benchmark supplies recommended security controls but is not itself a substitute for an applicable legal or organizational compliance obligation. “Maintain formal mappings between technical recommendations and the regulations or policies they help satisfy” would address that alternative cause, not the condition in this question: a DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace.

B:

“Validate Sentinel workspace identity, role permissions and content configuration during SOC onboarding” responds to this separate finding: a Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. This question instead needs “Record DCR destination IDs and run post-change ingestion checks whenever workspaces are consolidated”, so the alternative does not meet the stated condition.

C:

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” applies to that separate problem. The observed case is an administrator builds a valid data collection rule but points it at a test workspace while the SOC searches only its production workspace; choosing this alternative would address the wrong failure mode.

Question 640

While validating an Azure workload, the security team finds: A build pipeline promotes an image from Azure Container Registry without reviewing scanner findings or known severe package vulnerabilities. Which remediation best addresses the specific issue?

  1. Review the relevant Defender for Cloud DevOps infrastructure-as-code finding and fix the insecure template before deployment.
  2. Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment.
  3. Compare required features to current Defender for Servers plans and enable the appropriate supported tier for governed machines.
  4. Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings.

Explanation

Correct Answer

D:

The cause is: Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. The appropriate change is: Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings. Verify it with this outcome: Release evidence includes a current image scan report and a documented decision for any outstanding high-risk packages.

Incorrect Answers

A:

This action concerns defender for cloud devops iac misconfiguration, where Infrastructure-as-code syntax checks cannot replace security configuration assessment and governed release controls. The reported incident instead involves Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy.

B:

This action concerns defender for cloud alert investigation evidence, where A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. The corrective response here is “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings”; this alternative does not provide that response.

C:

This action concerns microsoft defender for servers plan 2 eligibility, where Defender for Servers capabilities vary by plan tier, resource scope and supported deployment requirements. The stem reports a build pipeline promotes an image from Azure Container Registry without reviewing scanner findings or known severe package vulnerabilities; this control addresses a different failure condition.