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 22

Question 210

A Microsoft Azure administrator receives this requirement: An audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions. What observation is the strongest validation evidence?

  1. Activation is rejected until the applicant satisfies the configured challenge and succeeds only for authorized operators.
  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. The operator reads the approved container but is denied access to an unrelated descendant subscription.

Explanation

Correct Answer

C:

This validates the specific control for reader role versus resource modification: The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. The associated corrective action is: Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized. Testing a different component would not establish this result.

Incorrect Answers

A:

PIM role settings have not required the intended multifactor or authentication-strength control at activation. “Configure the PIM role activation requirements to demand the approved strong authentication method” would address that alternative cause, not the condition in this question: the Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.

B:

“Assign the approved read-only role at a suitable management group with the intended child subscription coverage” responds to this separate finding: per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. This question instead needs “Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized”, so the alternative does not meet the stated condition.

D:

Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope” applies to that separate problem. The observed case is an audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions; choosing this alternative would address the wrong failure mode.

Question 211

During a cloud security review, the operations team observes: An externally hosted user connects to a firewall public IP and port but never reaches the internal application service because no translation rule exists. Which operating control most directly reduces this recurring risk?

  1. Include address-plan collision checks before authorizing VNet creation or peering requests.
  2. Review exposed DNAT entries against asset owners and remove obsolete Internet listeners.
  3. Audit shared gateway peering settings whenever a new spoke joins the hub.
  4. Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy.

Explanation

Correct Answer

B:

This guardrail addresses azure firewall dnat published service: Inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port. The prevention measure is: Review exposed DNAT entries against asset owners and remove obsolete Internet listeners. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. “Include address-plan collision checks before authorizing VNet creation or peering requests” would address that alternative cause, not the condition in this question: inbound public traffic requires a supported DNAT rule and corresponding inspection of destination and port.

C:

“Audit shared gateway peering settings whenever a new spoke joins the hub” responds to this separate finding: gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. This question instead needs “Review exposed DNAT entries against asset owners and remove obsolete Internet listeners”, so the alternative does not meet the stated condition.

D:

An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. “Distinguish L3-L4 network flows from HTTP/S application flows when designing firewall policy” applies to that separate problem. The observed case is an externally hosted user connects to a firewall public IP and port but never reaches the internal application service because no translation rule exists; choosing this alternative would address the wrong failure mode.

Question 212

During a cloud security review, the operations team observes: A SOC investigates role assignments but sees no Azure subscription management activity in Sentinel despite collecting VM system logs. After remediation, which test result best proves the intended change?

  1. Representative security events remain analyzable without exposing the prohibited personal payload fields.
  2. An authorized test role assignment creates a searchable subscription activity record in Sentinel.
  3. Expired indicators stop driving automatic actions and fresh verified indicators can be correlated with current events.
  4. The expected records appear only in approved production destinations and analysts can query them within the retention policy.

Explanation

Correct Answer

B:

This validates the specific control for sentinel azure activity data connector: Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. The associated corrective action is: Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace. Testing a different component would not establish this result.

Incorrect Answers

A:

Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. “Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema” would address that alternative cause, not the condition in this question: guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions.

C:

“Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics” responds to this separate finding: threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. This question instead needs “Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace”, so the alternative does not meet the stated condition.

D:

A DCR's configured destination governs where eligible telemetry is sent, regardless of the analyst's preferred query workspace. “Correct the authorized Log Analytics destination or workspace query scope while preserving the intended data source filters” applies to that separate problem. The observed case is a SOC investigates role assignments but sees no Azure subscription management activity in Sentinel despite collecting VM system logs; choosing this alternative would address the wrong failure mode.

Question 213

An Azure security engineer investigates the following incident: An administrator enables password-based SSH for Internet reachable Linux VMs and never rotates the shared password after personnel departures. Which explanation fits the observed symptoms most closely?

  1. Application secrets are stored in static Kubernetes configuration instead of an approved external secrets integration.
  2. Authentication to a container registry does not establish that deployed images meet vulnerability security requirements.
  3. Snapshot access is a separate data-exposure path that may be permitted by overly broad resource-level authorization.
  4. Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management.

Explanation

Correct Answer

D:

The described technical condition is: Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. The appropriate corrective action is: Use controlled SSH public-key authentication and restrict access through Bastion or approved private management. Confirm with: Only approved private keys authenticate to the private Linux VM and shared password login is unavailable.

Incorrect Answers

A:

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: shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management.

B:

“Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation” responds to this separate finding: authentication to a container registry does not establish that deployed images meet vulnerability security requirements. This question instead needs “Use controlled SSH public-key authentication and restrict access through Bastion or approved private management”, so the alternative does not meet the stated condition.

C:

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 administrator enables password-based SSH for Internet reachable Linux VMs and never rotates the shared password after personnel departures; choosing this alternative would address the wrong failure mode.

Question 214

