A SaaS team runs dev, staging, and prod in separate accounts and deploys to us-east-1 and eu-west-1. Auditors require artifacts promoted unchanged between stages, least-privilege cross-account deploys, and full pipeline history. Builds already run in CodeBuild. Which multi-account deployment pipeline provides role delegation with artifact promotion?

The central CodePipeline with cross-account IAM roles and replicated artifact bucket is correct because it satisfies every auditor constraint in one managed workflow: hosted in the tools account it centralizes orchestration, cross-account role assumption enables least-privilege delegation to dev, staging, and prod without long-term credentials, replication across us-east-1 and eu-west-1 makes the exact CodeBuild output available in both regions, promotion moves that identical object unchanged through stages preserving test evidence, and CodePipeline retains complete execution history with approvals for review. The tools-account CodePipeline that rebuilds a fresh CodeBuild artifact per stage fails the artifact concept because recompilation creates a different binary hash and invalidates prior tests even with identical source. The EventBridge-triggered CodeBuild deployment that assumes cross-account roles fails the pipeline concept because direct deployment lacks unified history, stage gates, and promotion tracking despite preserving immutability and delegation. The tools-account CodePipeline with replicated bucket promoting the identical build fails the delegation concept because shared bucket access does not provide scoped per-stage assumption, session logging, and easy revocation. As an exam caveat, rebuilding from identical source is not promoting an identical artifact. As a practical check, confirm one artifact revision flows across stages, target roles allow only narrow deploy actions trusted by the pipeline role, and replication covers both regions.