100% Latest & Updated Microsoft AZ-801 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 60
An RODC replication test fails only for one user whose group belongs to the RODC's denied password replication list. What change should be prioritized to restore the intended behavior?
- Verify that the user's credential was explicitly allowed and prepopulated before the outage.
- Adjust the allowed authentication design without weakening the RODC's privileged-account cache deny policy.
- Correct the RODC password replication policy and invalidate credentials exposed to the branch.
- Review the RODC revealed/cached account list and reset credentials for affected principals.
Explanation
Correct Answer
B:A denied policy explicitly overrides an allowed replication path for sensitive accounts. A suitable corrective action is to adjust the allowed authentication design without weakening the RODC's privileged-account cache deny policy.
Incorrect Answers
A:An allowed password replication policy does not guarantee the secret was already cached locally. However, a denied policy explicitly overrides an allowed replication path for sensitive accounts.
C:Deny-list and replication history determine which secrets may be present on that controller. In this situation, a denied policy explicitly overrides an allowed replication path for sensitive accounts.
D:A branch RODC compromise does not automatically imply every domain account secret was cached. However, a denied policy explicitly overrides an allowed replication path for sensitive accounts.
Question 61
A tier-zero service account must authenticate only from designated hardened workstations. What change should be prioritized to restore the intended behavior?
- Move the tested authentication policy from audit to enforcement mode and verify denied sessions.
- Add the intended principals to the silo and validate its enforcement mode.
- Configure an authentication policy silo with eligible account and device assignments.
- Apply tiered administrative logon restrictions using user-right assignments and protected access workstations.
Explanation
Correct Answer
C:Authentication silos tie supported accounts to allowed authentication contexts instead of relying on desktop location alone. The targeted remedy is to configure an authentication policy silo with eligible account and device assignments.
Incorrect Answers
A:Audit configuration observes violations; enforcement is required to reject authentication outside approved boundaries. Here, authentication silos tie supported accounts to allowed authentication contexts instead of relying on desktop location alone.
B:A silo definition has no effect until the correct accounts and allowed hosts are associated. In this situation, authentication silos tie supported accounts to allowed authentication contexts instead of relying on desktop location alone.
D:Limiting where privileged identities can sign in reduces attack paths through compromised end-user devices. Here, authentication silos tie supported accounts to allowed authentication contexts instead of relying on desktop location alone.
Question 62
An authentication policy silo is created but no users or service accounts are assigned, so targeted privileged logins are unaffected. Which administrative change most directly resolves the documented failure?
- Move the tested authentication policy from audit to enforcement mode and verify denied sessions.
- Configure an authentication policy silo with eligible account and device assignments.
- Review AdminSDHolder/SDProp protection and avoid using generic OU delegation for protected principals.
- Add the intended principals to the silo and validate its enforcement mode.
Explanation
Correct Answer
D:Add the intended principals to the silo and validate its enforcement mode. This addresses the condition because a silo definition has no effect until the correct accounts and allowed hosts are associated.
Incorrect Answers
A:Audit configuration observes violations; enforcement is required to reject authentication outside approved boundaries. In this situation, a silo definition has no effect until the correct accounts and allowed hosts are associated.
B:Authentication silos tie supported accounts to allowed authentication contexts instead of relying on desktop location alone. However, a silo definition has no effect until the correct accounts and allowed hosts are associated.
C:Protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance. Here, a silo definition has no effect until the correct accounts and allowed hosts are associated.
Question 63
A new helpdesk group needs password reset rights in one OU but not authority to edit group memberships or protected admin accounts. What is the best targeted remediation for the behavior described?
- Delegate narrowly scoped Reset Password permissions on the designated OU objects.
- Review AdminSDHolder/SDProp protection and avoid using generic OU delegation for protected principals.
- Replace the broad ACE with the minimum reset/unlock attributes and correct scope.
- Add the intended principals to the silo and validate its enforcement mode.
Explanation
Correct Answer
A:AD DS delegation is object- and action-specific; broad domain admin membership grants unrelated powers. For that reason, delegate narrowly scoped Reset Password permissions on the designated OU objects.
Incorrect Answers
B:Protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance. Here, AD DS delegation is object- and action-specific; broad domain admin membership grants unrelated powers.
C:Least-privilege directory ACLs prevent accidental edits to unrelated user properties. In this situation, AD DS delegation is object- and action-specific; broad domain admin membership grants unrelated powers.
D:A silo definition has no effect until the correct accounts and allowed hosts are associated. However, AD DS delegation is object- and action-specific; broad domain admin membership grants unrelated powers.
Question 64
A user with inherited OU write rights cannot modify a protected domain admin account and assumes replication is broken. Which administrative change most directly resolves the documented failure?
- Replace excessive privilege with a supported service-specific backup delegation and restrict DC logon rights.
- Review AdminSDHolder/SDProp protection and avoid using generic OU delegation for protected principals.
- Delegate narrowly scoped Reset Password permissions on the designated OU objects.
- Add the intended principals to the silo and validate its enforcement mode.
Explanation
Correct Answer
B:Review AdminSDHolder/SDProp protection and avoid using generic OU delegation for protected principals. The underlying technical reason is that protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance.
Incorrect Answers
A:Logon denial and directory privilege assignment solve different exposure paths; both require least-privilege design. Here, protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance.
C:AD DS delegation is object- and action-specific; broad domain admin membership grants unrelated powers. However, protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance.
D:A silo definition has no effect until the correct accounts and allowed hosts are associated. Here, protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance.
Question 65
A service account is mistakenly given unconstrained Kerberos delegation across application hosts. What is the best targeted remediation for the behavior described?
- Add service principal names for the application account but leave unconstrained delegation enabled on the same hosts.
- Replace excessive privilege with a supported service-specific backup delegation and restrict DC logon rights.
- Replace unconstrained delegation with reviewed constrained or resource-based constrained delegation as supported.
- Review AdminSDHolder/SDProp protection and avoid using generic OU delegation for protected principals.
Explanation
Correct Answer
C:Restricting service ticket forwarding limits the scope in which compromised service credentials can impersonate users. A suitable corrective action is to replace unconstrained delegation with reviewed constrained or resource-based constrained delegation as supported.
Incorrect Answers
A:SPNs let Kerberos identify the intended service; they do not restrict which downstream services the application account can impersonate on behalf of users. Unconstrained delegation remains an avoidable privilege exposure until the delegation scope is reduced.
B:Logon denial and directory privilege assignment solve different exposure paths; both require least-privilege design. However, restricting service ticket forwarding limits the scope in which compromised service credentials can impersonate users.
D:Protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance. In this situation, restricting service ticket forwarding limits the scope in which compromised service credentials can impersonate users.
Question 66
A domain administrator is allowed interactive logon to ordinary workstations, risking credential exposure on lower-trust hosts. Which response addresses the identified root cause without weakening other controls?
- Replace excessive privilege with a supported service-specific backup delegation and restrict DC logon rights.
- Configure an authentication policy silo with eligible account and device assignments.
- Review AdminSDHolder/SDProp protection and avoid using generic OU delegation for protected principals.
- Apply tiered administrative logon restrictions using user-right assignments and protected access workstations.
Explanation
Correct Answer
D:Limiting where privileged identities can sign in reduces attack paths through compromised end-user devices. The targeted remedy is to apply tiered administrative logon restrictions using user-right assignments and protected access workstations.
Incorrect Answers
A:Logon denial and directory privilege assignment solve different exposure paths; both require least-privilege design. However, limiting where privileged identities can sign in reduces attack paths through compromised end-user devices.
B:Authentication silos tie supported accounts to allowed authentication contexts instead of relying on desktop location alone. Here, limiting where privileged identities can sign in reduces attack paths through compromised end-user devices.
C:Protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance. In this situation, limiting where privileged identities can sign in reduces attack paths through compromised end-user devices.
Question 67
A custom AD DS delegation wizard grants the helpdesk 'Full Control' over every user object for simple password unlock duties. What would be the most defensible next action based on the observed symptoms?
- Replace the broad ACE with the minimum reset/unlock attributes and correct scope.
- Grant Reset Password permission on the intended OU but leave the original Full Control access-control entry in place.
- Replace unconstrained delegation with reviewed constrained or resource-based constrained delegation as supported.
- Correct and validate the service principal name and approved constrained delegation configuration.
Explanation
Correct Answer
A:Replace the broad ACE with the minimum reset/unlock attributes and correct scope. This addresses the condition because least-privilege directory ACLs prevent accidental edits to unrelated user properties.
Incorrect Answers
B:A narrow new delegation does not remove the existing Full Control ACE. Helpdesk staff would still have excessive rights over every user object until the broad entry is revoked or narrowed.
C:Restricting service ticket forwarding limits the scope in which compromised service credentials can impersonate users. However, least-privilege directory ACLs prevent accidental edits to unrelated user properties.
D:Kerberos ticket forwarding requires a resolvable service identity before delegation decisions can succeed. Here, least-privilege directory ACLs prevent accidental edits to unrelated user properties.
Question 68
An authentication silo audit reports attempts from an unauthorized server but they are not being blocked. Which supported action should be taken for this reported condition?
- Add the intended principals to the silo and validate its enforcement mode.
- Move the tested authentication policy from audit to enforcement mode and verify denied sessions.
- Configure an authentication policy silo with eligible account and device assignments.
- Delegate narrowly scoped Reset Password permissions on the designated OU objects.
Explanation
Correct Answer
B:Audit configuration observes violations; enforcement is required to reject authentication outside approved boundaries. For that reason, move the tested authentication policy from audit to enforcement mode and verify denied sessions.
Incorrect Answers
A:A silo definition has no effect until the correct accounts and allowed hosts are associated. In this situation, audit configuration observes violations; enforcement is required to reject authentication outside approved boundaries.
C:Authentication silos tie supported accounts to allowed authentication contexts instead of relying on desktop location alone. Here, audit configuration observes violations; enforcement is required to reject authentication outside approved boundaries.
D:AD DS delegation is object- and action-specific; broad domain admin membership grants unrelated powers. In this situation, audit configuration observes violations; enforcement is required to reject authentication outside approved boundaries.
Question 69
A credential-controlled service must access an SQL service on behalf of users, but Kerberos delegation fails because the target SPN is missing. What change should be prioritized to restore the intended behavior?
- Limit the front-end service's Kerberos delegation scope to SQL while leaving the target SQL service principal name unregistered.
- Review AdminSDHolder/SDProp protection and avoid using generic OU delegation for protected principals.
- Correct and validate the service principal name and approved constrained delegation configuration.
- Add the intended principals to the silo and validate its enforcement mode.
Explanation
Correct Answer
C:Correct and validate the service principal name and approved constrained delegation configuration. The underlying technical reason is that kerberos ticket forwarding requires a resolvable service identity before delegation decisions can succeed.
Incorrect Answers
A:Restricting delegation narrows the trusted downstream services, but the KDC still needs the target SQL service SPN to identify its account. This case reports an absent SPN, so delegation scope changes alone cannot complete Kerberos ticket acquisition.
B:Protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance. Here, Kerberos ticket forwarding requires a resolvable service identity before delegation decisions can succeed.
D:A silo definition has no effect until the correct accounts and allowed hosts are associated. However, Kerberos ticket forwarding requires a resolvable service identity before delegation decisions can succeed.
Question 70
A GPO denies interactive domain-controller logon to ordinary users but a service account still has Domain Admin rights for backups. Which supported action should be taken for this reported condition?
- Replace unconstrained delegation with reviewed constrained or resource-based constrained delegation as supported.
- Apply tiered administrative logon restrictions using user-right assignments and protected access workstations.
- Review AdminSDHolder/SDProp protection and avoid using generic OU delegation for protected principals.
- Replace excessive privilege with a supported service-specific backup delegation and restrict DC logon rights.
Explanation
Correct Answer
D:Logon denial and directory privilege assignment solve different exposure paths; both require least-privilege design. A suitable corrective action is to replace excessive privilege with a supported service-specific backup delegation and restrict DC logon rights.
Incorrect Answers
A:Restricting service ticket forwarding limits the scope in which compromised service credentials can impersonate users. Here, logon denial and directory privilege assignment solve different exposure paths; both require least-privilege design.
B:Limiting where privileged identities can sign in reduces attack paths through compromised end-user devices. In this situation, logon denial and directory privilege assignment solve different exposure paths; both require least-privilege design.
C:Protected privileged object ACLs are periodically controlled separately from ordinary OU inheritance. However, logon denial and directory privilege assignment solve different exposure paths; both require least-privilege design.
Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests