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 87

Question 860

An Azure security engineer investigates the following incident: A regulated organization needs to apply a coordinated security baseline to ten subscriptions, but administrators assign isolated definitions with inconsistent parameters. Which safeguard would best prevent this issue from recurring?

  1. Keep configuration policy checks separate from identity, data-plane and network access acceptance tests.
  2. Audit exclusions whenever subscriptions move between management groups or baseline assignments change.
  3. Review initiative versions and parameter mappings before every organization wide compliance rollout.
  4. Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change.

Explanation

Correct Answer

C:

This guardrail addresses azure policy initiative and parameter assignments: Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. The prevention measure is: Review initiative versions and parameter mappings before every organization wide compliance rollout. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. “Keep configuration policy checks separate from identity, data-plane and network access acceptance tests” would address that alternative cause, not the condition in this question: without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions.

B:

“Audit exclusions whenever subscriptions move between management groups or baseline assignments change” responds to this separate finding: an excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. This question instead needs “Review initiative versions and parameter mappings before every organization wide compliance rollout”, so the alternative does not meet the stated condition.

D:

Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client. “Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change” applies to that separate problem. The observed case is a regulated organization needs to apply a coordinated security baseline to ten subscriptions, but administrators assign isolated definitions with inconsistent parameters; choosing this alternative would address the wrong failure mode.

Question 861

An Azure security engineer investigates the following incident: An Azure SQL database is administered only by a shared SQL login, contrary to corporate requirements for named Entra identity lifecycle management. Which explanation fits the observed symptoms most closely?

  1. The file access path needs compatible secure SMB protocol and supported encrypted transport settings.
  2. TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.
  3. Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls.
  4. The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication.

Explanation

Correct Answer

D:

The described technical condition is: The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. The appropriate corrective action is: Configure the Microsoft Entra administrator and create appropriate contained database users and roles. Confirm with: Authorized Entra principals connect and act within granted database roles without using the shared SQL account.

Incorrect Answers

A:

The file access path needs compatible secure SMB protocol and supported encrypted transport settings. “Use supported modern SMB client configuration and private connectivity or TLS where applicable” would address that alternative cause, not the condition in this question: the SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication.

B:

“Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration” responds to this separate finding: tLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. This question instead needs “Configure the Microsoft Entra administrator and create appropriate contained database users and roles”, so the alternative does not meet the stated condition.

C:

Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. “Enable supported secret encryption and external secret management using Key Vault where required” applies to that separate problem. The observed case is an Azure SQL database is administered only by a shared SQL login, contrary to corporate requirements for named Entra identity lifecycle management; choosing this alternative would address the wrong failure mode.

Question 862

While validating an Azure workload, the security team finds: Three VNets are peered as A-to-hub and hub-to-B, but application teams expect A and B to communicate automatically without routes or appliances. Which remediation best addresses the specific issue?

  1. Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls.
  2. Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs.
  3. Correct the group membership query or approved explicit membership and deploy the security configuration.
  4. Change the governing security admin policy through approved central administration rather than widening local NSGs.

Explanation

Correct Answer

B:

The cause is: VNet peering does not inherently create transitive routing between other independently peered VNets. The appropriate change is: Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs. Verify it with this outcome: Traffic between the two spokes uses the intended hub transit path and is subject to inspection.

Incorrect Answers

A:

This action concerns service tag outbound allow scoping, where A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. The reported incident instead involves VNet peering does not inherently create transitive routing between other independently peered VNets.

C:

This action concerns virtual network manager dynamic network group, where The dynamic network group criteria do not include the intended VNet attributes or scope. The corrective response here is “Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs”; this alternative does not provide that response.

D:

This action concerns azure virtual network manager security admin rules, where An enforced security admin deny rule has higher governance precedence than the workload NSG allow. The stem reports three VNets are peered as A-to-hub and hub-to-B, but application teams expect A and B to communicate automatically without routes or appliances; this control addresses a different failure condition.

Question 863

A platform security assessment reveals this issue: Developers redeploy vulnerable old container tags because artifact repositories retain uncontrolled image versions without review. Which recurring validation best protects against the observed problem?

  1. Validate ACR private link and data endpoint DNS as part of cluster network changes.
  2. Reassess API throttling limits and correlation identifiers following traffic-pattern changes.
  3. Review container image lifecycle and tag policy with vulnerability remediation records.
  4. Prohibit sharing account keys with external consumers and inventory issued SAS capabilities.

Explanation

Correct Answer

C:

This guardrail addresses acr image retention and digest hygiene: Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. The prevention measure is: Review container image lifecycle and tag policy with vulnerability remediation records. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Private ACR registry connectivity needs supported Private Link endpoint and correct DNS resolution for registry access. “Validate ACR private link and data endpoint DNS as part of cluster network changes” would address that alternative cause, not the condition in this question: unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment.

