Reviewing a #CCDE book is definitely taking me back to the days of preparing for and taking the practical. Here are some of the things that can help you perform your best. A 🧵
Connect with the scenario. This may seem obvious but you can't approach this without putting you in the shoes of the network designer. In most exams, you answer a question in isolation. Here, you go along a story and have to live with your decision, and the business as well.
A scenario will have background information. Is it relevant how much revenue the business has? How many stores they have? Or is it there just to make you find more relevant information such as current problem areas or iniatives? Learn to filter this info.
Be conservative in what you highlight. Highlighting is for key information. Don't get carried away with using different colors, unless you feel that it helps you. Most often you should highlight business considerations rather than then number of a ports in a switch.
This is one of the most mentally challenging exams you can take. You will not be comfortable. You will most likely feel like you are failing. This is normal. You may have answered something correctly but the story takes you somewhere else. This is by design.
Do not answer questions in isolation. Always connect with the scenario and back to key details like architectural guidelines, business requirements and constraints. The question may seem simple but might be checking if you are adhering to what was communicated previously.
Do not answer based on "best practices" or based on what protocols you prefer over others. You have bias but you must set this aside in the exam. Maybe ISIS is cooler than OSPF but you have to pick what is best for the business.
This means that sometimes the correct answer is something that seems like obsolete tech or a suboptimal solution, which may very well be true, but it is the best design based on business requirements and constraints. You must always consider this.
This is an exam where you may feel overloaded with information. You have to be comfortable reading a lot of text, skimming through it to find important details. You get blasted with e-mails and documents. Build mental stamina by reading and working through scenarios.
As in any exam when searching for the correct answer you will try to find what answers are incorrect or suboptimal. You can throw away what will not work but what may seem suboptimal may be the right answer. Keep in mind what you learned earlier and highlighted.
It takes a lot of practice, even for very skilled people to prepare for this exam. Having deep technical knowledge is not enough, you need to build that design mindset. It's challenging and takes different amount of time for different people. The process is super beneficial.
Good luck in your studies! Let me know if you have questions and I will do my best to respond.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
It can be difficult getting the experience to become a network architect, but there are many things you can do even if your role today does not involve design. In this thread I will give you some pointers and feel free to add your own.
1/x
The first step is always the fundamentals. You need to have a good level of understanding of the fundamentals. If you don't know OSPF or ISIS, how will you know when to pick one over the other? You have to start with the fundamentals and get some operational experience also. 2/x
Start reading books on network design. Even if you aren't going for a certification, there are books like the CCDE study guide by my friend @CCDE066 There are books for the CCDP as well. You have the excellent The Art of network Architecture by @LadyNetwkr and @rtggeek 3/x
Some thoughts on CL outage, sorry @ioshints too lazy to blog this right now 🙂
First problem was input validation. It shouldn't have been possible to enter wildcards, but the validation failed (buggy code). It would make sense to add more logic here... 1/x
It shouldn't be allowed to filter traffic belong to CL infra, BGP, ISIS, loopbacks, management etc etc...
Second problem was this was implemented without running tests (from what I can tell). The rule could have been tested on a virtual device first. CP is easy to simulate. 2/x
The fault should have been caught in these tests and and the rules should not have made it to production.
Furthermore, there should be a ruleset, a safety net, of rules you can't override. You shouldn't be able to filter out traffic from the router itself. Think CP. 3/x
I've been working for the same company, Conscia, for more than five years now. This thread will describe why I have stayed and will help managers and leaders to understand how you can keep high performers around.
This is going to take a number of tweets.
Everything starts with culture. You can't fake culture. Forget about ping pong tables, free lunch and things of that nature. Those are fine but they are NOT culture. I don't, and probably most other high performers, have zero fucks to give about things like that.
Culture is something you build from the ground. With passionate employees that want to improve and that want to help others improve. You can try to, and can have some results improving culture, but if the company was built on shit culture, results won't be good.