100% Latest & Updated Microsoft AZ-801 Practice Test Questions, Exam Dumps & Verified Answers!
30 Days Free Updates, Instant Download!
Question 40
The owner wants to freeze baseline drift detection to a single weekly screenshot of policy settings. Which configuration or recovery action best matches this evidence?
- Run one effective-configuration comparison immediately after deployment, archive it, and stop further drift measurements.
- Use repeatable policy/configuration state assessment and drift comparison against a signed or versioned baseline.
- Select a security baseline supported for each server version and test the intended configuration before deployment.
- Inspect effective policy precedence and reconcile the conflicting baseline settings in the authoritative management source.
Explanation
Correct Answer
B:Effective baseline posture can change between manual screenshots and requires machine-readable state checks. A suitable corrective action is to use repeatable policy/configuration state assessment and drift comparison against a signed or versioned baseline.
Incorrect Answers
A:The snapshot can show that a server matched the baseline on one date, but it will miss later policy changes or local configuration drift. The requirement is repeatable detection, not a permanent conclusion based on one comparison.
C:Version-specific settings and feature availability can make an otherwise reasonable baseline incompatible. However, effective baseline posture can change between manual screenshots and requires machine-readable state checks.
D:A local security configuration can be overwritten by Group Policy; effective resultant policy matters. Here, effective baseline posture can change between manual screenshots and requires machine-readable state checks.
Question 41
A hybrid identity tenant needs to block commonly breached passwords when users change passwords on AD DS domain controllers. Which supported action should be taken for this reported condition?
- Confirm the Password Protection proxy service responds but leave the forest unregistered and DC agents absent from the domain controllers.
- Install the on-premises Password Protection agents but leave the policy in Audit mode indefinitely while claiming weak passwords are blocked.
- Deploy Microsoft Entra Password Protection proxy and DC agents with registered forest and audited policy.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
Explanation
Correct Answer
C:On-premises password-change enforcement requires the domain controller agents, not only a cloud tenant toggle. The targeted remedy is to deploy Microsoft Entra Password Protection proxy and DC agents with registered forest and audited policy.
Incorrect Answers
A:A working proxy by itself doesn't evaluate on-premises AD password-change attempts. Registered forest and configured DC agents are required to apply the banned-password checks where AD DS processes them.
B:Audit mode records password-policy violations without rejecting those password changes. The requirement is enforcement against weak passwords at the domain controllers after safe testing.
D:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. In this situation, on-premises password-change enforcement requires the domain controller agents, not only a cloud tenant toggle.
Question 42
The team sees custom banned words applied to cloud users but AD DS password changes continue accepting them at branch DCs. What change should be prioritized to restore the intended behavior?
- Edit only the cloud banned-password list, without checking whether the proxy and DC agents apply the policy to branch domain controllers.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
- Register one replacement Password Protection proxy but do not check whether the affected branch domain controllers have working DC agents.
- Verify the Password Protection DC agents, proxy connectivity and registration on the affected AD forest.
Explanation
Correct Answer
D:Verify the Password Protection DC agents, proxy connectivity and registration on the affected AD forest. This addresses the condition because a cloud-only banned-password policy cannot enforce on-premises changes without the installed hybrid components.
Incorrect Answers
A:A tenant-side list alone doesn't establish that AD DS domain controllers process and enforce its rules. The scenario concerns password changes accepted on those DCs, so agent deployment and registration are the key evidence.
B:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. Here, a cloud-only banned-password policy cannot enforce on-premises changes without the installed hybrid components.
C:A proxy alone doesn't perform banned-password checks during on-premises password changes. Each relevant DC needs a functioning DC agent and a valid path to the registered proxy and policy; replacing only the proxy leaves that enforcement gap untested.
Question 43
Domain accounts must lock after repeated wrong passwords but investigators configured only password minimum length. What change should be prioritized to restore the intended behavior?
- Configure an AD DS account lockout policy appropriate to the risk and user population.
- Set AD DS password history requirements with an appropriate minimum age and change control.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
- Deploy Microsoft Entra Password Protection proxy and DC agents with registered forest and audited policy.
Explanation
Correct Answer
A:Password length concerns password construction; lockout counters and duration govern repeated failed authentication. For that reason, configure an AD DS account lockout policy appropriate to the risk and user population.
Incorrect Answers
B:Password history rejects recent reused values; minimum age alone does not maintain a remembered password list. In this situation, password length concerns password construction; lockout counters and duration govern repeated failed authentication.
C:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. However, password length concerns password construction; lockout counters and duration govern repeated failed authentication.
D:On-premises password-change enforcement requires the domain controller agents, not only a cloud tenant toggle. Here, password length concerns password construction; lockout counters and duration govern repeated failed authentication.
Question 44
A fine-grained password policy should apply to privileged accounts but is attached to an organizational unit rather than eligible users or global security groups. Which configuration or recovery action best matches this evidence?
- Review and correct the resultant password settings object and precedence value.
- Assign the password settings object to the intended eligible users or global security group.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
- Set AD DS password history requirements with an appropriate minimum age and change control.
Explanation
Correct Answer
B:Assign the password settings object to the intended eligible users or global security group. The underlying technical reason is that fine-grained password policies target users and global security groups, not arbitrary OU link inheritance.
Incorrect Answers
A:The effective fine-grained policy is selected by precedence and direct/group applicability, not the author's display name. In this situation, fine-grained password policies target users and global security groups, not arbitrary OU link inheritance.
C:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. Here, fine-grained password policies target users and global security groups, not arbitrary OU link inheritance.
D:Password history rejects recent reused values; minimum age alone does not maintain a remembered password list. In this situation, fine-grained password policies target users and global security groups, not arbitrary OU link inheritance.
Question 45
An engineer sets a lower-precedence password settings object expecting it to override a higher-priority privileged-account policy. Which Windows Server or Azure operation best addresses the reported fault?
- Assign the password settings object to the intended eligible users or global security group.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
- Review and correct the resultant password settings object and precedence value.
- Investigate repeated wrong-secret authentication and service dependencies instead of changing maximum password age.
Explanation
Correct Answer
C:The effective fine-grained policy is selected by precedence and direct/group applicability, not the author's display name. A suitable corrective action is to review and correct the resultant password settings object and precedence value.
Incorrect Answers
A:Fine-grained password policies target users and global security groups, not arbitrary OU link inheritance. However, the effective fine-grained policy is selected by precedence and direct/group applicability, not the author's display name.
B:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. Here, the effective fine-grained policy is selected by precedence and direct/group applicability, not the author's display name.
D:Lockout is driven by bad authentication attempts; password expiry controls when a valid secret must change. However, the effective fine-grained policy is selected by precedence and direct/group applicability, not the author's display name.
Question 46
A user repeatedly chooses the same password and the team has enabled only minimum password age. Which administrative change most directly resolves the documented failure?
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
- Configure an AD DS account lockout policy appropriate to the risk and user population.
- Investigate repeated wrong-secret authentication and service dependencies instead of changing maximum password age.
- Set AD DS password history requirements with an appropriate minimum age and change control.
Explanation
Correct Answer
D:Password history rejects recent reused values; minimum age alone does not maintain a remembered password list. The targeted remedy is to set AD DS password history requirements with an appropriate minimum age and change control.
Incorrect Answers
A:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. Here, password history rejects recent reused values; minimum age alone does not maintain a remembered password list.
B:Password length concerns password construction; lockout counters and duration govern repeated failed authentication. In this situation, password history rejects recent reused values; minimum age alone does not maintain a remembered password list.
C:Lockout is driven by bad authentication attempts; password expiry controls when a valid secret must change. However, password history rejects recent reused values; minimum age alone does not maintain a remembered password list.
Question 47
After enabling Entra Password Protection the proxy's registration expires, but admins keep changing cloud password policies. Which implementation step directly corrects the underlying problem?
- Repair and validate the proxy/forest registration and network connectivity to the service.
- Restart the Password Protection DC agents and clear their local logs while leaving the proxy's expired registration unchanged.
- Deploy Microsoft Entra Password Protection proxy and DC agents with registered forest and audited policy.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
Explanation
Correct Answer
A:Repair and validate the proxy/forest registration and network connectivity to the service. This addresses the condition because hybrid enforcement needs the local agent-to-proxy-to-service trust chain to function.
Incorrect Answers
B:Restarting a DC-side service does not renew an expired proxy/forest registration with the tenant. The reported registration failure must be corrected and connectivity validated before DCs can reliably obtain the on-premises banned-password policy.
C:On-premises password-change enforcement requires the domain controller agents, not only a cloud tenant toggle. Here, hybrid enforcement needs the local agent-to-proxy-to-service trust chain to function.
D:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. In this situation, hybrid enforcement needs the local agent-to-proxy-to-service trust chain to function.
Question 48
A business wants password policies at the tenant boundary and on-premises AD DS enforced identically but has not reconciled supported custom banned-password behavior. What is the best targeted remediation for the behavior described?
- Begin with Microsoft Entra Password Protection audit mode and inspect DC agent events.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
- Verify the Password Protection DC agents, proxy connectivity and registration on the affected AD forest.
- Deploy Microsoft Entra Password Protection proxy and DC agents with registered forest and audited policy.
Explanation
Correct Answer
B:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. For that reason, test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
Incorrect Answers
A:Audit mode records candidate rejections for evaluation, whereas enforce mode blocks weak password changes. However, hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication.
C:A cloud-only banned-password policy cannot enforce on-premises changes without the installed hybrid components. In this situation, hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication.
D:On-premises password-change enforcement requires the domain controller agents, not only a cloud tenant toggle. However, hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication.
Question 49
A pilot must collect attempted weak-password failures without rejecting real users during initial rollout. Which response addresses the identified root cause without weakening other controls?
- Immediately switch the full on-premises password policy to Enforced mode instead of first collecting pilot audit results.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
- Begin with Microsoft Entra Password Protection audit mode and inspect DC agent events.
- Verify the Password Protection DC agents, proxy connectivity and registration on the affected AD forest.
Explanation
Correct Answer
C:Begin with Microsoft Entra Password Protection audit mode and inspect DC agent events. The underlying technical reason is that audit mode records candidate rejections for evaluation, whereas enforce mode blocks weak password changes.
Incorrect Answers
A:The stated pilot needs to observe attempted weak passwords without denying users. Enforced mode rejects them and changes pilot behavior before the team evaluates impact.
B:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. In this situation, audit mode records candidate rejections for evaluation, whereas enforce mode blocks weak password changes.
D:A cloud-only banned-password policy cannot enforce on-premises changes without the installed hybrid components. Here, audit mode records candidate rejections for evaluation, whereas enforce mode blocks weak password changes.
Question 50
A shared service account triggers password lockout incidents even though password expiry is disabled. Which supported action should be taken for this reported condition?
- Set AD DS password history requirements with an appropriate minimum age and change control.
- Test cloud and AD DS password changes under the intended Entra Password Protection mode before enforcing a claim of parity.
- Review and correct the resultant password settings object and precedence value.
- Investigate repeated wrong-secret authentication and service dependencies instead of changing maximum password age.
Explanation
Correct Answer
D:Lockout is driven by bad authentication attempts; password expiry controls when a valid secret must change. A suitable corrective action is to investigate repeated wrong-secret authentication and service dependencies instead of changing maximum password age.
Incorrect Answers
A:Password history rejects recent reused values; minimum age alone does not maintain a remembered password list. In this situation, lockout is driven by bad authentication attempts; password expiry controls when a valid secret must change.
B:Hybrid password policy outcomes depend on agent state, custom lists, audit/enforce mode and replication. However, lockout is driven by bad authentication attempts; password expiry controls when a valid secret must change.
C:The effective fine-grained policy is selected by precedence and direct/group applicability, not the author's display name. Here, lockout is driven by bad authentication attempts; password expiry controls when a valid secret must change.
Configuring Windows Server Hybrid Advanced Services (AZ-801) Practice Tests