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 83

Question 820

While validating an Azure workload, the security team finds: An app connects to SQL using an old driver that ignores certificate validation, allowing a man-in-the-middle risk despite nominal encryption. Which condition most directly explains the failure?

  1. Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination.
  2. Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing.
  3. TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption.
  4. The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication.

Explanation

Correct Answer

B:

The described technical condition is: Encrypted SQL transport without trusted server certificate validation can leave client identity vulnerable to spoofing. The appropriate corrective action is: Configure supported SQL driver encryption with certificate chain and hostname validation enabled. Confirm with: The client connects only to the legitimate database endpoint and rejects an untrusted test certificate.

Incorrect Answers

A:

Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. “Enable supported SQL auditing with the necessary categories and protected retention settings” 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:

“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 “Configure supported SQL driver encryption with certificate chain and hostname validation enabled”, so the alternative does not meet the stated condition.

D:

The SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. “Configure the Microsoft Entra administrator and create appropriate contained database users and roles” 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 821

While validating an Azure workload, the security team finds: A regulated storage service must use two separate layers of encryption, but a team enables only the default server-side encryption layer. Which configuration change most directly resolves this problem?

  1. Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage.
  2. Enable supported blob versioning and define backup or lifecycle protection for critical objects.
  3. Create a supported user delegation SAS using Microsoft Entra authorized delegation and least privilege.
  4. Set AllowSharedKeyAccess to false where supported after migrating legitimate clients to Entra or user-delegation SAS.

Explanation

Correct Answer

A:

The cause is: The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. The appropriate change is: Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage. Verify it with this outcome: The storage account reports infrastructure encryption enabled in addition to regular service-side encryption.

Incorrect Answers

B:

This action concerns blob versioning prior content recovery, where Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The reported incident instead involves The specified infrastructure encryption requirement needs the supported additional service-side encryption layer.

C:

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 corrective response here is “Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage”; this alternative does not provide that response.

D:

This action concerns storage shared key authorization disable, where The account has not disabled Shared Key authorization where the application's supported operations permit identity-based control. The stem reports a regulated storage service must use two separate layers of encryption, but a team enables only the default server-side encryption layer; this control addresses a different failure condition.

Question 822

The cloud operations team reviews the following risk: A daemon app cannot obtain access tokens after a certificate of service availability window because its application client secret has expired. What governance practice would best prevent the same failure?

  1. Control redirect URI changes through code review and restrict registrations to trusted application owners.
  2. Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes.
  3. Inventory service principal credential expiry and automate safe replacement before deadlines.
  4. Test vault data-plane access with the actual managed identity rather than relying on ARM role labels.

Explanation

Correct Answer

C:

This guardrail addresses application client secret expiration: The app registration client credential has expired and the workload has no safe rotation mechanism. The prevention measure is: Inventory service principal credential expiry and automate safe replacement before deadlines. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The application's registered redirect URI does not match the callback URI used in the authorization request. “Control redirect URI changes through code review and restrict registrations to trusted application owners” would address that alternative cause, not the condition in this question: the app registration client credential has expired and the workload has no safe rotation mechanism.

B:

“Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes” responds to this separate finding: the workload is not using its platform-managed identity and therefore depends on long-lived application secrets. This question instead needs “Inventory service principal credential expiry and automate safe replacement before deadlines”, so the alternative does not meet the stated condition.

D:

Resource management Contributor does not automatically grant Key Vault secrets data access in the RBAC permission model. “Test vault data-plane access with the actual managed identity rather than relying on ARM role labels” applies to that separate problem. The observed case is a daemon app cannot obtain access tokens after a certificate of service availability window because its application client secret has expired; choosing this alternative would address the wrong failure mode.

Question 823

During a cloud security review, the operations team observes: An Application Gateway intermittently returns 502 even though backend VMs are up because the health probe checks an incorrect hostname and path. What technical cause best accounts for the described behavior?

  1. The backend health probe is failing due to its configured request host, path or expected response rather than VM availability.
  2. SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings.
  3. Backend HTTP settings do not enforce the required HTTPS connection to backend servers.
  4. The function hosting plan and network integration/DNS are not configured for the required private destination.

Explanation

Correct Answer

A:

The described technical condition is: The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. The appropriate corrective action is: Correct the custom health probe to match the actual service endpoint and backend settings. Confirm with: Application Gateway reports healthy targets and completes an end-to-end request to the application.

Incorrect Answers

B:

SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. “Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls” would address that alternative cause, not the condition in this question: the backend health probe is failing due to its configured request host, path or expected response rather than VM availability.

C:

“Configure backend HTTPS with appropriate certificate trust and listener/backend settings” responds to this separate finding: backend HTTP settings do not enforce the required HTTPS connection to backend servers. This question instead needs “Correct the custom health probe to match the actual service endpoint and backend settings”, so the alternative does not meet the stated condition.

D:

The function hosting plan and network integration/DNS are not configured for the required private destination. “Configure a supported Functions hosting plan with VNet integration and correct private DNS resolution” applies to that separate problem. The observed case is an Application Gateway intermittently returns 502 even though backend VMs are up because the health probe checks an incorrect hostname and path; choosing this alternative would address the wrong failure mode.

