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 51

Question 500

A Microsoft Azure administrator receives this requirement: A security team reviews only its principal production subscription and misses unmanaged virtual machines in recently acquired subscriptions. What observation is the strongest validation evidence?

  1. The inventory includes the acquired subscriptions, identifies owners and reveals previously unreviewed internet-exposed machines.
  2. The targeted risky configuration is remediated and the secure-score control reflects an appropriate improvement on reevaluation.
  3. The custom standard displays measurable compliance results for relevant encrypted resources rather than unsupported manual declarations.
  4. Previously unknown externally reachable assets are identified, attributed to an owner and queued for risk assessment.

Explanation

Correct Answer

A:

This validates the specific control for azure asset inventory missing subscriptions: A security inventory that excludes child subscriptions and connected accounts cannot give complete exposure or asset ownership coverage. The associated corrective action is: Build an authorized inventory from Defender for Cloud and Azure Resource Graph across governed subscriptions and management groups. Testing a different component would not establish this result.

Incorrect Answers

B:

Secure score is based on security-control recommendations and affected resources, not just a raw count of findings. “Review secure-score control weights, exposure and business impact, then prioritize closing the highest-risk actionable gap” would address that alternative cause, not the condition in this question: a security inventory that excludes child subscriptions and connected accounts cannot give complete exposure or asset ownership coverage.

C:

“Build the supported custom standard from approved Azure Policy content and map its controls to the organization's documented obligations” responds to this separate finding: custom enterprise controls need an appropriately implemented Defender for Cloud custom standard linked to valid assessment definitions. This question instead needs “Build an authorized inventory from Defender for Cloud and Azure Resource Graph across governed subscriptions and management groups”, so the alternative does not meet the stated condition.

D:

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 team reviews only its principal production subscription and misses unmanaged virtual machines in recently acquired subscriptions; choosing this alternative would address the wrong failure mode.

Question 501

While validating an Azure workload, the security team finds: A security program expects passwordless sign-in but permits only password-and-SMS methods in the authentication methods policy. Which result confirms the relevant security control is effective?

  1. The recreated VM authenticates to its approved resource using the newly granted managed identity.
  2. A pilot user signs in with the intended passwordless credential under Conditional Access enforcement.
  3. Both functions obtain tokens for the approved user-assigned identity without duplicating secrets.
  4. The function uses token-based access without a stored application client secret and writes only permitted blobs.

Explanation

Correct Answer

B:

This validates the specific control for passwordless authentication method policy: Microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users. The associated corrective action is: Enable the approved passwordless method and complete secure user registration. Testing a different component would not establish this result.

Incorrect Answers

A:

A system-assigned managed identity is tied to its Azure resource lifecycle and a recreated resource may have a new principal. “Enable a new system-assigned identity and explicitly assign the required least-privilege role to its new principal” would address that alternative cause, not the condition in this question: microsoft Entra authentication method settings have not enabled the chosen supported passwordless method for eligible users.

C:

“Create an authorized user-assigned managed identity, attach it to the workloads and scope its permissions correctly” responds to this separate finding: separate system-assigned identities do not provide the stable reusable principal desired across resources. This question instead needs “Enable the approved passwordless method and complete secure user registration”, so the alternative does not meet the stated condition.

D:

The workload is not using its platform-managed identity and therefore depends on long-lived application secrets. “Enable an appropriate managed identity and grant narrowly scoped storage data authorization to that identity” applies to that separate problem. The observed case is a security program expects passwordless sign-in but permits only password-and-SMS methods in the authentication methods policy; choosing this alternative would address the wrong failure mode.

Question 502

A regulated Azure tenant has this security condition: A tenant permits employees to consent to any third-party application, resulting in a rogue app receiving broad mailbox-related scopes. Which result confirms the relevant security control is effective?

  1. Only the approved workflow obtains short-lived Azure tokens without transmitting a static client secret.
  2. A test unverified high-risk application cannot gain requested scopes through ordinary user consent.
  3. The failing app identity, time and error reason are identified in the service principal log stream.
  4. The daemon accesses only approved Graph resources without impersonating an absent signed-in user.

Explanation

Correct Answer

B:

This validates the specific control for user consent policies for third party apps: The user consent configuration permits risky OAuth grants without publisher and permission restrictions. The associated corrective action is: Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow. Testing a different component would not establish this result.

Incorrect Answers

A:

Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. “Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret” would address that alternative cause, not the condition in this question: the user consent configuration permits risky OAuth grants without publisher and permission restrictions.

C:

“Inspect service principal sign-in logs and correlated credential or conditional policy results” responds to this separate finding: non-interactive service principal authentication has dedicated sign-in logs not represented in user interactive sign-in views. This question instead needs “Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow”, so the alternative does not meet the stated condition.

D:

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 tenant permits employees to consent to any third-party application, resulting in a rogue app receiving broad mailbox-related scopes; choosing this alternative would address the wrong failure mode.

Question 503

While validating an Azure workload, the security team finds: An analyst receives generic Azure Contributor access at a storage account yet cannot list blobs using Microsoft Entra authorization, despite managing account settings. What governance practice would best prevent the same failure?

  1. Review management-plane versus data-plane permissions separately in storage access design.
  2. Review group ownership and membership periodically rather than accumulating direct role assignments.
  3. Investigate deny assignments as well as allow grants when diagnosing apparent RBAC permission anomalies.
  4. Test conditioned Azure RBAC access against both permitted and forbidden resource attributes.

Explanation

Correct Answer

A:

This guardrail addresses dataactions for azure data plane: Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. The prevention measure is: Review management-plane versus data-plane permissions separately in storage access design. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

B:

Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. “Review group ownership and membership periodically rather than accumulating direct role assignments” would address that alternative cause, not the condition in this question: azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.

C:

“Investigate deny assignments as well as allow grants when diagnosing apparent RBAC permission anomalies” responds to this separate finding: azure deny assignments can block an operation even if an allow role grants that operation at the same or an inherited scope. This question instead needs “Review management-plane versus data-plane permissions separately in storage access design”, 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. “Test conditioned Azure RBAC access against both permitted and forbidden resource attributes” applies to that separate problem. The observed case is an analyst receives generic Azure Contributor access at a storage account yet cannot list blobs using Microsoft Entra authorization, despite managing account settings; choosing this alternative would address the wrong failure mode.

Question 504

A Microsoft Azure administrator receives this requirement: A payment-system security baseline requires hardware-protected encryption keys but the vault administrators deploy software-protected keys only. Which operating control most directly reduces this recurring risk?

  1. Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards.
  2. Keep configuration policy checks separate from identity, data-plane and network access acceptance tests.
  3. Match vault tier and key protection type to compliance requirements before key creation and migration.
  4. Monitor external TLS endpoints separately from Key Vault certificate inventory and verify renewal propagation.

Explanation

Correct Answer

C:

This guardrail addresses key vault hsm keys versus software keys: Software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type. The prevention measure is: Match vault tier and key protection type to compliance requirements before key creation and migration. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Critical backup operations can require multiuser authorization using a protected Resource Guard in a separately controlled administrative boundary. “Review backup operator and Resource Guard separation to prevent a single account from bypassing recovery safeguards” would address that alternative cause, not the condition in this question: software-protected keys do not satisfy a documented hardware key protection requirement without an approved HSM-backed key type.

B:

“Keep configuration policy checks separate from identity, data-plane and network access acceptance tests” responds to this separate finding: azure Policy resource compliance assesses configured resource properties but is not a replacement for blob data-plane authorization testing. This question instead needs “Match vault tier and key protection type to compliance requirements before key creation and migration”, so the alternative does not meet the stated condition.

D:

Renewal of a vault certificate does not guarantee that each dependent application has imported or rebound the newest certificate version. “Monitor external TLS endpoints separately from Key Vault certificate inventory and verify renewal propagation” applies to that separate problem. The observed case is a payment-system security baseline requires hardware-protected encryption keys but the vault administrators deploy software-protected keys only; choosing this alternative would address the wrong failure mode.

Question 505

While validating an Azure workload, the security team finds: An administrator edits Virtual Network Manager configuration definitions but never deploys the configuration to the required target regions. Which configuration change most directly resolves this problem?

  1. Correct the group membership query or approved explicit membership and deploy the security configuration.
  2. Deploy the approved configuration to the correct regions and verify the deployed state.
  3. Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy.
  4. Renumber or redesign the address space before establishing peering or use an approved translation architecture.

