2–5 years · Mid — Linux · CI/CD · Docker · Kubernetes · Terraform · Monitoring
Identifies the source of the drift through audits; compares current configurations against the version-controlled state; decides on remediation strategy (rollback or fix); communicates changes to relevant teams; enhances monitoring for future drifts.
What practices would you implement to minimise configuration drift in the future?
Cross-checks application logs for any anomalies; inspects upstream dependencies and their latency; verifies if there are any network issues outside the application; considers load testing to replicate the issue; reviews service health checks and their configurations.
The logs show intermittent timeouts. How can you improve the reliability of the service?
Uses top or htop to identify the processes consuming the most CPU; checks the service's logs for errors or unexpected behaviour; reviews recent changes or deployments that may have affected performance; examines system metrics for memory or I/O bottlenecks; considers using strace to trace system calls.
The service is revealed to have inefficient queries. How can you address this issue?
Reviews the error message for specific resource details; checks the current state of the infrastructure against the desired state; considers running terraform refresh to update the state; examines any manual changes made to the infrastructure; plans the changes with terraform plan to ensure no further conflicts.
What strategies can you implement to prevent state file conflicts in the future?
Communicates with stakeholders about the delay; assesses the impact on users and critical services; checks logs for the maintenance process; considers scaling down non-critical services; plans for a rollback if necessary.
How would you improve the maintenance process to avoid such overruns in the future?
Checks the container logs for error messages; inspects the Dockerfile for potential build issues; verifies the container's entry point and command; ensures all required environment variables and volumes are correctly set; tests the container locally to reproduce the issue.
The logs indicate a permissions error on a mounted volume. How do you resolve this?
Load six more — you will get questions you have not seen first.
Give me six more →Say your answer out loud before revealing. Reading the answer first feels like learning and is not.