How to handle Longgggg questions ?
In going over many of the Practice exams, I have come
across many questions that are over a paragraph long,
or seem to tell a story and go on forever and ever.
This might result in wasting needed time to review other
important questions on the exam. What is the best strategy
for dealing with these "long" questions, thanks, Ric
across many questions that are over a paragraph long,
or seem to tell a story and go on forever and ever.
This might result in wasting needed time to review other
important questions on the exam. What is the best strategy
for dealing with these "long" questions, thanks, Ric
Richard Krenzel
Comments
-
kujayhawk93 Member Posts: 355ricktea wrote:This might result in wasting needed time to review other
important questions on the exam
OK, that's my smarta$$ answer. My serious answer is that you need to treat all 100 questions on the exam as being important, and if you run into a long one, just read it and answer. Stop looking for shortcuts. -
ricktea Inactive Imported Users Posts: 118thanks, appreciate the advice, I like to read questions carefully
but some of them go on and on.Richard Krenzel -
mikej412 Member Posts: 10,086 ■■■■■■■■■■One trick that may work -- jump to the end of the question first and see if it asks "the question." Once you have an idea what they might be looking for then you'll have a better idea what information is important and what isn't.
This works for me on Cisco questions where they may have an "exhibit" (network diagram, configuration) and then a shaggy dog question.
You still want to read the entire question and all the answers carefully -- you just don't to waste lots of time trying to analyse and understand things that may not be part of the answer.:mike: Cisco Certifications -- Collect the Entire Set! -
ricktea Inactive Imported Users Posts: 118I have tried that before, you do tend to skim down at the bottom
and even look at the answers also to get some idea what they
are asking, and then go back to the question and read it again.
thanksRichard Krenzel