Slashdot Mirror


CCNA Certification Library

Michael Bennett Cohn writes "Cisco Press' CCNA Self-Study Certification Library by Wendell Odom consists of two books: the ICND guide and the INTRO guide, corresponding to tests 640-811 and 641-821, respectively. Passing each of those tests will make you a CCNA; so will passing combined exam 640-801. I passed exam 640-801 in one try, with no real networking experience and having taken no classes. The ICND and INTRO books comprised my primary training materials." To sort out a bit of that alphabet soup, CCNA stands for "Cisco Certified Network Associate" and ICND for "Interconnecting Cisco Networking Devices," though if you're in the market for this book you probably already knew that. Read on for the rest of Michael Bennett Cohn's review. Self-Study Certification Library author Wendell Odom pages 1232 (combined) publisher Cisco Press rating 6 reviewer Michael Bennett Cohn ISBN 1587200953 summary Useful but annoying; Decent study materials for Cisco tests 640-811 and 641-821.

Although it is possible to enroll in official ICND and INTRO courses created by Cisco, the books that make up this "library," apparently, are not the books used in those courses. Within the ICND book, Odom refers to "the ICND course, on which the exam is partly based," suggesting that what you have in your hands is a reverse-engineered study guide: a study guide for an exam that is based on a course that does not use said book. Odom occasionally presents tables that he claims come from the ICND course. Clearly, some parts of the course are not fair game for the study guide.

In other words, don't think that just because you are reading the official Cisco press CCNA study guides, you are dealing with a set of information that is as close as possible to the set of information from which the test was drawn.

Studying these books will prepare you for the CCNA in the same way that reading the Encyclopedia Britannica from A to Z will prepare you to identify the capital of Nairobi. It goes without saying that a CCNA candidate should not be studying just to pass a test, she should be studying to qualify herself for a job. But in this case, the difference between the material presented and the material actually making up the test is excessive.

Odom goes to a lot of effort to make the reader feel like he is being spoken to by a friend. "Fun, isn't it?" he writes, after presenting an illustration of function groups and access points that I had to re-draw for myself several times in order to understand. Later, he describes Inverse ARP as "another case of learning by listening, a great lesson for real life!" Gee, thanks. The subtle condescension in the non-humorous asides, the gleeful overuse of exclamation points, and the fable in which Pebbles Flintstone invents networking is compounded by the persistent contextual encapsulation of every single topic in the book. Odom tells you what he's going to tell you, then he tells you, then he tells you what he's told you, much more than necessary.

A better way to put the flustered reader at ease might have been to proofread the books. The ICND guide, especially, is so full of typos that it is often embarrassing to read. In some cases, these are nothing more than obvious misspellings that can be passed over without much more than a little annoyance (e.g. ICND p. 472, "status enquiry messages"). In other cases, the meaning of the sentence is muddled. Worse, the configuration examples have obviously not been proofread either, resulting in, for example, the prompt "R1(config)#" when the appropriate prompt is "R1(config-if)." The difference may seem trivial, but understanding its significance is the kind of stuff the CCNA is all about.

Each book comes with a CD containing a practice test engine and a router simulator (both from Boson). The mistakes in the ICND book pale in comparison to those in the CD test engines. In fact, an argument could be made that studying with those practice tests will hinder more than help the CCNA candidate who has not read the books thoroughly enough to recognize the mistakes. Many multiple-choice questions count correct answers wrong and vice versa (and some of these are taken directly from the books, which usually give the correct answer). A configuration entered into the CLI on a simulator question will be graded as wrong, and the user will then be presented with an identical configuration as an example of the correct way to solve the problem.

None of these problems change the fact that these books will, if used correctly, absolutely help you pass the CCNA. But do it this way: Read the INTRO book. Take the exam right away. If you don't pass, flip through the ICND book and find the areas that you actually need to work on. You'll save months of study time that could be better spent working on your CCNP.

I give the library as a whole 3 out of 5 stars.

