APURV
  • Home
  • Journey
  • Projects
  • Blogs
  • Interview
  • Exams
Resume
APURV

Building scalable, secure, and production-ready cloud infrastructure. Automation first.

NAVIGATION

HomeExperienceProjectsCertificationsSkills

TECH STACK

AWSGCPK8sCI/CDLinuxDocker

CONNECT

LinkedInGitHubEmailResume

Β© 2026 Apurv Gujjar. All rights reserved.
Apurv Gujjar
Apurv GujjarDevOps & Cloud Engineer
|Interview Documentation
Portfolio
Handbooks
🎯LinuxπŸ™Git & GitHubπŸ€–GitHub Actions🌐Networking☁AWSπŸ› Terraform🐳Docker☸KubernetesπŸ“ŠMonitoringπŸ›‘DevSecOpsπŸ’°Cost Optimization🚨Incident ScenariosπŸ‘€HR & Behavioral☁GCP🐍Python
Interview DocumentationGit & GitHub

Git & GitHub

Comprehensive Git Version Control & Branching Guide for DevOps Engineers

Q1

What is Git, and how does its distributed model differ from older centralized version control systems?

πŸ’¬Answer

Git is a free, open-source distributed version control system (DVCS) designed to handle everything from small to very large projects with speed and efficiency. Unlike older centralized systems (like SVN or CVS), every Git clone is a full-fledged repository with complete history and full version-tracking capabilities, independent of network access or a central server.

Q2

# Why it is Used:

Q3

What is version control, and why is it considered the absolute starting point for any DevOps pipeline?

Q4

Can you explain the main architectural areas of Git? How do files transition between them?

Q5

How do you explain the difference between Git and GitHub to a non-technical stakeholder?

Q6

What actually happens under the hood when we execute a 'git commit' command?

Q7

What is a Git object? Can you name the four primary object types stored in the database?

Q8

What is a Git branch under the hood? Does creating a branch duplicate our files?

Q9

# How it works:

Q10

How do you explain the difference between 'git merge' and 'git rebase'? What is the Golden Rule of Rebasing?

Q11

What is 'cherry-picking' in Git, and can you describe a scenario where you would use it?

Q12

# Common Use Cases:

Q13

What is a 'squash merge' and why is it useful when merging Pull Requests into a main branch?

Q14

# Why it is used:

Q15

What is a 'fast-forward' merge? How can we prevent Git from doing this automatically?

Q16

# How it works:

Q17

Can you contrast reset, revert, and restore? Which one is safest for shared remote branches?

Q18

If I run a 'git reset --hard' and lose my last three commits, how would you recover them?

Q19

# Recovery Workflow:

Q20

What is 'git reflog' and how does it differ from 'git log'?

Q21

What does it mean to be in a 'detached HEAD' state? How do we fix it and preserve our work?

Q22

# How it happens:

Q23

# Implications:

Q24

How do you recover a local branch that was accidentally deleted using 'git branch -D'?

Q25

# Recovery Workflow:

Q26

What actually triggers a merge conflict in Git?

Q27

Walk me through your step-by-step process for resolving a merge conflict.

Q28

Can you explain Git Flow? What are the roles of the main, develop, feature, release, and hotfix branches?

Q29

What is GitHub Flow, and how does it compare to Git Flow for SaaS deployment models?

Q30

# Core Workflow:

Q31

What is Trunk-Based Development, and how do feature flags enable it?

Q32

# Key Principles:

Apurv Gujjar - DevOps & Cloud Engineer
Created by

Apurv Gujjar

DevOps & Cloud Engineer

Specialized in:DevOpsAWSGCPKubernetesTerraformDocker
View Portfolio