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 33

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.

Question 321

A Microsoft Azure administrator receives this requirement: A Container Apps environment publishes an administrative endpoint to everyone although it should accept only private application traffic. Which underlying control gap is responsible for the issue?

  1. The application's ingress configuration enables external exposure instead of internal-only routing.
  2. Control-plane version compliance is distinct from node OS image and node pool security patch state.
  3. Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity.
  4. The container group relies on a long-lived shared credential rather than supported managed identity authorization.

Explanation

Correct Answer

A:

The described technical condition is: The application's ingress configuration enables external exposure instead of internal-only routing. The appropriate corrective action is: Configure internal ingress and supported network isolation for the Container App environment. Confirm with: Authorized internal clients reach the service while public Internet attempts are denied.

Incorrect Answers

B:

Control-plane version compliance is distinct from node OS image and node pool security patch state. “Schedule supported AKS node image updates and verify rollout health across node pools” would address that alternative cause, not the condition in this question: the application's ingress configuration enables external exposure instead of internal-only routing.

C:

“Configure a secure Container Apps secret reference or managed identity for database access” responds to this separate finding: sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. This question instead needs “Configure internal ingress and supported network isolation for the Container App environment”, so the alternative does not meet the stated condition.

D:

The container group relies on a long-lived shared credential rather than supported managed identity authorization. “Enable an appropriate managed identity on the container group and grant limited blob data access” applies to that separate problem. The observed case is a Container Apps environment publishes an administrative endpoint to everyone although it should accept only private application traffic; choosing this alternative would address the wrong failure mode.

Question 322

A regulated Azure tenant has this security condition: An application uses a custom hostname but presents an unrelated default certificate, causing client hostname validation failures. Which result confirms the relevant security control is effective?

  1. The function reaches the private SQL endpoint with no public database network dependency.
  2. TLS clients validate the intended hostname and chain without accepting certificate warnings.
  3. A test flow negotiates TLS to both gateway and backend without exposing plaintext on the internal leg.
  4. Controlled malicious request patterns are blocked while normal requests pass and logs record rule decisions.

Explanation

Correct Answer

B:

This validates the specific control for custom domain tls certificate binding: The custom domain has no correct TLS certificate binding for the expected host name. The associated corrective action is: Bind a valid certificate to the custom hostname using an approved App Service certificate mechanism. Testing a different component would not establish this result.

Incorrect Answers

A:

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” would address that alternative cause, not the condition in this question: the custom domain has no correct TLS certificate binding for the expected host name.

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 “Bind a valid certificate to the custom hostname using an approved App Service certificate mechanism”, so the alternative does not meet the stated condition.

D:

The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. “After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener” applies to that separate problem. The observed case is an application uses a custom hostname but presents an unrelated default certificate, causing client hostname validation failures; choosing this alternative would address the wrong failure mode.

Question 323

During a cloud security review, the operations team observes: A team assigns the same Azure resource role individually to dozens of analysts, then former team members retain access when the department changes. What observation is the strongest validation evidence?

  1. Removing a user from the group removes inherited resource access after propagation, without changing role assignments.
  2. The operator views security inventory in both existing and newly attached eligible subscriptions.
  3. An authorized test modifies the intended tags while the operator retains no additional administration privileges.
  4. Authorized tagged blobs can be updated while attempted writes to excluded blobs are rejected.

Explanation

Correct Answer

A:

This validates the specific control for group based azure rbac: Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. The associated corrective action is: Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls. Testing a different component would not establish this result.

Incorrect Answers

B:

Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. “Assign the approved read-only role at a suitable management group with the intended child subscription coverage” would address that alternative cause, not the condition in this question: direct per-user role assignments can persist after personnel changes without a managed membership lifecycle.

C:

“Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized” responds to this separate finding: the Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. This question instead needs “Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls”, so the alternative does not meet the stated condition.

D:

A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” applies to that separate problem. The observed case is a team assigns the same Azure resource role individually to dozens of analysts, then former team members retain access when the department changes; choosing this alternative would address the wrong failure mode.

Question 324

While validating an Azure workload, the security team finds: An external partner receives a long-lived SAS token with unrestricted permissions and broad network access for a short upload job. Which outcome most clearly verifies that the issue is resolved?

  1. A test overwrite creates a retrievable previous version that administrators can restore.
  2. A controlled deletion can be reversed within retention without rebuilding the entire account.
  3. Encrypted data remains accessible using the approved customer key while unauthorized key use fails.
  4. The partner uploads an authorized object before expiry and cannot delete unrelated blobs or reuse an expired token.

Explanation

Correct Answer

D:

This validates the specific control for service sas expiry and ip restrictions: The SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose. The associated corrective action is: Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions. Testing a different component would not establish this result.

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 SAS grants excessive lifetime, permissions and source scope relative to the intended upload purpose.

