Transit wants weekend schema deploys to require on-call sign-off even when weekday approvals already exist. Which pipeline design fits?

Transit wants weekend schema deploys to require on-call sign-off even when weekday approvals already exist. The fitting pipeline design is to configure approval triggers so weekend deployment windows require additional on-call sign-off before release. Time-boxed approval rules recognize that municipal transit changes during quieter weekend windows still need a responsible, available approver—weekday approvals do not automatically cover off-hours risk. This is an environment/window gate in CI/CD, not a removal of controls.

Removing all approvals on weekends to speed emergency schema pushes fails by concept: emergencies still need identity-bound authorization; removing gates maximizes unattended change. Allowing any developer to bypass environments when the calendar says Saturday fails least privilege and environment protection—calendar day is not an authorization substitute. Disabling notifications so on-call staff never see weekend deploy requests fails operationally: even a configured approval is useless if the on-call never learns a release is waiting.

Exam caveat: DP-800-style pipeline questions treat approvals and environment checks as tunable controls; when the stem asks for weekend on-call sign-off, choose additional approvals for that window rather than bypasses. Speed and silence distractors invert the requirement.

Operational check: configure the production (or transit schema) environment so deployments in the weekend window require the on-call approval group; schedule a test release into that window and confirm it pauses for sign-off, notifies on-call, and only proceeds after approval. Verify weekday policy still applies on weekdays and that bypass rights are not granted solely because the calendar reads Saturday.