B:

“Reassess API throttling limits and correlation identifiers following traffic-pattern changes” responds to this separate finding: the API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. This question instead needs “Review container image lifecycle and tag policy with vulnerability remediation records”, so the alternative does not meet the stated condition.

D:

Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. “Prohibit sharing account keys with external consumers and inventory issued SAS capabilities” applies to that separate problem. The observed case is developers redeploy vulnerable old container tags because artifact repositories retain uncontrolled image versions without review; choosing this alternative would address the wrong failure mode.

Question 864

A regulated Azure tenant has this security condition: A background daemon calls Microsoft Graph without a signed-in user but requests delegated permission scopes that rely on user context. What governance practice would best prevent the same failure?

  1. Review tenant-local service principal assignments and consent during vendor onboarding and exit.
  2. Audit app role assignments and test default-deny authorization paths during release reviews.
  3. Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles.
  4. Review delegated and application permissions separately for every new unattended integration.

Explanation

Correct Answer

D:

This guardrail addresses delegated versus application api permissions: Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. The prevention measure is: Review delegated and application permissions separately for every new unattended integration. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. “Review tenant-local service principal assignments and consent during vendor onboarding and exit” would address that alternative cause, not the condition in this question: delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions.

B:

“Audit app role assignments and test default-deny authorization paths during release reviews” responds to this separate finding: successful authentication does not establish application authorization; app roles and assignments are not enforced. This question instead needs “Review delegated and application permissions separately for every new unattended integration”, so the alternative does not meet the stated condition.

C:

Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. “Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles” applies to that separate problem. The observed case is a background daemon calls Microsoft Graph without a signed-in user but requests delegated permission scopes that rely on user context; choosing this alternative would address the wrong failure mode.

Question 865

The cloud operations team reviews the following risk: A SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation. Which outcome most clearly verifies that the issue is resolved?

  1. Application Gateway reports healthy targets and completes an end-to-end request to the application.
  2. Authorized internal clients call the API through a permitted private path and public probes fail.
  3. Only authorized internal clients reach hosted apps, and operations can verify the isolated hosting path.
  4. The managed instance deploys in the intended delegated subnet and responds only to permitted connections.

Explanation

Correct Answer

D:

This validates the specific control for azure sql managed instance subnet requirements: SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The associated corrective action is: Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls. Testing a different component would not establish this result.

Incorrect Answers

A:

The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. “Correct the custom health probe to match the actual service endpoint and backend settings” would address that alternative cause, not the condition in this question: sQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.

B:

“Configure a supported APIM private networking option and restrict public gateway exposure as required” responds to this separate finding: the chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. This question instead needs “Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls”, so the alternative does not meet the stated condition.

C:

The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. “Deploy a supported internal App Service Environment and configure ingress and outbound network controls” applies to that separate problem. The observed case is a SQL Managed Instance deployment fails network prerequisites because engineers place the instance in a shared VM subnet without the correct delegation; choosing this alternative would address the wrong failure mode.

Question 866

A production Azure security implementation shows this failure: An administrator enables password-based SSH for Internet reachable Linux VMs and never rotates the shared password after personnel departures. What should the engineer implement first to address the weakness?

  1. Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths.
  2. Enable supported vault soft delete and enhanced protection settings including immutable backup where required.
  3. Use controlled SSH public-key authentication and restrict access through Bastion or approved private management.
  4. Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible.

Explanation

Correct Answer

C:

The cause is: Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. The appropriate change is: Use controlled SSH public-key authentication and restrict access through Bastion or approved private management. Verify it with this outcome: Only approved private keys authenticate to the private Linux VM and shared password login is unavailable.

Incorrect Answers

A:

This action concerns aks private cluster control plane, where The cluster uses a public API server endpoint rather than a supported private AKS cluster design. The reported incident instead involves Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management.

B:

This action concerns recovery services vault soft delete, where Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. The corrective response here is “Use controlled SSH public-key authentication and restrict access through Bastion or approved private management”; this alternative does not provide that response.

D:

This action concerns aks key vault csi secret retrieval, where Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. The stem reports an administrator enables password-based SSH for Internet reachable Linux VMs and never rotates the shared password after personnel departures; this control addresses a different failure condition.

Question 867

A Microsoft Azure administrator receives this requirement: A scheduled Sentinel rule runs every 15 minutes but looks back only two minutes, allowing delayed logs to fall into unobserved intervals. Which underlying control gap is responsible for the issue?

  1. Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance.
  2. Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained.
  3. Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation.
  4. A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation.

Explanation

Correct Answer

D:

The described technical condition is: A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. The appropriate corrective action is: Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay. Confirm with: Late-arriving simulated authentication events are detected once without producing excessive duplicate incidents.

