A media organisation must distinguish between two content-authenticity technologies for its AI image pipeline: one embeds a cryptographically signed record of an asset's origin and edit history as metadata travelling alongside the file, while the other embeds an imperceptible signal directly into the pixels so it survives recompression and resharing. Which statement most accurately characterises the conceptual difference between these two approaches?
- ABoth invisible watermarking and provenance metadata cryptographically sign the asset, so either one alone proves the editing history and neither can be removed without invalidating the file.
- BProvenance metadata is embedded in the pixels and survives recompression, whereas invisible watermarking is external metadata that is removed the moment the file is re-exported.
- CProvenance metadata standards such as C2PA carry rich signed assertions but can be stripped when a file is re-exported, whereas invisible watermarking embeds a signal into the content itself that tends to survive transformations like compression. Correct
- DBoth technologies are visible overlays applied to the rendered image, differing only in whether the overlay is a logo or a QR code that viewers can scan.
Why A is wrong: Tempting because both relate to authenticity, but watermarking encodes a bit-pattern rather than a signed edit history, and metadata can be stripped without corrupting the visible content, so this overstates both.
Why B is wrong: Tempting as a plausible labelling, but it reverses the two: it is the watermark that lives in the signal and the manifest metadata that is strippable, so the roles are swapped.
Why C is correct: Correct: a C2PA manifest is signed metadata bound to the file and is lost if the metadata is removed, while an invisible watermark lives in the signal and persists through many transformations, so the two are complementary rather than equivalent.
Why D is wrong: Tempting because visible credential badges exist, but the question describes imperceptible and metadata-borne mechanisms, neither of which is a visible overlay, so this mischaracterises both.