Ways To Complete CCNA In Several Month, 2 Steps To Achieve Success

There was such amazingly positive feedback regarding my last publish about learning from previous not passers in the real ccie lab, I decided to do this series on my own personal blunders in the actual lab examination. Certainly, it is my hope that numerous can learn from these mistakes, and continue on to stand out in many fewer attempts than I experienced! Anyway, I will be throwing in a few that I actually did not make, but I felt like I made them when they occurred to my students. The thing is, when my students take the examination, I feel pretty connected to them. Like ET the Extraterrestrial or something!

Easily, the dumbest thing I ever individually did in the lab was obsessing about a 2 point non-core task that I was struggling with and not leaving it. That is right, wasting about 45 minutes of valuable lab time, not getting the task right after all that time, and blowing my chances of passing right out the wonderful Research Triangle Park, North Carolina window. I know this may sound ridiculous, and it might seem like something you readers might never do, but trust me, it can happen. The thing is, I was so cocksure in this area of the lab technologies, I thought, there is no way I will miss these points - www.realccielab.org

I, like most of you, often obsess about getting even the smallest configuration right. It is extremely interesting how tough it could be to leave a task in the lab examination. I learned to make use of a Skipped Task Tracker and this really helped me to physically and psychologically leave a task.

Yet another thing I wish to mention about this mistake is the fact that 45 minutes seemed like 10. Yes, time could get pretty funny on you in the examination. Make sure to be watching an actual time keeping device and not seeking to be intuitive about how much time is passing.

Note the heading of this document, IT WAS ccie r&s lab. My description of non-core is anything that I could skip, and it CANNOT impact anything else, no other points can be impacted. This is my own personal description, and notice just how it deviates from a lot of the training vendors around. Often times, they will just say something like OSPF tasks are Core. No, I do not agree. OSPF tasks are core only if they could impact other points in the lab examination.

To provide one more instance of core and con-core from the Routing and Switching track, a non-core task would be a QoS task relating to how packets ought to be prioritized as they are sent out of a router interface. If you do not complete this task, or if you should mess it up, it cannot effect you for the other points there are to acquire in the lab exam. A core task, this is one in which if you do not complete it properly, it costs you greatly. A good example would be a failure to provide connectivity to a backbone device that will inject routes into your lab domain.

Of course, that's right readers, I was completing the lab orderly, and everything was progressing smoothly, and I got STUCK on a task. Not simply any task, a NON-CORE task. Because it was a topic I knew very well, I just could not bring myself to leave it. What a big mistake.