Hotspot Question
You build a test environment. The test environment contains one Active Directory forest.
The forest contains a single domain named contoso.com.
The domain contains the servers configured as shown in the following table.
You run the following commands.
New-ADReplicationSite Site1
New-ADReplicationSite Site2
New-ADReplicationSubnet -Name “192.168.1.0/24” -Site Site1
New-ADReplicationSubnet -Name “192.168.2.0/24” -Site Site2
New-ADReplicationSiteLink -Name “SiteLink1” -SitesIncluded Site1,Site2 -Cost 100 –
ReplicationFrequencyInMinutes 15
You promote Server3 and Server4 to domain controllers by using the default options.
Use the drop-down menus to select the answer choice that completes each statement.
Answer: 
Not sure about this answer – if DC1 only talks to Server3/4, how come Server4 can talk to all DCs? Surely it will “never be replicated” to all DCs?
0
0
Remember that the PS commands do nothing with the servers!
All servers will stay in the DEFAULT-SITE-NAME!
“be replicated to all contoso.com domain controllers”
“take two replication cycles to be replicated” (from Server4 to PDC first, than to all others)
0
0
Note that the servers are promoted to DCs after the creation of the sites. So I think they’ll be moved at this time, automatically…
0
0
And adding more information to this conversation:
“Server objects are created in AD DS by applications or services, and they are placed into a site based on their IP address. ***When you add the Active Directory Domain Services server role to a server, a server object is created in the AD DS site that contains the subnet to which the server’s IP address maps.*** If the domain controller’s IP address does not map to any site in the forest, the domain controller’s server object is created in the site of the domain controller that provides the replication source for AD DS.”
Since the question says nothing about disabling the Bridge All Site Link (BASL), I believe that:
– Creating an object on DC1 will replicate to everyone, since BASL links all DCs;
– And creating an object on Server4 will take on replication cycle, again, due to BASL and the site link between Site3 and Site4.
https://technet.microsoft.com/en-us/library/cc754697.aspx
What do you guys think?
1
0
With a fresh domain you have a Default-First-Site and a Default-First-Site-Link automatically created and when you created the sites they would be automatically added to Default-First-Site-Link. The default cost of the Link is 100 so the new Link between the new sites (1 and 2) would not take priority – hence one replication cycle.(I think).
0
0
And I think it would replicate to all the DC’s as the sites will still be in the Default-First-Site-Link too. (not the answer shown).
0
0
OK – could be talking p*ss there. If you create a site with the ADS&S gui tool you’re forced to pick a site link. With the PS command you’re not by the looks of things. In that case I might agree with Strider.
0
0
I’m wondering about the significance of the “using the default options” statement. Could that maybe add the new DC’s to the default-first-site-name site and therefore replication would work all round. Maybe not in which case I’d say the user would only replicate to DC2 and the “never be replicated” option for part 2 would make sense. Quite a tricky question really.
0
0
Yeah Watcher, when you use the PS command the new Sites are NOT added into Default-IP-Site-Link.
So initially we “assume” DC1 and DC2 are in this Default Link, then Site 3 and 4 have their own link.
Then shouldn’t the answers be:
– DC2 only
– Neverbe replicated
0
0
When you create a site via powershell it is not added to the default site link. This doesn’t matter though since the question shows the creation of a site link and adding the two new sites to it.
So we have three sites, default site2 and site3.. With two site links default and site2-site3. Bridging is enabled so replication will happen between all dcs.
0
0
Watcher & strider must be correct.
Cerlin,
bridge all site links only makes the current sitelinks transentive. Unfortunatly there is no link in common to make it transentive.
The defaultipsitelink, is not connected to all the sites.
When you create a site in the GUI you must add it to a link, when using PS noting is asked to link. (its just a sitelink doing, nothing,, or to be used as a start)
DC1 & DC2 are in the same site. (DEFAUL-FIRST-SITE-NAME)
Server3 & 4 are connected with a site link.
DC1&2 (DEFAULT-FIRST-SITE-NAME) is not in any connected to Site 1 or 2.
hoping this will clear things up.
and please!! correct me if I’m wrong.
0
0
The sites are made first and then de servers are promoted. By the ip address they are placed at site1 and 2. The bridge settings seems to be default, so changes will be replicated to all sites. It just takes 2 steps.
0
0
I’m with itopia. I tested this in a lab, and the objects replicated to all DC’s.
1. All Contoso DC’s
2. 2 Replication Cycles.
0
0
Just bringing in some background to back up your tests:
“Server objects are created in AD DS by applications or services, and they are placed into a site based on their IP address. When you add the Active Directory Domain Services server role to a server, a server object is created in the AD DS site that contains the subnet to which the server’s IP address maps. If the domain controller’s IP address does not map to any site in the forest, the domain controller’s server object is created in the site of the domain controller that provides the replication source for AD DS.”
“Server objects are not created in Default-First-Site-Name by default unless there are no other sites in the forest.”
https://technet.microsoft.com/en-us/library/cc754697.aspx
0
0
I did the test in my lab with the exact order reported in the question:
1) DC1 replicates only to DC2
2) Never be replicated (Replication occurs only between Server3 and Server4)
Sites Site1 and Site2 created with PS command are not added to DafaultIpSiteLink, so the Default-Site is not connected to Sites 1 and 1.
4
0
… sorry Site1 and Site2
2
0
Thanks Franco, i believe this is correct.
As qwe says: Server objects are created in AD DS by applications or services, and they are placed into a site based on their IP address
And Site1/2 are not connected to any other site as you say, for “bridge all site links” to work there has to be a site link created that links them.
1
0
tricky, tricky.
when you create the site with New-ADReplicationSite cmdlet it will be isolated from DefaultIPSiteLink. So basically in this situation we have Server3 and Server4 separated from DC1 and DC2.
agree with Strider and Watcher.
answer is:
– be replicated to DC2 only
– never be replicated
2
0
Everything should be replicated to all DCs every replication cycle.
“Bridge all site links” is enabled by default. As long as a site is in a site link it should be replicated to- even if the it’s the only site in the site link.
The first link has to be wrong because DC1 and DC2 are presumably in the same Default-Site-Name.
Default-Site-Name is in Default-Site-Link. Sitelink1 has Site1 and Site2. Sitelink1 and Default–Site-Link are bridged since the question doesn’t say Bridge All Site Links was disabled.
1
0
Based on this:
“A site link bridge connects two or more site links and enables transitivity between site links. Each site link in a bridge MUST have a site in common with another site link in the bridge. The Knowledge Consistency Checker (KCC) uses the information on each site link to compute the cost of replication between sites in one site link and sites in the other site links of the bridge. Without the presence of a common site between site links, the KCC also cannot establish direct connections between domain controllers in the sites that are connected by the same site link bridge.”
https://technet.microsoft.com/en-us/library/cc753638(v=ws.10).aspx
I too think that correct answers should be:
1- Be replicated to DC2 only (since DC1 and DC2 are the only ones in Default-first-site-link and there’s no link in common that connects to the other DC’s, DC1 only replicates to DC2).
2- Never be replicated (Server4 only has a site link in common with Server3, so it’s the only DC it can connect to.)
1
0
I wonder what they mean with this statement in the question: “You promote Server3 and Server4 to domain controllers by using the default options.”
When you’re promoting the servers to domain controllers in the page of “Domain Controllers Options” in site name, if no other site exists, by default, Default-First-Site-Name is selected, but in this case, you already have created other sites, which means that in that field there will be other options, as you can read here:
http://social.technet.microsoft.com/wiki/contents/articles/20098.setting-up-additional-active-directory-domain-controller-with-windows-server-2012.aspx
“If you only have a single site then it will be displayed by default, if you have multiple site names, then using the drop down list select the preferred site”
When you already have multiple sites (which is the case here) by default that site name field is blank, and you have to select from the list which site you want to add (i tried that in lab).
Now i wonder “by using the default options” like we’re told in the question, do they mean in that case that you pick Default-First-Site-Name instead of one of the sites you created?
If so, then all DC’s will be on the same site, which means they all connect with each other because they’re all in DEFAULTIPSITELINK. If this is what they mean then answers would be:
1 – be replicated to all contoso.com domain controllers;
2 – take one replication cycle to be replicated.
Otherwise i’ll stick to the answers i gave in my previous post.
3
0
A site link. To create a site, you must add the new site to an existing site link. You can use the default site link (DEFAULTIPSITELINK) if no other site link exists. If you have more than two existing sites and you are adding a site, you might add the site to an existing site link and then create a new site link and associate the new site with that site link. In most cases, you then remove the new site from the old site link.
https://technet.microsoft.com/en-us/library/cc732761.aspx
1. replicated to all
2. one replication cycle
0
0
when using the PS commands as stated above then you are able to create sites without any link, I suggest you test in lab
0
0
So whats the answer? im lost 😛
0
0
build up your labs properly and check my answers here at this one:
http://www.aiotestking.com/microsoft/use-the-drop-down-menus-to-select-the-answer-choice-that-completes-each-statement-48
0
0
Site link bridging has nothing to do with this question. The matter is in de Default-Site-Link and the Default-Site. They exist from the beginning.
So: – be replicated to all.
– take one replication cycle.
0
0
Guys this one has caused me uttmost amount of stress so I decided to just build it in my test lab and figure it out.
When you run the PS commands NOT the gui, it 100% does not add the site to the default site link this I can confirm.
Therefore we now have two sets of sitelinks with 2 servers in each. Now because site-link bridging is not disabled, when I created a new user in DC1 it immediately replicated to DC2, Server 3 and Server4. The reason is the originating DC is in the default site link and hence the bridge will kick in and replicate it out.
The interesting part is what happens next, when you create a user in Server3 the user remains on Server3 only and never gets replicated.
So With that in mind my answer would be replicate to all DC and never replicate
Try it out for yourself and youll be surprised the results
0
1