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 24

Question 230

The cloud operations team reviews the following risk: Linux servers ship system telemetry but their authentication facility events are missing from the central detection environment. Which explanation fits the observed symptoms most closely?

  1. A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities.
  2. Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance.
  3. Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows.
  4. A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination.

Explanation

Correct Answer

D:

The described technical condition is: A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. The appropriate corrective action is: Enable the required syslog facility and severity in the Linux data collection rule and verify agent association. Confirm with: A controlled authentication test yields a timestamped syslog record in the authorized workspace.

Incorrect Answers

A:

A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. “Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content” would address that alternative cause, not the condition in this question: a DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination.

B:

“Align workspace or table retention to approved investigation and regulatory needs, considering costs and supported retention modes” responds to this separate finding: security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. This question instead needs “Enable the required syslog facility and severity in the Linux data collection rule and verify agent association”, so the alternative does not meet the stated condition.

C:

Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. “Create and enable an appropriate Sentinel analytic rule for the suspicious traffic pattern while retaining the dashboard for context” applies to that separate problem. The observed case is linux servers ship system telemetry but their authentication facility events are missing from the central detection environment; choosing this alternative would address the wrong failure mode.

Question 231

An Azure security engineer investigates the following incident: An Azure VM has TCP 3389 permanently exposed from all Internet addresses, and a security owner needs time-limited emergency access instead. Which result confirms the relevant security control is effective?

  1. A test VM reports the intended confidential security posture and protected boot chain.
  2. An approved SSH client reaches the private VM through Bastion without a VM public IP.
  3. The port opens only for an approved source and limited interval, then closes automatically.
  4. Approved administrators reach private VMs using Bastion while direct Internet RDP and SSH attempts fail.

Explanation

Correct Answer

C:

This validates the specific control for defender for cloud jit vm management: The VM's NSG exposes a persistent management port rather than enforcing just-in-time access. The associated corrective action is: Configure supported just-in-time VM access and remove persistent open management rules. Testing a different component would not establish this result.

Incorrect Answers

A:

Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory. “Choose supported confidential VM features and configure the correct security type and encryption settings” would address that alternative cause, not the condition in this question: the VM's NSG exposes a persistent management port rather than enforcing just-in-time access.

B:

“Use a supported Bastion native-client connection and required RBAC and network prerequisites” responds to this separate finding: supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. This question instead needs “Configure supported just-in-time VM access and remove persistent open management rules”, so the alternative does not meet the stated condition.

D:

Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. “Deploy Azure Bastion and remove unnecessary public management IPs and broad NSG management rules” applies to that separate problem. The observed case is an Azure VM has TCP 3389 permanently exposed from all Internet addresses, and a security owner needs time-limited emergency access instead; choosing this alternative would address the wrong failure mode.

Question 232

A platform security assessment reveals this issue: A Kubernetes service crashes repeatedly but the security team collects only VM infrastructure metrics and lacks container and audit diagnostics. What technical cause best accounts for the described behavior?

  1. The application's ingress configuration enables external exposure instead of internal-only routing.
  2. The Container App does not use an attached managed identity with the correct Key Vault data-plane permission.
  3. AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health.
  4. The container group relies on a long-lived shared credential rather than supported managed identity authorization.

Explanation

Correct Answer

C:

The described technical condition is: AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. The appropriate corrective action is: Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels. Confirm with: Security analysts can correlate pod restart, audit and security signals for the affected workload.

Incorrect Answers

A:

The application's ingress configuration enables external exposure instead of internal-only routing. “Configure internal ingress and supported network isolation for the Container App environment” would address that alternative cause, not the condition in this question: aKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health.

B:

“Attach a supported managed identity and grant the intended Key Vault secret-read role” responds to this separate finding: the Container App does not use an attached managed identity with the correct Key Vault data-plane permission. This question instead needs “Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels”, so the alternative does not meet the stated condition.

D:

The container group relies on a long-lived shared credential rather than supported managed identity authorization. “Enable an appropriate managed identity on the container group and grant limited blob data access” applies to that separate problem. The observed case is a Kubernetes service crashes repeatedly but the security team collects only VM infrastructure metrics and lacks container and audit diagnostics; choosing this alternative would address the wrong failure mode.

Question 233

A production Azure security implementation shows this failure: A hub appliance receives packets from a spoke VNet, but forwarding to another spoke fails because peerings were configured only for ordinary direct VNet traffic. What observation is the strongest validation evidence?

  1. Effective route inspection shows only intended propagated and explicit routes for the target subnet.
  2. Spoke-to-spoke traffic reaches its destination through the approved hub appliance and no unintended direct path exists.
  3. The newly assigned web VM receives authorized application traffic while non-member VMs remain excluded.
  4. The diagnostic result identifies the NSG rule responsible and the approved flow passes after targeted remediation.

