Your network contains an Active Directory domain named contoso.com. The functional level of the
forest is Windows Server 2008 R2.
Computer accounts for the marketing department are in an organizational unit (OU) named
Departments\Marketing\Computers. User accounts for the marketing department are in an OU
named Departments\Marketing\Users.
All of the marketing user accounts are members of a global security group named MarketingUsers.
All of the marketing computer accounts are members of a global security group named
MarketingComputers.
In the domain, you have Group Policy objects (GPOs) as shown in the exhibit. (Click the Exhibit
button.)
You create two Password Settings objects named PSO1 and PSO2. PSO1 is applied to
MarketingUsers. PSO2 is applied to MarketingComputers.
The minimum password length is defined for each policy as shown in the following table.
You need to identify the minimum password length required for each marketing user.
What should you identify?
A.
5
B.
6
C.
7
D.
10
E.
12
Why is a namespace wizard being shown, when asking about PSO’s ?
0
0
Appears to just be the wrong image posted.
0
0
Functional level is 2008, so PSO don’t apply, so D is not correct
Am i wrong?
0
0
yes, i’m wrong… nevermind 😛
0
0
hhhhhh nice one
0
0
Section:�Configure and Manage Group Policy
Password Setting Object (PSO) is another name for Fine Grain Password Policies. These PSOs allowed us to set up a different password policy based on security group membership. For example, an employee who is working on a multi billion dollar drug might need to have more characters in their password and more frequent password changes than someone who does not handle critical company data. PSOs allow us to do that.
Precedence:
In the case of a conflict in which a user is a member of more than one group with different PSOs assigned to each group, the one with the Precedence number that is lower will be the effective PSO
Applying fine-grained password policies: Fine-grained password policies apply only to user objects (or inetOrgPerson objects if they are used instead of user objects) and global security groups. They cannot be applied to Computer objects.
PSOs cannot be applied to organizational units (OUs) directly.
The PSO with the lowest priority takes precedence
If two PSOs have the same priority, the PSO with the smallest globally unique identifier (GUID) takes precedence.
http://technet.microsoft.com/en-us/library/cc770842%28v=ws.10%29.aspx
1
0
D – 10
0
0