主页 > CCIE系列认证> CCIE协作 > 实验考试


The Cisco CCIE® Collaboration lab exam is an eight-hour, hands-on exam which requires candidates to configure, and troubleshoot a series of complex network scenarios. The candidate will need to understand how the network and service components interoperate, and how the functional requirements translate into specific device configurations. Knowledge of troubleshooting is an important skill and candidates are expected to diagnose and solve issues as part of the CCIE Collaboration lab exam. The candidate will not configure all end-user systems; however, the candidate will be responsible for all devices residing in the network.


Lab Exam Topics


Lab Equipment and Software


Lab Exam v1.0 Format

(This lab format is applicable for lab exams scheduled BEFORE July 23, 2018.)


The CCIE® Collaboration lab v1.0 exam is a web-based delivery infrastructure which consists of one module. The Cisco documentation CD is available in the lab room, but the exam assumes knowledge of the more common protocols and technologies. The documentation can only be navigated using the index; the search function has been disabled. No outside reference materials are permitted in the lab room. You must report any suspected equipment issues to the proctor during the exam; adjustments cannot be made once the exam is over.


Each question on the lab has specific criterion. The labs are graded by proctors who ensure the criterion is met and points are awarded accordingly. The proctors use automatic tools to gather information from the routers to perform some preliminary evaluations, but the final determination of a correct or incorrect configuration is done by a trained proctor.


Lab Exam v2.0 Format

(This format is only applicable for lab exams scheduled ONJuly 23, 2018 and beyond.)


The CCIE® Collaboration v2.0 unifies written and lab exam topics into a unique curriculum, while explicitly disclosing which domains pertain to which exam, and the relative weight of each domain. In addition, the lab v2.0 exam consists of three modules:


  • Module 1: Troubleshooting
  • Module 2: Diagnostic
  • Module 3: Configuration


The modules in the lab exam are delivered in a fixed sequence. First is the Troubleshooting module, followed by the Diagnostic module, and lastly the Configuration module. The entire lab exam lasts up to eight hours.


It is important to note that the system does not allow the candidate to go back and forth between modules. When working in the Troubleshooting module, the candidates can choose to get extra 30 minutes in addition of two hours originally given to complete the Troubleshooting module. However, the candidate cannot see the Configuration module yet, and does not know where the extra time will be needed. If the candidate decides to use the extra 30 minutes for Troubleshooting module, the candidate will have only four and a half hours to complete the entire Configuration module. To maintain the total exam time to eight hours, the optional 30 minutes that the candidate decided to use in the Troubleshooting module is deducted automatically from the time originally allocated for the Configuration module. On the contrary, if the candidate spends only two hours in the Troubleshooting module, the Configuration module is credited by the time gained, therefore, the candidate will have five hours to complete the last module.


The Web-Based delivery system displays a warning message when the two hours has expired in the Troubleshooting module. The system asks if the candidate wants to continue working in the Troubleshooting module, adding up to extra 30 minutes; or if the candidate wants to stop working on the Troubleshooting module and advance to the next module.




Module 1: Troubleshooting

The Troubleshooting module delivers incidents that are independent of each other, which means that the resolution of one incident does not depend on the resolution of another.


The topology that is used in the Troubleshooting module is different than the topology used in the Configuration module. The devices and appliances used in the Troubleshooting module are completely virtualized.


The length of the Troubleshooting module is two hours; however, the candidate can borrow up to 30 minutes from the Configuration module. In other words, the candidate can choose to use the extra 30 minutes on Troubleshooting module or Configuration module.


Module 2: Diagnostics

The new Diagnostic module, 60 minutes in length, focuses on the skills required to properly diagnose issues in a collaboration network, without having access to actual collaboration network devices and applications. The main objective of the Diagnostic module is to assess the following key diagnostic skills:

  • Analyze
  • Correlate: Discerning multiple sources of documentation (such as e-mail threads, network topology diagrams, console outputs, logs and traces, and even traffic captures.)

