Subject: NetEss

OK, so I just passed NetEss. I scored a 982/1000, and it was a great feeling to come out of the testing room and have the girl say, "Wow, you really over studied." My reply was: "Actually, I'm surprised I got the one wrong."

Parts of the test were really difficult, others were almost identical to the Transcender tests.

Here's what I can remember:

 

Troubleshooting:

 

T1 / 3 cities:

2 questions with the 3 cities. The wording wasn't as clear as it was in some of the brain dumps and Transcenders. One question had the 3 cities with 2 T1 lines, and they were looking for 1 Mb of data transfer. The optional was 1 Mb if one link failed. The other optional was operation as normal even if one link failed. This was a C - meets required, but none of the optionals. The wording was such that you didn't know if they meant communication between all sites or just 1 site...

 

NetBIOS:

2 questions on the NetBIOS naming scheme. Both had 20,000 clients over 40 sites. Again the wording was strange, so that you really didn't know if they meant will this work in the future once a WAN was implemented. They didn't give any protocol information (such as IPX with NetBIOS), so I assumed that everything would work after the WAN was in place and I refrained from choosing the D - doesn't meet required results. The second question had the well-known one that had meaningful names based on department, location, server #. This one was A - met all required.

 

Layers:

Only one question about where things operate. This was a gateway operating at Transport on up

 

Gateways:

You want to connect a client running terminal emulation software to an IBM mainframe, which connectivity device do you use? A gateway.

 

Routers/Brouters/Bridges/Repeaters

 

PPP/SLIP:

 

Definitions/Standards:

 

NDIS:

The famous questions about NDIS and what it does. One was to allow compliant protocols to use compatible NIC cards or something close to that. No mention about multiple protocols.

The other question asked what it did. Something like allow transport protocols to use compliant NIC cards. I almost tripped up on this one, since two of the answers are really similar. Just remember that protocol layers perform services for the layer immediately above, and you'll have no problem. The other one that I almost put was: allow transport protocols send to compliant redirectors or something close to it.

 

Others: