mcAfee Secure Website
23

Microsoft AZ-801 Bundle

Exam Code: AZ-801

Exam Name Configuring Windows Server Hybrid Advanced Services

Certification Provider: Microsoft

Corresponding Certification: Microsoft Certified: Windows Server Hybrid Administrator Associate

AZ-801 Training Materials $25.00

Reliable & Actual Study Materials for AZ-801 Exam Success

The Latest AZ-801 Exam Questions as Experienced in the Actual Test!

  • 24
    Questions & Answers

    AZ-801 Questions & Answers

    326 Questions & Answers

    Includes questions types found on actual exam such as drag and drop, simulation, type in, and fill in the blank.

  • 25
    AZ-801 Video Course

    AZ-801 Training Course

    122 Video Lectures

    Based on Real Life Scenarios which you will encounter in exam and learn by working with real equipment.

exam =32

Configuring Windows Server Hybrid Advanced Services (AZ-801) 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: $164.98
Bundle Price: $139.98

Purchase Individually

  • exam =34
    Questions & Answers

    Questions & Answers

    326 Questions

    $124.99
    exam =35
  • exam =37
    AZ-801 Video Course

    Training Course

    122 Video Lectures

    $39.99

Microsoft AZ-801 Practice Test 15

Question 140

An AZ-801 historical administration case reports: A silo policy object exists but none of the intended identities are assigned. Which TWO choices provide the technical correction and a supporting acceptance test? (Select TWO.)

  1. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  2. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.
  3. An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.
  4. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  5. A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

Explanation

Correct Answers

D:

For A silo policy object exists but none of the intended identities are assigned, this action is the relevant response: Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. It reduces the risk that a stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced.

E:

This is an independent validation for the condition A silo policy object exists but none of the intended identities are assigned. The expected result is: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

Incorrect Answers

A:

Hybrid ad password policy and fine-grained rules: Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly. That mechanism alone cannot establish Authentication policy silos and privileged isolation for this question.

B:

Microsoft entra password protection for ad ds: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. That may be useful independently, but the missing requirement here is Authentication policy silos and privileged isolation.

C:

Domain controller hardening and ad delegation: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. Here the decisive check is Authentication policy silos and privileged isolation, not that separate capability.

Question 141

An enterprise Windows Server hybrid administration team finds: A newly installed domain controller has no Defender for Identity sensor. The team must preserve authorized operations and recoverability while meeting the documented service constraints. What is the most defensible remediation for the observed failure?

  1. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  2. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  3. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  4. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.

Explanation

Correct Answer

A:

The distinctive observation is: A newly installed domain controller has no Defender for Identity sensor. The appropriate intervention is: Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. This addresses the specific danger: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. Validate closure with: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Incorrect Answers

B:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. That may be useful independently, but the missing requirement here is Microsoft defender for identity sensors and alerts.

C:

Domain controller hardening and ad delegation: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. Here the decisive check is Microsoft defender for identity sensors and alerts, not that separate capability.

D:

Microsoft entra password protection for ad ds: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.

Question 142

The recovery/security observation is: A newly installed domain controller has no Defender for Identity sensor. What independent result establishes the change worked?

  1. A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.
  2. A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.
  3. An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.
  4. An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

Explanation

Correct Answer

B:

The separate check for the condition A newly installed domain controller has no Defender for Identity sensor is: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed. It validates the control to deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. It verifies an operational result rather than a configuration entry alone.

Incorrect Answers

A:

Microsoft entra password protection for ad ds: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. That mechanism alone cannot establish Microsoft defender for identity sensors and alerts for this question.

C:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. Here the decisive check is Microsoft defender for identity sensors and alerts, not that separate capability.

D:

Domain controller hardening and ad delegation: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.

Question 143

An enterprise Windows Server hybrid administration team finds: A sensor reports unhealthy yet the operations dashboard is ignored. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which supported administrative change best addresses this condition?

  1. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  2. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  3. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  4. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.

Explanation

Correct Answer

B:

The distinctive observation is: A sensor reports unhealthy yet the operations dashboard is ignored. The appropriate intervention is: Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. This addresses the specific danger: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. Validate closure with: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Incorrect Answers

A:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. That mechanism alone cannot establish Microsoft defender for identity sensors and alerts for this question.

C:

Authentication policy silos and privileged isolation: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. Here the decisive check is Microsoft defender for identity sensors and alerts, not that separate capability.

D:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.

Question 144

The legacy Windows Server administration finding is: A sensor reports unhealthy yet the operations dashboard is ignored. Which risk is the main consequence of this finding?

  1. Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal.
  2. Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials.
  3. A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad.
  4. A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced.

Explanation

Correct Answer

A:

The issue is: A sensor reports unhealthy yet the operations dashboard is ignored. The material risk is that blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. The corrective control is to deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. Confirm through: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Incorrect Answers

B:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. That may be useful independently, but the missing requirement here is Microsoft defender for identity sensors and alerts.

C:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. Here the decisive check is Microsoft defender for identity sensors and alerts, not that separate capability.

