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

战场攻略–第二部分

创建于: 2014-12-24 15:18:00          

在我之前博客“战场攻略-第一部分”中,我已经提到了一些你可以用在攻克CCIE路由和交换笔试及实验考试中故障排除部分的考试攻略。下面是考试攻略第二部分的内容。我们将讨论在实验考试中Diagnostic和Configuration部分的考试攻略。

 

 

Diagnostic考试 

  • 快速浏览下不同的小题,明确不同小题的答题格式(是多选题,点选题还是拖拽题),然后可以选择一题选项最少的问题先答(一般选项比较少的有可能意味着该问题相对简单。)
  • 将每个题看做是一个单独的情景状态。很有可能,组成该题目的子问题代表着每个得分的机会,有可能互相关联。
  • 快速回顾已提供的信息资源(包括题目本身,选项,提示文档,其他资源以及题目大纲)找到这些信息所处的位置可以帮助你快速对题目有一个初步的了解。
  • 仔细阅读题目及选项,明确题目要求你利用信息资源去解答的内容。
  • 找出并排除其他不相关的选项。如果有很多不确定的选项,需要根据其合理性,优先选择答案。
  • 使用逻辑故障排除法来了解网络症状并利用题目提供的信息来判断最有可能的形成该症状的原因。
  • 明确题目中所问及的要求,评估每个解决方案(根据提供给你的合理的答案选项);然后根据信息进行分析。
  • 将考试中提供给你的信息串联起来,再确认或者排除你的直觉判断,仅留下一个唯一的可能的解决方案。记住Diagnostic的题目每个仅只能提供一个解决方案。
  • 不要急于下结论。始终利用提供的文档客观地建立你的观点,最终确认你的解决方案。
  • 要留意花在每道题目上的时间,当时间快用完时,注意提示信息。当还剩下最后5分钟时倒计时条将会变成红色。
  • 使用在web界面上的导航功能来尽量减少滚动。表格里面的内容始终是可见的,会根据情景进行动态更新。你可以在另一个弹窗中打开拓扑图。

 

Configuration考试 

  • 快速浏览下所有的考试部分,找出高分的题目及相对低分的题目,找到题目之间互相之间的关系。
  • 根据你对题目互相之间关系的评估,决定你配置不同场景考题的顺序。
  • 根据你喜欢的方式,挑选考题来解答(比如,根据每道题的分值,需配置的设备的数量,考题的需求数量及考题中需求的表达清晰度等)。
  • 以每题为单位:仔细阅读所有考题的要求并找出显性及隐性需求。也就是说,有些考题需求很明确,而有些其他考题则通过给出的结果或附加的制约条件,含蓄地测试考生对其未明确显示的知识、功能或特性等掌握程度。
  • 记录每道题的回答进度以及你解答所有要求的自信心相对强度(你可以使用草稿纸或者电脑中的Notepad来记录)。
  • 留意并管理好你的答题时间。上一篇文章中也有提到,要在心里设定好“每题最长答题时间”。
  • 预测你的解决方案将会带来的效果,并计划好步骤来可靠的验证并核实结果。
  • 记得在跳到configuration模块之前要验证下之前配置好的内容。
  • 记住为了避免在答后面题目时出现多个相关题目均失分的情况,你可以尝试使用某项禁止的解决方案,这样能降低失分。
  • 当考生在设计解决方案时,在都能实施的情况下,选择能够快速实施的聪明解决方案要比用更繁琐的解决方案要好。比如,那些修改少且能够快速被复制及拷贝到多种设备中的配置脚本就是很好的解决方案选择。
  • 用系统地方法实施解决方案的配置能够减少遗漏配置需求-比如遗漏配置一个步骤,节点或接口等。例如,loopback 接口或在配置路由协议中的根vlan的前缀都是非常容易被遗漏的,不幸的是这些小错误将会让你付出非常昂贵的代价,这已在上一次的博客中已经提到过了…考生非常需要注意细节。
  • 验证已完成的答题结果,使用合适的show 命令来验证变量及计数的实际状态。
  • 及时保存配置的内容。尤其是那些已经完成验证的解决方案。须注意的是虽然不强制要求将配置保存在NVRAM中,但是保存在NVRAM中还是很推荐操作的。计分脚本会在你离开考试中心时及时加载,但设备不会在计分时重新加载。
  • 避免在最后一刻出现大的改动。另外,如果你没有时间完成全部考题,那么你就要考虑提前复查并验证之前完成的答题,而不是继续往下解决那些你可能无法完成的考题,或是会之前答过的解决方案,这样会打乱已回答完成的内容。
  • 请注意,不完整的解决方案是不能够得分的。必须完成所有的需求及指导,才可以获得该题的所有分数。
  • 使用提供给你的工具(Microsoft Windows Notepad, 复制/黏贴,Cisco documentation, 草稿纸及彩色笔)。
  • 提前了解如何使用Cisco documentation,在处理核心考题时不要依赖于它。知道主要功能及协议在documentation中的位置。
  • 熟悉在考试中使用的Web界面。

 