Question 824

An Azure security engineer investigates the following incident: A workload can reach one internal service but not another, and the incident team repeatedly edits a single NSG without checking inherited or parallel network controls. Which condition most directly explains the failure?

  1. Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply.
  2. Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg.
  3. An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group.
  4. The active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view.

Explanation

Correct Answer

D:

The described technical condition is: The active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view. The appropriate corrective action is: Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision. Confirm with: The diagnostic result identifies the NSG rule responsible and the approved flow passes after targeted remediation.

Incorrect Answers

A:

Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. “Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls” would address that alternative cause, not the condition in this question: the active enforcement context can include multiple NSGs and effective rules that differ from a single saved rule view.

B:

“Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path” responds to this separate finding: forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. This question instead needs “Use Network Watcher effective security rules and IP flow verification to locate the actual blocking decision”, so the alternative does not meet the stated condition.

C:

An ASG-based NSG rule matches only network interfaces associated with the referenced Application Security Group. “Assign the intended VM network interface to the approved ASG and retain least-privilege NSG criteria” applies to that separate problem. The observed case is a workload can reach one internal service but not another, and the incident team repeatedly edits a single NSG without checking inherited or parallel network controls; choosing this alternative would address the wrong failure mode.

Question 825

A Microsoft Azure administrator receives this requirement: A high-risk portal role accepts SMS-based MFA even though policy explicitly requires phishing-resistant authentication for privileged operations. After remediation, which test result best proves the intended change?

  1. An SMS-only sign-in fails the privileged requirement while an authorized phishing-resistant method succeeds.
  2. A supervised break-glass validation succeeds while ordinary privileged users remain subject to strong controls.
  3. A lost key can be revoked and replaced without allowing unverified MFA bypass.
  4. The targeted legacy authentication attempt is rejected while modern approved sign-in remains operational.

Explanation

Correct Answer

A:

This validates the specific control for phishing resistant authentication strength: The selected Conditional Access grant control does not enforce a phishing-resistant authentication strength. The associated corrective action is: Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods. Testing a different component would not establish this result.

Incorrect Answers

B:

The policy targets protected emergency principals without the approved tightly controlled recovery exclusions. “Apply the documented emergency access exclusion and protect recovery identities with independent safeguards” would address that alternative cause, not the condition in this question: the selected Conditional Access grant control does not enforce a phishing-resistant authentication strength.

C:

“Configure managed passkey or FIDO2 registration and secure recovery procedures with independent identity verification” responds to this separate finding: strong authentication adoption lacks an approved registration, recovery and revocation lifecycle. This question instead needs “Configure the supported phishing-resistant authentication strength and enroll eligible FIDO2 or certificate-based methods”, so the alternative does not meet the stated condition.

D:

The tenant has not blocked legacy authentication clients that can bypass modern authentication capabilities. “Create a policy that blocks legacy client authentication for the necessary users and applications” applies to that separate problem. The observed case is a high-risk portal role accepts SMS-based MFA even though policy explicitly requires phishing-resistant authentication for privileged operations; choosing this alternative would address the wrong failure mode.

Question 826

A platform security assessment reveals this issue: A workload reaches approved web APIs but an administrator adds a network rule permitting every public IP in an ASN rather than the business service hostnames. Which operating control most directly reduces this recurring risk?

  1. Review FQDN-based application rules for wildcard overreach and domain ownership changes.
  2. Document and test non-transitive peerings before granting inter-spoke network access.
  3. Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy.
  4. Audit shared gateway peering settings whenever a new spoke joins the hub.

Explanation

Correct Answer

A:

This guardrail addresses azure firewall application rule fqdn filtering: A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. The prevention measure is: Review FQDN-based application rules for wildcard overreach and domain ownership changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

VNet peering does not inherently create transitive routing between other independently peered VNets. “Document and test non-transitive peerings before granting inter-spoke network access” would address that alternative cause, not the condition in this question: a broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering.

C:

“Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy” responds to this separate finding: an HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. This question instead needs “Review FQDN-based application rules for wildcard overreach and domain ownership changes”, so the alternative does not meet the stated condition.

D:

Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. “Audit shared gateway peering settings whenever a new spoke joins the hub” applies to that separate problem. The observed case is a workload reaches approved web APIs but an administrator adds a network rule permitting every public IP in an ASN rather than the business service hostnames; choosing this alternative would address the wrong failure mode.

Question 827

A platform security assessment reveals this issue: An attacker with backup administrative rights tries to delete backup items permanently to defeat future recovery after ransomware deployment. Which underlying control gap is responsible for the issue?

  1. Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault.
  2. Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration.
  3. Cluster authorization is not aligned with identity-based RBAC and separation of duties.
  4. Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization.

Explanation

Correct Answer

A:

The described technical condition is: Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. The appropriate corrective action is: Enable supported vault soft delete and enhanced protection settings including immutable backup where required. Confirm with: A deletion attempt cannot immediately eradicate protected backup recovery points and recovery remains possible.

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: backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault.

