Top 5 Reasons Why People Fail CCIE Lab Exam

hello everyone my name is Nick and in this video I'm going to talk about top five reasons why people fail CAE lab exam first of all just as quick introduction I have to CC is in routing and switching and data center also I have experience failing my lab attempt also I took all my attempts in three different locations so you should be pretty confident that I know what I am talking about and as a quick disclaimer in this video I won't be talking about what CCIE is how important it is for your career how difficult it is to achieve in this video I'm going to talk about specific reasons why you may fail your lab examination so with that being said let's move forward and before we go to other reasons I would like to mention a couple of mistakes which you can make and fail your lab exam it may sound pretty obvious but I need to mention it in order to even make your attempt you should arrive to right place and on time and this could be pretty tricky if you travel from different City or even different country and you are not that familiar with that publication hotel so you should keep in mind things like jet lag traffic you should prepare a route from your hotel or other location to the application also you should remember that lab starts quite early so just be 100% sure that you know how to get from your place to lab location on time also you should know that there is a policy so technically you can be late but if you're late for two hours or more you won't be allowed to even start your attempt also one more minor thing but still it could be quite important don't violate exam rules if you do violate them you will obviously your attempt will obviously cancelled probably will be banned from first attempts and if you have to say that's a status will be revoked so don't do that very very stupid mistakes so now we are ready to move forward and discuss proper reasons why most people fail ciaela exam so I'm a first reason here is related to health and body issues lab exam lasts for eight hours and also you will have 15 maybe 30 maybe 40 minutes lunch break so you will be there at least for 8 hours probably 9 hours including lunch and for that period of time you'll be working really really hard you'll be configuring complex things you will be working with very big topology you will be troubleshooting things and in order to pass that exam I would say your mind and your body should be in perfect state of readiness in order to achieve that state I suggest I recommend you to have a good proper sleep again Rome and what have just mentioned jetlag that lab starts early that you need to travel from your hotel to lab location probably you would want to have a breakfast so take into account a lot of things and have a proper sleep next tip I would like to mention here is related to lunch I know people who ate too much at lunch and they actually felt sleepy so be aware lunch is located in the middle of your lab exam so you start your lab in the middle you go and have your lunch then you go back and continue configuring troubleshooting etc etc etc so obviously it won't it wouldn't be a good idea to feel sleepy when you come back from your lunch and you also need and at that point you still need to configure basically half of your lab and I think I would like to mention here is related to lab room temperature temp temperature yeah because it could be quite cold so my recommendation here is to take proper clothes with you so you can put something calm if it's the cold or you could take something off if it's too hot so this is basically things which are related to body health and let's move forward and next reason I would like to talk about is related to relying on Proctor for too much and let me clarify what I mean by that first of all I need to mention that Proctor's they don't have that goal to ruin your lab exam Potter's are there to help you but not to do things on your behalf listen again and please listen carefully because from my standpoint it is very very important Proctor's are there to help you but not to do things on your behalf to pass the CA lab exam you should be able to make your own and independent decisions so what do I mean by help first of all if there is something out of your control proctor suit should help with it is there something out of scope for your track Proctor's also should help is it so let me give you an example so if you are if you are making an attempt to pass SB or collaboration track and there is something wrong is firewall I know why I should have firewall in the lab but let's say you have s a firewall or firepower firepower firewall and then you are come in you're 100% sure that it's somehow affects your lap your lap and you don't know how to fix it because well you don't it's not security torque it's collaboration or service provider in that case Proctor should help you and again one more example is weighted to problems with power so for example if power is broken for some device for some router or some switch in your lab exam and you basically cannot access it at all obviously Proctor should help in this situation as well but on the other hand if you messed up triple a configuration and you messed up it completely so you don't have access over telnet SSH console that's completely your fault you should understand that you should you should understand that you messed up your and you messed up with that part and you probably messed up your lap and Proctor's a in that case they probably able to help you also I already mentioned CCA lab exam it tests your ability to make independent decisions so if you want to clarify desk if you vote to clarify some question you can ask Proctor to help you with it but I suggest I suggest you not to rely on his answer for 100% so again that's your decision this your lab you should take care of it and also I gave you a couple of examples but they were kind of extremes also there are many things in between but again remember that's your lab that's your decision and if you ask Proctor for something you should just define you should prove your point so is there something wrong with power you should clearly state it so mister on this there is something wrong with power with with the device I can access it at all I can't access council I can access SSH then let I didn't do anything with Triple A or rbac Auerbach configuration so there's clearly something wrong with power so you should be very clear you should prove your point in that case Proctor will help you and again be aware they are not there to fail your lab they say the hell that goal in mind there's a they are there to help you but again make your own decisions this is your lab and Cisco test you how you can make your own decisions you're all independent decisions so let's move forward and next thing I would like to talk about is related to prioritization and time management as I've already said society lab exam is quite complex or very complex to be honest and topology is very big when you start your examination you are presented with a question paper which has all the tasks Cisco wants you to accomplish in your lab and the order you are presented in that question paper in most cases it is not the same order you should use for actual configuration let me explain it so you may have a task in section one to configure IPSec tunnel but things related to physical connectivity between IPSec nodes or routing congestion see between those thoughts are somewhere in section three and maybe section four so in my opinion it makes no sense to configure IPSec and troubles and try to troubleshoot it but you don't have I peer ability and it makes no sense to troubleshoot OSPF iterations adjacency if you don't have physical connectivity if you don't have proper balance or if your physical link between routers I don't know isn't done state so my suggestion here is use common common sense so if you need to configure IPSec first of all ensures that there is physical link in proper state there is routing exchange if you need routing exchange the Rings IP reach ability and finally you should start configuring IP psycho troubleshooting IPSec and actually this approach applies to basically every technology I know so for example it makes no sense to configure or troubleshoot boot from I skies if your UCS chassis is not is not discovered yet so again I use common sense and do things in proper order so in order to avoid mistakes here you should take a look at your question paper read it from A to Z I read all tasks and come up with an action plan how you would tackle Hollywood tackle this exam as a whole not per section not per task but as a whole if we fail to do so you may find yourself in a very difficult situation so for example let's say you configure something in section one and in three hours maybe in four hours and five hours you find out that in section five there is a task which has interdependence II with tasks from section one and you need to reconfigure something in section one but you already configured it maybe your troubleshoot something maybe you did proper verification for all villains or IP addresses that all this stuff is correct and now you need to reconfigure it from from scratch this is obviously not a good situation so again read through the whole question paper identify action plan identify interdependencies between different sections between tasks and different sections etcetera etcetera etcetera so come up with a reasonable action plan with reasonable order of operation and also there is one more thing here which is related to time management so we should be aware of all things in your lab which may take some time so for example if you need to do a reboot of your router of of your switch which obviously takes I don't know three five maybe seven minutes you should be aware of that all for example there are some things which take time by design for example a blade or racks or boot process so if you need to reboot your router switch if you need to boot blade and you started that process you initiated you shouldn't be just sitting at staring at your CLI and wait until boots while it is booting or rebooting you should be doing other tasks and in order to not spend your time again just staring at your screen so be aware of it again lab is quiet big you have lots of complex tasks you don't have that luxury to spend some time just staring at your screen so that's all for that reason again let's move forward so we have only two more reasons to discuss here and let's start with low attention to details lots of people fail a lab exam because they didn't pay enough attention to detail and let me clarify what I mean by that first of all if you have any restrictions in your question paper you should honor it for example if you are asked if you are asked not to configure static routes do not configure static routes if you are asked to configure specific multicast mode configure that specific multicast mode not other one also if there are if you are given some specific IDs on names for objects or policies use them exactly the same way they are presented to you again in a question paper so if you are asked to configure VLAN 10 configure VLAN 10 not be known 100 not be known 1000 not be known 110 just VLAN 10 the same way as it stated if there is a name for that field a question paper for example bill and prod and protease is in capitals configure it the same way prod in capitals not prod in lowercase or not some different name and not leave that will result name at all so if that bill has some name you should configure it and also you know in your lab you may face traps or tricks unfortunately here I can share with you examples because obviously it will violate exam rules but a general recommendation here would be to carefully read the question paper and pay attention to it inside the question statements there could be traps but also there could be tips so it could be also useful for you so again read it very carefully and also you should plan some time to check to verify your lab when you are finished so when you finished all troubleshooting all configuration you should some some time to check that your solution is compliant with restrictions that you used proper names proper IDs etc etc again in my opinion as I told you at the beginning I felt one of my attempts and I think that I failed it because of actually low tension to details and traps inside the lab so just pay proper attention and lastly reason I want to discuss today is related to lack a fundamental knowledge so all issues with already discussed they are fixable and you can fix them quite easy and quite fast but if you don't have fundamental knowledge unfortunately unfortunately this issue you can't fix it fast or easy so if you don't know technology chances of passing lab exam are very very thing but anyways if you manage to pass your lab exam somehow but you still for some reason don't know fundamental knowledge for the track again that's not a good situation so in order to get a society level job you will still be interviewed and just imagine what happens in that case if you don't know technology for which you have expert level certification so just keep in mind obviously you should know that stuff which are going to configure in your lab exam there is no other way so does that being said that's pretty much it to summarize I would I would like to mention that first of all don't do stupid mistakes know your location know how to get there be aware that lab starts early etc etc etc next be aware of health and body related issues so have a proper sleep don't eat too much don't feel sleepy be in a good in a good shape in a good state both in terms of your body and your brain next don't rely on Proctor for underlying project too much again this AE is about your own independent decisions that's what Cisco tests you for next pay attention to time management and prioritization again come up with proper plan come up with proper order and read the whole question paper at the very beginning and again do stuff in order which makes sense next way attention to details so be aware of restrictions be aware of i d--'s proper names for objects or policies and finally obviously you should have proper fundamental knowledge for the technology you are trying to pass a CSA you lab exam for so with that being said I wish you good luck I know that this exam is very tough I tried it three times passed on due to so again good luck have fun and get your si si si

Channel: Sneaky Subnet

Views: 2,491

Rating: 4.768116 out of 5

Keywords: ccie, cisco ccie, ccie lab, ccie exam, ccie rs, ccie dc, cisco, cisco certification, ccie lab exam, ccie routing and switching, ccie data center, data center, routing and switching, ccie enterprise infrastructure, cisco expert, expert

Id: RUasCHs6WxE

Length: 17min 7sec (1027 seconds)

Published: Mon Feb 10 2020