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 12

Question 110

An AZ-801 historical administration case reports: A test account loses access because its application lacks an acceptable Kerberos flow. Which TWO options together describe an appropriate response and a distinct verification? (Select TWO.)

  1. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  2. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.
  3. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  4. An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.
  5. A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Explanation

Correct Answers

A:

For A test account loses access because its application lacks an acceptable Kerberos flow, this action is the relevant response: Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. It reduces the risk that legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials.

D:

This is an independent validation for the condition A test account loses access because its application lacks an acceptable Kerberos flow. The expected result is: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

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 Protected users group and authentication restrictions.

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 Protected users group and authentication restrictions, not that separate capability.

E:

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. Without demonstrating Protected users group and authentication restrictions, that option does not satisfy the requested outcome.

Question 111

An enterprise Windows Server hybrid administration team finds: A remote office RODC is configured to cache Domain Admins credentials. 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. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  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

D:

The distinctive observation is: A remote office RODC is configured to cache Domain Admins credentials. The appropriate intervention is: Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. This addresses the specific danger: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. Validate closure with: 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:

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

Question 112

The recovery/security observation is: A remote office RODC is configured to cache Domain Admins credentials. Which acceptance test should be required before closing the finding?

  1. Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.
  2. The identified legacy dependency migrates to an approved authentication method and targeted NTLM-deny tests pass.
  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

A:

The separate check for the condition A remote office RODC is configured to cache Domain Admins credentials is: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded. It validates the control to configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. It verifies an operational result rather than a configuration entry alone.

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

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 Rodc password replication and branch safety, 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 Rodc password replication and branch safety; the proposed alternative tests another control.

Question 113

An enterprise Windows Server hybrid administration team finds: Users in an offline branch cannot sign in because no permitted credentials were prepopulated. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which supported administrative change best addresses this condition?

  1. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  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. 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: Users in an offline branch cannot sign in because no permitted credentials were prepopulated. The appropriate intervention is: Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. This addresses the specific danger: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. Validate closure with: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

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

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 Rodc password replication and branch safety, 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 Rodc password replication and branch safety; the proposed alternative tests another control.

Question 114

The legacy Windows Server administration finding is: Users in an offline branch cannot sign in because no permitted credentials were prepopulated. Which failure mode most directly threatens this deployment?

  1. Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials.
  2. A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad.
  3. Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation.
  4. A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced.

Explanation

Correct Answer

B:

The issue is: Users in an offline branch cannot sign in because no permitted credentials were prepopulated. The material risk is that a compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. The corrective control is to configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. Confirm through: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

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

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 Rodc password replication and branch safety, 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 Rodc password replication and branch safety; the proposed alternative tests another control.

Question 115

An enterprise Windows Server hybrid administration team finds: An RODC receives the wrong password replication policy group after a domain change. 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 validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  2. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  3. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  4. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.

Explanation

Correct Answer

C:

The distinctive observation is: An RODC receives the wrong password replication policy group after a domain change. The appropriate intervention is: Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. This addresses the specific danger: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. Validate closure with: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

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

B:

Domain controller hardening and ad delegation: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. That may be useful independently, but the missing requirement here is Rodc password replication and branch safety.

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 Rodc password replication and branch safety; the proposed alternative tests another control.

Question 116

The recovery/security observation is: An RODC receives the wrong password replication policy group after a domain change. 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. An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.
  3. Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.
  4. A controlled security signal appears with correct identity and domain controller context and sensor health is confirmed.

Explanation

Correct Answer

C:

The separate check for the condition An RODC receives the wrong password replication policy group after a domain change is: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded. It validates the control to configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. It verifies an operational result rather than a configuration entry alone.

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.

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 Rodc password replication and branch safety; the proposed alternative tests another control.

Question 117

An enterprise Windows Server hybrid administration team finds: A security review never inspects which credentials were actually cached on the RODC. 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. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  2. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  3. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  4. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.

Explanation

Correct Answer

A:

The distinctive observation is: A security review never inspects which credentials were actually cached on the RODC. The appropriate intervention is: Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. This addresses the specific danger: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. Validate closure with: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

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

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 Rodc password replication and branch safety, 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 Rodc password replication and branch safety; the proposed alternative tests another control.

Question 118

The legacy Windows Server administration finding is: A security review never inspects which credentials were actually cached on the RODC. Which failure mode most directly threatens this deployment?

  1. A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad.
  2. A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced.
  3. Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation.
  4. Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk.

Explanation

Correct Answer

A:

The issue is: A security review never inspects which credentials were actually cached on the RODC. The material risk is that a compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. The corrective control is to configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. Confirm through: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

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

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 Rodc password replication and branch safety, 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 Rodc password replication and branch safety; the proposed alternative tests another control.

Question 119

An enterprise Windows Server hybrid administration team finds: A branch controller is stolen and responders cannot identify the potentially exposed accounts. 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. 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. 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

A:

The distinctive observation is: A branch controller is stolen and responders cannot identify the potentially exposed accounts. The appropriate intervention is: Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope. This addresses the specific danger: A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad. Validate closure with: Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

Incorrect Answers

B:

Domain controller hardening and ad delegation: Broad delegated rights and unrestricted domain controller logons can enable directory takeover or silent privilege escalation. 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.

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 Rodc password replication and branch safety; the proposed alternative tests another control.

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.