Join Telegram Study Group ▷
Over the past few months, I have been studying how people prepare for CCIE routing and switching lab laboratories. I have spoken to many recent CCIE and a group of CCIE candidates. They all admit that a lot of hands-on practice is important. As I mentioned in the CCIE roadmap, themes, and blueprints, CCIE R candidates do need to know a range of techniques. It also seems helpful to practice using one or more preparation suppliers to expose job seekers to different problem styles.
But I believe that successful CCIE candidates need to have some serious soft skills so that they can prove that they have technical knowledge that is certified as CCIE in eight hours of testing
Soft skills are part of CCIE preparation and laboratory attitudes and methods. Many people post ideas about soft skills on their blogs or comment on CLN or GroupStudy discussions. Cisco has even released 10 tips for taking laboratory exams here:
http://www.cisco.com/web/learning/le3/ccie/rs/lab_exam_tips.html
Cisco also posted a brief video demo to help familiarize candidates with the online interface here: https://cciedump.spoto.net/lab-dumps.php that they say includes tips to help you be more efficient on the lab.
My explanations of soft skills based on two Cisco documents come together. These "soft skills" are required so that CCIE candidates can efficiently complete the CCIE experiment:
A) The lab is graded, so manage your points.
B) The lab has an online interface, so be prepared for an online interface.
C) The lab has an online interface, so understand what the demo says the interface supports.
D) The lab has an online interface, so practice using Putty for console access.
E) The lab is a timed test, so practice with time constraints.
F) The lab is a timed test, so manage your time during the exam.
A) The lab is graded, so manage your points
You don’t need 100% pass the exam, you only need 80% of the troubleshooting time and 80% of the configuration time to pass the exam. Therefore, in practice and in practice, you need to remember the key value of each problem and how long it takes to resolve the problem. As Cisco said, "Don’t waste too much time when dealing with two or three points.
If the 2-point problem in any part will take you too long to resolve it, be ready to skip this problem until the section ends, or simply ignore it. (This may be really hard for a linear thinker, but it’s a very good strategic decision. CCIE candidates need to meet hardpoints to pass the lab exam, but they do not need to complete all the daunting tasks.
However, don’t sacrifice connectivity. You can intentionally implement repairs that are not allowed in the lab, lose some points, but still have access to all devices.
You should scan the entire lab and pay attention to the most easily accomplished content. At the time of the exam, you’d like to first complete the simplest point so that you can pass through the section.
B) The lab has an online interface, so be prepared for an online interface
You should be as familiar with the online interface as possible in order to be as efficient as possible in the lab. Watch the demo video. Watch again. There are no more paper exams-virtual topology, test questions, documents and some guidelines, and other tools are presented online through the lab delivery system and accessed through a centralized toolbar. You should follow this format as much as possible in the last few weeks of your lab practice. For example, you should read the practice lab scene and view the chart electronically. You should practice reading the entire simulation lab quickly in an electronic format.
You can also use the Cisco Learning Labs to practice the IOU experience. For example, although not as complex as a CCIE lab, the TSHOT lab may help to view tickets, view online charts when tasks are resolved, use Putty, and so on.
C) The lab has an online interface, so understand what the demo says the interface supports
When you click the device on the topology diagram, you are connected to the device console. (for the troubleshooting section, this is a virtual device).
Each console session displays the device name in the upper left corner. You can adjust the copy/paste option slightly. You do not need to always open a console session on all devices. Focus on a subset of devices affected by a particular event and open other devices as needed. You can reload the device into the initial lab from the manage Devices tab.
You can view one event or chart at a time in a separate pop-up window, or you can view all events or charts in the troubleshooting section of a pop-up window. You should practice reading the entire experiment quickly at the beginning of this section. During the experiment, only controlled links to lab-approved Cisco documents are provided, which you can access through the help section. You can view one section or chart at a time in a separate pop-up window, or all events and charts in the configuration section of another pop-up window.
D) The lab has an online interface, so practice using Putty for console access
The online tool appears to use a customized version of Putty, so practice using Putty exclusively before your lab.
Bruno van der Werve from Cisco posted some examples of what can be changed in the console sessions here: https://learningnetwork.cisco.com/
Console Configuration Options
It is efficient to copy and paste between putty windows and move between multiple windows. Practice using Windows notepad to type common configuration commands, and then copy and paste them into multiple devices. When practicing and working, copy/paste and navigate in Putty as the standard operation process.
Copy Paste
E) The lab is a timed test, so practice with time constraints
Set the hard limit on time to increase the speed by practice. If the troubleshooting scheme takes 2 hours to complete, set the timer to 2 hours. Start the timer and start the process by reading the * ALL * of the scene. And then there’s a selectivity, first of all, to do the most simple task. It is planned to subdivide your time between events, but leave some space for review. As a result,10 tickets are obtained within two hours, leaving their ticket residence time no more than 8 minutes, and time to scan all tickets at the beginning and to process more difficult tickets at the end. Set the second timer for each ticket. Since the laboratory map will be electronically displayed, start with the electronic diagram. You can sketch other charts, but do not use the plotted chart or create a sketch unless your overall plan timer is started. Then practice other scenarios, each with a timeless than 7 minutes, rather than a 6-minute walk to each ticket. Apply the same procedure to the configuration section to read the * ENTIRE * scene, select the most simple task, and then first execute them.
F) The lab is a timed test, so manage your time during the exam
Develop a goal to get enough scores to pass each of the experimental sections as soon as possible. First, perform the simplest task. You can manage your time in each section by subdividing the time in the event or configuration section while leaving some space for the review. Write down the events or topics that you have skipped, and then continue. Track your point of view what you’ve done, what you want to see again, the time you estimate is too time-consuming for the lab time budget. After you complete the first pass of this section, check your time, calculate the score, check the completed work, and then view the "Find Again" item. Check your time, calculate the score again, and then process the remaining items and always want to get enough scores to pass the exam quickly.
Note
The Troubleshooting section has a maximum of 2 hours. Cisco says “Candidates who finish the troubleshooting section early may proceed on to the configuration section.”
This is a pretty strong hint that if you can complete the troubleshooting section quickly, you can move on to the configuration section. If you finish troubleshooting, checked your results, and know you have sufficient points to pass troubleshooting, you should move on to the configuration section. You can NOT move back from the configuration section to the troubleshooting section.
Although this earlier video still shows a printed lab manual, it offers some useful tips, such as reading the whole experiment, so that you will not change the earlier configuration for later requirements and use the trainer to clarify the problem.
More Recommended Articles
1. 7 Notes in CCIE Security Lab Exam You Should Notice
2. CCIE Security Lab V5 PASS+PASS+PASS = FAIL|| Re-view
3. After Experiencing in Cisco Changes in Exam, I Finally Got the CCIE Certified
