A county wants fusion analysts to reuse the same artifact packages the SOC already collected. What integration goal is that?

A county that wants fusion analysts to reuse the same artifact packages the SOC already collected is pursuing avoidance of duplicate collection through shared civic automation outputs. Avoiding duplicate analysis by rebuilding civic automation artifact packages inside fusion still requires re-collecting the evidence inside fusion rather than reusing the SOC's existing package, so it creates duplicate collection instead of avoiding it. Sharing the SOC's existing packages—with proper custody metadata—lets fusion extend analysis without restarting forensic acquisition from scratch.

Why the other options fail by concept: Avoiding duplicate analysis by rebuilding civic automation artifact packages inside fusion fails because rebuilding the package inside fusion repeats collection work instead of reusing the SOC's already-collected evidence, so it misstates the county's integration goal. Avoiding duplicate collection by requesting civic automation artifact packages from fusion reverses the sharing direction because the SOC already holds the collected packages, so asking fusion to supply them does not enable fusion to reuse the SOC's evidence. Avoiding duplicate collection by recreating civic automation artifact packages within fusion defeats reuse because recreating the packages inside fusion repeats the SOC's collection instead of sharing the same package, so it does not avoid duplicate collection.

Exam caveat: Shared packages must preserve integrity hashes and access controls; reuse is not a license for uncontrolled copying into personal storage. Operational check: after SOC collection completes on a lab host, grant fusion a read path to the same package, verify hashes still match, and confirm fusion is reusing that package to avoid duplicate collection rather than rebuilding it inside fusion and duplicating the work.