Explanation

Correct Answer

B:

The cause is: Saving network manager intent does not itself apply connectivity or security configuration to target regions. The appropriate change is: Deploy the approved configuration to the correct regions and verify the deployed state. Verify it with this outcome: The destination VNet shows the new intended connectivity or security policy after successful deployment.

Incorrect Answers

A:

This action concerns virtual network manager dynamic network group, where The dynamic network group criteria do not include the intended VNet attributes or scope. The reported incident instead involves Saving network manager intent does not itself apply connectivity or security configuration to target regions.

C:

This action concerns azure firewall application rule fqdn filtering, where A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. The corrective response here is “Deploy the approved configuration to the correct regions and verify the deployed state”; this alternative does not provide that response.

D:

This action concerns overlapping vnet address spaces, where Azure VNet peering requires non-overlapping address spaces; overlapping ranges make direct peering invalid. The stem reports an administrator edits Virtual Network Manager configuration definitions but never deploys the configuration to the required target regions; this control addresses a different failure condition.

Question 506

A platform security assessment reveals this issue: A Front Door application must privately reach an Azure origin, yet its backend storage or app remains publicly accessible to any Internet client. What observation is the strongest validation evidence?

  1. The security team queries the required firewall rule-match records for a controlled test flow.
  2. Authorized flow records are available for investigation with correct source, destination and decision context.
  3. Diagnostics identify the exact applicable rule and the corrected flow matches approved connectivity.
  4. Front Door continues serving approved requests but direct Internet calls to the origin are blocked.

Explanation

Correct Answer

D:

This validates the specific control for front door private link origin protection: The Front Door origin connection is not constrained through a supported private-link origin with public access restriction. The associated corrective action is: Configure a supported Private Link origin and restrict direct public access to the origin service. Testing a different component would not establish this result.

Incorrect Answers

A:

Required Azure Firewall resource logs were not exported to an appropriate Log Analytics workspace or storage destination. “Configure relevant firewall diagnostic categories and secure retention for rule and threat events” would address that alternative cause, not the condition in this question: the Front Door origin connection is not constrained through a supported private-link origin with public access restriction.

B:

“Enable the supported Virtual Network flow logs and associated analytics or storage retention” responds to this separate finding: network flow logging has not been configured for the relevant virtual network monitoring scope. This question instead needs “Configure a supported Private Link origin and restrict direct public access to the origin service”, so the alternative does not meet the stated condition.

C:

The blocking or allowing NSG rule should be identified using the effective IP flow evaluation rather than assumed from a saved template. “Run Network Watcher IP flow verify with the test source, destination, direction and port” applies to that separate problem. The observed case is a Front Door application must privately reach an Azure origin, yet its backend storage or app remains publicly accessible to any Internet client; choosing this alternative would address the wrong failure mode.

Question 507

While validating an Azure workload, the security team finds: A production confidential client uses a shared text secret in CI logs despite a security requirement for stronger app authentication. Which result confirms the relevant security control is effective?

  1. Only the approved workflow obtains short-lived Azure tokens without transmitting a static client secret.
  2. The daemon accesses only approved Graph resources without impersonating an absent signed-in user.
  3. The application authenticates with its secured credential while the old secret is revoked and unusable.
  4. A test unverified high-risk application cannot gain requested scopes through ordinary user consent.

Explanation

Correct Answer

C:

This validates the specific control for certificate based app credential: The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. The associated corrective action is: Configure a certificate credential or supported workload federation and remove the leaked text secret. Testing a different component would not establish this result.

Incorrect Answers

A:

Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. “Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret” would address that alternative cause, not the condition in this question: the confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity.

B:

“Select approved application permissions with administrator consent and configure client-credentials access” responds to this separate finding: delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. This question instead needs “Configure a certificate credential or supported workload federation and remove the leaked text secret”, so the alternative does not meet the stated condition.

D:

The user consent configuration permits risky OAuth grants without publisher and permission restrictions. “Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow” applies to that separate problem. The observed case is a production confidential client uses a shared text secret in CI logs despite a security requirement for stronger app authentication; choosing this alternative would address the wrong failure mode.

Question 508

