You are not getting too close at all

 

So right now the troubleshooting is a part of a single test.

 

Based on the response of Yusuf they are in the future going to break the
test apart like they have with R&S version 4.0 into three sections

30 minutes OEQ

2.5 hours Troubleshooting test.

You then connect to a separate rack of equipment and

5 hours configuration.

 

That is not the current format but will be moving to it possibly even with
the version 3.0 of Security

 

This is a big reason why in volume 1 we have done both a troubleshooting lab
and a configuration for each technology as I could see that this was
becoming a larger portion of the test.

 

Regards,

 

Tyson Scott - CCIE #13513 R&S and Security

Technical Instructor - IPexpert, Inc.


Telephone: +1.810.326.1444 
Cell: +1.248.504.7309
Fax: +1.810.454.0130
Mailto:  [email protected]

 

Join our free online support and peer group communities:
<http://www.IPexpert.com/communities> http://www.IPexpert.com/communities

 

IPexpert - The Global Leader in Self-Study, Classroom-Based, Video On Demand
and Audio Certification Training Tools for the Cisco CCIE R&S Lab, CCIE
Security Lab, CCIE Service Provider Lab , CCIE Voice Lab and CCIE Storage
Lab Certifications.

 

From: Stuart Hare [mailto:[email protected]] 
Sent: Monday, June 29, 2009 5:43 PM
To: Tyson Scott
Subject: Troubleshooting

 

Tyson,

 

Quick question mate on troubleshooting sections, as Im a bit nervous about
about asking this on the forum to Yusuf, as Im not sure if Im cutting a
little close to the edge.

He mentioned that there would be no troubleshooting section for security
currently, but Im now confused about what they class as a troubleshooting
section.

Anyone who has took the lab knows that there are tasks in the lab that are
partially configured or broken that you need to troubleshoot to get working,
wouldnt this be classed as just that, or do you think they are going back to
something similar to the 2 day lab where troubleshooting played a huge part?


Stu


-- 
Stuart Hare

[email protected]



Reply via email to