|
Home > Archive > 70-217 > March 2002 > Thu 70-217 Question of the Day
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Thu 70-217 Question of the Day
|
|
| wbafrank 2002-03-28, 5:22 am |
| And today's poser is ....
Q42. Your newly implemented Windows 2000 network has several domains. They are: Dom1.com, Dom2.com, and Dom3.com. You realized that you created some users in Dom1, and you meant to create them in Dom2.com. You have decided the best option is to move these users from one domain to another. During the move, you get a message that the move operation has failed. Which of the following are the most likely reasons the move failed? (Choose all that apply)
A. The user's samAccountName is already in the target domain.
B. The user's name does not follow the standard naming convention of the target domain.
C. The user's password is longer than the security of the target domain requires.
D. The user's password is shorter than the security of the target domain requires.
Good Luck .... see you tomorrow for the answer!! | |
| CyberDude 2002-03-28, 6:16 am |
| I will go for B as I think the SAM account is only used in a workgroup enviroment, and that the password does not conform would just mean that the user has to change it when he/she logs on.  | |
| robertmillar 2002-03-28, 10:29 am |
| D | |
| unreal 2002-03-28, 9:09 pm |
| "A" seems might be correct, but I think an error message, such as "the user account is already in the domain", would pop up instead of "something has failed". I think, that's MS style.
"C",for security, who would mind longer password, the longer the better, untill you get bored 
So my pick are:
B. The user's name does not follow the standard naming convention of the target domain.
D. The user's password is shorter than the security of the target domain requires. | |
| KScheler 2002-03-29, 8:00 am |
| I'll go with A.
Password length should not matter.
If all domains are W2k, then it should already be using the correct naming convention. | |
|
|
|
|
|