Loading...
首页 > 就业指导> 博客 > 文档

战场攻略–第一部分

创建于: 2014-11-19 18:10:12          

正如我之前博客“你准备好攻克考试了吗?”所承诺的,在这篇博客中我将针对CCIE 路由和交换考试中每个模块的具体攻略做详细的讲解。我会将这些战略要点按照逻辑顺序列出来,当然这也不是硬性的考试战略流程。考生可以依照自己的需要相应地学习。

 

很有可能以下的很多考试战略比较显而易见,但是,尽管如此,我依然非常希望以下战略可以帮助到一些考生。这份列表不尽完整,因此如果你能想到更有效地的考试战略,也请分享给我们。

 

CCIE 路由和交换笔试

  • 仔细地阅读考题,包括题干,问题选项及补充材料等(如果有的话)
  • 排除不太可能,不可能及显而易见的错误答案,找到最可能或最合理的选项。
  • 如果有可能的话,确定答案选项之间的差异
  • 试着了解考题中产品的技术概念
  • 评估你觉得似是而非的选项,将那些表面上看上去似是而非但事实上是“干扰”的选项排除掉(不正确的选项)这样,才能保证正确的选择。
  • 如果你不能立即找到答案,不要过于浪费时间思考此问题,先估一个答案然后开始做下一题。等你有时间或者改变想法时,再回过来重新思考答案。
  • 不要相信“传说”(如“总是选最长的答案”或“总是选第一个或最后一个选项”)

 

CCIE路由和交换实验考试故障排除模块

  • 仔细地阅读所有资料,包括问题,图表及规则。
  • 试着识别每道题最有可能被测试的考点(如二层,三层,四层,控制表及数据表等)
  • 确定每道题的最高分值
  • 根据分值细心筛选每道题,或者先选择回答你感觉非常得心应手的考题,或者基于题目中涉及的hops数量进行筛选。

这个过程会因人而异,但是我建议还是先从低分值的题目开始答起,这样可以建立更多信心并且尽可能多的为自己稳稳地积更多分数。

  • 集中精力在“mini-diagram”在每道题中标示的区域。这些diagram的主要目的就是让你快速地找到相关的设备。他们并不意味着readable,因此你可以保留主要的diagram总在一个弹出的窗口,根据自己的需要调整窗口大小。
  • 不要期望最佳的实验考试场景或实验考试设计。别去试图理解全部场景,但是要集中在mini-diagrams标注的区域,然后找出那个区域需要的配置。在开始答题之前不需要理解全部拓扑结构。
  • 不要让自己长时间陷入任何一个特定的问题的思考中;管理好你的时间!设定每道题的最多答题时间,如果在这段时间中你无法解决这道题,请跳到下一题。等你有时间了再来回顾这道题。
  • 由于逻辑方式的思考可能会带来多种可能,这时通过自问自答的方式来隔绝每种状况,开始发散或缩小可能性。希望你能够将可能性缩小到一个设备,接口或特点。而那个也许就是罪魁祸首。
  • 当你试图证明你的直觉是对的,记得要追踪任何发生的变化以至于你能够在发现自己直觉错误的情况下及时系统地改正。
  • 如果你对你做的配置造成的变化有任何迟疑,你可以重新加载设备,让他们还原为初始的有问题的配置。记得虚拟设备重启要比硬件平台快很多。
  • 在你开始配置你的最后解决方案之前回顾并重新评估题目的要求。
  • 思考时多想几个方案,然后实施最简单或使用最少命令的配置方案。
  • 为每道题目的验证做好笔记记录,做出任何改变对之前已解决的配置有影响要做回归测试。
  • 记录哪些考题已经被解决了,以及你找到答案的那份自信程度。
  • 请把目标放在获得总分的80%上。把所剩的时间用在验证你已答的题目上,而不是去尝试答你未答出的新题目上。记得当你在所有模块中获得的最低分数时,你就不需要在Troubleshooting模块上获得超过80%的成绩!

