CLA (C language) exam-day guide

Stop expanding your scope. Review your own error log and the topics you have repeatedly missed rather than starting new material. For a C-language exam, prioritize the areas that are both high-yield and easy to lose points on: pointer and array decay, pointer arithmetic, const placement and what it qualifies, the difference between declarations and definitions, storage duration and linkage, struct layout and padding, and the semantics of the standard library functions you use most. Re-derive the tricky ones on paper: what a declaration means when read right-to-left, why a two-dimensional array parameter needs a column count, and what happens when you pass an array to a function. Do two or three timed sets under exam conditions, then review every wrong answer to the underlying rule, not just the correct option.

Write a one-page personal cheat sheet in your own words covering only rules you have gotten wrong: operator precedence and associativity traps, integer promotion and usual arithmetic conversions, signed versus unsigned comparison pitfalls, short-circuit evaluation, sequence points and undefined behavior, string function return values, and the difference between the preprocessor and the compiler. Rewrite it from memory the next day. This sheet is for study only; leave it at home on test day unless the provider explicitly permits reference material.

Confirm logistics in writing: appointment time, test-center address or remote-testing requirements, ID requirements, permitted aids, break policy, and the reschedule deadline. Fix sleep now rather than the night before. Prepare clothes in layers, since testing rooms are often cold, and check the weather and transit schedule for the morning.

Do a light review only: skim your cheat sheet, the error log, and one or two code-reading examples. No new topics and no full-length practice test the day before; fatigue costs more points than one more topic gains. Pack your ID, confirmation, and any permitted items in one bag and place it by the door. Set two alarms. Confirm the route and departure time, including buffer for check-in. Eat a normal dinner, avoid heavy caffeine late in the day, and go to bed at your usual time.

Eat a normal breakfast and hydrate, but not excessively if breaks are limited. Arrive early per the provider's instructions. Leave your phone, smartwatch, and notes stowed as directed. During check-in, follow the proctor's instructions exactly and ask where the restroom is before you are seated. Once seated, use any provided scratch material to write down the few rules you most often forget before the clock starts, if the provider allows writing before the exam begins.

Read each question to the end before answering; many C questions hinge on one qualifier such as const, static, or the exact type of an argument. For code-reading items, trace values on paper rather than in your head, and check loop bounds, off-by-one indexing, and whether a pointer is dereferenced before or after increment. For questions about undefined or implementation-defined behavior, answer what the standard guarantees, not what your compiler happens to do. If a question is genuinely unfamiliar, mark your best answer and move on; do not let one item consume the time budget for several. Track the clock against the number of questions remaining and reserve the last few minutes to confirm you have answered every item if the format penalizes blanks.

Note which topics actually appeared and how you felt about them while it is fresh, since this guides a retake if needed. Confirm with the provider when results are released and how to access them. If you did not pass, check the retake waiting period and any diagnostic report before scheduling again.