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 14

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.

Question 131

An enterprise Windows Server hybrid administration team finds: An administrator account is allowed to obtain service tickets from any workstation. 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. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  2. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  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

C:

The distinctive observation is: An administrator account is allowed to obtain service tickets from any workstation. The appropriate intervention is: Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. This addresses the specific danger: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. Validate closure with: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

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 Authentication policy silos and privileged isolation 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 Authentication policy silos and privileged isolation.

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 Authentication policy silos and privileged isolation; the proposed alternative tests another control.

Question 132

The recovery/security observation is: An administrator account is allowed to obtain service tickets from any workstation. Which acceptance test should be required before closing the finding?

  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 restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.
  4. An access test denies unapproved directory writes and DC sign-in while delegated routine tasks still succeed.

Explanation

Correct Answer

C:

The separate check for the condition An administrator account is allowed to obtain service tickets from any workstation is: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events. It validates the control to use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. 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 Authentication policy silos and privileged isolation 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 Authentication policy silos and privileged isolation.

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 Authentication policy silos and privileged isolation; the proposed alternative tests another control.

Question 133

An enterprise Windows Server hybrid administration team finds: A test authentication silo blocks the designated jump server because it was not added. 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. 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. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.

Explanation

Correct Answer

D:

The distinctive observation is: A test authentication silo blocks the designated jump server because it was not added. The appropriate intervention is: Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. This addresses the specific danger: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. Validate closure with: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

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 Authentication policy silos and privileged isolation 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 Authentication policy silos and privileged isolation.

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 Authentication policy silos and privileged isolation, not that separate capability.

Question 134

The legacy Windows Server administration finding is: A test authentication silo blocks the designated jump server because it was not added. Why is the observed configuration unacceptable?

  1. Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials.
  2. Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly.
  3. Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy.
  4. A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced.

Explanation

Correct Answer

D:

The issue is: A test authentication silo blocks the designated jump server because it was not added. The material risk is that a stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. The corrective control is to use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. Confirm through: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

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 Authentication policy silos and privileged isolation 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 Authentication policy silos and privileged isolation.

C:

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. Here the decisive check is Authentication policy silos and privileged isolation, not that separate capability.

Question 135

An enterprise Windows Server hybrid administration team finds: A privileged service account remains usable on unrelated application hosts. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which intervention should the team prioritize under these constraints?

  1. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  2. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  3. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  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: A privileged service account remains usable on unrelated application hosts. The appropriate intervention is: Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. This addresses the specific danger: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. Validate closure with: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

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 Authentication policy silos and privileged isolation 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 Authentication policy silos and privileged isolation.

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 Authentication policy silos and privileged isolation; the proposed alternative tests another control.

Question 136

The recovery/security observation is: A privileged service account remains usable on unrelated application hosts. What independent result establishes the change worked?

  1. The identified legacy dependency migrates to an approved authentication method and targeted NTLM-deny tests pass.
  2. Policy-result checks and representative user tests demonstrate the intended password and lockout behavior for each group.
  3. A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.
  4. An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

Explanation

Correct Answer

C:

The separate check for the condition A privileged service account remains usable on unrelated application hosts is: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events. It validates the control to use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. It verifies an operational result rather than a configuration entry alone.

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 Authentication policy silos and privileged isolation 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 Authentication policy silos and privileged isolation.

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 Authentication policy silos and privileged isolation; the proposed alternative tests another control.

Question 137

An enterprise Windows Server hybrid administration team finds: An engineer enables silo settings without testing the Kerberos authentication policies. 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. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  2. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  3. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  4. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.

Explanation

Correct Answer

C:

The distinctive observation is: An engineer enables silo settings without testing the Kerberos authentication policies. The appropriate intervention is: Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. This addresses the specific danger: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. Validate closure with: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

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 Authentication policy silos and privileged isolation 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 Authentication policy silos and privileged isolation.

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 Authentication policy silos and privileged isolation; the proposed alternative tests another control.

Question 138

The legacy Windows Server administration finding is: An engineer enables silo settings without testing the Kerberos authentication policies. Why is the observed configuration unacceptable?

  1. A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced.
  2. Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy.
  3. A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad.
  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: An engineer enables silo settings without testing the Kerberos authentication policies. The material risk is that a stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. The corrective control is to use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. Confirm through: A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.

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 Authentication policy silos and privileged isolation.

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 Authentication policy silos and privileged isolation, 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 Authentication policy silos and privileged isolation; the proposed alternative tests another control.

Question 139

An enterprise Windows Server hybrid administration team finds: A silo policy object exists but none of the intended identities are assigned. 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. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  2. Separate privileged administration, limit domain controller sign-in, and delegate only narrowly scoped directory modifications.
  3. Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths.
  4. Deploy and health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.

Explanation

Correct Answer

C:

The distinctive observation is: A silo policy object exists but none of the intended identities are assigned. The appropriate intervention is: Use supported authentication policies and silos to confine protected accounts to permitted hosts and services with tested Kerberos paths. This addresses the specific danger: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. Validate closure with: 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:

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 Authentication policy silos and privileged isolation.

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 Authentication policy silos and privileged isolation; the proposed alternative tests another control.

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.