Production checklist

Compatibility and behavior

• The MongoDB server, drivers, topology, and required commands are covered by published compatibility data.
• Representative application reads, writes, transactions, and failures pass through the intended pipeline.
• Unsupported behavior has an explicit application fallback.

Security

• TLS and identity settings are verified on both connection legs.
• Secrets are stored outside source and pipeline definitions.
• Database identities follow least privilege.
• Administrative access and audit retention meet your requirements.

Reliability

• Capacity and availability are tested with your traffic profile.
• Health signals and actionable alerts are integrated.
• Control-plane interruption, runtime restart, and upstream failure are tested.
• A direct or alternate connection path is documented where appropriate.

Change management

• The active pipeline revision is recorded.
• A known-good release and configuration are available.
• Upgrade and rollback procedures have been rehearsed.
• Owners, escalation paths, and a maintenance window are defined.

This checklist is operational guidance, not a certification or compliance statement.