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 11

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.

Question 101

An enterprise Windows Server hybrid administration team finds: A domain administrator uses NTLM to reach a legacy application and is added to Protected Users. 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. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  2. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.
  3. Configure Read-Only Domain Controller password-replication allow and deny policies for branch users and validate cached credential scope.
  4. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.

Explanation

Correct Answer

A:

The distinctive observation is: A domain administrator uses NTLM to reach a legacy application and is added to Protected Users. The appropriate intervention is: Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. This addresses the specific danger: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. Validate closure with: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

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

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 Protected users group and authentication restrictions, 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 Protected users group and authentication restrictions; the proposed alternative tests another control.

Question 102

The recovery/security observation is: A domain administrator uses NTLM to reach a legacy application and is added to Protected Users. 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. 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. Credential-cache inspection shows only authorized branch identities cached and protected administrator accounts excluded.

Explanation

Correct Answer

C:

The separate check for the condition A domain administrator uses NTLM to reach a legacy application and is added to Protected Users is: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails. It validates the control to apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. 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 Protected users group and authentication restrictions 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 Protected users group and authentication restrictions.

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 Protected users group and authentication restrictions; the proposed alternative tests another control.

Question 103

An enterprise Windows Server hybrid administration team finds: An operator expects Protected Users to protect ordinary local machine accounts. 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. 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. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.

Explanation

Correct Answer

C:

The distinctive observation is: An operator expects Protected Users to protect ordinary local machine accounts. The appropriate intervention is: Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. This addresses the specific danger: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. Validate closure with: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

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

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

D:

Hybrid ad password policy and fine-grained rules: Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly. The observed issue still requires Protected users group and authentication restrictions; the proposed alternative tests another control.

Question 104

The legacy Windows Server administration finding is: An operator expects Protected Users to protect ordinary local machine accounts. What specific exposure does the condition create?

  1. Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly.
  2. A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced.
  3. A compromised branch RODC can expose improperly cached privileged secrets if replication policy is overly broad.
  4. Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials.

Explanation

Correct Answer

D:

The issue is: An operator expects Protected Users to protect ordinary local machine accounts. The material risk is that legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. The corrective control is to apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. Confirm through: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

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

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

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

Question 105

An enterprise Windows Server hybrid administration team finds: A privileged session still uses a weak legacy authentication path after a policy rollout. The team must preserve authorized operations and recoverability while meeting the documented service constraints. Which intervention should the team prioritize under these constraints?

  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. Collect NTLM audit events, map application dependencies, and phase targeted restrictions while moving supported workloads to stronger authentication.
  4. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.

Explanation

Correct Answer

D:

The distinctive observation is: A privileged session still uses a weak legacy authentication path after a policy rollout. The appropriate intervention is: Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. This addresses the specific danger: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. Validate closure with: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

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

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

Question 106

The recovery/security observation is: A privileged session still uses a weak legacy authentication path after a policy rollout. What evidence would best demonstrate that the remediation is effective?

  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. A restricted admin can authenticate on the approved host but fails from unapproved computers with auditable events.
  4. The identified legacy dependency migrates to an approved authentication method and targeted NTLM-deny tests pass.

Explanation

Correct Answer

B:

The separate check for the condition A privileged session still uses a weak legacy authentication path after a policy rollout is: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails. It validates the control to apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. 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 Protected users group and authentication restrictions for this question.

C:

Authentication policy silos and privileged isolation: A stolen privileged credential can be reused from arbitrary machines when authentication boundaries are not enforced. Here the decisive check is Protected users group and authentication restrictions, 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 Protected users group and authentication restrictions; the proposed alternative tests another control.

Question 107

An enterprise Windows Server hybrid administration team finds: A critical service identity is placed in Protected Users without compatibility review. 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 validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  2. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  3. 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

B:

The distinctive observation is: A critical service identity is placed in Protected Users without compatibility review. The appropriate intervention is: Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. This addresses the specific danger: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. Validate closure with: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

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

C:

Ntlm inventory audit and reduction: Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk. Here the decisive check is Protected users group and authentication restrictions, 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 Protected users group and authentication restrictions; the proposed alternative tests another control.

Question 108

The legacy Windows Server administration finding is: A critical service identity is placed in Protected Users without compatibility review. What specific exposure does the condition create?

  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. Disabling NTLM globally without inventory can break business applications, while perpetual permissive use permits relay and downgrade risk.
  4. Unhealthy agents or a mismatched audit/enforce rollout can leave banned passwords accepted despite an apparently configured tenant policy.

Explanation

Correct Answer

A:

The issue is: A critical service identity is placed in Protected Users without compatibility review. The material risk is that legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. The corrective control is to apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. Confirm through: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

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

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 Protected users group and authentication restrictions, 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 Protected users group and authentication restrictions; the proposed alternative tests another control.

Question 109

An enterprise Windows Server hybrid administration team finds: A test account loses access because its application lacks an acceptable Kerberos flow. 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 health-check password protection agents and proxy infrastructure for AD DS, including banned-password policies and operation modes.
  2. Deploy and validate Defender for Identity sensors on supported domain controllers, with healthy telemetry and triaged identity alerts.
  3. Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies.
  4. Apply correctly scoped domain and fine-grained password policies with lockout settings and predictable resultant-policy checks.

Explanation

Correct Answer

C:

The distinctive observation is: A test account loses access because its application lacks an acceptable Kerberos flow. The appropriate intervention is: Apply Protected Users membership only to suitable privileged accounts after validating supported Kerberos authentication paths and service dependencies. This addresses the specific danger: Legacy NTLM or credential caching dependencies can break sign-in, while leaving privileged accounts unprotected exposes reusable credentials. Validate closure with: An approved privileged test identity authenticates over the required protected path and disallowed legacy authentication fails.

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

D:

Hybrid ad password policy and fine-grained rules: Weak or conflicting password policies can permit guessing attacks or lock out legitimate privileged identities unexpectedly. The observed issue still requires Protected users group and authentication restrictions; the proposed alternative tests another control.

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.