From: Jay Hennigan (jay@xxxxxxxx)
Date: Fri Jan 11 2002 - 03:27:58 GMT-3
On Fri, 11 Jan 2002, Albert Lu wrote:
> I would also add the points for each section, and also a time column.
>
> Device R1 R2 R3 R4 R5 Cat5 Time
> Section
> 1.1 (4) x x 30m
> 1.2 (1) x x x x 15m
> 1.3 (2) x x 10m
> 2.1 (1) x x 20m
>
> Obviously the time column has to be an estimation. I would base it on
> completing the lab in 6hours, dividing into the way Caslow divides the
> different Levels.
Preparing that would take too long for me. Keep in mind that you will
have no idea as to the number of elements and their point values before
the clock starts ticking. And what seems to be a short simple question
can be a complex tricky one.
What I did was three columns:
Nailed Done Undone
1.1 (4)
1.2 (3)
...
For each item, if I was sure I had nailed it, I'd "X" under the first
column. If I configured but wasn't 100% sure, I'd "X" the second. If I
knew that I hadn't met the requirements or skipped the item, the third.
I'd write the item numbers and point values in order as I came to them.
Then go back and double-check, first do the undone, then test the "Done"
to move to "Nailed". Questions for the proctor on clarifications of the
requirements were typically "done" column items.
> You would have to force yourself to move on if you have not completed the
> section in the allocated time.
With my system, if a question could be skipped and still allow the completion
of further elements, then just mark it as Undone.
> Of course, you would have to take into
> consideration that you can't really move on to sections that are dependent
> on other sections (eg. if FR is not working, IP will not work).
Yep, and this is a big gotcha, dependencies. Best to read the whole
test through with an eye on dependencies and seeing what goes together
first, then dive in. You'll probably want to do things more or less in
the order given, but may want to combine related requirements to configure
two sections at once.
> Why 6 hours? I feel 6 hours is doable, and when you finish the lab with 2
> hours to spare, there is alot less pressure and allows for you to switch
> hats an pretend to be a proctor to pick apart your configs.
>
> Also, finishing the lab in 6 hours does not mean you blindly type in the
> configs and hope that it works in the end. It means you have 90% certainty
> that it is correct, and you have tested each section.
My concern with this approach is that the time spent in creating a time
budget is time that could have been spent configuring, testing, debugging,
or searching for that elusive item on the CD. You get zero points for
outlining a time budget. For each element that you're unsure of, you need
to make a decision as you go in terms of the effort you'll put in to it.
Factors to consider are dependencies of other elements, point value,
and time spent/remaining.
-- Jay Hennigan - CCIE #7880 - Network Administration - jay@west.net NetLojix Communications, Inc. - http://www.netlojix.com/ WestNet: Connecting you to the planet. 805 884-6323
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:24 GMT-3