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 17

Question 160

A production Azure security implementation shows this failure: A subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet. What should the engineer implement first to address the weakness?

  1. Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls.
  2. Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path.
  3. Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes.
  4. Inspect both effective rule sets and adjust the explicitly intended rule at the blocking scope.

Explanation

Correct Answer

A:

The cause is: Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. The appropriate change is: Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls. Verify it with this outcome: Unauthorized Internet egress fails while approved endpoints remain reachable through logged channels.

Incorrect Answers

B:

This action concerns asymmetric routing around network virtual appliance, where Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. The reported incident instead involves Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply.

C:

This action concerns stateful nsg return traffic behavior, where NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. The corrective response here is “Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls”; this alternative does not provide that response.

D:

This action concerns subnet versus nic nsg evaluation, where Both applicable subnet and NIC NSG security rules affect connectivity; an allow at one layer cannot override a deny at another. The stem reports a subnet has no custom outbound deny rule, and developers assume that absence of custom rules means workload VMs cannot reach the Internet; this control addresses a different failure condition.

Question 161

During a cloud security review, the operations team observes: A scheduled Sentinel rule runs every 15 minutes but looks back only two minutes, allowing delayed logs to fall into unobserved intervals. Which operating control most directly reduces this recurring risk?

  1. Review incident grouping semantics and false-merging risk with a representative detection dataset.
  2. Include evidence that logs are arriving when implementing new high-impact network policies.
  3. Monitor ingestion delay and align scheduled rule lookback to actual source latency.
  4. Review playbook connection identities and least-privilege rights before enabling automated containment.

Explanation

Correct Answer

C:

This guardrail addresses sentinel analytics frequency lookback mismatch: A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. The prevention measure is: Monitor ingestion delay and align scheduled rule lookback to actual source latency. A control in another subsystem would not prevent this specific recurrence.

Incorrect Answers

A:

Alert and incident grouping settings may produce duplicate cases when the aggregation criteria do not reflect the investigation unit. “Review incident grouping semantics and false-merging risk with a representative detection dataset” would address that alternative cause, not the condition in this question: a rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation.

B:

“Include evidence that logs are arriving when implementing new high-impact network policies” responds to this separate finding: network traffic enforcement and security telemetry are separate; required resource logs must be routed through supported diagnostic settings. This question instead needs “Monitor ingestion delay and align scheduled rule lookback to actual source latency”, so the alternative does not meet the stated condition.

D:

Playbook execution permissions and each target service's RBAC are distinct from permission to create or update Sentinel incidents. “Review playbook connection identities and least-privilege rights before enabling automated containment” applies to that separate problem. The observed case is a scheduled Sentinel rule runs every 15 minutes but looks back only two minutes, allowing delayed logs to fall into unobserved intervals; choosing this alternative would address the wrong failure mode.

Question 162

An Azure security engineer investigates the following incident: A records container must resist deletion for a required retention period, but standard user write permissions allow documents to be overwritten. Which remediation best addresses the specific issue?

  1. Assign Storage Blob Data Reader to the application identity at the appropriate container scope.
  2. Configure the appropriate time-based immutability policy or legal hold for the protected container.
  3. Enable infrastructure encryption on eligible storage accounts at the appropriate creation stage.
  4. Enable supported blob versioning and define backup or lifecycle protection for critical objects.

Explanation

Correct Answer

B:

The cause is: Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. The appropriate change is: Configure the appropriate time-based immutability policy or legal hold for the protected container. Verify it with this outcome: Authorized reads continue while deletes or overwrites prohibited by retention are rejected.

Incorrect Answers

A:

This action concerns blob storage data rbac, where Management-plane storage Contributor does not necessarily include blob data read DataActions. The reported incident instead involves Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone.

C:

This action concerns storage infrastructure double encryption, where The specified infrastructure encryption requirement needs the supported additional service-side encryption layer. The corrective response here is “Configure the appropriate time-based immutability policy or legal hold for the protected container”; this alternative does not provide that response.

D:

This action concerns blob versioning prior content recovery, where Blob soft delete alone does not necessarily preserve every previous overwrite without appropriate versioning. The stem reports a records container must resist deletion for a required retention period, but standard user write permissions allow documents to be overwritten; this control addresses a different failure condition.

Question 163

A production Azure security implementation shows this failure: 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. What is the most appropriate corrective step?

  1. Disable BGP route propagation on the relevant route table where the approved design requires static steering.
  2. Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path.
  3. Add a supported outbound deny or narrowly scoped allow strategy and route traffic through approved egress controls.
  4. Account for established-flow state and terminate or recreate relevant sessions when validating emergency block changes.

Explanation

Correct Answer

B:

The cause is: Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg. The appropriate change is: Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path. Verify it with this outcome: End-to-end requests and replies traverse the expected appliance path without asymmetric session drops.

Incorrect Answers

A:

This action concerns BGP gateway route propagation control, where Gateway route propagation remains enabled for the route table and influences effective routing selections. The reported incident instead involves Forward and return route paths are asymmetric, bypassing the stateful inspection device on the return leg.

C:

This action concerns default outbound network access control, where Default NSG security rules can allow outbound Internet connectivity unless explicit higher-priority restrictions apply. The corrective response here is “Repair route tables and network design so eligible bidirectional sessions traverse the same supported inspection path”; this alternative does not provide that response.

D:

This action concerns stateful nsg return traffic behavior, where NSGs are stateful and existing established flows can persist until their flow records expire despite rule changes. The stem reports 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; this control addresses a different failure condition.

Question 164

The cloud operations team reviews the following risk: A client attempts to mount Azure Files using an obsolete insecure SMB configuration and cannot meet company encryption and authentication requirements. Which result confirms the relevant security control is effective?

  1. An eligible client mounts the share securely while outdated unencrypted access fails.
  2. The application resolves its SQL host to the private endpoint and Internet SQL connection attempts fail.
  3. Authorized Entra principals connect and act within granted database roles without using the shared SQL account.
  4. Secrets are protected in the intended storage path and only approved workload identities can retrieve values.

Explanation

Correct Answer

A:

This validates the specific control for azure files secure smb transit: The file access path needs compatible secure SMB protocol and supported encrypted transport settings. The associated corrective action is: Use supported modern SMB client configuration and private connectivity or TLS where applicable. Testing a different component would not establish this result.

Incorrect Answers

B:

The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. “Create an approved SQL Private Endpoint and private DNS mapping, then disable unnecessary public access” would address that alternative cause, not the condition in this question: the file access path needs compatible secure SMB protocol and supported encrypted transport settings.

C:

“Configure the Microsoft Entra administrator and create appropriate contained database users and roles” responds to this separate finding: the SQL server or managed instance has not enabled and governed the intended Microsoft Entra database authentication. This question instead needs “Use supported modern SMB client configuration and private connectivity or TLS where applicable”, so the alternative does not meet the stated condition.

D:

Kubernetes Secret encoding is not encryption and does not replace supported encryption-at-rest or managed secret controls. “Enable supported secret encryption and external secret management using Key Vault where required” applies to that separate problem. The observed case is a client attempts to mount Azure Files using an obsolete insecure SMB configuration and cannot meet company encryption and authentication requirements; choosing this alternative would address the wrong failure mode.

Question 165

During a cloud security review, the operations team observes: An organization requires isolated multi-app hosting with restricted inbound access, but deployments use a public App Service plan and broad access restrictions. What is the most appropriate corrective step?

  1. Deploy a supported internal App Service Environment and configure ingress and outbound network controls.
  2. Configure a supported APIM private networking option and restrict public gateway exposure as required.
  3. Create or configure a qualifying dedicated delegated subnet and apply approved SQL Managed Instance network controls.
  4. Create the approved Front Door WAF geographic match rule with a documented action and exclusions.

Explanation

Correct Answer

A:

The cause is: The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary. The appropriate change is: Deploy a supported internal App Service Environment and configure ingress and outbound network controls. Verify it with this outcome: Only authorized internal clients reach hosted apps, and operations can verify the isolated hosting path.