B:

“Enable blob soft delete with an appropriate retention period and verify the restore process” responds to this separate finding: the storage account lacks blob soft delete retention to recover recently removed objects. This question instead needs “Generate a short-lived SAS with minimum upload permissions and appropriate IP or protocol restrictions”, so the alternative does not meet the stated condition.

C:

Storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. “Configure customer-managed key encryption and grant the storage account identity the required key permissions” applies to that separate problem. The observed case is an external partner receives a long-lived SAS token with unrestricted permissions and broad network access for a short upload job; choosing this alternative would address the wrong failure mode.

Question 325

During a cloud security review, the operations team observes: A regulated organization needs to apply a coordinated security baseline to ten subscriptions, but administrators assign isolated definitions with inconsistent parameters. What observation is the strongest validation evidence?

  1. Authorized operators can restore data while prohibited backup protection reduction operations are rejected.
  2. Each child subscription reports consistent compliance results and the documented initiative parameters match approved standards.
  3. The approved identity retrieves only authorized secrets and a formerly permitted but unassigned identity is denied.
  4. A restored test key operates in the approved recovery location with its expected identity and cryptographic properties.

Explanation

Correct Answer

B:

This validates the specific control for azure policy initiative and parameter assignments: Without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions. The associated corrective action is: Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope. Testing a different component would not establish this result.

Incorrect Answers

A:

An immutable backup vault, where supported and configured, restricts operations that could weaken configured backup protection. “Configure the supported immutable-vault protection state and evaluate whether to lock it after full recovery testing” would address that alternative cause, not the condition in this question: without a centrally governed policy initiative, related definitions and their parameters may drift across subscriptions.

C:

“Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model” responds to this separate finding: key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active. This question instead needs “Package the approved policy definitions into a parameterized initiative and assign it at the applicable management group scope”, 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. “Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault” applies to that separate problem. The observed case is a regulated organization needs to apply a coordinated security baseline to ten subscriptions, but administrators assign isolated definitions with inconsistent parameters; choosing this alternative would address the wrong failure mode.

Question 326

A platform security assessment reveals this issue: A detection rule flags suspicious logins but incidents contain only free-text messages and cannot link the affected user or source IP. Which operating control most directly reduces this recurring risk?

  1. Treat monitoring visualization and executable detection content as separate acceptance requirements.
  2. Require a reproducible evidence trail and peer review for high-severity Sentinel incident closure.
  3. Validate analytic-rule entity mapping whenever query schema, connector or source field naming changes.
  4. Include evidence that logs are arriving when implementing new high-impact network policies.

Explanation

Correct Answer

C:

This guardrail addresses sentinel entity mapping accuracy: Useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers. The prevention measure is: Validate analytic-rule entity mapping whenever query schema, connector or source field naming changes. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Workbooks visualize queried telemetry but do not replace enabled analytic rules or explicit alert workflows. “Treat monitoring visualization and executable detection content as separate acceptance requirements” would address that alternative cause, not the condition in this question: useful Sentinel entity correlation requires accurate supported mapping from query columns to entity identifiers.

B:

“Require a reproducible evidence trail and peer review for high-severity Sentinel incident closure” responds to this separate finding: incident titles alone cannot establish benign behavior; entities, event timestamps and correlated evidence require investigation. This question instead needs “Validate analytic-rule entity mapping whenever query schema, connector or source field naming changes”, so the alternative does not meet the stated condition.

D:

Network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. “Include evidence that logs are arriving when implementing new high-impact network policies” applies to that separate problem. The observed case is a detection rule flags suspicious logins but incidents contain only free-text messages and cannot link the affected user or source IP; choosing this alternative would address the wrong failure mode.

Question 327

The cloud operations team reviews the following risk: A Sentinel scheduled analytic rule remains inactive although its KQL query finds relevant suspicious authentication events when run manually. Which safeguard would best prevent this issue from recurring?

  1. Test analytic-rule enablement and lookback windows before treating a workbook chart as a detection.
  2. Test cloud identity telemetry coverage whenever tenant logging or connector permissions change.
  3. Validate DCR associations and event filtering with a known test event after agent or scope changes.
  4. Run rule-order regression tests whenever introducing broad case-management automation.

Explanation

Correct Answer

A:

This guardrail addresses sentinel analytics scheduled rule query: A saved KQL query does not generate incidents until a supported analytic rule is enabled with schedule and alert grouping settings. The prevention measure is: Test analytic-rule enablement and lookback windows before treating a workbook chart as a detection. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Microsoft Entra sign-in audit events need the appropriate supported connector or diagnostic routing and access permissions. “Test cloud identity telemetry coverage whenever tenant logging or connector permissions change” 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.