D:

Authentication policy silos and privileged isolation: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.

Question 145

An enterprise Windows Server hybrid administration team finds: A suspected lateral movement sequence has no identity timeline in the investigation portal. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which intervention should the team prioritize under these constraints?

  1. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.
  2. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  3. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  4. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.

Explanation

Correct Answer

C:

The distinctive observation is: A suspected lateral movement sequence has no identity timeline in the investigation portal. The appropriate intervention is: Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. This addresses the specific danger: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. Validate closure with: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Incorrect Answers

A:

Microsoft entra password protection for ad ds: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. That mechanism alone cannot establish Microsoft defender for identity sensors and alerts for this question.

B:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. That may be useful independently, but the missing requirement here is Microsoft defender for identity sensors and alerts.

D:

Ntlm inventory audit and reduction: Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.

Question 146

The recovery/security observation is: A suspected lateral movement sequence has no identity timeline in the investigation portal. What independent result establishes the change worked?

  1. An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.
  2. The identified legacy dependency migrates to an approved authentication method and targeted NTLM-deny tests pass.
  3. A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.
  4. A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

Explanation

Correct Answer

C:

The separate check for the condition A suspected lateral movement sequence has no identity timeline in the investigation portal is: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed. It validates the control to deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. It verifies an operational result rather than a configuration entry alone.

Incorrect Answers

A:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. That mechanism alone cannot establish Microsoft defender for identity sensors and alerts for this question.

B:

Ntlm inventory audit and reduction: Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk. That may be useful independently, but the missing requirement here is Microsoft defender for identity sensors and alerts.

D:

Microsoft entra password protection for ad ds: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.

Question 147

An enterprise Windows Server hybrid administration team finds: An agent upgrade blocks required connectivity to the detection service. The team must preserve authorized operations and recoverability while meeting the documented service constraints. What is the strongest supported way to correct this operational weakness?

  1. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  2. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  3. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  4. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.

Explanation

Correct Answer

B:

The distinctive observation is: An agent upgrade blocks required connectivity to the detection service. The appropriate intervention is: Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. This addresses the specific danger: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. Validate closure with: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Incorrect Answers

A:

Domain controller hardening and ad delegation: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. That mechanism alone cannot establish Microsoft defender for identity sensors and alerts for this question.

C:

Ntlm inventory audit and reduction: Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk. Here the decisive check is Microsoft defender for identity sensors and alerts, not that separate capability.

D:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.

Question 148

The legacy Windows Server administration finding is: An agent upgrade blocks required connectivity to the detection service. Which risk is the main consequence of this finding?

  1. Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation.
  2. Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk.
  3. A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad.
  4. Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal.

Explanation

Correct Answer

D:

The issue is: An agent upgrade blocks required connectivity to the detection service. The material risk is that blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. The corrective control is to deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. Confirm through: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Incorrect Answers

A:

Domain controller hardening and ad delegation: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. That mechanism alone cannot establish Microsoft defender for identity sensors and alerts for this question.

B:

Ntlm inventory audit and reduction: Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk. That may be useful independently, but the missing requirement here is Microsoft defender for identity sensors and alerts.

C:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. Here the decisive check is Microsoft defender for identity sensors and alerts, not that separate capability.

Question 149

An enterprise Windows Server hybrid administration team finds: A security team relies on endpoint alerts but lacks domain controller sign-in telemetry. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which corrective control best meets the stated recovery and security requirements?

  1. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  2. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  3. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  4. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.

Explanation

Correct Answer

A:

The distinctive observation is: A security team relies on endpoint alerts but lacks domain controller sign-in telemetry. The appropriate intervention is: Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. This addresses the specific danger: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. Validate closure with: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Incorrect Answers

B:

Hybrid ad password policy and fine-grained rules: Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly. That may be useful independently, but the missing requirement here is Microsoft defender for identity sensors and alerts.

C:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. Here the decisive check is Microsoft defender for identity sensors and alerts, not that separate capability.

D:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.

Question 150

An AZ-801 historical administration case reports: A security team relies on endpoint alerts but lacks domain controller sign-in telemetry. Which TWO options together describe an appropriate response and a distinct verification? (Select TWO.)

  1. Policy-result checks and representative user tests demonstrate the intended password and lockout behavior for each group.
  2. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  3. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  4. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  5. A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Explanation

Correct Answers

C:

For A security team relies on endpoint alerts but lacks domain controller sign-in telemetry, this action is the relevant response: Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts. It reduces the risk that blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal.

E:

This is an independent validation for the condition A security team relies on endpoint alerts but lacks domain controller sign-in telemetry. The expected result is: A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Incorrect Answers

A:

Hybrid ad password policy and fine-grained rules: Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly. That mechanism alone cannot establish Microsoft defender for identity sensors and alerts for this question.

B:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. That may be useful independently, but the missing requirement here is Microsoft defender for identity sensors and alerts.

D:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. The observed issue still requires Microsoft defender for identity sensors and alerts; the proposed alternative tests another control.