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 57

Question 560

A Microsoft Azure administrator receives this requirement: A data lake account permits access from all public networks despite a requirement to accept only applications in approved VNets. What technical cause best accounts for the described behavior?

  1. Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning.
  2. The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks.
  3. The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose.
  4. Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone.

Explanation

Correct Answer

B:

The described technical condition is: The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. The appropriate corrective action is: Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required. Confirm with: Approved clients access data and unauthorized public source IPs receive network access denial.

Incorrect Answers

A:

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” 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.

C:

“Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions” responds to this separate finding: the SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. 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:

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” 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 561

A platform security assessment reveals this issue: 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 recurring validation best protects against the observed problem?

  1. Review network group membership drift after subscription and resource tagging changes.
  2. Review exposed DNAT entries against asset owners and remove obsolete Internet listeners.
  3. Review FQDN-based application rules for wildcard overreach and domain ownership changes.
  4. Document and test non-transitive peerings before granting inter-spoke network access.

Explanation

Correct Answer

D:

This guardrail addresses vnet peering non transitivity: VNet peering does not inherently create transitive routing between other independently peered VNets. The prevention measure is: Document and test non-transitive peerings before granting inter-spoke network access. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The dynamic network group criteria do not include the intended VNet attributes or scope. “Review network group membership drift after subscription and resource tagging changes” would address that alternative cause, not the condition in this question: vNet peering does not inherently create transitive routing between other independently peered VNets.

B:

“Review exposed DNAT entries against asset owners and remove obsolete Internet listeners” responds to this separate finding: inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. This question instead needs “Document and test non-transitive peerings before granting inter-spoke network access”, so the alternative does not meet the stated condition.

C:

A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. “Review FQDN-based application rules for wildcard overreach and domain ownership changes” applies to that separate problem. The observed case is 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; choosing this alternative would address the wrong failure mode.

Question 562

A platform security assessment reveals this issue: A support analyst runs SELECT against a customer table and sees full personal identifiers although the business requirement is to mask those fields for nonprivileged readers. What is the most appropriate corrective step?

  1. Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration.
  2. Configure supported SQL driver encryption with certificate chain and hostname validation enabled.
  3. Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers.
  4. Enable supported secret encryption and external secret management using Key Vault where required.

Explanation

Correct Answer

C:

The cause is: SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. The appropriate change is: Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers. Verify it with this outcome: A low-privilege test user sees masked values while approved privileged users follow their allowed data access.

Incorrect Answers

A:

This action concerns transparent data encryption at rest, where TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. The reported incident instead involves SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege.

B:

This action concerns azure sql network tls encryption, where Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. The corrective response here is “Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers”; this alternative does not provide that response.

D:

This action concerns aks secrets encryption at rest governance, where Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. The stem reports a support analyst runs SELECT against a customer table and sees full personal identifiers although the business requirement is to mask those fields for nonprivileged readers; this control addresses a different failure condition.

Question 563

A Microsoft Azure administrator receives this requirement: A security team allows all Internet outbound destinations because a VM must access Azure Storage, bypassing an existing policy intended to restrict egress. What should the engineer implement first to address the weakness?

  1. Change the governing security admin policy through approved central administration rather than widening local NSGs.
  2. Renumber or redesign the address space before establishing peering or use an approved translation architecture.
  3. Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs.
  4. Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls.

Explanation

Correct Answer

D:

The cause is: A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges. The appropriate change is: Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls. Verify it with this outcome: The VM reaches its approved Azure service while unrelated Internet destinations remain blocked.

Incorrect Answers

A:

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 reported incident instead involves A broad Internet NSG destination rule does not take advantage of service-tag-based restriction to known Azure service ranges.

B:

This action concerns overlapping vnet address spaces, where Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. The corrective response here is “Use the appropriate Azure service tag in a narrowly scoped network rule together with service-specific controls”; this alternative does not provide that response.

C:

This action concerns vnet peering non transitivity, where VNet peering does not inherently create transitive routing between other independently peered VNets. The stem reports a security team allows all Internet outbound destinations because a VM must access Azure Storage, bypassing an existing policy intended to restrict egress; this control addresses a different failure condition.

Question 564

A production Azure security implementation shows this failure: File-share users access Azure Files with a shared storage account key even though access must follow corporate user identities and ACLs. Which recurring validation best protects against the observed problem?

  1. Audit file-share permissions at both Azure share level and file system ACL layers.
  2. Test audit data delivery and access controls after SQL platform and diagnostic changes.
  3. Review masking policies alongside direct data export and privileged bypass paths.
  4. Test client OS support, outbound port requirements and SMB security before migrations.