C:

“Validate DCR associations and event filtering with a known test event after agent or scope changes” responds to this separate finding: azure Monitor Agent ingestion relies on a data collection rule with appropriate data sources, transformation and destination association. This question instead needs “Test analytic-rule enablement and lookback windows before treating a workbook chart as a detection”, so the alternative does not meet the stated condition.

D:

Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. “Run rule-order regression tests whenever introducing broad case-management automation” 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 328

The cloud operations team reviews the following risk: An enterprise requires VM host-level encryption for temporary disks and caches, but only customer-managed guest volume encryption is enabled. What governance practice would best prevent the same failure?

  1. Review JIT requests and ensure routine administrative ports remain closed outside authorized windows.
  2. Confirm supported VM sizes and host encryption settings before regulated VM deployment.
  3. Test Bastion SKU and client feature support before designing remote-administration access.
  4. Audit VM management ports and prefer controlled bastion connectivity with MFA and access logging.

Explanation

Correct Answer

B:

This guardrail addresses encryption at host for virtual machines: Guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement. The prevention measure is: Confirm supported VM sizes and host encryption settings before regulated VM deployment. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The VM's NSG exposes a persistent management port rather than enforcing just-in-time access. “Review JIT requests and ensure routine administrative ports remain closed outside authorized windows” would address that alternative cause, not the condition in this question: guest volume encryption alone does not necessarily cover the host-side temporary disk and cache encryption requirement.

C:

“Test Bastion SKU and client feature support before designing remote-administration access” responds to this separate finding: supported Bastion native-client or tunnel features can provide private access where the chosen SKU and features allow. This question instead needs “Confirm supported VM sizes and host encryption settings before regulated VM deployment”, so the alternative does not meet the stated condition.

D:

Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. “Audit VM management ports and prefer controlled bastion connectivity with MFA and access logging” applies to that separate problem. The observed case is an enterprise requires VM host-level encryption for temporary disks and caches, but only customer-managed guest volume encryption is enabled; choosing this alternative would address the wrong failure mode.

Question 329

A Microsoft Azure administrator receives this requirement: Traffic enters through a virtual appliance but reply packets use a more direct route, causing stateful firewall drops even though each isolated hop is reachable. Which recurring validation best protects against the observed problem?

  1. Validate both directions of protected flows after any UDR, peering or subnet address change.
  2. Test actual outbound reachability instead of relying on the presence of an NSG attachment alone.
  3. Include established-session and fresh-connection checks in NSG incident response validation.
  4. Check gateway propagation behavior and route specificity before applying default-route policy.

Explanation

Correct Answer

A:

This guardrail addresses asymmetric routing around network virtual appliance: Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. The prevention measure is: Validate both directions of protected flows after any UDR, peering or subnet address change. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. “Test actual outbound reachability instead of relying on the presence of an NSG attachment alone” would address that alternative cause, not the condition in this question: forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg.

C:

“Include established-session and fresh-connection checks in NSG incident response validation” 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 “Validate both directions of protected flows after any UDR, peering or subnet address change”, so the alternative does not meet the stated condition.

D:

Gateway route propagation remains enabled for the route table and influences effective routing selections. “Check gateway propagation behavior and route specificity before applying default-route policy” applies to that separate problem. The observed case is traffic enters through a virtual appliance but reply packets use a more direct route, causing stateful firewall drops even though each isolated hop is reachable; choosing this alternative would address the wrong failure mode.

Question 330

A Microsoft Azure administrator receives this requirement: A public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application. What is the most appropriate corrective step?

  1. After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener.
  2. Deploy a supported internal App Service Environment and configure ingress and outbound network controls.
  3. Configure a supported APIM private networking option and restrict public gateway exposure as required.
  4. Correct the custom health probe to match the actual service endpoint and backend settings.

Explanation

Correct Answer

A:

The cause is: The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode. The appropriate change is: After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener. Verify it with this outcome: Controlled malicious request patterns are blocked while normal requests pass and logs record rule decisions.

Incorrect Answers

B:

This action concerns internal app service environment isolation, where The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. The reported incident instead involves The Web Application Firewall policy is configured in detection mode instead of enforcement prevention mode.

C:

This action concerns api management private network access, where The chosen API Management networking mode and private endpoint or VNet integration do not meet the intended access boundary. The corrective response here is “After tuning exclusions, switch the approved WAF policy to prevention mode for the protected listener”; this alternative does not provide that response.

D:

This action concerns application gateway backend health probes, where The backend health probe is failing due to its configured request host, path or expected response rather than VM availability. The stem reports a public app behind Application Gateway shows malicious request matches in WAF logs but continues forwarding them to the application; this control addresses a different failure condition.