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 52

Question 510

A regulated Azure tenant has this security condition: A security team deploys Log Analytics and expects the workspace to provide Microsoft Sentinel analytics and incidents without onboarding Sentinel. 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. Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition.
  3. Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema.
  4. Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics.

Explanation

Correct Answer

A:

The cause is: A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. The appropriate change is: Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content. Verify it with this outcome: The workspace exposes Sentinel analytics, incident management and authorized security content appropriately.

Incorrect Answers

B:

This action concerns sentinel automation rule order and stop processing, where Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. The reported incident instead involves A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities.

C:

This action concerns azure monitor transformation for sensitive fields, where Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. The corrective response here is “Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content”; this alternative does not provide that response.

D:

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 stem reports a security team deploys Log Analytics and expects the workspace to provide Microsoft Sentinel analytics and incidents without onboarding Sentinel; this control addresses a different failure condition.

Question 511

A Microsoft Azure administrator receives this requirement: A security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events. After remediation, which test result best proves the intended change?

  1. An eligible client mounts the share securely while outdated unencrypted access fails.
  2. The client connects only to the legitimate database endpoint and rejects an untrusted test certificate.
  3. A controlled database operation produces an accessible audit record with principal and action details.
  4. Secrets are protected in the intended storage path and only approved workload identities can retrieve values.

Explanation

Correct Answer

C:

This validates the specific control for azure sql auditing destination configuration: Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. The associated corrective action is: Enable supported SQL auditing with the necessary categories and protected retention settings. Testing a different component would not establish this result.

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: azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination.

B:

“Configure supported SQL driver encryption with certificate chain and hostname validation enabled” responds to this separate finding: encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. This question instead needs “Enable supported SQL auditing with the necessary categories and protected retention settings”, so the alternative does not meet the stated condition.

D:

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 a security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events; choosing this alternative would address the wrong failure mode.

Question 512

During a cloud security review, the operations team observes: An app team creates an NSG allow for a port that organizational policy denies through Virtual Network Manager security admin rules, but access still fails. Which underlying control gap is responsible for the issue?

  1. A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges.
  2. Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid.
  3. An enforced security admin deny rule has higher governance precedence than the workload NSG allow.
  4. The dynamic network group criteria do not include the intended VNet attributes or scope.

Explanation

Correct Answer

C:

The described technical condition is: An enforced security admin deny rule has higher governance precedence than the workload NSG allow. The appropriate corrective action is: Change the governing security admin policy through approved central administration rather than widening local NSGs. Confirm with: The forbidden flow remains blocked until a reviewed policy exception is applied centrally.

Incorrect Answers

A:

A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. “Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls” would address that alternative cause, not the condition in this question: an enforced security admin deny rule has higher governance precedence than the workload NSG allow.

B:

“Renumber or redesign the address space before establishing peering or use an approved translation architecture” responds to this separate finding: azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. This question instead needs “Change the governing security admin policy through approved central administration rather than widening local NSGs”, so the alternative does not meet the stated condition.

D:

The dynamic network group criteria do not include the intended VNet attributes or scope. “Correct the group membership query or approved explicit membership and deploy the security configuration” applies to that separate problem. The observed case is an app team creates an NSG allow for a port that organizational policy denies through Virtual Network Manager security admin rules, but access still fails; choosing this alternative would address the wrong failure mode.

Question 513

A regulated Azure tenant has this security condition: A container image with known vulnerable packages is pulled into production AKS because teams check only that the registry login succeeds. Which outcome most clearly verifies that the issue is resolved?

  1. The vulnerable image is detected and a patched replacement is deployed before production exposure.
  2. Approved application flows succeed while prohibited cross-namespace traffic is dropped.
  3. Authorized in-network management clients reach the API while external Internet probes cannot.
  4. Recreated instances retrieve approved secrets securely without relying on local ephemeral disk recovery.

Explanation

Correct Answer

A:

This validates the specific control for aks workload image scanning: Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. The associated corrective action is: Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation. Testing a different component would not establish this result.

Incorrect Answers

