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 13

Question 120

An AZ-801 historical administration case reports: A branch controller is stolen and responders cannot identify the potentially exposed accounts. Which TWO choices provide the technical correction and a supporting acceptance test? (Select TWO.)

  1. An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.
  2. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  3. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  4. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  5. Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

Explanation

Correct Answers

D:

For A branch controller is stolen and responders cannot identify the potentially exposed accounts, this action is the relevant response: Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. It reduces the risk that a compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad.

E:

This is an independent validation for the condition A branch controller is stolen and responders cannot identify the potentially exposed accounts. The expected result is: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

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 Rodc password replication and branch safety 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 Rodc password replication and branch safety.

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 Rodc password replication and branch safety, not that separate capability.

Question 121

An enterprise Windows Server hybrid administration team finds: A help desk needs password reset rights but receives permission to change domain-wide groups. 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. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  2. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  3. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  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 help desk needs password reset rights but receives permission to change domain-wide groups. The appropriate intervention is: Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. This addresses the specific danger: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. Validate closure with: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

Incorrect Answers

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 Domain controller hardening and ad delegation.

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 Domain controller hardening and ad delegation, 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 Domain controller hardening and ad delegation; the proposed alternative tests another control.

Question 122

The recovery/security observation is: A help desk needs password reset rights but receives permission to change domain-wide groups. Which acceptance test should be required before closing the finding?

  1. An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.
  2. A controlled password change against a disallowed term is rejected under effective enforced policy while agent health remains green.
  3. Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.
  4. The identified legacy dependency migrates to an approved authentication method and targeted NTLM-deny tests pass.

Explanation

Correct Answer

A:

The separate check for the condition A help desk needs password reset rights but receives permission to change domain-wide groups is: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed. It validates the control to separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. It verifies an operational result rather than a configuration entry alone.

Incorrect Answers

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 Domain controller hardening and ad delegation.

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 Domain controller hardening and ad delegation, not that separate capability.

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 Domain controller hardening and ad delegation; the proposed alternative tests another control.

Question 123

An enterprise Windows Server hybrid administration team finds: A standard server administrator can sign in interactively to domain controllers. 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 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. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  4. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.

Explanation

Correct Answer

C:

The distinctive observation is: A standard server administrator can sign in interactively to domain controllers. The appropriate intervention is: Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. This addresses the specific danger: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. Validate closure with: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

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 Domain controller hardening and ad delegation for this question.

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 Domain controller hardening and ad delegation.

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 Domain controller hardening and ad delegation; the proposed alternative tests another control.

Question 124

The legacy Windows Server administration finding is: A standard server administrator can sign in interactively to domain controllers. Which failure mode most directly threatens this deployment?

  1. Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly.
  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. Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation.

Explanation

Correct Answer

D:

The issue is: A standard server administrator can sign in interactively to domain controllers. The material risk is that broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. The corrective control is to separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. Confirm through: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

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 Domain controller hardening and ad delegation 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 Domain controller hardening and ad delegation.

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 Domain controller hardening and ad delegation, not that separate capability.

Question 125

An enterprise Windows Server hybrid administration team finds: An OU delegation grants control of protected privileged accounts by mistake. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which intervention should the team prioritize under these constraints?

  1. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  2. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  3. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  4. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.

Explanation

Correct Answer

B:

The distinctive observation is: An OU delegation grants control of protected privileged accounts by mistake. The appropriate intervention is: Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. This addresses the specific danger: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. Validate closure with: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

Incorrect Answers

A:

Rodc password replication and branch safety: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. That mechanism alone cannot establish Domain controller hardening and ad delegation 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 Domain controller hardening and ad delegation, not that separate capability.

D:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. The observed issue still requires Domain controller hardening and ad delegation; the proposed alternative tests another control.

Question 126

The recovery/security observation is: An OU delegation grants control of protected privileged accounts by mistake. Which acceptance test should be required before closing the finding?

  1. An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.
  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. Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

Explanation

Correct Answer

A:

The separate check for the condition An OU delegation grants control of protected privileged accounts by mistake is: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed. It validates the control to separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. It verifies an operational result rather than a configuration entry alone.

Incorrect Answers

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 Domain controller hardening and ad delegation.

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 Domain controller hardening and ad delegation, 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 Domain controller hardening and ad delegation; the proposed alternative tests another control.

Question 127

An enterprise Windows Server hybrid administration team finds: A service identity is made Domain Admin merely to update one computer attribute. 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. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  2. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  3. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  4. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.

Explanation

Correct Answer

D:

The distinctive observation is: A service identity is made Domain Admin merely to update one computer attribute. The appropriate intervention is: Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. This addresses the specific danger: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. Validate closure with: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

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 Domain controller hardening and ad delegation 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 Domain controller hardening and ad delegation.

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 Domain controller hardening and ad delegation, not that separate capability.

Question 128

The legacy Windows Server administration finding is: A service identity is made Domain Admin merely to update one computer attribute. Why is the observed configuration unacceptable?

  1. Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk.
  2. Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation.
  3. Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly.
  4. A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad.

Explanation

Correct Answer

B:

The issue is: A service identity is made Domain Admin merely to update one computer attribute. The material risk is that broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. The corrective control is to separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. Confirm through: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

Incorrect Answers

A:

Ntlm inventory audit and reduction: Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk. That mechanism alone cannot establish Domain controller hardening and ad delegation for this question.

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 Domain controller hardening and ad delegation, 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 Domain controller hardening and ad delegation; the proposed alternative tests another control.

Question 129

An enterprise Windows Server hybrid administration team finds: A domain controller permits remote administration from untrusted workstation networks. 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. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  2. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  3. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  4. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.

Explanation

Correct Answer

B:

The distinctive observation is: A domain controller permits remote administration from untrusted workstation networks. The appropriate intervention is: Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. This addresses the specific danger: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. Validate closure with: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

Incorrect Answers

A:

Authentication policy silos and privileged isolation: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. That mechanism alone cannot establish Domain controller hardening and ad delegation for this question.

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 Domain controller hardening and ad delegation, not that separate capability.

D:

Protected users group and authentication restrictions: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. The observed issue still requires Domain controller hardening and ad delegation; the proposed alternative tests another control.

Question 130

An AZ-801 historical administration case reports: A domain controller permits remote administration from untrusted workstation networks. 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. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  3. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  4. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  5. An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

Explanation

Correct Answers

B:

For A domain controller permits remote administration from untrusted workstation networks, this action is the relevant response: Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications. It reduces the risk that broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation.

E:

This is an independent validation for the condition A domain controller permits remote administration from untrusted workstation networks. The expected result is: An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

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 Domain controller hardening and ad delegation 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 Domain controller hardening and ad delegation, 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 Domain controller hardening and ad delegation; the proposed alternative tests another control.