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 3

Question 20

A Microsoft Azure administrator receives this requirement: A Kubernetes service crashes repeatedly but the security team collects only VM infrastructure metrics and lacks container and audit diagnostics. Which operating control most directly reduces this recurring risk?

  1. Review environment variables and container logging for unintended credential exposure.
  2. Track identity integration feature lifecycle before Kubernetes version upgrades.
  3. Test AKS diagnostic collection coverage after cluster upgrades and namespace changes.
  4. Scan container deployment manifests and logs for accidentally exposed credentials.

Explanation

Correct Answer

C:

This guardrail addresses aks control plane and container logging: AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. The prevention measure is: Test AKS diagnostic collection coverage after cluster upgrades and namespace changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The container group relies on a long-lived shared credential rather than supported managed identity authorization. “Review environment variables and container logging for unintended credential exposure” 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:

“Track identity integration feature lifecycle before Kubernetes version upgrades” responds to this separate finding: the workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. This question instead needs “Test AKS diagnostic collection coverage after cluster upgrades and namespace changes”, so the alternative does not meet the stated condition.

D:

Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. “Scan container deployment manifests and logs for accidentally exposed credentials” 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 21

A platform security assessment reveals this issue: A pod mounts static secrets in its deployment manifest even though the enterprise wants rotating secrets from Azure Key Vault. Which recurring validation best protects against the observed problem?

  1. Use private API endpoint requirements during AKS cluster provisioning and access reviews.
  2. Test both ingress and egress network policies with real pods after label changes.
  3. Validate secret refresh and authorization when rotating Key Vault credentials consumed by clusters.
  4. Review snapshot export and managed disk permissions as part of sensitive VM data governance.

Explanation

Correct Answer

C:

This guardrail addresses aks key vault csi secret retrieval: Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. The prevention measure is: Validate secret refresh and authorization when rotating Key Vault credentials consumed by clusters. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The cluster uses a public API server endpoint rather than a supported private AKS cluster design. “Use private API endpoint requirements during AKS cluster provisioning and access reviews” would address that alternative cause, not the condition in this question: application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration.

B:

“Test both ingress and egress network policies with real pods after label changes” responds to this separate finding: namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. This question instead needs “Validate secret refresh and authorization when rotating Key Vault credentials consumed by clusters”, so the alternative does not meet the stated condition.

D:

Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization. “Review snapshot export and managed disk permissions as part of sensitive VM data governance” applies to that separate problem. The observed case is a pod mounts static secrets in its deployment manifest even though the enterprise wants rotating secrets from Azure Key Vault; choosing this alternative would address the wrong failure mode.

Question 22

While validating an Azure workload, the security team finds: An externally hosted user connects to a firewall public IP and port but never reaches the internal application service because no translation rule exists. 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. Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service.
  3. Correct the group membership query or approved explicit membership and deploy the security configuration.
  4. Deploy the approved configuration to the correct regions and verify the deployed state.

Explanation

Correct Answer

B:

The cause is: Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. The appropriate change is: Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service. Verify it with this outcome: The published external endpoint reaches only the approved internal listener and is logged.

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 Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port.

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 “Create an authorized Azure Firewall DNAT rule mapping the intended public address and port to the private service”; this alternative does not provide that response.

D:

This action concerns central network intent deployment region, where Saving network manager intent does not itself apply connectivity or security configuration to target regions. The stem reports an externally hosted user connects to a firewall public IP and port but never reaches the internal application service because no translation rule exists; this control addresses a different failure condition.

Question 23

While validating an Azure workload, the security team finds: An organization wants just-in-time privileged access but several permanent Global Administrator assignments are created without review or notification. Which explanation fits the observed symptoms most closely?

  1. Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles.
  2. Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments.
  3. The group entitlement has no scheduled access review or defined decision maker to remove stale members.
  4. A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block.

Explanation

Correct Answer

B:

The described technical condition is: Standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments. The appropriate corrective action is: Review permanent assignments and configure PIM alerts, justification and eligible access where feasible. Confirm with: Security receives and investigates alerts for new permanent privileged assignments, reducing unnecessary standing admins.

Incorrect Answers

A:

Permanent privileged group membership bypasses the intended time-bounded activation workflow for group-derived roles. “Configure PIM for Groups with eligible membership and required activation controls where supported” would address that alternative cause, not the condition in this question: standing tenant-wide administrator access lacks PIM monitoring and risk-based alert response for privileged assignments.

C:

“Configure Microsoft Entra access reviews for the relevant group with reviewers and automatic remediation as authorized” responds to this separate finding: the group entitlement has no scheduled access review or defined decision maker to remove stale members. This question instead needs “Review permanent assignments and configure PIM alerts, justification and eligible access where feasible”, so the alternative does not meet the stated condition.

D:

A Conditional Access policy in report-only state evaluates hypothetical results without enforcing the configured block. “Review report-only results, correct exclusions and switch the approved policy to On for enforcement” applies to that separate problem. The observed case is an organization wants just-in-time privileged access but several permanent Global Administrator assignments are created without review or notification; choosing this alternative would address the wrong failure mode.

