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 32

Question 310

During a cloud security review, the operations team observes: A data lake account permits access from all public networks despite a requirement to accept only applications in approved VNets. What should the engineer implement first to address the weakness?

  1. Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege.
  2. Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required.
  3. Configure customer-managed key encryption and grant the storage account identity the required key permissions.
  4. Enable supported blob versioning and define backup or lifecycle protection for critical objects.

Explanation

Correct Answer

B:

The cause is: The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks. The appropriate change is: Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required. Verify it with this outcome: Approved clients access data and unauthorized public source IPs receive network access denial.

Incorrect Answers

A:

This action concerns user delegation sas for blob storage, where Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. The reported incident instead involves The storage account network firewall rules allow broad public endpoints instead of restricting to designated networks.

C:

This action concerns storage customer managed key in key vault, where Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. The corrective response here is “Limit storage network access to appropriate VNets or Private Endpoints and configure DNS as required”; this alternative does not provide that response.

D:

This action concerns blob versioning prior content recovery, where Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The stem reports a data lake account permits access from all public networks despite a requirement to accept only applications in approved VNets; this control addresses a different failure condition.

Question 311

An Azure security engineer investigates the following incident: File-share users access Azure Files with a shared storage account key even though access must follow corporate user identities and ACLs. Which configuration change most directly resolves this problem?

  1. Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access.
  2. Verify and enable supported SQL Transparent Data Encryption with the approved key management configuration.
  3. Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers.
  4. Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs.

Explanation

Correct Answer

D:

The cause is: Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. The appropriate change is: Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs. Verify it with this outcome: Approved users mount the file share with identities and cannot read restricted directories.

Incorrect Answers

A:

This action concerns azure sql private endpoint dns and public disable, where The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. The reported incident instead involves Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model.

B:

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 corrective response here is “Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs”; this alternative does not provide that response.

C:

This action concerns dynamic data masking limited disclosure, where SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. The stem reports file-share users access Azure Files with a shared storage account key even though access must follow corporate user identities and ACLs; this control addresses a different failure condition.

Question 312

A platform security assessment reveals this issue: An application subnet can access many Azure Storage accounts even though governance permits only designated corporate storage resource IDs. What observation is the strongest validation evidence?

  1. A capture or configuration review confirms sensitive payloads are cryptographically protected over the private circuit.
  2. Approved corporate storage access succeeds and a test unapproved storage destination is denied.
  3. Workload clients resolve to the private endpoint and unauthenticated public network access is denied.
  4. Clients inside authorized networks reach the app over the private endpoint while public requests fail.

Explanation

Correct Answer

B:

This validates the specific control for service endpoint policy destination allowlist: The subnet uses a general storage service endpoint without a service endpoint policy restricting eligible storage destinations. The associated corrective action is: Apply an appropriate service endpoint policy restricting the subnet to approved storage resources. Testing a different component would not establish this result.

Incorrect Answers

A:

ExpressRoute private connectivity does not by itself guarantee encryption of application data in transit. “Implement supported IPsec over ExpressRoute or application-layer TLS encryption according to the threat model” 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:

“Create an approved Private Endpoint in the workload VNet and disable or restrict the service's public access” responds to this separate finding: a private endpoint has not been configured or public network access has not been restricted for the resource. This question instead needs “Apply an appropriate service endpoint policy restricting the subnet to approved storage resources”, so the alternative does not meet the stated condition.

D:

Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. “Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required” 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 313

While validating an Azure workload, the security team finds: An Azure SQL database is administered only by a shared SQL login, contrary to corporate requirements for named Entra identity lifecycle management. Which configuration change most directly resolves this problem?

  1. Enable supported secret encryption and external secret management using Key Vault where required.
  2. Define appropriate masking functions and remove unnecessary UNMASK permissions from ordinary readers.
  3. Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access.
  4. Configure the Microsoft Entra administrator and create appropriate contained database users and roles.

Explanation

Correct Answer

D:

The cause is: The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. The appropriate change is: Configure the Microsoft Entra administrator and create appropriate contained database users and roles. Verify it with this outcome: Authorized Entra principals connect and act within granted database roles without using the shared SQL account.

Incorrect Answers

A:

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 reported incident instead involves The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication.

B:

This action concerns dynamic data masking limited disclosure, where SQL dynamic data masking has not been configured correctly or the analyst has an unmask-capable privilege. The corrective response here is “Configure the Microsoft Entra administrator and create appropriate contained database users and roles”; this alternative does not provide that response.

C:

This action concerns azure sql private endpoint dns and public disable, where The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. The stem reports an Azure SQL database is administered only by a shared SQL login, contrary to corporate requirements for named Entra identity lifecycle management; this control addresses a different failure condition.