The cloud operations team reviews the following risk: An App Service certificate stored in Key Vault renews through a provider but the application still serves an expired certificate chain. Which result confirms the relevant security control is effective?

  1. A protected backup deletion request fails until a separate authorized security approver grants the required permission.
  2. A restored test key operates in the approved recovery location with its expected identity and cryptographic properties.
  3. A TLS test of the service displays the new valid leaf certificate and trusted chain before the old one expires.
  4. The approved identity retrieves only authorized secrets and a formerly permitted but unassigned identity is denied.

Explanation

Correct Answer

C:

This validates the specific control for key vault certificate renewal import chain: Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. The associated corrective action is: Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint. 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: renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version.

B:

“Verify supported restore boundaries and perform an authorized restore test into a compatible recovery vault” responds to this separate finding: key Vault backup and restore is constrained by service-specific region, geography, subscription and vault compatibility rules. This question instead needs “Repair the supported certificate integration and deployment binding and verify the complete chain and expiration time at the endpoint”, so the alternative does not meet the stated condition.

D:

Key Vault data-plane permission behavior depends on the selected vault authorization model, so old access policies are not sufficient when RBAC is active. “Assign the appropriate Key Vault Secrets User role at the narrowest needed scope under the active RBAC model” applies to that separate problem. The observed case is an App Service certificate stored in Key Vault renews through a provider but the application still serves an expired certificate chain; choosing this alternative would address the wrong failure mode.

Question 215

A platform security assessment reveals this issue: A leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation. Which recurring validation best protects against the observed problem?

  1. Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes.
  2. Track enrollment, lost-device recovery and phishing-resistance outcomes before expanding passwordless adoption.
  3. Inventory service principal credential expiry and automate safe replacement before deadlines.
  4. Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents.

Explanation

Correct Answer

D:

This guardrail addresses identity protection user risk response: No effective user-risk-based identity protection response has been configured for the relevant identities. The prevention measure is: Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. “Prefer managed identities for Azure hosted workloads and audit residual credentials and permission scopes” would address that alternative cause, not the condition in this question: no effective user-risk-based identity protection response has been configured for the relevant identities.

B:

“Track enrollment, lost-device recovery and phishing-resistance outcomes before expanding passwordless adoption” responds to this separate finding: microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. This question instead needs “Review identity risk dismissals and remediation reports for excessive overrides or unhandled incidents”, so the alternative does not meet the stated condition.

C:

The app registration client credential has expired and the workload has no safe rotation mechanism. “Inventory service principal credential expiry and automate safe replacement before deadlines” applies to that separate problem. The observed case is a leaked user credential is flagged as high user risk but the tenant allows unlimited sign-ins without password change or protective escalation; choosing this alternative would address the wrong failure mode.

Question 216

A regulated Azure tenant has this security condition: A protected API receives requests with expired or incorrectly signed bearer tokens but the gateway forwards them unchecked. Which configuration change most directly resolves this problem?

  1. Issue a narrowly scoped SAS or Entra-based authorization without distributing storage account keys.
  2. Grant the appropriate ACR pull permission and remove excess push or management roles.
  3. Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles.
  4. Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims.

Explanation

Correct Answer

D:

The cause is: API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy. The appropriate change is: Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims. Verify it with this outcome: Valid authorized tokens succeed while expired or wrong-audience tokens fail at the gateway.

Incorrect Answers

A:

This action concerns storage shared key versus sas distinction, where Disclosing the storage account key exposes account-level shared-key authority beyond an individual scoped SAS delegation. The reported incident instead involves API Management does not have the necessary JWT signature, issuer, audience and expiration validation policy.

B:

This action concerns acr push and pull role separation, where The workload has an overly broad registry data role instead of the necessary pull-only authorization. The corrective response here is “Apply a supported validate-jwt policy with the correct trusted identity provider metadata and required claims”; this alternative does not provide that response.

C:

This action concerns acr administrator account disablement, where The ACR admin user is a broad shared credential unsuitable for least-privilege production pipeline access. The stem reports a protected API receives requests with expired or incorrectly signed bearer tokens but the gateway forwards them unchecked; this control addresses a different failure condition.

Question 217

A regulated Azure tenant has this security condition: A SOC needs to reconstruct a cloud intrusion from six months ago but only configured short retention for critical authentication telemetry. Which safeguard would best prevent this issue from recurring?

  1. Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators.
  2. Review security telemetry retention alongside legal requirements and realistic incident lookback needs.
  3. Retest analytic watchlist joins after source schema or naming normalization changes.
  4. Recheck monitored Linux facilities and filtering after operating system or detection-content upgrades.

Explanation

Correct Answer

B:

This guardrail addresses sentinel data retention investigation needs: Security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance. The prevention measure is: Review security telemetry retention alongside legal requirements and realistic incident lookback needs. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. “Periodically validate indicator providers, TTL handling and the risk of blocking based on uncorroborated indicators” would address that alternative cause, not the condition in this question: security investigation capability depends on applicable Log Analytics retention configuration and compliant data governance.

C:

