RE: task analysis

Here are some pointers I think you should keep in mind:

- read EVERY word very carefully (including the task sub-heading). Often times, the choice of configuration or tool comes down to ONE word.
- use the point value of the task to help gauge the relative level of difficulty, or the amount of configuration required, or both.
- remember the scope of tasks as outlined in my Expanded Blueprint. An extreme example would be - using OSPF MD5 authentication to protect updates between the OSPF speakers as opposed to building an IPSec tunnel! :)
- if some additional configuration cannot hurt (and could only help) - go for it. A simple example would be: sw mo acc; sw acc vlan 10, as oppossed to simply sw acc vlan 10.

Anthony Sequeira
ine.com

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of GS
Sent: Friday, December 03, 2010 2:39 PM
To: Cisco certification
Subject: task analysis

dear Experts ...

When interpreting the task requirement, how do you know whether you are under/over-analyzing it?
If it under-analyzed, you risk of losing points. If it is over-analyzed, you risk of losing time.

The mind chatter in my mind goes like this: "hey ... this is an expert-level exam, it can't be that simple" or "they can't be serious in asking you to do X,Y,Z in such a limited time just for N points".

I know this is a judgement call, but any suggestion/recommendation is appreciated.

thanks!

Blogs and organic groups at http://www.ccie.net
Received on Fri Dec 03 2010 - 16:28:45 ART