尽量不要使用Troubleshooting模块中的额外答题时间,因为你可能更需要把这些时间花在Configuration模块上,那里的最低分值概念没有Troulbeshooting和Diagnostic部分来的重要。

 

敬请期待下期

 

---------------------------------------中英文对照------------------------------------

Battlefield Tactics – Part 1

 

As promised in the previous post, here is an attempt at compiling some specific tactics for each CCIE R&S exam module. I tried to order the bullet points with a logical sequence, but it’s not to be considered as a hard-coded process. 

 

Very likely, many of these suggestions will appear quite obvious, but, nevertheless, I really hope that they might prove useful to some candidates. The list is certainly not exhaustive, so if you can think of other effective tactics, please do not hesitate to share them in the comments below.

 

CCIE R&S Written Exam


  • Carefully read the complete test item, including the question stem, answer choices, and supplementary material, if any.
  • Eliminate the unlikely, improbable, or absurd answer choices and identify the most likely or most plausible choices.
  • Identify differences between pairs of answer choices, if any.
  • Try to understand the technical concept that the item is testing.
  • Evaluate the answer choices you’ve determined to be plausible, attempting to eliminate those that might seem plausible on the surface but are nevertheless “distracters” (incorrect answer choices). In this manner, continue to home in on the correct response! 
  • If you can’t find any solution, well, take an educated guess and move on to the next item before you get too bogged down and waste time. But, don’t hesitate to reconsider later if you have time, and change your mind.
  • Do not believe myths (like “always pick the longest answer” or “always choose the first or last option”)!

 

Troubleshooting Module of the CCIE R&S Lab Exam

 

  • Carefully read all resources, including questions, diagrams, and guidelines.
  • Try to identify the most likely topic being tested in each item (for example, Layer 2, Layer 3, Layer 4, control plane versus data plane, etc.).
  • Identify items with a high point value.
  • Cherry-pick items according to their point value, or those revolving around topics with which you feel comfortable, or even based on the number of hops that might be involved (if applicable). This process is quite personal, but I’d recommend actually starting first with items that have a low point value in order to build confidence and start collecting some points as soon as possible.
  • Focus on the region highlighted by the “mini-diagram” that is provided in each item stem. The only purpose of these diagrams is to help you quickly find the device(s) that the item is referring to. They are not meant to be readable, so keep the main diagram open in a pop-up window and resize it to fit your taste and need.
  • Don’t expect best-practice scenarios or designs. Don’t try to understand the whole scenario, but again, focus on the region highlighted by the mini-diagrams and figure out what the configuration is supposed to do in that region. There is no need to understand the whole topology before getting started.
  • Don’t let yourself get mired with a particular item; manage your time! Set a maximum time per item and move on to the next item if you can’t solve an item within that period. Then, come back to it later on if you have time.
  • Question yourself in order to isolate the issue to as few likely cause(s) as possible by using a logical methodology, starting wide and narrowing down to as few hops as possible. Hopefully, you’ll be able to narrow things down to the one device, interface, or feature that is the most likely culprit.
  • As you attempt to confirm your hunches, keep track of any changes that you make so that you can systematically undo them if your hunch is wrong.
  • Use the option to reload devices to their initial broken configuration if you have any doubts about the changes that you made and you want to revert to the initial situation. Remember that the virtual devices reboot much faster compared to hardware platforms.
  • Review or re-evaluate the guidelines before jumping to configure your final solution.
  • Think of alternate solutions and go for the simplest and/or the least demanding in terms of configuration work.
  • Keep a notepad with the validation tests for each item, and do regression tests when changing anything that could impact previously resolved items.
  • Keep track of which items were resolved, as well as the confidence level you possess in terms of having found the solution.
  • Aim for achieving 80 percent of the total score and use the last few minutes to verify your work rather than attempting a new item. Remember that while you need to achieve the minimum score in all modules, you don’t actually need more than 80 percent in the Troubleshooting Module!
  • Try not to use the optional extra time in the Troubleshooting Module, as you will most likely need that time in the Configuration Module, where the minimum score concept isn’t as important as for Troubleshooting and Diagnostic...

 

To be continued…

评论 (0)