More in CI/CD & Automation — page 7
What is a CI/CD quality gate? Give a simple example.
WHAT IT TESTS: Go/no-go policy enforcement in CI/CD, not just test execution. ANSWER: Thresholds blocking merges; a minimal new-code gate with 0 critical issues & 70% new-code coverage. RED FLAG: Tests or linters as gates without thresholds.
How would you design a multi-arch build process and anticipate challenges?
WHAT IT TESTS: Cross-platform CI/CD orchestration and build abstraction. ANSWER OUTLINE: Mention buildx or cross-compilation, split native and emulated builds, cache per-arch layers.
Compare ephemeral container agents versus persistent build agents
WHAT IT TESTS: Tradeoffs between isolation and speed. ANSWER OUTLINE: Ephemeral agents ensure clean state but add cold-start latency; persistent agents speed builds via caching yet risk config drift.
Explain dependency management and diamond conflicts in automated builds
Tests transitive dependency resolution and conflict strategies in build pipelines. Strong answers mention nearest-wins eviction, strict versioning, shading, or classloader isolation. Red flag: manual jar swaps or pinning without understanding ABI breakage.
Your build times increased significantly. How do you investigate and optimize?
Tests methodical CI/CD bottleneck analysis and build optimization tactics. Strong answers baseline the timeline, isolate the slowest stage with metrics, then apply parallelism, caching, or dependency pruning.
How do build tools differ from compilers or interpreters?
This tests whether you see compilation as only one step in a repeatable pipeline. A strong answer covers dependency resolution, transitive libraries, task automation, and artifact packaging.
Compare git submodules and git subtree for CI/CD
Tests dependency integration trade-offs in CI. Submodules need recursive clones and pinned commits, complicating checkout; subtree inlines code, simplifying clone but bloating history. Red flag: omitting submodule detached HEAD pain or calling subtree free.
How do you fully remove leaked credentials from Git history?
This tests Git history rewriting and incident response. Rotate the secret first, then use git-filter-repo to purge the file, force-push main, and require all teammates to re-clone before resuming. A red flag is recommending git revert or skipping rotation.
How do you safely merge a 50-commit stale branch with conflicts?
WHAT IT TESTS: Your discipline for resolving long-lived branch drift without breaking team CI. ANSWER OUTLINE: Assess relevance, merge main locally, validate via draft PR and tests, merge off-peak with rollback ready.
How do feature flags enable unfinished work in Trunk-Based Development?
WHAT IT TESTS: Using feature flags to integrate unfinished work in main while keeping it hidden. ANSWER OUTLINE: Commit behind off flags; CI/CD deploys trunk continuously; flags gate exposure for gradual rollouts.
Describe Trunk-Based Development principles and CI/CD benefits
Tests if you view TBD as a CI/CD enabler versus GitFlow. Good answers name a single trunk, branches under 24 hours, pre-integrate builds, and feature flags, tying daily commits to releasable code and less merge hell. Red flag: endorsing long-lived branches.
Describe using a pre-push Git hook for checks and its CI limitations.
It tests client-side automation versus server-side policy. An executable .git/hooks/pre-push script runs tests and exits non-zero to block, noting hooks are not cloned, skipped via --no-verify, and local-only. A red flag is treating them as policy gate.
Difference between git merge and git rebase before a pull request
WHAT IT TESTS: Grasp of linear vs branched history and CI traceability. ANSWER: Rebase rewrites SHAs, duplicating CI builds; merge keeps identity and triggers one build. RED FLAG: Calling rebase safer while ignoring force-push and broken links.
How does your CI/CD strategy differ between monoliths and microservices?
WHAT IT TESTS: Grasp of release coupling and blast radius. ANSWER OUTLINE: Contrast monolith unified builds with microservice independent deploys, side-by-side versions, and service gates. RED FLAG: Shared pipeline for all services or no monolith rollback.
Pipeline is green but lead time grows. Three areas to investigate?
This tests distinguishing pipeline health from delivery flow efficiency. A strong answer targets pre-merge wait states, slow green pipeline stages, and post-merge deployment friction, using time-in-stage metrics.
What is a build artifact and why build once deploy many crucial?
Tests whether you see artifacts as immutable deployable units. A strong answer says one binary is promoted through all stages, config is externalized, and rebuilding per environment creates drift. Red flag: accepting per-environment rebuilds.
Describe the typical CI pipeline sequence from push to deploy
This tests stage ordering and failure handling. A strong answer lists build, test, and deploy stages; notes intra-stage parallelism and inter-stage sequencing; and mentions early termination on failure.
What is CI, and what is its single most important goal?
WHAT IT TESTS: Distinguishing CI as keeping code workable, not just builds. ANSWER OUTLINE: Frequent merges to a shared branch with automated build and test; top goal is a workable integrated codebase.
Platform Orchestrator: Infrastructure's Travel Agent
A platform orchestrator is infrastructure's travel agent: describe an app and it provisions compute, databases, and caches across clouds automatically. It shines once teams outgrow per-service Terraform. Adopt it too early and it becomes a bottleneck.
Backstage: The Developer Portal Framework
Backstage is a framework for building a developer portal, not a ready-made dashboard. It centralizes ownership, docs, and tooling when microservice sprawl hides context. The footgun is treating it as a product you deploy without upkeep; the catalog rots.