Incorrect Answers

A:

Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. “Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes” would address that alternative cause, not the condition in this question: a rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation.

B:

“Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema” responds to this separate finding: unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. This question instead needs “Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay”, so the alternative does not meet the stated condition.

C:

Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics” applies to that separate problem. The observed case is a scheduled Sentinel rule runs every 15 minutes but looks back only two minutes, allowing delayed logs to fall into unobserved intervals; choosing this alternative would address the wrong failure mode.

Question 868

The cloud operations team reviews the following risk: A security owner exports a list of all VMs but accidentally filters only resources tagged Production while untagged systems remain deployed. What governance practice would best prevent the same failure?

  1. Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks.
  2. Cross-check inventory queries against management group scope and subscription lifecycle, not only user-maintained labels.
  3. Require residual-risk signoff and evidence of compensating controls before closing high-severity posture exceptions.
  4. Require attribution evidence and review of discovered assets before initiating high-impact external remediation.

Explanation

Correct Answer

B:

This guardrail addresses defender for cloud azure resource graph query validation: Tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth. The prevention measure is: Cross-check inventory queries against management group scope and subscription lifecycle, not only user-maintained labels. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. “Reconcile cloud project lifecycle and connector coverage during recurring multicloud inventory checks” would address that alternative cause, not the condition in this question: tag-based inventory selection excludes untagged assets and is insufficient as a complete governance source of truth.

C:

“Require residual-risk signoff and evidence of compensating controls before closing high-severity posture exceptions” responds to this separate finding: recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. This question instead needs “Cross-check inventory queries against management group scope and subscription lifecycle, not only user-maintained labels”, so the alternative does not meet the stated condition.

D:

Attack-surface discovery may produce candidates that require ownership and affiliation validation before remediation. “Require attribution evidence and review of discovered assets before initiating high-impact external remediation” applies to that separate problem. The observed case is a security owner exports a list of all VMs but accidentally filters only resources tagged Production while untagged systems remain deployed; choosing this alternative would address the wrong failure mode.

Question 869

During a cloud security review, the operations team observes: An AWS account appears in Defender for Cloud inventory but its resources have no useful configuration findings after onboarding. What technical cause best accounts for the described behavior?

  1. Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet.
  2. A multicloud connector can exist while its required permissions, services or security plan settings are incomplete.
  3. A security inventory that excludes child subscriptions and connected accounts cannot give complete exposure or asset ownership coverage.
  4. Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path.

Explanation

Correct Answer

B:

The described technical condition is: A multicloud connector can exist while its required permissions, services or security plan settings are incomplete. The appropriate corrective action is: Review and repair the AWS connector's authorized access and enable applicable posture assessment capabilities. Confirm with: Target AWS resources appear with relevant configuration posture assessments and appropriate permission health.

Incorrect Answers

A:

Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. “Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains” would address that alternative cause, not the condition in this question: a multicloud connector can exist while its required permissions, services or security plan settings are incomplete.

C:

“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 “Review and repair the AWS connector's authorized access and enable applicable posture assessment capabilities”, so the alternative does not meet the stated condition.

D:

Recording risk acceptance changes governance status but does not remediate the vulnerable configuration or remove its exploit path. “Reassess the finding, record accountable risk approval and implement a real fix or independently tested compensating controls” applies to that separate problem. The observed case is an AWS account appears in Defender for Cloud inventory but its resources have no useful configuration findings after onboarding; choosing this alternative would address the wrong failure mode.

Question 870

During a cloud security review, the operations team observes: Two Azure Functions need a consistent workload principal across independent deployments, but each uses a transient system-assigned identity that breaks shared policy references. What should the engineer implement first to address the weakness?

  1. Replace the expired secret using a controlled rotation or migrate to certificate credentials or workload identity federation.
  2. Provision or consent the enterprise application service principal and configure appropriate access and controls.
  3. Assign the scoped Key Vault Secrets User role or appropriate narrower data access to the managed identity.
  4. Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly.

Explanation

Correct Answer

D:

The cause is: Separate system-assigned identities do not provide the stable reusable principal desired across resources. The appropriate change is: Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly. Verify it with this outcome: Both functions obtain tokens for the approved user-assigned identity without duplicating secrets.

Incorrect Answers

A:

This action concerns application client secret expiration, where The app registration client credential has expired and the workload has no safe rotation mechanism. The reported incident instead involves Separate system-assigned identities do not provide the stable reusable principal desired across resources.

B:

This action concerns enterprise application service principal, where The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. The corrective response here is “Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly”; this alternative does not provide that response.

C:

This action concerns key vault data role for workload identity, where Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. The stem reports two Azure Functions need a consistent workload principal across independent deployments, but each uses a transient system-assigned identity that breaks shared policy references; this control addresses a different failure condition.