我希望这篇博客能够为你带来帮助,欢迎你的回复及评论。
祝大家新年快乐,学习愉快!

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

In my previous post, we looked at some useful tactics that you can employ when tackling the CCIE R&S written exam and the Troubleshooting portion of the CCIE R&S lab exam. Here in this second part of my compilation of tactics, we’ll look at the Diagnostic and Configuration components of the lab exam.

 

Diagnostic Exam

  • Quickly glance over the different tickets, identify the format of the answer choices (multiple choice, point-and-click, drag-and-drop) and choose which item to start with, perhaps the one with the fewest number of answer choices. (An item with fewer choices is probably slightly easier than one with more choices.)
  • Work each ticket as a unique scenario. Most likely, the sub-questions that make up the ticket, and represent an opportunity to score, are very much related to each other.
  • Quickly review the available resources (including the question itself, answer choices, documents and other resources, and guidelines) to get an initial overview of what information is available to you and where it is located.
  • Carefully read the question and answer choices to understand exactly what you are being asked to do with the resources.
  • Identify and eliminate any absurd answer choices, if any; and, ideally, try to prioritize the remaining answer choices according to plausibility.
  • Use a logical troubleshooting methodology to understand the symptoms and identify the most likely causes based on the documentation and resources that have been provided.
  • Keeping in mind the specific question being asked, evaluate each possible solution (based on the plausible answer choices available to you) and build an analysis based on the evidence before you.
  • Correlate information from your documents in order to further confirm or infirm your hunches and isolate things down to the only possible solution. Remember that Diagnostic items always have only one possible solution!
  • Take care to avoid jumping to conclusions. Always use the documentation to objectively build your argument and confirm your solution.
  • Keep track of the time spent on each item and watch out for the warning message when time is almost expired. The countdown timer will also turn red when there are only 5 minutes left.
  • Use the navigation features in the web interface in order to minimize scrolling. A table of contents is always visible and will be dynamically updated depending on the context. Open topology diagrams in a separate pop-up window.

 

Configuration Exam

  • Quickly glance over all sections of the exam and try to identify the core items versus the stub ones; that is, try to identify the item interdependency.
  • Based on your assessment of how the items interrelate, determine the overall sequence of implementation that you will follow to configure the exam scenario.
  • Cherry-pick items according to your preferred approach (for example, according to score point value, the number of devices you need to configure, the number of requirements and clarity with which they are presented, etc.).
  • Work each item as a unit: carefully read all requirements and identify explicit versus implicit requirements. That is, some requirements are very clear in what they ask for while others might implicitly test knowledge of some option or functionality or feature without calling it explicitly but by providing a description of the outcome or by adding some constraints.
  • Keep track of your overall progress for each item, and your relative confidence with how you solved all the requirements. (You may use scratch paper or a Microsoft Windows notepad document for this purpose).
  • Keep an eye on the clock and manage your time. Set a mental timer “item max-time” as discussed in previous posts.
  • Anticipate the expected effect of your solution and plan the procedure to reliably verify and validate its outcome.
  • Remember to verify what is already preconfigured before jumping to configuration mode right away.
  • Keep in mind that it might be better to use a prohibited solution and lose points for one item only as compared to losing many more points for multiple dependent items downstream.
  • When designing your solution, try to find a smart configuration option that is much faster to implement compared to other tedious options, though both ways may be valid. For example, think about configuration scripts that can be quickly copied and pasted into multiple devices with minimal changes.
  • Implement your solution with a very systematic approach in order to minimize the possibility of forgetting to configure a required step, node, or interface. For example, it is very easy to miss a loopback interface or a stub vlan prefix into the routing protocol configuration but unfortunately this would be a very expensive mistake as discussed in previous posts... Attention to the details! 
  • Verify that the expected outcome has been achieved and use appropriate show commands to validate the actual status of any variable or counter.
  • Save your configurations often, especially after having validated any solution. Note that it’s not mandatory to save a configuration to NVRAM, but it is highly recommended. The grading script is run right after you leave the examination center and devices are not reloaded before doing so.
  • Avoid large changes at the last minute. In addition, if you won’t have time to complete all items, consider going back and further verifying the work that is completed rather than moving forward with an item that you may not be able to complete or that may break previous solutions.
  • Keep in mind that a partial solution is not acceptable and doesn't entitle you to partial scoring! All requirements and guidelines must be met in order to collect the points for an item.
  • Use the tools that are available to you (Microsoft Windows Notepad, copy/paste, Cisco documentation, scratch paper and colored pens).
  • Know your way around Cisco documentation in advance and do not rely on it for handling core topics. Know at the outset where most features and protocols are documented.
  • Familiarize yourself with the web interface used in the exam. Both the Cisco Learning Labs (https://learningnetworkstore.cisco.com/cisco-learning-labs ) and the Cisco CCIE Lab Builder (https://learningnetworkstore.cisco.com/cisco-ccie-lab-builder ) use the same delivery engine as the lab exam, so they make for good practice with the interface.

 

I hope this is helpful. As always, please feel free to comment below. 
Happy end of the year to everyone and happy studying!

评论 (0)