CCIE - First Lab Attempt Experience.

CCNA 200-301

CCNA 200-301

CCNP Enterprise

CCNP Enterprise

CCNP Security

CCNP Security

CCIE Enterprise Lab

CCIE Enterprise Lab

CCIE Security Lab

CCIE Security Lab

CCNP Service Provider

CCNP Service Provider

CCNP Data Center

CCNP Data Center

CCNP Collaboration

CCNP Collaboration

CCIE DC Lab

CCIE DC Lab

ic_r
ic_l
CCIE - First Lab Attempt Experience.
images

You haven’t heard much from me recently for a very good reason. I have had no life. None whatsoever. No biking, no going out, no watching TV, nothing. All my spare time has revolved around one thing: CCIE  lab exam study. This year I set myself a challenge, of becoming a CCIE (Cisco Certified Internetworking Expert). This is a top-level networking certification, highly respected within the industry.

Becoming CCIE certified involves passing a written exam, taken at any one of hundreds of testing centers around the world. That part needs a bit of study, but it’s straightforward. That then qualifies you to register for the real meat of it-the 8-hour practical exam, taken at a limited number of lab locations around the world. These have limited seats available and depending on where you are, it can be tricky getting seats. Luckily my nearest location is Sydney, which is usually not too tricky to get space at.

Because of other rather important things going on in my life – i.e. I’m getting married next week–I had to schedule my first lab attempt for this week. I always knew that it was a bit tight to get ready by this time, but I thought I could just about do it. I do any hands-on work with Cisco equipment these days, so all the practice I get is in my time, on my dime. I’ve mostly been using training materials from SPOTO in my study program. These give me some structure to work from, as I try to cover the enormous range of topics covered in CCIE Routing and Switching these days.

Almost every night I’m either reading or practicing scenarios on rented routers and switches. At least one whole weekend day is taken up with practice lab scenarios. Closer to lab time, this was both weekend days. My iPad has audio lectures loaded on it. When I’m driving to and from Tauranga for work, this is usually what I’m listening to. Some people keep track of the total hours they spend studying. I don’t, but trust me, it’s a lot. I really don’t know how Anna puts up with it all, I really don’t. She has been amazingly supportive though.

All this work, but it turns out that I’m not quite there yet. Close, but just not quite there. Recently I tried a couple of practice labs from the Cisco 360 program. These offer a pretty reasonably simulation of what you might expect from the lab. One of them I was just below passing, the second one I passed. 

Note: There are two parts to it, troubleshooting and configuration, and you need 80% in both parts to pass. So I knew I was on track. Not certain to pass, but certainly in the frame.

This week I traveled to Sydney, for my first lab attempt. Things started out reasonably well, and I was reasonably sure I would pass the first part, troubleshooting. Sometimes candidates know they’ve failed the first part, and so they don’t make a proper effort in the configuration part. But I thought I was doing OK, and I thought I was going OK for time. I wasn’t rushing, I spent a bit of time reading through the questions, looking at the diagrams, getting a feel for what’s going on. The last thing you want is to find that a question near the end of the exam completely changes how you should have done something at the start. It’s a classic Cisco trick, to have something late in the day that breaks everything you thought you’d configured earlier.

I started working my way through the configuration section. I could understand pretty much all the core stuff, but the problem was time. After a couple of hours, I realized I just wasn’t moving through the marks fast enough. I also got tripped up by the deliberate mistakes Cisco had inserted. I was prepared for a misconfiguration, I was ready for something added that would actively break things. That took a little longer than it should have to track down and fix. At lunchtime I was OK, but only just.

After lunch, I worked my way through the rest of the items, all except for 3. Two of them were on a complex, but niche topic, and would have required a huge amount of work for the marks. One was dependent on the other, so I chose to skip those questions, as it didn’t affect anything else. The third thing I could have worked it out, but I was running out of time, and didn’t want to risk breaking other things. I took too long configuring things, but I did have the time to properly verify everything, other than full connectivity. Provided I got every other section right, I could pass the exam, even with the missing sections. So I was certain I’d success, and it would be easy to pass.

This morning I got my score report. Passed troubleshooting (the section that trips up most candidates) and configuration. Having a CCIE number for me today. 

I was so happy that I have passed the exam. SPOTO has provided some real exam study and dumps that are the same as the real exam. There are some professional tutors to train your certification exam.