Here is 42 out of the 58 questions I got directly from the test.

• • Not simply what I studied.

I just got back from taking the Networking Essentials exam. The way everyone at this site talked, I was very doubtful that I would pass my first time. All I did was skim through the book, barely reading the conclusions and I did none of the questions from the book. What I did do was obtain the transcender exam questions. Did all the exams once and reviewed each of my wrong answers. I never retook them until I got 100% like is recommended by everyone. In between each exam I read responses from the braindump. I tell you what, you underrate this site. I truly believe that I could have simply read through all the responses here and passed easily. Great work to all that contribute.

Oh yea, I got a 948/1000.

Every question on my exam was on this site somewhere (except two):

1. You have one segment on network ethernet and one token ring, you are looking to put nwlink ipx addressing, what should you install?

A. Repeater

B. Router

C. Bridge

D. Gateway

I choose B - Router. Look it up, this was the exact question (I just took the exam 30 min ago). I did get 100% on the implementation section. Is that where this goes?

2. The second one was on of those situation ones where you are looking to add 24 users in the next year, your network is running 70% and you need to cut that by 50%.

• • • • • • optional needs are: 1. network to keep this improved performance after 24 users are added

2. ability for continued growth

3. inexpensive.

Their solution is: upgrade everything to 100baseT.

I have no Idea to what extent upgrading to 100baseT increases network performance, I just know it's not cheap. I said all but inexpensive met. I am definitely not confident of this (86% troubleshooting)

Other Questions (answers)

• I must have had 5 questions where I choose Protocol analyzer as the answer. If you hear the phrase:

"packet level" choose protocol analyzer.

"Checking for bad NIC" - protocol analyzer.

"Taking tests over time" - protocol analyzer,

• I had 2 questions on ATM - key words: "video", "over 100mbs"

• I had another 6-10 questions where you had to choose the reason why computer couldn't connect to network or to shared components on the network. Know:

-In new client can't access anything and nwlink - Frame Type (2-3 Q's),

-" " Ethernet - transceiver. (2 Q's)

-If new computer can't access certain shared resources - protocol mismatch.

-If computer was working and now not and only one not accessing network - choose the answer relating to only client. There were more, sorry.

• I had a question where coax readings were terminator=50, something else infinity, and cable=0. I said replace cable because somewhere here I read choose the component with reading 0.

• Also had network where they used /U and /AU 10base2 cables and had problems. Remember - switch /U to /AU

• 2 scenarios with t1 lines connecting offices. One with 2 lines and one with 3. Remember you need a loop for redundancy.

• 2 scenarios on netBIOS naming. Remember Hex will work as long as it's < 15 characters but is not descriptive.

• RIP is the only routing protocol to worry about.

• Know that only LAT, NetBEUI, and DLC are not routable

• Know that UNC name consists of computer name and share name

• one question stated something about which types of servers perform application processing:

1. file and print servers

2. application servers

I choose both, you may want to look it up. I don't know what the definition of an application server is but it sounded good.

Quick answers

Many of the simple ones - ISDN replacing phone lines.

- Gateway does protocol translation (2 Q's)

- use router to eliminate broadcast storms

- 10baseT = UTP

- 10base2 = BNC connectors

- crosstalk = signal crosses to another wire

- choose nwlink ipx for small peer to peer

- Windows 95 can't use user level security

- use repeater for 10baseT 300 feet

- Connection oriented = assured delivery

- SLIP and PPP support telephone connectivity

- SLIP doesn't support data compression

- mesh diagram

Things to remember

• Remember Audit = checking who touched what network files

• Remember peer to peer = small 10 user network. Can't be used for 750 computer net (question)

• They always referred to Novell as "nwlink IPX"

• Remember - messing with packet or window size will not help network performance.

• Remember - appletalk does not support nwlink IPX

• Remember - choose brouter with TCP/IP and NetBeui

• Remember - choose router with only TCP/IP