During preflight, why are links checked?

During preflight, why are links checked?

• A. To ensure links resolve to valid, accessible assets.
• B. To improve link aesthetics.
• C. To change hyperlink color.
• D. To embed fonts into linked files.

Answer: (A)

Link checks during preflight ensure that every reference points to a real, accessible asset. In production workflows, documents often rely on linked images, graphics, or external resources. The preflight step verifies that the file paths or URLs actually resolve to existing files or reachable destinations so the final output can render correctly. If a link is broken or the asset isn’t available, you could end up with missing images or failed loads, which undermines the integrity of the document. This matters because catching and fixing these issues early prevents surprises in proofs or final delivery. The other options don’t fit the purpose: improving aesthetics, changing hyperlink color, or embedding fonts into linked files are separate tasks unrelated to ensuring that references actually point to usable resources.

Link checks during preflight ensure that every reference points to a real, accessible asset. In production workflows, documents often rely on linked images, graphics, or external resources. The preflight step verifies that the file paths or URLs actually resolve to existing files or reachable destinations so the final output can render correctly. If a link is broken or the asset isn’t available, you could end up with missing images or failed loads, which undermines the integrity of the document.

This matters because catching and fixing these issues early prevents surprises in proofs or final delivery. The other options don’t fit the purpose: improving aesthetics, changing hyperlink color, or embedding fonts into linked files are separate tasks unrelated to ensuring that references actually point to usable resources.