70-294 QOTD for June 7th

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

Gavin is a network administrator for a Windows Server 2003 AD network. The company he works for has a Head office downtown Boise and two branch offices; one in Eagle and a brand new branch office in Meridian. The head office has three domain controllers and 150 users. Each branch office has one domain controller and 25 users. All domain controllers run Windows Server 2003 and all client machines run Windows XP Professional. The Head Office and the Eagle office report no difficulties but the new branch in Meridian complains about slow logon times and delays in object search times. Gavin calls Phil, a consultant with a great deal of experience in setting up Windows Server 2003 Active Directory networks. After some discussion on how Gavin set up all three offices, the consultant comes up with the most likely reason for the Meridian branch office problem. What does Phil tell Gavin? Choose only one answer.

A. Gavin has set up the Head Office with two Global Catalog servers and the Eagle office with one Global Catalog server but neglected to assign the Domain Controller in the Meridian office as a Global Catalog server. As a result, the users at the Meridian office must contact one of the Global Catalog servers at the Head Office in order to logon or do cross-site searches over a slow WAN link. Gavin should assign the DC at Meridian to be a Global Catalog server.
B. Gavin has set up the Head Office with two Global Catalog servers and the Meridian office with one Global Catalog server but has not set up the Eagle office with a Global Catalog server. Due to increased replication traffic between the GC servers at Head Office and Meridian over a slow WAN link, logon and search traffic is slowed. Gavin should remove the GC server capacity from the DC at Meridian.
C. Gavin has set up two Global Catalog servers at the Head Office but none at either branch office. One of the DCs that is a GC server at the head office is offline. The Eagle office is able to use the remaining Head Office GC server for logons and searches but the Meridian office nodes are continuing to attempt to connect to the offline GC server. As a result, the traffic from the Meridian office is being sent to the other GC server which is now overloaded and unable to perform adequately for the Meridian users. Gavin should troubleshoot the offline server and either bring it back on line or assign the third DC at Head Office to be a GC server for load balancing.
D. Gavin has set up two Global Catalog servers at Head Office and none at either branch office. Head Office is connected to both of the branch offices via a T1 line which is sufficient for all logon and search traffic so neither office should be having difficulties with logons and searches. The T1 line has gone down between Head Office and Meridian and a back-up ISDN line has automatically taken over. Since the ISDN line is a much slower link, it has inhibited the logon and search times from Meridian and Head Office. Gavin should contact his telco provider and arrange to have the T1 repaired and brought back up immediately.

Answer later.

 

Oh man! Ad-blocking software has been detected! :'(

This website is run by the community, for the community... and it needs advertisements in order to keep running. Blocking our ads means your killing our stats!
Please disable your ad-block, or become a premium member to hide all advertisements and this notice.

im gonna go with A
i guess D seems possible, but im sticking with A

 

Phil says A

 

I go with A aswell

 

Anyone else before time runs out?

 

Answer time. A is indeed the answer. The Meridian site has not Global Catalog server on site so must contact the one at Main Office, resulting in slow logons and searches. The answer would be to make the on-site DC a Global Catalog server. Alternately, Universal Name Caching would be an option.

While D may seem tempting, it implies that there are dedicated lines to two different GC servers at Main Office and it seems more likely that you wouldn't have one GC server dedicated for one site and one for the other.

Good one. More tomorrow.

 

Sorry for all the trouble Guys - glad Phil fixed it

 

I've obviously missed something again. What are you talking about, Gav?

 

Erm, Phil patching up my mess again, Trip.

 

That's what friends are for, Gav.

 

Lucky that Phil and Gav got it sorted.