Incorrect Answers

B:

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 reported incident instead involves The design lacks the dedicated App Service Environment network isolation model required for the stated hosting boundary.

C:

This action concerns azure sql managed instance subnet requirements, where SQL Managed Instance needs a dedicated subnet with supported delegation, route and network settings. The corrective response here is “Deploy a supported internal App Service Environment and configure ingress and outbound network controls”; this alternative does not provide that response.

D:

This action concerns front door waf geographic access controls, where The access policy needs a supported Azure Front Door WAF custom rule matching client geography at the edge. The stem reports an organization requires isolated multi-app hosting with restricted inbound access, but deployments use a public App Service plan and broad access restrictions; this control addresses a different failure condition.

Question 166

An Azure security engineer investigates the following incident: A network security monitoring pipeline forwards full raw payload fields into an analytics workspace even though policy permits only necessary metadata. Which remediation best addresses the specific issue?

  1. Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema.
  2. Enable the required syslog facility and severity in the Linux data collection rule and verify agent association.
  3. Configure sufficient query lookback, appropriate frequency and deduplication for the observed ingestion delay.
  4. Configure the supported Azure Activity connector and required subscription diagnostic or policy associations to the selected workspace.

Explanation

Correct Answer

A:

The cause is: Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained. The appropriate change is: Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema. Verify it with this outcome: Representative security events remain analyzable without exposing the prohibited personal payload fields.

Incorrect Answers

B:

This action concerns azure monitor dcr linux syslog facility, where A DCR must collect the relevant Linux syslog facilities and severities and route them to the intended destination. The reported incident instead involves Unsupported or missing DCR transformation can allow data not required for the security use case to be ingested or retained.

C:

This action concerns sentinel analytics frequency lookback mismatch, where A rule's query period and ingestion latency determine whether delayed events are included in scheduled evaluation. The corrective response here is “Apply a supported DCR transformation that filters or projects approved fields and validates the resulting table schema”; this alternative does not provide that response.

D:

This action concerns sentinel azure activity data connector, where Guest operating system telemetry does not automatically include the Azure subscription Activity Log that tracks control-plane actions. The stem reports a network security monitoring pipeline forwards full raw payload fields into an analytics workspace even though policy permits only necessary metadata; this control addresses a different failure condition.

Question 167

During a cloud security review, the operations team observes: A background daemon calls Microsoft Graph without a signed-in user but requests delegated permission scopes that rely on user context. What is the most appropriate corrective step?

  1. Configure a federated identity credential with restricted issuer, subject and audience, and remove the stored secret.
  2. Define application roles, assign them to approved users or groups and validate role claims in the app.
  3. Configure a certificate credential or supported workload federation and remove the leaked text secret.
  4. Select approved application permissions with administrator consent and configure client-credentials access.

Explanation

Correct Answer

D:

The cause is: Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions. The appropriate change is: Select approved application permissions with administrator consent and configure client-credentials access. Verify it with this outcome: The daemon accesses only approved Graph resources without impersonating an absent signed-in user.

Incorrect Answers

A:

This action concerns workload identity federation in ci pipeline, where Secret-based automation ignores supported federated workload identity trust between the CI issuer and Entra. The reported incident instead involves Delegated permissions require a user context, whereas unattended client credentials typically use supported application permissions.

B:

This action concerns application role assignment authorization, where Successful authentication does not establish application authorization; app roles and assignments are not enforced. The corrective response here is “Select approved application permissions with administrator consent and configure client-credentials access”; this alternative does not provide that response.

C:

This action concerns certificate based app credential, where The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. The stem reports a background daemon calls Microsoft Graph without a signed-in user but requests delegated permission scopes that rely on user context; this control addresses a different failure condition.

Question 168

The cloud operations team reviews the following risk: A multi-tenant SaaS app authenticates users successfully but grants every signed-in user an administrator feature because role assignments are absent. Which configuration change most directly resolves this problem?

  1. Configure a certificate credential or supported workload federation and remove the leaked text secret.
  2. Restrict user consent to eligible verified apps and low-risk scopes or require administrator approval workflow.
  3. Define application roles, assign them to approved users or groups and validate role claims in the app.
  4. Define and publish the intended API scope and update client permissions and authorization enforcement.

