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 10

Question 90

An AZ-801 historical administration case reports: A password rule linked to an OU is mistaken for an effective fine-grained domain policy. Which TWO options together describe an appropriate response and a distinct verification? (Select TWO.)

  1. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  2. Policy-result checks and representative user tests demonstrate the intended password and lockout behavior for each group.
  3. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  4. Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.
  5. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.

Explanation

Correct Answers

A:

For A password rule linked to an OU is mistaken for an effective fine-grained domain policy, this action is the relevant response: Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks. It reduces the risk that weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly.

B:

This is an independent validation for the condition A password rule linked to an OU is mistaken for an effective fine-grained domain policy. The expected result is: Policy-result checks and representative user tests demonstrate the intended password and lockout behavior for each group.

Incorrect Answers

C:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. Here the decisive check is Hybrid ad password policy and fine-grained rules, 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 Hybrid ad password policy and fine-grained rules; the proposed alternative tests another control.

E:

Ntlm inventory audit and reduction: Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk. Without demonstrating Hybrid ad password policy and fine-grained rules, that option does not satisfy the requested outcome.

Question 91

An enterprise Windows Server hybrid administration team finds: A domain controller accepts a banned corporate-name password after proxy connectivity is lost. 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 health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.
  2. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  3. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  4. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.

Explanation

Correct Answer

A:

The distinctive observation is: A domain controller accepts a banned corporate-name password after proxy connectivity is lost. The appropriate intervention is: Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. This addresses the specific danger: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. Validate closure with: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

Incorrect Answers

B:

Authentication policy silos and privileged isolation: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. That may be useful independently, but the missing requirement here is Microsoft entra password protection for ad ds.

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 entra password protection for ad ds, not that separate capability.

D:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. The observed issue still requires Microsoft entra password protection for ad ds; the proposed alternative tests another control.

Question 92

The recovery/security observation is: A domain controller accepts a banned corporate-name password after proxy connectivity is lost. What evidence would best demonstrate that the remediation is effective?

  1. A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.
  2. A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.
  3. An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.
  4. A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

Explanation

Correct Answer

B:

The separate check for the condition A domain controller accepts a banned corporate-name password after proxy connectivity is lost is: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green. It validates the control to deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. It verifies an operational result rather than a configuration entry alone.

Incorrect Answers

A:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. That mechanism alone cannot establish Microsoft entra password protection for ad ds 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 entra password protection for ad ds, 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 entra password protection for ad ds; the proposed alternative tests another control.

Question 93

An enterprise Windows Server hybrid administration team finds: A password protection deployment remains in audit mode while administrators assume enforcement. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which supported administrative change best addresses this condition?

  1. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.
  2. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  3. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  4. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.

Explanation

Correct Answer

A:

The distinctive observation is: A password protection deployment remains in audit mode while administrators assume enforcement. The appropriate intervention is: Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. This addresses the specific danger: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. Validate closure with: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

Incorrect Answers

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 entra password protection for ad ds.

C:

Hybrid ad password policy and fine-grained rules: Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly. Here the decisive check is Microsoft entra password protection for ad ds, 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 entra password protection for ad ds; the proposed alternative tests another control.

Question 94

The legacy Windows Server administration finding is: A password protection deployment remains in audit mode while administrators assume enforcement. Which risk is the main consequence of this finding?

  1. Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy.
  2. Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly.
  3. Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk.
  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 password protection deployment remains in audit mode while administrators assume enforcement. The material risk is that unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. The corrective control is to deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. Confirm through: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

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 entra password protection for ad ds.

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 entra password protection for ad ds, 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 entra password protection for ad ds; the proposed alternative tests another control.

Question 95

An enterprise Windows Server hybrid administration team finds: One branch domain controller lacks the required password protection agent. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which intervention should the team prioritize under these constraints?

  1. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  2. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  3. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  4. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.

Explanation

Correct Answer

D:

The distinctive observation is: One branch domain controller lacks the required password protection agent. The appropriate intervention is: Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. This addresses the specific danger: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. Validate closure with: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

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 entra password protection for ad ds for this question.

B:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. That may be useful independently, but the missing requirement here is Microsoft entra password protection for ad ds.

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 entra password protection for ad ds, not that separate capability.

Question 96

The recovery/security observation is: One branch domain controller lacks the required password protection agent. What evidence would best demonstrate that the remediation is effective?

  1. Policy-result checks and representative user tests demonstrate the intended password and lockout behavior for each group.
  2. A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.
  3. A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.
  4. Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

Explanation

Correct Answer

B:

The separate check for the condition One branch domain controller lacks the required password protection agent is: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green. It validates the control to deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. It verifies an operational result rather than a configuration entry alone.

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 entra password protection for ad ds for this question.

C:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. Here the decisive check is Microsoft entra password protection for ad ds, 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 entra password protection for ad ds; the proposed alternative tests another control.

Question 97

An enterprise Windows Server hybrid administration team finds: A custom banned-password entry is never synchronized to on-premises agents. 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. 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. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.

Explanation

Correct Answer

A:

The distinctive observation is: A custom banned-password entry is never synchronized to on-premises agents. The appropriate intervention is: Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. This addresses the specific danger: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. Validate closure with: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

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 entra password protection for ad ds.

C:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. Here the decisive check is Microsoft entra password protection for ad ds, 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 entra password protection for ad ds; the proposed alternative tests another control.

Question 98

The legacy Windows Server administration finding is: A custom banned-password entry is never synchronized to on-premises agents. Which risk is the main consequence of this finding?

  1. Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials.
  2. Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal.
  3. A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced.
  4. Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy.

Explanation

Correct Answer

D:

The issue is: A custom banned-password entry is never synchronized to on-premises agents. The material risk is that unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. The corrective control is to deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. Confirm through: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

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 entra password protection for ad ds for this question.

B:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. That may be useful independently, but the missing requirement here is Microsoft entra password protection for ad ds.

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 entra password protection for ad ds, not that separate capability.

Question 99

An enterprise Windows Server hybrid administration team finds: An agent audit reports errors yet the team treats cloud policy creation as complete. 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. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  3. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.
  4. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.

Explanation

Correct Answer

C:

The distinctive observation is: An agent audit reports errors yet the team treats cloud policy creation as complete. The appropriate intervention is: Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. This addresses the specific danger: Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy. Validate closure with: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

Incorrect Answers

A:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. That mechanism alone cannot establish Microsoft entra password protection for ad ds for this question.

B:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. That may be useful independently, but the missing requirement here is Microsoft entra password protection for ad ds.

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 entra password protection for ad ds; the proposed alternative tests another control.

Question 100

An AZ-801 historical administration case reports: An agent audit reports errors yet the team treats cloud policy creation as complete. Which TWO choices provide the technical correction and a supporting acceptance test? (Select TWO.)

  1. A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.
  2. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  3. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.
  4. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  5. A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

Explanation

Correct Answers

C:

For An agent audit reports errors yet the team treats cloud policy creation as complete, this action is the relevant response: Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes. It reduces the risk that unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy.

E:

This is an independent validation for the condition An agent audit reports errors yet the team treats cloud policy creation as complete. The expected result is: A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.

Incorrect Answers

A:

Microsoft defender for identity sensors and alerts: Blind spots in domain controller telemetry can hide lateral movement or credential attacks despite a configured cloud portal. That mechanism alone cannot establish Microsoft entra password protection for ad ds for this question.

B:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. That may be useful independently, but the missing requirement here is Microsoft entra password protection for ad ds.

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 entra password protection for ad ds; the proposed alternative tests another control.