A regulated Azure tenant has this security condition: A production application breaks after a storage account key rotation because all clients use one static key with no staged rollover design. Which configuration change most directly resolves this problem?

  1. Enable appropriate APIM subscription requirements and validate product/API associations.
  2. Apply registry retention and approved immutable digest-based deployment practices with vulnerability checks.
  3. Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys.
  4. Disable unnecessary ACR admin access and use Microsoft Entra identities or managed identities with scoped registry roles.

Explanation

Correct Answer

C:

The cause is: The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes. The appropriate change is: Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys. Verify it with this outcome: Applications remain available through rotation and old leaked keys cease to authorize access.

Incorrect Answers

A:

This action concerns api management subscription key usage, where The API or product does not require the intended APIM subscription key or equivalent authentication control. The reported incident instead involves The client authentication design has no key rotation or identity-based alternative and assumes an account key never changes.

B:

This action concerns acr image retention and digest hygiene, where Unmanaged image tags and retention practices permit insecure or obsolete artifacts to remain available for deployment. The corrective response here is “Use a controlled secondary-key migration or migrate to Microsoft Entra authentication and rotate compromised keys”; this alternative does not provide that response.

D:

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 production application breaks after a storage account key rotation because all clients use one static key with no staged rollover design; this control addresses a different failure condition.

Question 509

A regulated Azure tenant has this security condition: A protected custom API expects clients to request a least-privilege read scope, but the scope is not defined in the API's app registration. Which safeguard would best prevent this issue from recurring?

  1. Recertify high-impact OAuth application permissions and remove obsolete grants.
  2. Audit app role assignments and test default-deny authorization paths during release reviews.
  3. Audit federation subject patterns to prevent arbitrary branches or repositories from assuming deployment roles.
  4. Version and review exposed API scopes so newly added privileges require explicit consent.

Explanation

Correct Answer

D:

This guardrail addresses expose an api permission scope: The protected application registration has not exposed an OAuth permission scope for the required delegated operation. The prevention measure is: Version and review exposed API scopes so newly added privileges require explicit consent. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

The OAuth permission grant exceeds the app's functional requirements and creates unnecessary directory-wide compromise impact. “Recertify high-impact OAuth application permissions and remove obsolete grants” would address that alternative cause, not the condition in this question: the protected application registration has not exposed an OAuth permission scope for the required delegated operation.

B:

“Audit app role assignments and test default-deny authorization paths during release reviews” responds to this separate finding: successful authentication does not establish application authorization; app roles and assignments are not enforced. This question instead needs “Version and review exposed API scopes so newly added privileges require explicit consent”, so the alternative does not meet the stated condition.

C:

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 a protected custom API expects clients to request a least-privilege read scope, but the scope is not defined in the API's app registration; choosing this alternative would address the wrong failure mode.

Question 510

A regulated Azure tenant has this security condition: A security team deploys Log Analytics and expects the workspace to provide Microsoft Sentinel analytics and incidents without onboarding Sentinel. Which configuration change most directly resolves this problem?

  1. Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content.
  2. Review rule order, matching conditions and any stop-processing behavior, then move the precise severity rule ahead of broad disposition.
  3. Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema.
  4. Configure supported threat-intelligence ingestion and review indicator validity, expiration and source confidence in analytics.

Explanation

Correct Answer

A:

The cause is: A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities. The appropriate change is: Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content. Verify it with this outcome: The workspace exposes Sentinel analytics, incident management and authorized security content appropriately.

Incorrect Answers

B:

This action concerns sentinel automation rule order and stop processing, where Automation rule ordering and stopping behavior can prevent more specific rules from executing as intended. The reported incident instead involves A Log Analytics workspace stores supported telemetry but must be enabled and configured for Microsoft Sentinel capabilities.

C:

This action concerns azure monitor transformation for sensitive fields, where Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. The corrective response here is “Enable Microsoft Sentinel on the intended eligible Log Analytics workspace and configure required data sources and content”; this alternative does not provide that response.

D:

This action concerns sentinel threat intelligence indicator freshness, where Threat indicators can become stale or incorrect and need trusted ingestion, expiry handling and contextual confirmation. The stem reports a security team deploys Log Analytics and expects the workspace to provide Microsoft Sentinel analytics and incidents without onboarding Sentinel; this control addresses a different failure condition.