Explanation

Correct Answer

A:

This guardrail addresses azure files identity based smb authentication: Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. The prevention measure is: Audit file-share permissions at both Azure share level and file system ACL layers. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. “Test audit data delivery and access controls after SQL platform and diagnostic changes” would address that alternative cause, not the condition in this question: shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model.

C:

“Review masking policies alongside direct data export and privileged bypass paths” responds to this separate finding: sQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. This question instead needs “Audit file-share permissions at both Azure share level and file system ACL layers”, so the alternative does not meet the stated condition.

D:

The file access path needs compatible secure SMB protocol and supported encrypted transport settings. “Test client OS support, outbound port requirements and SMB security before migrations” applies to that separate problem. The observed case is file-share users access Azure Files with a shared storage account key even though access must follow corporate user identities and ACLs; choosing this alternative would address the wrong failure mode.

Question 565

A production Azure security implementation shows this failure: A short-lived Azure Container Instance job uses a copied account key to fetch blobs, and its image logs inadvertently disclose the key. What is the most appropriate corrective step?

  1. Schedule supported AKS node image updates and verify rollout health across node pools.
  2. Migrate to supported Microsoft Entra Workload ID and update service accounts and identity bindings.
  3. Configure supported Azure Monitor and Container Insights or equivalent AKS observability channels.
  4. Enable an appropriate managed identity on the container group and grant limited blob data access.

Explanation

Correct Answer

D:

The cause is: The container group relies on a long-lived shared credential rather than supported managed identity authorization. The appropriate change is: Enable an appropriate managed identity on the container group and grant limited blob data access. Verify it with this outcome: The container reads approved blobs using its identity without a stored storage key.

Incorrect Answers

A:

This action concerns aks node image upgrade hygiene, where Control-plane version compliance is distinct from node OS image and node pool security patch state. The reported incident instead involves The container group relies on a long-lived shared credential rather than supported managed identity authorization.

B:

This action concerns aks legacy pod identity migration, where The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. The corrective response here is “Enable an appropriate managed identity on the container group and grant limited blob data access”; this alternative does not provide that response.

C:

This action concerns aks control plane and container logging, where AKS workload and Kubernetes audit telemetry require explicit monitoring and log collection beyond resource health. The stem reports a short-lived Azure Container Instance job uses a copied account key to fetch blobs, and its image logs inadvertently disclose the key; this control addresses a different failure condition.

Question 566

A production Azure security implementation shows this failure: A Sentinel scheduled analytic rule remains inactive although its KQL query finds relevant suspicious authentication events when run manually. Which underlying control gap is responsible for the issue?

  1. A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination.
  2. Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained.
  3. A saved KQL query does not generate incidents until a supported analytic rule is enabled with schedule and alert grouping settings.
  4. Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents.

Explanation

Correct Answer

C:

The described technical condition is: A saved KQL query does not generate incidents until a supported analytic rule is enabled with schedule and alert grouping settings. The appropriate corrective action is: Create or enable the scheduled analytic rule with appropriate query frequency, lookback and incident configuration. Confirm with: A controlled event matching the rule leads to an appropriately timed alert or incident with the expected entities.

Incorrect Answers

A:

A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. “Enable the required syslog facility and severity in the Linux data collection rule and verify agent association” would address that alternative cause, not the condition in this question: a saved KQL query does not generate incidents until a supported analytic rule is enabled with schedule and alert grouping settings.

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 “Create or enable the scheduled analytic rule with appropriate query frequency, lookback and incident configuration”, so the alternative does not meet the stated condition.

D:

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” applies to that separate problem. The observed case is a Sentinel scheduled analytic rule remains inactive although its KQL query finds relevant suspicious authentication events when run manually; choosing this alternative would address the wrong failure mode.

Question 567

A Microsoft Azure administrator receives this requirement: An application needs to send DNS queries to a custom resolver over UDP, but Azure Firewall has only an HTTPS application rule for the resolver host. What should the engineer implement first to address the weakness?

  1. Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow.
  2. Deploy the approved configuration to the correct regions and verify the deployed state.
  3. Implement supported hub-spoke transit with a router or firewall and correct peering flags and UDRs.
  4. Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy.

Explanation

Correct Answer

A:

The cause is: An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. The appropriate change is: Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow. Verify it with this outcome: Only the authorized DNS queries succeed and firewall logs show the intended rule match.

