Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
22 results across 1 active filter
Page 1 of 1
Builds a small, immutable, non-root .NET runtime image with controlled inputs, external configuration, graceful lifecycle behavior, and a practical patching strategy.
Keeps images environment-neutral while handling configuration precedence, secret delivery, rotation, and startup validation safely.
Connects orchestrator requests and limits to .NET GC, thread-pool behavior, throttling, OOM termination, and capacity planning.
Separates ephemeral instance files from durable data and sends logs, uploads, caches, and diagnostics to storage with explicit lifecycle ownership.
Uses immutable image identity, controlled promotion, registry security, and deliberate base-image rebuilding instead of mutable latest tags.
Explains bind addresses, published ports, internal DNS, service identity, and why localhost changes meaning across container boundaries.
Explains process isolation, shared kernels, image-based deployment, and where containers differ operationally from virtual machines.
Builds a story about collaborating during an incident without chaos or duplicated work.
Uses instance state, termination reasons, events, logs, configuration, probes, and resource evidence to distinguish common container startup failures.
Builds deterministic images efficiently by controlling context, restore layers, dependency inputs, and cache invalidation.
Uses Compose for reproducible local dependencies while preserving fast inner loops, realistic readiness, and clear differences from production orchestration.
Builds a story about turning an incident into regression guards, observability, and process improvement.
Handles SIGTERM, traffic draining, cancellation, background work, and termination deadlines without losing accepted work or hanging rollout.
Coordinates readiness, server draining, lifecycle timeouts, background work, and platform termination during a Spring Boot shutdown.
Reviews correctness, boundaries, failure behavior, capacity, security, observability, delivery, and recovery through concrete evidence.
Explains the small set of Kubernetes resources needed to run and expose a replicated stateless API without drowning the answer in platform vocabulary.
Separates traffic eligibility, process recovery, and slow startup so health checks do not amplify dependency failures or restart healthy work.
Coordinates old and new application versions, expand-and-contract schema changes, migration ownership, readiness, and rollback during rolling releases.
Reduces container privileges through non-root execution, minimal images, controlled filesystems, and explicit capability requirements.
Builds a story about taking responsibility for a production bug, mitigating impact, and preventing recurrence.
Designs scheduled work for overlap, multiple replicas, restart, failure, and durable ownership instead of assuming one execution.
Combines Spring Boot signals into an operator-focused baseline for service health, dependencies, capacity, releases, and actionable alerts.