C:

“Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope” responds to this separate finding: cluster authorization is not aligned with identity-based RBAC and separation of duties. This question instead needs “Enable supported vault soft delete and enhanced protection settings including immutable backup where required”, 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. “Restrict disk snapshot export permissions and control SAS-based snapshot access to approved principals” applies to that separate problem. The observed case is an attacker with backup administrative rights tries to delete backup items permanently to defeat future recovery after ransomware deployment; choosing this alternative would address the wrong failure mode.

Question 828

During a cloud security review, the operations team observes: A security analyst concludes there are no vulnerable resources because the Defender inventory is filtered to a single region rather than the global workload footprint. Which underlying control gap is responsible for the issue?

  1. A connector's project enrollment or organization-level integration scope may omit newly created GCP projects.
  2. An exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed.
  3. Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet.
  4. Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types.

Explanation

Correct Answer

D:

The described technical condition is: Inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types. The appropriate corrective action is: Clear or expand the inventory filter and verify the evaluated scope against resource ownership records. Confirm with: Previously hidden resources are included and their vulnerability or configuration status can be assessed.

Incorrect Answers

A:

A connector's project enrollment or organization-level integration scope may omit newly created GCP projects. “Inspect connector scope and project discovery requirements and enroll or synchronize the missing governed projects” would address that alternative cause, not the condition in this question: inventory filters can hide assets and assessments outside selected subscriptions, regions or resource types.

B:

“Validate exemption justification, owner, expiry and business controls or actually remediate the resource” responds to this separate finding: an exemption documents an exception to a recommendation but is not evidence that the underlying risk was technically removed. This question instead needs “Clear or expand the inventory filter and verify the evaluated scope against resource ownership records”, so the alternative does not meet the stated condition.

C:

Internal Azure Resource Manager inventories do not discover every external asset or subsidiary-hosted exposure visible on the public Internet. “Use Microsoft Defender External Attack Surface Management to discover and validate external assets associated with owned domains” applies to that separate problem. The observed case is a security analyst concludes there are no vulnerable resources because the Defender inventory is filtered to a single region rather than the global workload footprint; choosing this alternative would address the wrong failure mode.

Question 829

A production Azure security implementation shows this failure: A security initiative is assigned at a management group, but one production subscription does not appear in its compliance dashboard because it was excluded by notScopes. What observation is the strongest validation evidence?

  1. A protected backup deletion request fails until a separate authorized security approver grants the required permission.
  2. Authorized operators can restore data while prohibited backup protection reduction operations are rejected.
  3. Key metadata and approved validation demonstrate hardware-backed protection for the sensitive workload.
  4. The production subscription enters the relevant compliance assessment and its resources receive the expected enforcement.

Explanation

Correct Answer

D:

This validates the specific control for azure policy scope and notscopes exclusions: An excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended. The associated corrective action is: Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control. Testing a different component would not establish this result.

Incorrect Answers

A:

Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. “Configure multiuser authorization for sensitive backup operations and grant the Resource Guard permissions to independent approvers” would address that alternative cause, not the condition in this question: an excluded scope on the policy assignment prevents the affected descendants from being evaluated as intended.

B:

“Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing” responds to this separate finding: an immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. This question instead needs “Inspect the assignment notScopes and remove the unintended subscription exclusion with approved change control”, so the alternative does not meet the stated condition.

C:

Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. “Provision supported HSM-protected keys in the appropriate vault tier and migrate applications according to key-dependency rules” applies to that separate problem. The observed case is a security initiative is assigned at a management group, but one production subscription does not appear in its compliance dashboard because it was excluded by notScopes; choosing this alternative would address the wrong failure mode.

Question 830

The cloud operations team reviews the following risk: A design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint. Which explanation fits the observed symptoms most closely?

  1. The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address.
  2. Regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint.
  3. Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.
  4. The provider has not published a supported Private Link Service behind an eligible standard internal load balancer.

Explanation

Correct Answer

C:

The described technical condition is: Service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet. The appropriate corrective action is: Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service. Confirm with: The service resolves to a VNet private address and only permitted private clients connect.

Incorrect Answers

A:

The private DNS zone or VNet link is missing so the canonical hostname does not resolve to the private endpoint address. “Configure the correct privatelink DNS zone record and link the client VNet to the zone” would address that alternative cause, not the condition in this question: service Endpoints secure public service access from selected subnets but do not create a private IP endpoint in the VNet.

B:

“Configure an inbound Private Endpoint for App Service and restrict the public endpoint as required” responds to this separate finding: regional VNet integration affects outbound connectivity, not private inbound access to the App Service endpoint. This question instead needs “Use a supported Private Endpoint and appropriate DNS and public-access restrictions for the service”, so the alternative does not meet the stated condition.

D:

The provider has not published a supported Private Link Service behind an eligible standard internal load balancer. “Configure Azure Private Link Service with the required load balancer, NAT configuration and connection approval” applies to that separate problem. The observed case is a design requires a workload service to have a private IP inside the application VNet, but engineers propose only a Storage service endpoint; choosing this alternative would address the wrong failure mode.