Incorrect Answers

B:

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 reported incident instead involves An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.

C:

This action concerns vnet peering non transitivity, where VNet peering does not inherently create transitive routing between other independently peered VNets. The corrective response here is “Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow”; this alternative does not provide that response.

D:

This action concerns azure firewall application rule fqdn filtering, where A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. The stem reports an application needs to send DNS queries to a custom resolver over UDP, but Azure Firewall has only an HTTPS application rule for the resolver host; this control addresses a different failure condition.

Question 568

An Azure security engineer investigates the following incident: A team monitors database firewall access but has no alerting for anomalous SQL injection or suspicious database sign-ins. Which remediation best addresses the specific issue?

  1. Configure the appropriate alert or recommendation trigger and authorize the workflow identity to run the selected playbook.
  2. Enable the appropriate Defender for SQL or Databases protection plan and configure supported alert routing.
  3. Configure supported Defender for Storage threat detection and alert routing for the sensitive storage accounts.
  4. Apply the supported patch or approved mitigating control, rescan and reconcile the vulnerability recommendation.

Explanation

Correct Answer

B:

The cause is: Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan. The appropriate change is: Enable the appropriate Defender for SQL or Databases protection plan and configure supported alert routing. Verify it with this outcome: A safe simulated anomalous database activity test generates the expected protection alert without changing legitimate data.

Incorrect Answers

A:

This action concerns defender for cloud workflow automation trigger scope, where A Logic App definition needs a correctly scoped Defender for Cloud workflow automation rule and supported trigger conditions. The reported incident instead involves Database firewall configuration does not itself enable the relevant Defender for Databases threat detection plan.

C:

This action concerns defender for storage sensitive data threat detection, where Access logs record activity but are not the same as managed storage threat detection for anomalous or malicious behavior. The corrective response here is “Enable the appropriate Defender for SQL or Databases protection plan and configure supported alert routing”; this alternative does not provide that response.

D:

This action concerns defender vulnerability management remediation validation, where A vulnerability finding remains an exposure until remediation or an approved compensating mitigation is implemented and verified. The stem reports a team monitors database firewall access but has no alerting for anomalous SQL injection or suspicious database sign-ins; this control addresses a different failure condition.

Question 569

A production Azure security implementation shows this failure: A secret-reading application was migrated to a Key Vault private endpoint but continues resolving the vault hostname to a public IP address. Which operating control most directly reduces this recurring risk?

  1. Match vault tier and key protection type to compliance requirements before key creation and migration.
  2. Review initiative versions and parameter mappings before every organization wide compliance rollout.
  3. Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change.
  4. Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan.

Explanation

Correct Answer

C:

This guardrail addresses key vault private endpoint dns resolution: Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client. The prevention measure is: Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change. 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: private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client.

B:

“Review initiative versions and parameter mappings before every organization wide compliance rollout” responds to this separate finding: without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. This question instead needs “Test private DNS resolution from each peered client network whenever Key Vault endpoints or links change”, so the alternative does not meet the stated condition.

D:

Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. “Document and periodically test Key Vault backup recovery compatibility before relying on a cross-region disaster recovery plan” applies to that separate problem. The observed case is a secret-reading application was migrated to a Key Vault private endpoint but continues resolving the vault hostname to a public IP address; choosing this alternative would address the wrong failure mode.

Question 570

A platform security assessment reveals this issue: An AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current. What is the most appropriate corrective step?

  1. Configure a secure Container Apps secret reference or managed identity for database access.
  2. Assign appropriate Azure Policy Kubernetes policies and deploy supported enforcement components.
  3. Attach a supported managed identity and grant the intended Key Vault secret-read role.
  4. Schedule supported AKS node image updates and verify rollout health across node pools.

Explanation

Correct Answer

D:

The cause is: Control-plane version compliance is distinct from node OS image and node pool security patch state. The appropriate change is: Schedule supported AKS node image updates and verify rollout health across node pools. Verify it with this outcome: The node pools report patched images and workloads continue meeting availability requirements.

Incorrect Answers

A:

This action concerns container apps secret references, where Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. The reported incident instead involves Control-plane version compliance is distinct from node OS image and node pool security patch state.

B:

This action concerns azure policy admission for aks, where Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. The corrective response here is “Schedule supported AKS node image updates and verify rollout health across node pools”; this alternative does not provide that response.

C:

This action concerns container apps managed identity auth, where The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The stem reports an AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current; this control addresses a different failure condition.