Question 24

A regulated Azure tenant has this security condition: A data lake receives unusual external blob reads and the organization relies only on daily access log exports for incident detection. Which result confirms the relevant security control is effective?

  1. Release evidence includes a current image scan report and a documented decision for any outstanding high-risk packages.
  2. The critical exposed resource is patched or protected first and the residual exposure is documented.
  3. A controlled suspicious access simulation generates a triageable security alert containing the impacted storage context.
  4. The case records corroborated benign activity or documented remediation of the suspicious command chain.

Explanation

Correct Answer

C:

This validates the specific control for defender for storage sensitive data threat detection: Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. The associated corrective action is: Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts. Testing a different component would not establish this result.

Incorrect Answers

A:

Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings” would address that alternative cause, not the condition in this question: access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior.

B:

“Use Defender vulnerability recommendations and workload context to prioritize the exposed production flaw” responds to this separate finding: patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. This question instead needs “Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts”, so the alternative does not meet the stated condition.

D:

A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. “Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment” applies to that separate problem. The observed case is a data lake receives unusual external blob reads and the organization relies only on daily access log exports for incident detection; choosing this alternative would address the wrong failure mode.

Question 25

A Microsoft Azure administrator receives this requirement: A client attempts to mount Azure Files using an obsolete insecure SMB configuration and cannot meet company encryption and authentication requirements. Which underlying control gap is responsible for the issue?

  1. Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.
  2. The file access path needs compatible secure SMB protocol and supported encrypted transport settings.
  3. TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.
  4. TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing.

Explanation

Correct Answer

B:

The described technical condition is: The file access path needs compatible secure SMB protocol and supported encrypted transport settings. The appropriate corrective action is: Use supported modern SMB client configuration and private connectivity or TLS where applicable. Confirm with: An eligible client mounts the share securely while outdated unencrypted access fails.

Incorrect Answers

A:

Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. “Configure supported SQL driver encryption with certificate chain and hostname validation enabled” would address that alternative cause, not the condition in this question: the file access path needs compatible secure SMB protocol and supported encrypted transport settings.

C:

“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 “Use supported modern SMB client configuration and private connectivity or TLS where applicable”, so the alternative does not meet the stated condition.

D:

TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. “Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients” applies to that separate problem. The observed case is a client attempts to mount Azure Files using an obsolete insecure SMB configuration and cannot meet company encryption and authentication requirements; choosing this alternative would address the wrong failure mode.

Question 26

During a cloud security review, the operations team observes: An application subnet can access many Azure Storage accounts even though governance permits only designated corporate storage resource IDs. Which recurring validation best protects against the observed problem?

  1. Treat private transport and payload encryption as separate security controls in architecture reviews.
  2. Review storage resource ID allowlists whenever approved service endpoint destinations change.
  3. Inventory subnet service endpoint configuration and service firewall allowances together.
  4. Verify DNS zone links and forwarders for all VNets consuming a private service.

Explanation

Correct Answer

B:

This guardrail addresses service endpoint policy destination allowlist: The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations. The prevention measure is: Review storage resource ID allowlists whenever approved service endpoint destinations change. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations.

C:

“Inventory subnet service endpoint configuration and service firewall allowances together” responds to this separate finding: the required virtual network Service Endpoint is not enabled for the subnet approved by the storage firewall. This question instead needs “Review storage resource ID allowlists whenever approved service endpoint destinations change”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is an application subnet can access many Azure Storage accounts even though governance permits only designated corporate storage resource IDs; choosing this alternative would address the wrong failure mode.

Question 27

An Azure security engineer investigates the following incident: A Kubernetes control-plane API endpoint is reachable from the public Internet even though the application platform requires private administration. Which explanation fits the observed symptoms most closely?

  1. The cluster uses a public API server endpoint rather than a supported private AKS cluster design.
  2. Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration.
  3. The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.
  4. Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management.

Explanation

Correct Answer

A:

The described technical condition is: The cluster uses a public API server endpoint rather than a supported private AKS cluster design. The appropriate corrective action is: Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths. Confirm with: Authorized in-network management clients reach the API while external Internet probes cannot.

Incorrect Answers

B:

Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration. “Configure supported Secrets Store CSI Driver with Key Vault and workload identity where eligible” would address that alternative cause, not the condition in this question: the cluster uses a public API server endpoint rather than a supported private AKS cluster design.

C:

“Configure workload identity on the service account and scoped access to the target Key Vault” responds to this separate finding: the workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. This question instead needs “Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths”, so the alternative does not meet the stated condition.

D:

Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. “Use controlled SSH public-key authentication and restrict access through Bastion or approved private management” applies to that separate problem. The observed case is a Kubernetes control-plane API endpoint is reachable from the public Internet even though the application platform requires private administration; choosing this alternative would address the wrong failure mode.

Question 28