“Retest analytic watchlist joins after source schema or naming normalization changes” responds to this separate finding: watchlist matching requires appropriate field normalization and meaningful identity identifiers rather than arbitrary string equality. This question instead needs “Review security telemetry retention alongside legal requirements and realistic incident lookback needs”, so the alternative does not meet the stated condition.

D:

A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. “Recheck monitored Linux facilities and filtering after operating system or detection-content upgrades” applies to that separate problem. The observed case is a SOC needs to reconstruct a cloud intrusion from six months ago but only configured short retention for critical authentication telemetry; choosing this alternative would address the wrong failure mode.

Question 218

The cloud operations team reviews the following risk: An administrator intends to require MFA and compliant devices but configures the policy to accept any one selected control. Which explanation fits the observed symptoms most closely?

  1. The grant control operator allows any selected requirement rather than requiring all specified requirements.
  2. The policy targets protected emergency principals without the approved tightly controlled recovery exclusions.
  3. The target cloud application selection is wrong and policy enforcement does not cover the actual resource.
  4. The targeted policy does not include the guest or external user population for the protected application.

Explanation

Correct Answer

A:

The described technical condition is: The grant control operator allows any selected requirement rather than requiring all specified requirements. The appropriate corrective action is: Select the required combination of grant controls and confirm the intended AND behavior. Confirm with: A test sign-in with only MFA fails, while one meeting both MFA and device compliance succeeds.

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 grant control operator allows any selected requirement rather than requiring all specified requirements.

C:

“Include the intended enterprise application or cloud resource in the Conditional Access assignment” responds to this separate finding: the target cloud application selection is wrong and policy enforcement does not cover the actual resource. This question instead needs “Select the required combination of grant controls and confirm the intended AND behavior”, so the alternative does not meet the stated condition.

D:

The targeted policy does not include the guest or external user population for the protected application. “Extend the policy to the correct external-user categories and trust settings using supported B2B controls” applies to that separate problem. The observed case is an administrator intends to require MFA and compliant devices but configures the policy to accept any one selected control; choosing this alternative would address the wrong failure mode.

Question 219

A production Azure security implementation shows this failure: An application registered in a software supplier tenant needs access to a customer's API, but the customer assumes the supplier's role grants automatically apply locally. Which operating control most directly reduces this recurring risk?

  1. Review tenant-local service principal assignments and consent during vendor onboarding and exit.
  2. Require review and documented business purpose before granting tenant-wide application consent.
  3. Version and review exposed API scopes so newly added privileges require explicit consent.
  4. Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles.

Explanation

Correct Answer

A:

This guardrail addresses cross tenant service principal consent: Cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls. The prevention measure is: Review tenant-local service principal assignments and consent during vendor onboarding and exit. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

The requested high-privilege permission requires administrator consent and cannot be authorized by normal user consent. “Require review and documented business purpose before granting tenant-wide application consent” would address that alternative cause, not the condition in this question: cross-tenant app authorization requires the consuming tenant's service principal, consent and local assignment controls.

C:

“Version and review exposed API scopes so newly added privileges require explicit consent” responds to this separate finding: the protected application registration has not exposed an OAuth permission scope for the required delegated operation. This question instead needs “Review tenant-local service principal assignments and consent during vendor onboarding and exit”, so the alternative does not meet the stated condition.

D:

Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. “Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles” applies to that separate problem. The observed case is an application registered in a software supplier tenant needs access to a customer's API, but the customer assumes the supplier's role grants automatically apply locally; choosing this alternative would address the wrong failure mode.

Question 220

A Microsoft Azure administrator receives this requirement: An App Service allows deprecated TLS versions for an API that handles sensitive data although newer clients support TLS 1.2 or later. Which operating control most directly reduces this recurring risk?

  1. Assess ASE deployment and subnet requirements before choosing it for strict regulated isolation.
  2. Test regional edge WAF policies with representative client source conditions and observe false positives.
  3. Test TLS protocol settings and certificate expiry after changes to public application endpoints.
  4. Track custom domain certificate validity and binding renewal before expiration.

Explanation

Correct Answer

C:

This guardrail addresses minimum tls protocol enforcement: The app's minimum TLS version configuration permits an outdated protocol that violates the security baseline. The prevention measure is: Test TLS protocol settings and certificate expiry after changes to public application endpoints. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. “Assess ASE deployment and subnet requirements before choosing it for strict regulated isolation” would address that alternative cause, not the condition in this question: the app's minimum TLS version configuration permits an outdated protocol that violates the security baseline.

B:

“Test regional edge WAF policies with representative client source conditions and observe false positives” responds to this separate finding: the access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. This question instead needs “Test TLS protocol settings and certificate expiry after changes to public application endpoints”, so the alternative does not meet the stated condition.

D:

The custom domain has no correct TLS certificate binding for the expected host name. “Track custom domain certificate validity and binding renewal before expiration” applies to that separate problem. The observed case is an App Service allows deprecated TLS versions for an API that handles sensitive data although newer clients support TLS 1.2 or later; choosing this alternative would address the wrong failure mode.