While these diagnostic activities are naturally part of overall troubleshooting skills, they have been designed as a separate lab module because the format of the items is significantly different. In the Troubleshooting module, the candidate needs to be able to troubleshoot and resolve issues on actual collaboration network devices and applications.


In the Diagnostic module candidates need to make choices between pre-defined options to either indicate:

  • What is the root cause of the issue?
  • Where is the issue located in the diagram?
  • What critical piece of information allows us to identify what the root cause is?
  • What piece of information is missing to be able to identify the root cause?


The Diagnostic module does not provide actual access to any devices or applications; rather, it provides the candidate with a set of documentation that represents a snapshot of a realistic situation that might present itself at a given point in time to a collaboration engineer in an investigative process. For example, a support engineer might need to provide the root cause analysis to the customer, or help a colleague who is stuck in a troubleshooting process; or summarize transpired investigation steps.


Within the Diagnostic module, the items are presented in a format that is similar to the Written exam. It includes:

  • Multiple-Choice (single answer or multiple answers).
  • Drag-and-Drop type style.
  • Point-and-Click on diagrams.

The Diagnostic module questions (called tickets) contain a set of documentation that the candidate must consult to understand the problem scenario. Then in turn, the candidate analyzes and correlates information (after discerning between valuable and worthless information) to make a right choice among the predefined options listed in the item.

The tickets do not require candidates to write anything to provide the answer. All tickets are Close-Ended, in another words the grading is deterministic, which ensures fair and consistent scoring. This approach also helps to grant credit to the candidates that accurately identify the root cause of a networking issue, but fail to resolve it within the defined constraints, which the Troubleshooting module does not offer.


Real-Life experience is certainly the best training to prepare for the module. However, real-life experience is embedded when preparing for the Troubleshooting module. Candidates with limited experience should focus on discovering, practicing and applying efficient and effective troubleshooting methodologies that are used for any realistic networking challenge.


Module 3: Configuration

The Configuration module is conducted in a topology that closely resembles an actual production Collaboration network with various key components.

Although the major part of this module is based on virtual instances of Cisco collaboration appliances, you might be asked to work with physical devices as well.



In order to pass the lab exam, the candidate must meet these two conditions:

  1. The total sum of all module scores must be at least the minimum value of the overall cut score or higher.
  2. The minimum cut score of each individual module must be achieved.


The reason for these criteria is to prevent the candidate from passing the lab exam while failing or even bypassing a module, for example, the Diagnostic module.


The point value of each item in each lab module is shown on  the candidate guide, which is provided at the lab exam. The points are granted  only when all the criteria of the item are met. No partial score is granted on  any item.





Candidates can review lab exam results online (login required), usually within 48 hours. Results are Pass/Fail and failing score reports indicate major topic areas where additional study and preparation may be useful.


Reevaluation of Lab Results

A Reread involves having a second proctor load your configurations into a rack to re-create the test and re-score the entire exam.  Rereads are available for the Routing and Switching, and Service Provider technology tracks.


A Review involves having a second proctor verify your answers and any applicable system-generated debug data saved from your exam. Reviews are available for all other tracks.


Payment Terms

Candidates to make your request within 14 days following the exam date by using the "Request for Reread" link next to the lab record. A Reread costs ,000 USD and a Review costs 0 USD. Payment is made online via credit card and the Reread or Review will be initiated upon successful payment. You may not cancel the appeal request once the process has been initiated. Refunds are given only when results change from fail to pass.


Lab Locations

CCIE lab exams are offered at nine permanent lab facilities at Cisco locations around the world, and various mobile lab locations. Visit CCIE Lab Exam Locations to learn more about the locations,  detailed information regarding start times, directions to facilities and hotel recommendations


Lab and Practical Exam Registration

Candidates who have taken and passed the CCIE written exam are eligible to schedule the lab and practical exams. Visit CCIE – Book Your Exam for registration details.