Loading
Pick a focused question that fits your time, stack, and interview goal.
5 results across 1 active filter
Page 1 of 1
Chooses a deployment strategy from capacity, compatibility, risk, observability, and rollback needs, then defines progressive promotion and abort signals.
Explains same-artifact promotion, environment-specific configuration, approvals, smoke testing, drift detection, and production traceability.
Uses declarative infrastructure, reviewed plans, environment parameters, protected deployment identities, state management, and drift control without hiding operational risk.
Protects source, dependencies, workflows, build identities, runners, artifacts, and deployment verification while preserving traceability and patch response.
Covers build-once deployment, tests, artifact traceability, slot deployment, smoke checks, approvals, and post-release monitoring.