Explanation

Correct Answer

C:

The cause is: Successful authentication does not establish application authorization; app roles and assignments are not enforced. The appropriate change is: Define application roles, assign them to approved users or groups and validate role claims in the app. Verify it with this outcome: A basic user receives only permitted features while a role-assigned administrator gets controlled privileges.

Incorrect Answers

A:

This action concerns certificate based app credential, where The confidential client uses an exposed symmetric secret rather than an approved certificate credential or managed workload identity. The reported incident instead involves Successful authentication does not establish application authorization; app roles and assignments are not enforced.

B:

This action concerns user consent policies for third party apps, where The user consent configuration permits risky OAuth grants without publisher and permission restrictions. The corrective response here is “Define application roles, assign them to approved users or groups and validate role claims in the app”; this alternative does not provide that response.

D:

This action concerns expose an api permission scope, where The protected application registration has not exposed an OAuth permission scope for the required delegated operation. The stem reports a multi-tenant SaaS app authenticates users successfully but grants every signed-in user an administrator feature because role assignments are absent; this control addresses a different failure condition.

Question 169

A production Azure security implementation shows this failure: An application needs to send DNS queries to a custom resolver over UDP, but Azure Firewall has only an HTTPS application rule for the resolver host. What observation is the strongest validation evidence?

  1. A spoke workload reaches the on-premises network via the shared hub gateway without deploying a second gateway.
  2. The forbidden flow remains blocked until a reviewed policy exception is applied centrally.
  3. Approved HTTPS hosts are reachable and unrelated hosts in the same IP ranges are rejected.
  4. Only the authorized DNS queries succeed and firewall logs show the intended rule match.

Explanation

Correct Answer

D:

This validates the specific control for azure firewall network rule ip protocol: An HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design. The associated corrective action is: Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow. Testing a different component would not establish this result.

Incorrect Answers

A:

Gateway transit and remote gateway usage flags are not configured consistently on the hub and spoke peerings. “Enable the approved gateway-transit and use-remote-gateways settings while respecting platform constraints” would address that alternative cause, not the condition in this question: an HTTPS FQDN application rule does not match a UDP DNS flow that needs a supported network rule or DNS proxy design.

B:

“Change the governing security admin policy through approved central administration rather than widening local NSGs” responds to this separate finding: an enforced security admin deny rule has higher governance precedence than the workload NSG allow. This question instead needs “Create the appropriately scoped UDP network rule or configure the supported firewall DNS proxy workflow”, so the alternative does not meet the stated condition.

C:

A broad address rule is not the appropriate least-privilege control for supported HTTP/S FQDN filtering. “Configure scoped Azure Firewall application rules for the required FQDNs and ports under the correct policy” applies to that separate problem. The observed case is an application needs to send DNS queries to a custom resolver over UDP, but Azure Firewall has only an HTTPS application rule for the resolver host; choosing this alternative would address the wrong failure mode.

Question 170

During a cloud security review, the operations team observes: A service principal with Storage Blob Data Contributor can write to all containers although the workload should only update blobs carrying an approved classification tag. Which underlying control gap is responsible for the issue?

  1. PIM role settings have not required the intended multifactor or authentication-strength control at activation.
  2. Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle.
  3. Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access.
  4. A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.

Explanation

Correct Answer

D:

The described technical condition is: A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. The appropriate corrective action is: Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations. Confirm with: Authorized tagged blobs can be updated while attempted writes to excluded blobs are rejected.

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: a broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires.

B:

“Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls” responds to this separate finding: direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. This question instead needs “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations”, so the alternative does not meet the stated condition.

C:

Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” applies to that separate problem. The observed case is a service principal with Storage Blob Data Contributor can write to all containers although the workload should only update blobs carrying an approved classification tag; choosing this alternative would address the wrong failure mode.