Pointers on How to Pass PhilNITS (FE) - Part II

(this is a sequel to an earlier post : http://abrightfit.blogspot.com/2008/07/pointers-on-how-to-pass-philnits-fe.html)

My previous pointers on passing the PhilNITS-FE exam focuses on the "preparation" stage, this entry focuses on tips for the "actual exam day."

Reminder : General Description of the Exam (both AM and PM exams)

Tips for the AM Exam

• Try to simplify first before computing/solving (especially true for large numbers, decimal points or complicated equations)
• Do not leave any item blank. Actual scoring might have weighted score per choice.
• Do not spend too much time on “conceptual” or definition-type questions if you do not have any idea about it. Better to guess then proceed with next item.
• “Units” are very important during computations
• Choose the best answer when you feel there seems to be more than one correct answer
• Usually you can readily eliminate one or two of the answer choices
• Sometimes you can quickly (but intelligently) guess the correct answers (you may review your answer using the conventional way if there is still time later)
• Review your answers if there is still time remaining. There are no additional points for submitting your papers early
• Suggested time allocation : 1.5 mins per question
  

Tips for the PM Exam

• Decide your language of preference (C, Java) prior to the exam (but quickly scan also the other option, just in case it offers a much simpler problem to solve)
• Tracing the program may be the best way to find the correct answer (so practice your tracing/debugging skills so you can do it very quickly)
• All questions are designed that they can be answered, and “hints” and “clues” can be found within the program/question
• The fewer the sub-questions, the more weight (in points) they carry
• Exam questions are designed with the intent that any examinee with general knowledge can answer them
• Do not get intimidated by technically sounding terms that you are not familiar with, as usually a brief explanation about them is mentioned, or, they are not critical to the actual program
• Do not get overwhelmed by long questions, flowcharts, or codes (if you do, you will fail to properly understand the program flow)
• The longer the question, the more “clues” are mentioned in the question itself
• Sometimes the answers are already inside the question text, and can be found without reading the code or flowchart
• Program modules are often highly independent from each other (as part of a good coding practice), so you can break them down and analyse by modules (instead of analyzing the program flow as a whole)
• It might be a good idea to have a “quick glance” at the answer choices to better understand each question
• It is most likely that you will have to go back and refer to the original questions when answering the sub-questions
• Manage your reading time well (see suggestions for time allocation)
• Suggested time allocation : 15 mins each (for the "Easy" questions #1, 2, 3, 6, 7), 30 mins each (for the "Difficult" questions #4, 5, 8, 9)

Properly Filling Up Your Answer Sheets

• If you filled up your examinee number incorrectly, you get NO SCORE for the entire exam set!
• If you improperly marked your answers, you get NO POINTS for that particular question
• All questions for the morning exam is compulsory. Do not leave any item blank
• If you failed to mark the “Selection Column” (between C and Java questions) properly, you will get NO POINTS for those particular questions
• If you change your answer, completely and neatly erase your previous answer (exams will be checked by scanning machines)

As a last piece of advice, it might be wise to bring little snacks (more of the "brain food" type) and bottled water which you may eat during the long exam. Better bring also packed lunch as it might be hard to find fastfood centers during the exam day (usually falls on a Sunday).