B:

Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. “Enable the supported network policy option and enforce namespace/pod label based allowlists” would address that alternative cause, not the condition in this question: authentication to a container registry does not establish that deployed images meet vulnerability security requirements.

C:

“Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths” 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 “Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation”, so the alternative does not meet the stated condition.

D:

Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. “Move credentials into a managed secrets service and use approved persistent data storage where needed” applies to that separate problem. The observed case is a container image with known vulnerable packages is pulled into production AKS because teams check only that the registry login succeeds; choosing this alternative would address the wrong failure mode.

Question 514

The cloud operations team reviews the following risk: A developer accidentally deletes important blobs and discovers no soft-deleted recovery versions because blob soft delete is off. Which result confirms the relevant security control is effective?

  1. The partner uploads an authorized object before expiry and cannot delete unrelated blobs or reuse an expired token.
  2. Shared Key requests are rejected while approved identity-based blob operations succeed.
  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

C:

This validates the specific control for blob soft delete recovery window: The storage account lacks blob soft delete retention to recover recently removed objects. The associated corrective action is: Enable blob soft delete with an appropriate retention period and verify the restore process. Testing a different component would not establish this result.

Incorrect Answers

A:

The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. “Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions” would address that alternative cause, not the condition in this question: the storage account lacks blob soft delete retention to recover recently removed objects.

B:

“Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS” responds to this separate finding: the account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. This question instead needs “Enable blob soft delete with an appropriate retention period and verify the restore process”, 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 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 515

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 configuration change most directly resolves this problem?

  1. Enable appropriate APIM subscription requirements and validate product/API associations.
  2. Configure approved APIM rate-limit or quota policies keyed to appropriate identities or subscriptions.
  3. Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys.
  4. Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks.

Explanation

Correct Answer

A:

The cause is: The API or product does not require the intended APIM subscription key or equivalent authentication control. The appropriate change is: Enable appropriate APIM subscription requirements and validate product/API associations. Verify it with this outcome: A request without authorized API credentials is rejected and approved subscribers receive normal responses.

Incorrect Answers

B:

This action concerns apim throttling policy for abuse, where The API gateway lacks a suitable rate limit or quota enforcement policy for individual callers. The reported incident instead involves The API or product does not require the intended APIM subscription key or equivalent authentication control.

C:

This action concerns storage shared key versus sas distinction, where Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. The corrective response here is “Enable appropriate APIM subscription requirements and validate product/API associations”; this alternative does not provide that response.

D:

This action concerns acr image retention and digest hygiene, where Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. The stem reports an Azure API Management product accepts anonymous calls to a sensitive paid API because subscription enforcement is disabled; this control addresses a different failure condition.

Question 516

While validating an Azure workload, the security team finds: 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 condition most directly explains the failure?

  1. Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type.
  2. Built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment.
  3. An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection.
  4. An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended.

Explanation

Correct Answer

D:

The described technical condition is: An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. The appropriate corrective action is: Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control. Confirm with: The production subscription enters the relevant compliance assessment and its resources receive the expected enforcement.

Incorrect Answers

A:

Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. “Provision supported HSM-protected keys in the appropriate vault tier and migrate applications according to key-dependency rules” would address that alternative cause, not the condition in this question: an excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended.

B:

“Create and test a supported custom Azure Policy definition or initiative and attach it to the relevant regulatory assessment process” responds to this separate finding: built-in compliance assessments may not cover organization-specific obligations without a custom definition and properly mapped assessment. This question instead needs “Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control”, so the alternative does not meet the stated condition.

C:

An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. “Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 517

A Microsoft Azure administrator receives this requirement: An organization grants access to a SaaS vendor app based on its global application registration ID but forgets to create and manage the local enterprise application. Which underlying control gap is responsible for the issue?

  1. The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy.
  2. Separate system-assigned identities do not provide the stable reusable principal desired across resources.
  3. The application's registered redirect URI does not match the callback URI used in the authorization request.
  4. The workload is not using its platform-managed identity and therefore depends on long-lived application secrets.

Explanation

Correct Answer

