Exam Objectives and Project Planning
Know what the exam measures
The ACA-style exam blends software skill with design judgment. Objectives typically cluster into document setup, asset handling, type and color, editing and effects, and output. Learn each cluster's vocabulary: artboard, bleed, safe area, resolution, color mode, proof, preflight. Questions often ask which setting or workflow satisfies a stated intent, not which button exists.
Plan before you build
A credible plan states audience, purpose, medium, and constraints, then derives specifications from them. A print poster implies CMYK, 300 ppi raster assets, bleed and crop marks; a web banner implies RGB, pixel dimensions, and file-size limits. The trap is a question that describes a deliverable and offers settings that are individually valid but wrong for that medium - read the medium first, then judge the setting.
Client-facing discipline
Understand revision cycles, versioning, and handoff: collect fonts or outline them, package linked assets, and keep an editable master separate from exported copies. Expect questions on what to deliver to a printer versus a client versus a developer.
Worked example
A candidate is asked for settings for a two-sided A5 flyer for offset printing. Rule of thumb: derive from medium. Print → CMYK, 300 ppi images, 3 mm bleed, crop marks, fonts embedded or outlined. A distractor offering RGB at 72 ppi is a web answer; another offering bleed but no crop marks is incomplete.
Traps to watch
Absolute words (always, never), options that confuse file format with color mode, and scenarios where the correct answer is 'ask the client' or 'check the printer's spec'.