No offense but that example seems a bit hokey to me. How many quad CCIE's are there in the world now 12? Also, how many of them update route filters for a living? They are usually pretty high up (deserving or no). In Scott's case he was just nominated as everyone's favorite routing protocol.
Re: [j-nsp] 13 Tips for Passing Juniper Lab Tests Scott Morris to: Richard A Steenbergen 06/29/09 05:13 PM Sent by: juniper-nsp-boun...@puck.nether.net Cc: Juniper Puck Please respond to swm I feel a need to jump in here and note that this person noted below was most certainly not me (grin). But yes, you're right, they can't test for stupid. Any of these tests are meant to test technology knowledge. That's done through artificially strange scenarios. The rest is experience. *Scott Morris*, CCIE/x4/ (R&S/ISP-Dial/Security/Service Provider) #4713, JNCIE-M #153, JNCIS-ER, CISSP, et al. CCSI #21903, JNCI-M, JNCI-ER s...@emanon.com Knowledge is power. Power corrupts. Study hard and be Eeeeviiiil...... Richard A Steenbergen wrote: > On Mon, Jun 29, 2009 at 01:14:52PM -0600, Chris Grundemann wrote: > >> New blog post that folks on this list might find interesting / worth >> reading: http://bit.ly/43A7K (13 Tips for Passing Juniper Lab Tests) >> ~Chris >> > > Dude, really? Study a lot, read the question thoroughly, manage your > time carefully? What kind of pussy advice is this? :) I think you forgot > "eat a balanced breakfast" and "sharpen your #2 pencil". :) Only like > 20% of the book it actually on the exam, the only thing studying left me > with was a hurt liver from all the drinking it took to get that QoS crap > out of my head afterwards. > > Seriously though, your best advice is item #1, have some experience. If > you're new to this but you think you want to be a JNCIE, you will be > infinitely better served by getting a job at a company with a decent > network than you will be by putting 1000 olives in your basement and > memorizing the handful of artificial scenerios that they were able to > squeeze into an 8 hour lab. And probably have a lot more money at the > end of the day too. > > I once had a quad CCIE customer who intentionally configured his router > to leak a full table from their other transit provider to me, because > (and I really wish I was joking here) "why does it matter, your > prefix-list will catch it anyways". Alas they haven't figured out a > comprehensive way to test for stupid yet. :) > > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
