From: Darby Weaver (darbyweaver@yahoo.com)
Date: Thu Jan 25 2007 - 00:47:55 ART
Alex,
My own experience has been:
1. Do not ask them "how" to do something.
2. Be prepared to troubleshoot the situation - they
will give you your time back if you do have a problem
- they gave me mine back.
3. Know your options and ask guiding questions but not
questions that may indicate or appear to indicate that
you do not know the technology in question.
I had to ask for help 4 times in two labs:
1. Frame relay Question
2. Worm struck my computer.
==============================
1. Wrong lab - they gave me my 1st lab and it did not
match my lab physical layout.
2. Wrong lab again on the same attempt.
==============================================
==============================================
So my overall experiences are limited at best.
A proctor did tell me not enough candidates knew even
how to troubleshoot their frame relay to be able to
discern a hardware problem or their own configuration.
I had to troubleshoot mine and my switching/bridging
in order to validate and convey my concerns to the
proctor in order to get a new lab.
Overall, I have had good experiences with the proctors
I have had.
--- Alex De Gruiter <Alex.deGruiter@didata.com.au>
wrote:
> Hello,
>
> I am looking for the best advice on how to approach
> the proctor.
>
> I tried 2 completely different approaches for each
> of my labs. In the
> 1st I asked a lot of questions and received
> persistent negative
> feedback. So I posted a similar question to this one
> after the 1st lab,
> and I was torn down in flames by certain people who
> stated that I
> "obviously knew nothing"; if I had asked clear,
> reasonable questions, I
> would receive a response.
>
> So I spent time between lab attempts better learning
> the technologies,
> and in the 2nd lab asked very few questions. I
> basically ignored the
> proctor - on the few occassions that I did ask
> questions, I was met with
> a similar response to my 1st attempt.
>
> I am now faced with a dilemma. Due to locality there
> is one location
> that proves particularly practical in my endeavour
> to sit my next, and
> hopefully last, exam. The trouble is that if there
> are any areas of
> ambiguity... And lets face it, there are going to be
> at least 1 or 2
> areas of ambiguity, even small areas, in the lab...
> I honestly am lost
> when it comes to getting clarification from the
> proctor.
>
> So my question is: how can I structure a question in
> such a way that the
> response is useful? And, perhaps, should I simply
> not bother asking any
> questions at all?
>
> Advice appreciated.
>
> Alex
>
>
******************************************************************************
> - NOTICE FROM DIMENSION DATA AUSTRALIA
> This message is confidential, and may contain
> proprietary or legally privileged information. If
> you have received this email in error, please notify
> the sender and delete it immediately.
>
> Internet communications are not secure. You should
> scan this message and any attachments for viruses.
> Under no circumstances do we accept liability for
> any loss or damage which may result from your
> receipt of this message or any attachments.
>
******************************************************************************
>
>
This archive was generated by hypermail 2.1.4 : Thu Feb 08 2007 - 23:46:57 ART