Ensure that Server1 attempts to authenticate to DC3 first

Discussion in '70-412' started by howtired, May 27, 2016.

  1. ho

    howtired Member
    Member

    Joined:
    Apr 4, 2016
    Messages:
    18
    Likes Received:
    0
    Your network contains an Active Directory forest named contoso.com.
    The forest contains a single domain. The domain contains three domain controllers.
    The domain controllers are configured as shown in the following table.

    DC1 : Site1
    DC2: Site1
    DC3: Site2


    You plan to test an application on a server named Server1.
    Server1 is currently located in Site1. After the test, Server1 will be moved to Site2.
    You need to ensure that Server1 attempts to authenticate to DC3 first, while you test the application.
    What should you do?
    A.Create a new site and associate the site to an existing site link object.
    B.Modify the priority of site-specific service location (SRV) DNS records for Site2.
    C.Create a new subnet object and associate the subnet object to an existing site.
    D.Modify the weight of site-specific service location (SRV) DNS records Site1.

    Premium Dumps report solution as B.
    This anyway will not work, for two reasons.

    Reason1: NETLOGON will always try to authenticate Server1 to the site corresponding to its subnet. It will not go over a different site and its associated cost unless all DCs in site1 are unavailable.

    Reason2: even if for some reason the KCC topology would only consider SRV record priority,
    existing SRV DNS records for DC1, DC2 and DC3 will have a default priority value of 0.
    In order to give precedence to DC3 we would have to set a smaller value for SRV records resources in Site2. But of course no value smaller than 0 is allowed.

    https://technet.microsoft.com/en-us/library/cc742513(v=ws.11).aspx

    "Lower numbers are given higher preference. The highest priority or preference goes to a host (offering the service that is specified in this record) that has a priority value of zero (0)."

    Solution C should have no effect (create a new subnet and associate it to which site?)
    A is irrelevant.
    D aka lowering the weight would gige precedence on DCs with same priority, but I doubt would work in a real environment due to reason1.

    I'm at a loss here.
     
  2. M-alahdal

    M-alahdal Member
    Member

    Joined:
    Dec 6, 2016
    Messages:
    2
    Likes Received:
    0

    Dear visitor, you need to Register or Login to view links on Certify Chat.

    Your network contains an Active Directory forest named contoso.com.
    The forest contains a single domain. The domain contains three domain controllers.
    The domain controllers are configured as shown in the following table.

    DC1 : Site1
    DC2: Site1
    DC3: Site2

    You plan to test an application on a server named Server1.
    Server1 is currently located in Site1. After the test, Server1 will be moved to Site2.
    You need to ensure that Server1 attempts to authenticate to DC3 first, while you test the application.
    What should you do?
    A.Create a new site and associate the site to an existing site link object.
    B.Modify the priority of site-specific service location (SRV) DNS records for Site2.

    C.Create a new subnet object and associate the subnet object to an existing site.
    D.Modify the weight of site-specific service location (SRV) DNS records Site1.

    Premium Dumps report solution as B.
    This anyway will not work, for two reasons.

    Reason1: NETLOGON will always try to authenticate Server1 to the site corresponding to its subnet. It will not go over a different site and its associated cost unless all DCs in site1 are unavailable.

    Reason2: even if for some reason the KCC topology would only consider SRV record priority,
    existing SRV DNS records for DC1, DC2 and DC3 will have a default priority value of 0.
    In order to give precedence to DC3 we would have to set a smaller value for SRV records resources in Site2. But of course no value smaller than 0 is allowed.

    Dear visitor, you need to Register or Login to view links on Certify Chat.



    "Lower numbers are given higher preference. The highest priority or preference goes to a host (offering the service that is specified in this record) that has a priority value of zero (0)."

    Solution C should have no effect (create a new subnet and associate it to which site?)
    A is irrelevant.
    D aka lowering the weight would gige precedence on DCs with same priority, but I doubt would work in a real environment due to reason1.

    I'm at a loss here.
    Click to expand...
     

Share This Page