PrepAway - Latest Free Exam Questions & Answers

You need to ensure that User1 can log on to DC10 if the network link between the Main site and the Branch site

Your network contains an Active Directory domain named contoso.com. All domain
controllers run Windows Server 2012 R2. The domain contains two domain controllers.
The domain controllers are configured as shown in the following table.

You configure a user named User1 as a delegated administrator of DC10.
You need to ensure that User1 can log on to DC10 if the network link between the Main site
and the Branch site fails.
What should you do?

PrepAway - Latest Free Exam Questions & Answers

A.
Add User1 to the Domain Admins group.

B.
On DC10, modify the User Rights Assignment in Local Policies.

C.
Run repadmin and specify the /prp parameter.

D.
On DC10, run ntdsutil and configure the settings in the Roles context.

Explanation:
repadmin /prp will allow the password caching of the local administrator to the RODC.

16 Comments on “You need to ensure that User1 can log on to DC10 if the network link between the Main site and the Branch site

  1. Lostineurope says:

    Hard One.

    repadmin /prp add allow

    Specifies the host name of the RODC. You can specify the single-label host name or the fully qualified domain name (FQDN). In addition, you can use an asterisk (*) as a wildcard character to specify multiple RODCs in one domain.

    Specifies the name of the Security Principal that you want to Add to the Allowed List.

    Adds the specified security principal to the msDS-RevealOnDemandGroup attribute that is associated with the RODC. (This attribute is also known as the Allowed List.)




    0



    0
  2. Lostineurope says:

    Last Post didn’t come over correct. Missing the Parameters. This one makes more sense.

    Repadmin /prp Add RODCName Allow PRINCIPALName

    RODCName
    Specifies the host name of the RODC. You can specify the single-label host name or the fully qualified domain name (FQDN). In addition, you can use an asterisk (*) as a wildcard character to specify multiple RODCs in one domain.

    PRINCIPALName
    Specifies the name of the security principal that you want to add to the Allowed List.

    ADD
    Adds the specified Security Principal to the msDS-RevealOnDemandGroup Attribute that is associated with the RODC. (This attribute is also known as the Allowed List.)




    0



    0
  3. TTom says:

    From my point this is a tricky question.

    They are saying about : You configure a user named User1 as a delegated administrator of DC10.

    So why do you think: repadmin /prp ?

    Even MS said: You run the repadmin /prp command against a writable domain controller that runs Windows Server 2008 rather than an RODC.

    https://technet.microsoft.com/en-us/library/cc835090.aspx

    From windows 2008 we can delegate local administrator to RODC by:

    ntdsutil and dsmgmt

    So?
    https://technet.microsoft.com/pl-pl/library/cc755310(v=ws.10).aspx

    Using ntdsutil or dsmgmt to specify the delegated RODC administrator account is not recommended because the information is stored only locally on the RODC. Therefore, when you use ntdsutil local roles to delegate an administrator for the RODC […]

    also here we have eplanation:

    You can also configure role separation locally on the RODC after installation by using the Ntdsutil or Dsmgmt command line tools’ local roles option.

    http://windowsitpro.com/security/q-how-can-i-delegate-administrator-role-given-rodc-single-administrator-account

    For me this a MS trick to lead us to bad track.

    My answer:

    D.
    On DC10, run ntdsutil and configure the settings in the Roles context.
    Roles context = local roles option.

    What do you think ?




    0



    0
  4. Knight13 says:

    Answer is B.

    You give a user account the “log on locally” rights.

    This allows someone to log on to the sever to help with troubleshooting. Doesn’t need to be a domain account.




    0



    0
  5. Joe says:

    After further thought, this is my opinion…

    it can’t be B because although you can give them logon locally rights, if the RODC cannot communicate with a writeable DC then the account cannot be authenticated without the password being cached.
    But then again, does the user being a designated administrator give them the logon locally permissions or will we also need to do that? If so it would be both B and C




    0



    0
  6. Knight13 says:

    I meant give a “local user” log on local rights not a domain account. I got this from CBT Nuggets Video. That way if it is cut off from the network you still have a local account that can log on to the server to sort. Install new network card drivers etc.

    Because the account is a local one, if the RODC was stolen it would not contain any domain passwords, so this method is the most secure.




    0



    0
  7. MadMilkman says:

    There is same question, but with diffirent answers:

    A. Add User1 to the Domain Admins group.
    B. On DC10, run ntdsutil and configure the settings in the Roles context.
    C. Run repadmin and specify the /prp parameter.
    D. On DC1, modify the User Rights Assignment in Default Domain Controllers Group Policy object (GPO).

    Answer: D

    Explanation:
    Modify the following policy: Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment\Allow log on locally
    Note:
    * User Rights Assignment policies determines which users or groups have logon rights or
    privileges on the computer.
    * Delegated administrator accounts gain local administrative permissions to the RODC. These users can operate with privileges equivalent to the local computer’s Administrators group. They are not members of the Domain Admins or the domain built-in Administrators groups. This option is useful for delegating branch office administration without giving out domain administrative permissions. Configuring delegation of administration is not required.

    So It could be answere B to this question.




    0



    0
  8. Rick says:

    The answer is C because if you take the time to read this article, Microsoft tells you to NOT STORE the password locally on the machine. It actually tells you to create a security group and then assign the user(s) to that group.

    https://technet.microsoft.com/en-us/library/cc755310%28v=ws.10%29.aspx

    “So that the delegated RODC administrator can log on to the RODC when the wide area network (WAN) link to the hub site domain controller is not available, the delegated RODC administrator account password must be cached on the RODC. Note that the delegated RODC administrator account is not allowed to be cached on an RODC by default. Therefore, you have to modify the default PRP to allow the password to be cached, cache the password, and the recache it after every password change for successful logon to the RODC when the WAN is not available or a writable domain controller cannot be contacted. You must do this for every member of the security group that you specify as an administrator of the RODC.”

    And yes you’re welcome Hassan 🙂




    1



    0

Leave a Reply