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.)
Explanation
Correct Answers
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.
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
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.
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.
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.