Question 314

During a cloud security review, the operations team observes: Database administrators can see sensitive customer identifiers in plaintext despite a policy requiring only client applications to decrypt those values. After remediation, which test result best proves the intended change?

  1. Approved users mount the file share with identities and cannot read restricted directories.
  2. Authorized Entra principals connect and act within granted database roles without using the shared SQL account.
  3. The application resolves its SQL host to the private endpoint and Internet SQL connection attempts fail.
  4. Sensitive columns remain encrypted to the database engine while authorized clients decrypt needed values.

Explanation

Correct Answer

D:

This validates the specific control for sql always encrypted client column isolation: TDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. The associated corrective action is: Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients. Testing a different component would not establish this result.

Incorrect Answers

A:

Shared key authentication does not implement the intended identity-based SMB sign-in and file authorization model. “Configure supported identity-based Azure Files SMB authentication and appropriate share-level roles and file ACLs” would address that alternative cause, not the condition in this question: tDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing.

B:

“Configure the Microsoft Entra administrator and create appropriate contained database users and roles” responds to this separate finding: the SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. This question instead needs “Configure SQL Always Encrypted with appropriate column master and encryption keys and compatible clients”, so the alternative does not meet the stated condition.

C:

The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. “Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access” applies to that separate problem. The observed case is database administrators can see sensitive customer identifiers in plaintext despite a policy requiring only client applications to decrypt those values; choosing this alternative would address the wrong failure mode.

Question 315

While validating an Azure workload, the security team finds: A web app must call an internal database across a VNet, but only an App Service inbound access restriction is configured. Which result confirms the relevant security control is effective?

  1. The web app reaches the internal backend over the intended outbound integrated network path.
  2. Workload clients resolve to the private endpoint and unauthenticated public network access is denied.
  3. The selected subnet accesses the restricted account while unlisted subnets remain blocked.
  4. Clients inside authorized networks reach the app over the private endpoint while public requests fail.

Explanation

Correct Answer

A:

This validates the specific control for app service vnet integration outbound path: App Service inbound access restrictions do not provide the outbound VNet integration needed for private backend connections. The associated corrective action is: Configure regional App Service VNet integration and the necessary subnet routing and DNS. Testing a different component would not establish this result.

Incorrect Answers

B:

A private endpoint has not been configured or public network access has not been restricted for the resource. “Create an approved Private Endpoint in the workload VNet and disable or restrict the service's public access” 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.

C:

“Enable Microsoft.Storage service endpoint on the approved subnet and add its virtual network rule to storage” 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 “Configure regional App Service VNet integration and the necessary subnet routing and DNS”, so the alternative does not meet the stated condition.

D:

Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. “Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required” 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.

Question 316

The cloud operations team reviews the following risk: Just-in-time access has been enabled on a VM, but emergency users request an unrestricted source-address exception rather than their current approved workstation IP. What governance practice would best prevent the same failure?

  1. Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts.
  2. Confirm supported VM sizes and host encryption settings before regulated VM deployment.
  3. Schedule OS-level update compliance checks independent of ARM deployment status.
  4. Audit JIT source exceptions and flag broad ranges in privileged access logs.

Explanation

Correct Answer

D:

This guardrail addresses jit request ip restriction: JIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly. The prevention measure is: Audit JIT source exceptions and flag broad ranges in privileged access logs. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. “Document encryption-key dependencies and test recoverability before disabling legacy ADE artifacts” would address that alternative cause, not the condition in this question: jIT protects exposed management ports only when requested source addresses, port and duration are scoped correctly.

B:

“Confirm supported VM sizes and host encryption settings before regulated VM deployment” responds to this separate finding: guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. This question instead needs “Audit JIT source exceptions and flag broad ranges in privileged access logs”, so the alternative does not meet the stated condition.

C:

Azure resource deployment health does not automatically establish guest operating system patch compliance. “Schedule OS-level update compliance checks independent of ARM deployment status” applies to that separate problem. The observed case is just-in-time access has been enabled on a VM, but emergency users request an unrestricted source-address exception rather than their current approved workstation IP; choosing this alternative would address the wrong failure mode.

Question 317

A Microsoft Azure administrator receives this requirement: A single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements. What should the engineer implement first to address the weakness?

  1. Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers.
  2. Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault.
  3. Configure a correctly permissioned remediation task for supported existing resources after validating the Modify definition.
  4. Link the appropriate privatelink vault DNS zone and verify correct private records from the application virtual network.

Explanation

Correct Answer

A:

The cause is: Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. The appropriate change is: Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers. Verify it with this outcome: A protected backup deletion request fails until a separate authorized security approver grants the required permission.

Incorrect Answers

B:

This action concerns key vault backup restore regional limitation, where Key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. The reported incident instead involves Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary.

C:

This action concerns azure policy modify remediation for existing tags, where Modify policy can act on supported incoming requests while existing noncompliant resources require an applicable remediation task and managed identity permissions. The corrective response here is “Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers”; this alternative does not provide that response.

D:

This action concerns key vault private endpoint dns resolution, where Private Endpoint connectivity requires the corresponding private DNS resolution and network reachability from the client. The stem reports a single backup administrator can both change protection settings and delete backups, violating separation-of-duties requirements; this control addresses a different failure condition.

Question 318

A Microsoft Azure administrator receives this requirement: A subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet. What technical cause best accounts for the described behavior?

  1. Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg.
  2. Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply.
  3. NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes.
  4. The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires.

Explanation

Correct Answer

B:

The described technical condition is: Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. The appropriate corrective action is: Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls. Confirm with: Unauthorized Internet egress fails while approved endpoints remain reachable through logged channels.

Incorrect Answers

A:

Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. “Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path” would address that alternative cause, not the condition in this question: default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply.

C:

“Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes” responds to this separate finding: nSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. This question instead needs “Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls”, so the alternative does not meet the stated condition.

D:

The necessary peering settings for forwarded traffic through the hub were not enabled as the routing design requires. “Enable permitted forwarded traffic in the relevant peering directions and configure supporting UDRs” applies to that separate problem. The observed case is a subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet; choosing this alternative would address the wrong failure mode.

Question 319

A Microsoft Azure administrator receives this requirement: A Defender for Cloud alert reports suspicious VM command execution, but analysts close it immediately because the VM currently appears healthy. What should the engineer implement first to address the weakness?

  1. Enable the applicable App Service workload protection and route findings to the approved responder queue.
  2. Configure the approved GitLab integration in Defender for Cloud DevOps Security and validate scoped repositories.
  3. Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment.
  4. Review project and repository connector coverage and enable the supported assessment pipeline for the missing project.

Explanation

Correct Answer

C:

The cause is: A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines. The appropriate change is: Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment. Verify it with this outcome: The case records corroborated benign activity or documented remediation of the suspicious command chain.

Incorrect Answers

A:

This action concerns defender for app service protection plan, where Inventory visibility and generic baseline recommendations do not replace the dedicated supported Defender for App Service plan. The reported incident instead involves A single healthy state snapshot does not invalidate detection evidence such as process, identity, network and event timelines.

B:

This action concerns defender for cloud devops gitlab integration, where Code security inventory and posture coverage depend on a supported connector for the actual source-control platform. The corrective response here is “Investigate the alert's affected resources, identity context and supporting indicators before disposition and containment”; this alternative does not provide that response.

D:

This action concerns defender for cloud devops azure devops project coverage, where A DevOps connector does not guarantee automatic security scan visibility for every new project and repository. The stem reports a Defender for Cloud alert reports suspicious VM command execution, but analysts close it immediately because the VM currently appears healthy; this control addresses a different failure condition.

Question 320

An Azure security engineer investigates the following incident: A calendar integration with no directory management duties has been granted broad Directory.ReadWrite.All application permission. Which outcome most clearly verifies that the issue is resolved?

  1. The application authenticates with its secured credential while the old secret is revoked and unusable.
  2. Consent records show authorized approval and the application uses the narrower intended permission.
  3. The daemon accesses only approved Graph resources without impersonating an absent signed-in user.
  4. The integration performs its approved workflow while directory write attempts from the principal are denied.

Explanation

Correct Answer

D:

This validates the specific control for overprivileged oauth permission grant: The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. The associated corrective action is: Revoke the excessive permission and grant only the narrowly required API scopes or app roles. Testing a different component would not establish this result.

Incorrect Answers

A:

The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. “Configure a certificate credential or supported workload federation and remove the leaked text secret” would address that alternative cause, not the condition in this question: the OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact.

B:

“Have an authorized administrator evaluate and grant only the required application permission after review” responds to this separate finding: the requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. This question instead needs “Revoke the excessive permission and grant only the narrowly required API scopes or app roles”, so the alternative does not meet the stated condition.

C:

Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. “Select approved application permissions with administrator consent and configure client-credentials access” applies to that separate problem. The observed case is a calendar integration with no directory management duties has been granted broad Directory.ReadWrite.All application permission; choosing this alternative would address the wrong failure mode.