You can purchase the CCNA Certification Library from bn.com. Slashdot welcomes readers' book reviews -- to see your own review here, read the book review guidelines, then visit the submission page.

3 of 182 comments (clear)

  1. Re:CCNA is worthless for this very reason by Wingchild · · Score: 4, Interesting

    One of the more amusing job hunting experiences I ever had revolved around this concept.

    I had already passed their resume' screening and phone interview process and was now down to the face-to-face (also known as the `Eyes, Fingers and Toes` check) and an on-site technical interview. After a brief discussion of my qualifications and experiences, one of their lead engineers was called over.

    Him: Okay, let's begin. Define `TCP/IP`.
    Me: ... are you serious?
    Him: It's just a standard question.
    Me: ... did you see that I have an MCSE and have been a network engineer for four years now?
    Him: The MCSE is why I'm asking.

    I kid you not. At the time I was sincerely insulted, but having spent a career surrounded by engineers who didn't know their asses from their elbows, I can see why he held that belief. The threat of the Paper MCSE is quite real -- and now, unfortunately, Cisco's certifications are being proven to have the same flaws.

    Certifications in the tech world are just like degrees, people -- they're paper. They're that foot in the door. They're a proof that you can read a book and pass a standardized test. They don't guarantee employment. They may get you the interview, just don't expect more from them.

  2. Re:CCNA is worthless for this very reason by barryfandango · · Score: 3, Interesting

    I work in the IT department of an aerospace engineering company, and the Professional Engineers (aeronautical and mechanical) here got very territorial and downright pissed the first time our network administrator sent out an email with the sig "Microsoft Certified Systems Engineer."

    How is it that Microsoft gets away with using this phrase when the certification is not recognized by the association of professional engineers?

    --
    In all matters of opinion, our adversaries are insane. -Oscar Wilde
  3. Re:Brain Dumping by JudgeFurious · · Score: 3, Interesting

    Yeah, that about covers it.

    In my case I started this at home. Got the "addiction" and started buying and tinkering with computers as fast as my budget would allow. I used to be the guy who bought new games and secretly hoped something wouldn't work right out of the box so I could figure out why. One day I looked up and I knew enough that someone would actually pay me to fix PCs for a living.

    Eventually that led me to better technician jobs and finally the desire to work on bigger problems. I got an entry level position here where I still work and started learning networks from my boss (And he started his "addiction" in the early 70's). At one point about four years ago management decided that we all needed to be MCSE certified and laid out a bunch of money to a training company for classes and vouchers. We were running Novell then and since we had been given the "We're switching to NT now" speech (again from management) they felt like we needed some training.

    We were all like "Ok, whatever." I went to the first class and tried to get into it but I wasn't learning anything. Sure I was learning how much Microsoft thought of their product but everything relevant was stuff I learned on the job. I ended up passing on the rest of the classes and just picking up some "Dummies" books and finishing it on my own.

    The vouchers my company paid for were of some use (because I wouldn't have bothered to pay for those tests on my own) and we ended up using the class time for another employee who needed some SQL training but the content was worthless. It amounted to me spending time learning enough "Administrivia" as you so nicely put it just to pass a stupid test I didn't really need and didn't want in the first place.

    On the other hand my brother jumped into this field because you could make bank in it. He went to college, I didn't. He has a CIS (or one of those, I don't really know or care much) degree and as soon as he got out he went through the Certification feeding frenzy and jumped into a job from the get go that paid more than I was making. I tried to talk him into spending some time to learn a foundation but he wanted the money and he got it. The thing is though he's lost and in way over his head. I think it's only a matter of time before he's looking for work because he doesn't love this stuff and he doesn't know it well enough. His paper means not much in the long run.

    It might sound like I'm looking forward to him hitting the wall but I'm not. I really just wish he'd listened to me (and had gone after something he enjoyed instead of what he thought was going to get him in a BMW faster). I've seen enough of the paper admins to know that no good comes of it.

    --
    Appended to the end of comments you post. 120 chars.