Explanation

Correct Answer

B:

This validates the specific control for vnet peering forwarded traffic setting: The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. The associated corrective action is: Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs. 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: the necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.

C:

“Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria” responds to this separate finding: an ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. This question instead needs “Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs”, so the alternative does not meet the stated condition.

D:

The active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view. “Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision” applies to that separate problem. The observed case is a hub appliance receives packets from a spoke VNet, but forwarding to another spoke fails because peerings were configured only for ordinary direct VNet traffic; choosing this alternative would address the wrong failure mode.

Question 234

While validating an Azure workload, the security team finds: A central security owner enables a protection plan in one subscription and expects all subscriptions in the tenant to receive paid workload protection automatically. Which outcome most clearly verifies that the issue is resolved?

  1. The remediation operation succeeds and creates or updates only the intended governed configuration.
  2. The report documents coverage gaps and provides comparable evidence for each supported cloud control.
  3. The owner can demonstrate a mitigated exposure or a formally governed residual risk with appropriate expiration.
  4. Every governed subscription reports the expected Defender workload plan state and billed resource scope.

Explanation

Correct Answer

D:

This validates the specific control for defender for cloud environment settings inheritance: Defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption. The associated corrective action is: Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope. Testing a different component would not establish this result.

Incorrect Answers

A:

DeployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. “Inspect the assignment identity and grant the minimum documented remediation role at the required resource scope” would address that alternative cause, not the condition in this question: defender for Cloud protection plan and coverage settings require appropriate subscription or connector scope rather than tenant-wide assumption.

B:

“Check supported AWS assessment coverage, connector health and applicable cloud-specific configuration rules before comparing results” responds to this separate finding: control applicability and enabled cloud connectors differ across providers, so absent assessment coverage is not equivalent to a passing control. This question instead needs “Inspect plan configuration across intended subscriptions and configure the approved deployment method for each scope”, so the alternative does not meet the stated condition.

C:

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 a central security owner enables a protection plan in one subscription and expects all subscriptions in the tenant to receive paid workload protection automatically; choosing this alternative would address the wrong failure mode.

Question 235

The cloud operations team reviews the following risk: A data lake account permits access from all public networks despite a requirement to accept only applications in approved VNets. Which outcome most clearly verifies that the issue is resolved?

  1. Authorized reads continue while deletes or overwrites prohibited by retention are rejected.
  2. Shared Key requests are rejected while approved identity-based blob operations succeed.
  3. Approved clients access data and unauthorized public source IPs receive network access denial.
  4. A test overwrite creates a retrievable previous version that administrators can restore.

Explanation

Correct Answer

C:

This validates the specific control for storage firewall authorized private network: The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. The associated corrective action is: Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required. Testing a different component would not establish this result.

Incorrect Answers

A:

Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. “Configure the appropriate time-based immutability policy or legal hold for the protected container” would address that alternative cause, not the condition in this question: the storage account network firewall rules allow broad public endpoints instead of restricting to designated networks.

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 “Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required”, so the alternative does not meet the stated condition.

D:

Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. “Enable supported blob versioning and define backup or lifecycle protection for critical objects” applies to that separate problem. The observed case is a data lake account permits access from all public networks despite a requirement to accept only applications in approved VNets; choosing this alternative would address the wrong failure mode.

Question 236

While validating an Azure workload, the security team finds: A short-lived Azure Container Instance job uses a copied account key to fetch blobs, and its image logs inadvertently disclose the key. Which outcome most clearly verifies that the issue is resolved?

  1. An allowed management source can connect while test sources outside the ranges are blocked.
  2. The container reads approved blobs using its identity without a stored storage key.
  3. Noncompliant privileged pod manifests are rejected or audited according to policy while compliant ones run.
  4. Security analysts can correlate pod restart, audit and security signals for the affected workload.

Explanation

Correct Answer

B:

This validates the specific control for azure container instances managed identity: The container group relies on a long-lived shared credential rather than supported managed identity authorization. The associated corrective action is: Enable an appropriate managed identity on the container group and grant limited blob data access. Testing a different component would not establish this result.

Incorrect Answers

A:

The cluster's public API server authorized IP ranges were not configured for restricted administrative access. “Configure approved API server authorized IP ranges or move to private control-plane access” would address that alternative cause, not the condition in this question: the container group relies on a long-lived shared credential rather than supported managed identity authorization.

C:

“Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components” responds to this separate finding: cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. This question instead needs “Enable an appropriate managed identity on the container group and grant limited blob data access”, so the alternative does not meet the stated condition.

D:

AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. “Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels” applies to that separate problem. The observed case is a short-lived Azure Container Instance job uses a copied account key to fetch blobs, and its image logs inadvertently disclose the key; choosing this alternative would address the wrong failure mode.

