Cgi Interview Questions (9+ Questions)

Identify and terminate active user sessions for production maintenance and reboots. Learn how to use w, who, and last commands to identify logged-in users with their terminal, login time, and source IP addresses. This guide covers notifying users of session termination, using pkill or kill to disconnect sessions by terminal, documenting terminated sessions for audit trails, and ensuring maintenance windows proceed without blocking interactive sessions. Essential for emergency maintenance procedures, compliance with deployment scripts, and managing controlled system restarts in production environments.

Diagnose Linux hardware failures using kernel message buffer analysis and system logs. Learn how to detect machine check exceptions (MCE), ECC memory errors, disk I/O failures, PCI bus issues, thermal throttling, and CPU hardware faults. This guide covers filtering dmesg output for hardware error patterns, interpreting kernel messages, identifying failing components, and capturing hardware error logs for analysis. Essential for investigating production server instability, preventing unexpected reboots, and implementing proactive hardware monitoring strategies.

Harden container security by deploying the gVisor sandbox runtime (runsc) to intercept and filter syscalls at the user-space level. Add a defense-in-depth security layer that blocks kernel-level attacks, prevents privilege escalation, and isolates containers from host kernel vulnerabilities. Configure daemon.json to register runsc, execute containers with --runtime=runsc, and verify dangerous syscalls fail. Essential for high-security deployments, compliance requirements, and protecting against kernel exploitation in multi-tenant environments.

We have a Git repository that has detached head. Head is basically our latest commit and detached head means that the head that we are currently located at is not pointing to any Git branch, any points directly to commit or tag. It happens when we check out directly tag or we check out directly at comit hash, or we can check out some remote branch. How we can restore from detached head is we either need to return to some existing branch or we have to create a new branch from that detached head. Run git status. We can see that GIT message that head is detached. We'll create new branch by typing Git Checkout the name of the branch, or you can run more modern command Git Switch. Run checkout minus B. And then name of the branch.

We have two branches, main and development, and we need to create feature login based on the development branch. First move to this repository. Next we'll check out our development branch. If we type git branch and name of the branch, it'll create new branch from the development branch because we ar...

🔒 Premium Content

Detailed explanation and solution available for premium members.

Upgrade to Premium →

Deploy an NGINX Pod on Kubernetes: Simple Test Pod Using nginx:latest Image. Learn how to quickly deploy a basic NGINX pod on Kubernetes to validate cluster health, scheduling, and container networking. This hands-on task walks through creating a pod named nginx-pod using the official nginx:latest image, ideal for Kubernetes beginners, lab environments, and smoke testing new clusters. By running a standalone NGINX pod, you can verify that your cluster pulls images correctly, starts containers without errors, and is ready for more advanced workloads like Deployments, Services, and Ingress-based HTTP routing.

Kubernetes Deployment Rollback: Fix web-app ImagePullBackOff prod Namespace. Emergency rollback failed web-app deployment in prod namespace stuck in ImagePullBackOff after bad update. Restore previous working revision using kubectl rollout undo to recover production traffic instantly. Master deployment history management, zero-downtime recovery, revision tracking, image verification rollback, and production incident response. Perfect for CI/CD failures, bad image deployments, blue-green rollback, observability alerting, and SRE incident management.

Configure Route 53 failover routing with a primary record associated with a health check and a secondary fallback record for automatic DNS failover.

Scan local filesystems to locate orphaned files owned by UIDs that no longer map to any user account, then report each file's path and numeric owner along with a total count.