A platform security assessment reveals this issue: An AKS cluster is enrolled in Azure and its nodes receive basic VM updates, but cluster configuration threats and workload alerts are not monitored. What technical cause best accounts for the described behavior?

  1. DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions.
  2. Node management alone does not provide full supported Defender for Containers security posture and workload protection.
  3. Vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations.
  4. Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy.

Explanation

Correct Answer

B:

The described technical condition is: Node management alone does not provide full supported Defender for Containers security posture and workload protection. The appropriate corrective action is: Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster. Confirm with: The cluster reports supported posture assessments and security alerts for its monitored Kubernetes workloads.

Incorrect Answers

A:

DevOps security connector setup can leave repository coverage incomplete due to scope, app installation or permissions. “Inspect the GitHub app installation and connector repository inclusion, then authorize only the intended repositories” would address that alternative cause, not the condition in this question: node management alone does not provide full supported Defender for Containers security posture and workload protection.

C:

“Enable the supported Defender for Key Vault plan and configure alert notifications for investigated unusual access” responds to this separate finding: vault access configuration and log retention do not independently supply timely specialized threat detection for suspicious vault operations. This question instead needs “Enable the relevant Defender for Containers protection and supported Kubernetes integration for the cluster”, so the alternative does not meet the stated condition.

D:

Container image storage and signing do not establish that the image has been vulnerability assessed and meets release policy. “Enable supported image vulnerability scanning and block deployment of images with unaccepted severe findings” applies to that separate problem. The observed case is an AKS cluster is enrolled in Azure and its nodes receive basic VM updates, but cluster configuration threats and workload alerts are not monitored; choosing this alternative would address the wrong failure mode.

Question 29

A Microsoft Azure administrator receives this requirement: On-premises Windows servers lack cloud security recommendations because the organization monitors only native Azure virtual machines. Which recurring validation best protects against the observed problem?

  1. Use cloud-specific capability and licensing matrices when enabling cross-cloud workload protection.
  2. Verify assignment identity rights with a pilot remediation instead of granting subscription Owner as a workaround.
  3. Audit non-Azure server enrollment and connector freshness whenever the hybrid server fleet changes.
  4. Revalidate exemption evidence and age periodically so exceptions do not mask ongoing exposure.

Explanation

Correct Answer

C:

This guardrail addresses azure arc hybrid server posture: Defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans. The prevention measure is: Audit non-Azure server enrollment and connector freshness whenever the hybrid server fleet changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Protection plans and agentless scanning coverage have provider-specific onboarding and subscription or account conditions. “Use cloud-specific capability and licensing matrices when enabling cross-cloud workload protection” would address that alternative cause, not the condition in this question: defender for Cloud hybrid security assessment requires appropriately connected non-Azure machines and enabled applicable plans.

B:

“Verify assignment identity rights with a pilot remediation instead of granting subscription Owner as a workaround” responds to this separate finding: deployIfNotExists or Modify remediation needs the policy assignment managed identity to have sufficient role permissions at the target scope. This question instead needs “Audit non-Azure server enrollment and connector freshness whenever the hybrid server fleet changes”, so the alternative does not meet the stated condition.

D:

An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. “Revalidate exemption evidence and age periodically so exceptions do not mask ongoing exposure” applies to that separate problem. The observed case is on-premises Windows servers lack cloud security recommendations because the organization monitors only native Azure virtual machines; choosing this alternative would address the wrong failure mode.

Question 30

A Microsoft Azure administrator receives this requirement: An Internet-facing App Service is listed in Defender for Cloud inventory but has no platform-specific attack detection despite known attempts. Which operating control most directly reduces this recurring risk?

  1. Continuously combine vulnerability severity with external reachability and asset importance in remediation planning.
  2. Test storage malware inspection and quarantine handling separately from encryption and access control checks.
  3. Include App Service protection in onboarding checks for Internet-exposed web applications.
  4. Verify container plan coverage and Kubernetes monitoring dependencies during every cluster deployment.

Explanation

Correct Answer

C:

This guardrail addresses defender for app service protection plan: Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. The prevention measure is: Include App Service protection in onboarding checks for Internet-exposed web applications. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Patch priority should consider vulnerability severity, exploitability, exposure and business criticality instead of a simple ticket age queue. “Continuously combine vulnerability severity with external reachability and asset importance in remediation planning” would address that alternative cause, not the condition in this question: inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan.

B:

“Test storage malware inspection and quarantine handling separately from encryption and access control checks” responds to this separate finding: storage encryption at rest does not inspect uploaded content for malware; appropriate Defender for Storage capabilities must be enabled where supported. This question instead needs “Include App Service protection in onboarding checks for Internet-exposed web applications”, so the alternative does not meet the stated condition.

D:

Node management alone does not provide full supported Defender for Containers security posture and workload protection. “Verify container plan coverage and Kubernetes monitoring dependencies during every cluster deployment” applies to that separate problem. The observed case is an Internet-facing App Service is listed in Defender for Cloud inventory but has no platform-specific attack detection despite known attempts; choosing this alternative would address the wrong failure mode.