Question 237

A production Azure security implementation shows this failure: An app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption. What observation is the strongest validation evidence?

  1. The client connects only to the legitimate database endpoint and rejects an untrusted test certificate.
  2. A low-privilege test user sees masked values while approved privileged users follow their allowed data access.
  3. Secrets are protected in the intended storage path and only approved workload identities can retrieve values.
  4. An eligible client mounts the share securely while outdated unencrypted access fails.

Explanation

Correct Answer

A:

This validates the specific control for azure sql network tls encryption: Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. The associated corrective action is: Configure supported SQL driver encryption with certificate chain and hostname validation enabled. Testing a different component would not establish this result.

Incorrect Answers

B:

SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. “Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers” would address that alternative cause, not the condition in this question: encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.

C:

“Enable supported secret encryption and external secret management using Key Vault where required” responds to this separate finding: kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. This question instead needs “Configure supported SQL driver encryption with certificate chain and hostname validation enabled”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption; choosing this alternative would address the wrong failure mode.

Question 238

An Azure security engineer investigates the following incident: A pod mounts static secrets in its deployment manifest even though the enterprise wants rotating secrets from Azure Key Vault. Which remediation best addresses the specific issue?

  1. Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible.
  2. Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation.
  3. Use controlled SSH public-key authentication and restrict access through Bastion or approved private management.
  4. Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths.

Explanation

Correct Answer

A:

The cause is: Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. The appropriate change is: Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible. Verify it with this outcome: The running pod obtains the required secret without the value embedded in the deployed manifest.

Incorrect Answers

B:

This action concerns aks workload image scanning, where Authentication to a container registry does not establish that deployed images meet vulnerability security requirements. The reported incident instead involves Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration.

C:

This action concerns linux ssh key management, where Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. The corrective response here is “Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible”; this alternative does not provide that response.

D:

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 stem reports a pod mounts static secrets in its deployment manifest even though the enterprise wants rotating secrets from Azure Key Vault; this control addresses a different failure condition.

Question 239

An Azure security engineer investigates the following incident: A storage account passes an Azure Policy compliance assessment, and its administrator asserts that this proves every blob operation is authorized. What governance practice would best prevent the same failure?

  1. Match vault tier and key protection type to compliance requirements before key creation and migration.
  2. Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan.
  3. Keep configuration policy checks separate from identity, data-plane and network access acceptance tests.
  4. Validate versionless and version-specific key behavior for each customer-managed key integration before scheduling rotation.

Explanation

Correct Answer

C:

This guardrail addresses azure policy evaluation versus data plane checks: Azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. The prevention measure is: Keep configuration policy checks separate from identity, data-plane and network access acceptance tests. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. “Match vault tier and key protection type to compliance requirements before key creation and migration” would address that alternative cause, not the condition in this question: azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing.

B:

“Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan” responds to this separate finding: key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. This question instead needs “Keep configuration policy checks separate from identity, data-plane and network access acceptance tests”, so the alternative does not meet the stated condition.

D:

A service configured with a version-specific key URI may not automatically follow newer key versions without a supported integration design. “Validate versionless and version-specific key behavior for each customer-managed key integration before scheduling rotation” applies to that separate problem. The observed case is a storage account passes an Azure Policy compliance assessment, and its administrator asserts that this proves every blob operation is authorized; choosing this alternative would address the wrong failure mode.

Question 240

During a cloud security review, the operations team observes: A web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured. Which recurring validation best protects against the observed problem?

  1. Test both private-resolution success and public-path denial whenever a new Private Endpoint is added.
  2. Verify DNS zone links and forwarders for all VNets consuming a private service.
  3. Validate App Service inbound and outbound network controls independently in deployment testing.
  4. Check supported private endpoint network policy settings before relying on subnet inspection rules.

Explanation

Correct Answer

C:

This guardrail addresses app service vnet integration outbound path: App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. The prevention measure is: Validate App Service inbound and outbound network controls independently in deployment testing. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

A private endpoint has not been configured or public network access has not been restricted for the resource. “Test both private-resolution success and public-path denial whenever a new Private Endpoint is added” would address that alternative cause, not the condition in this question: app Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections.

B:

“Verify DNS zone links and forwarders for all VNets consuming a private service” responds to this separate finding: the private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. This question instead needs “Validate App Service inbound and outbound network controls independently in deployment testing”, so the alternative does not meet the stated condition.

D:

Private Endpoint network policies need appropriate supported subnet settings before NSG or UDR policies can apply as intended. “Check supported private endpoint network policy settings before relying on subnet inspection rules” applies to that separate problem. The observed case is a web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured; choosing this alternative would address the wrong failure mode.