A:

The described technical condition is: The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. The appropriate corrective action is: Provision or consent the enterprise application service principal and configure appropriate access and controls. Confirm with: The consuming tenant lists the app service principal and can enforce authorized user assignment.

Incorrect Answers

B:

Separate system-assigned identities do not provide the stable reusable principal desired across resources. “Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly” would address that alternative cause, not the condition in this question: the multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy.

C:

“Register the exact approved redirect URI and update the app client flow accordingly” responds to this separate finding: the application's registered redirect URI does not match the callback URI used in the authorization request. This question instead needs “Provision or consent the enterprise application service principal and configure appropriate access and controls”, so the alternative does not meet the stated condition.

D:

The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. “Enable an appropriate managed identity and grant narrowly scoped storage data authorization to that identity” applies to that separate problem. The observed case is an organization grants access to a SaaS vendor app based on its global application registration ID but forgets to create and manage the local enterprise application; choosing this alternative would address the wrong failure mode.

Question 518

While validating an Azure workload, the security team finds: A storage account is limited to selected VNets but a newly created workload subnet reaches only the public service and fails its access restriction. Which remediation best addresses the specific issue?

  1. Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval.
  2. Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage.
  3. Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service.
  4. Configure regional App Service VNet integration and the necessary subnet routing and DNS.

Explanation

Correct Answer

B:

The cause is: The required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. The appropriate change is: Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage. Verify it with this outcome: The selected subnet accesses the restricted account while unlisted subnets remain blocked.

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 required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall.

C:

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 corrective response here is “Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage”; this alternative does not provide that response.

D:

This action concerns app service vnet integration outbound path, where App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. The stem reports a storage account is limited to selected VNets but a newly created workload subnet reaches only the public service and fails its access restriction; this control addresses a different failure condition.

Question 519

During a cloud security review, the operations team observes: A storage engineer has Storage Blob Data Reader at a management group while security expects access limited to one storage container, resulting in read access across child subscriptions. What technical cause best accounts for the described behavior?

  1. NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule.
  2. Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted.
  3. Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle.
  4. PIM role settings have not required the intended multifactor or authentication-strength control at activation.

Explanation

Correct Answer

B:

The described technical condition is: Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. The appropriate corrective action is: Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope. Confirm with: The operator reads the approved container but is denied access to an unrelated descendant subscription.

Incorrect Answers

A:

NotActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. “Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment” would address that alternative cause, not the condition in this question: azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted.

C:

“Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls” responds to this separate finding: direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. This question instead needs “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope”, so the alternative does not meet the stated condition.

D:

PIM role settings have not required the intended multifactor or authentication-strength control at activation. “Configure the PIM role activation requirements to demand the approved strong authentication method” applies to that separate problem. The observed case is a storage engineer has Storage Blob Data Reader at a management group while security expects access limited to one storage container, resulting in read access across child subscriptions; choosing this alternative would address the wrong failure mode.

Question 520

A platform security assessment reveals this issue: A SOC creates a Sentinel workbook showing a spike in denied firewall connections and assumes it will automatically open incidents. What technical cause best accounts for the described behavior?

  1. Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents.
  2. Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.
  3. Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation.
  4. Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events.

Explanation

Correct Answer

B:

The described technical condition is: Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. The appropriate corrective action is: Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context. Confirm with: A controlled attack-pattern simulation opens a detection incident and the workbook continues displaying its trend.

Incorrect Answers

A:

Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. “Grant only the necessary supported firewall action permission to the playbook identity and verify the Logic App connection” would address that alternative cause, not the condition in this question: workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.

C:

“Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics” responds to this separate finding: threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. This question instead needs “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context”, so the alternative does not meet the stated condition.

D:

Sentinel automation rule event triggers distinguish incident creation, updates and other supported workflow events. “Change the automation rule to the correct incident-created trigger with the intended scoped conditions” applies to that separate problem. The observed case is a SOC creates a Sentinel workbook showing a spike in denied firewall connections and assumes it will automatically open incidents; choosing this alternative would address the wrong failure mode.