That is a hard question to answer definitively. It is a juggling act between reading comprehension, choosing your approach based on requirements, accurate application of configs, and speed of application. You have 8 hours to complete the lab and you will have a 20 min lunch thrown in the middle somewhere. The time you start, have lunch, and finish will depend on the testing facility.
Personally, my goal is to get through the configs with 2 hours remaining for: - Tackling any questions I didn't know "off the top of my head" - Doing an end-to-end validation of the lab to catch any oversights / screw ups In reality, the goal of having 2 hours left over for testing/validation is a real challenge. All I can say is that everyone I have heard from who passed the test were able to knock out the core configurations in 5 - 6 hours and had 1.5 - 2 hours dedicated to checking their work. That isn't to say there aren't people who pass without this validation process. Just that I don't know of any. -- William Bell blog: http://ucguerrilla.com twitter: @ucguerrilla On Jan 14, 2013, at 12:52 PM, Chrysostomos Christofi wrote: > Guys > > they say that you have to be very fast in the lab > what actual that means? > > do you have time for check every task? > > you can check every task when you finish it ,or if you check every task then > you will not have a time to finish the remaining lab > > can you pls send your feedback? > > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > Are you a CCNP or CCIE and looking for a job? Check out > www.PlatinumPlacement.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com Are you a CCNP or CCIE and looking for a job? Check out www.PlatinumPlacement.com
