✅ Databases Interview Questions & Answers 💾💡

1️⃣ What is a Database?
A: A structured collection of data stored electronically for efficient retrieval and management. Examples: MySQL (relational), MongoDB (NoSQL), PostgreSQL (advanced relational with JSON support)—essential for apps handling user data in 2025's cloud era.

2️⃣ Difference between SQL and NoSQL
⦁ SQL: Relational with fixed schemas, tables, and ACID compliance for transactions (e.g., banking apps).
⦁ NoSQL: Flexible schemas for unstructured data, scales horizontally (e.g., social media feeds), but may sacrifice some consistency for speed.

3️⃣ What is a Primary Key?
A: A unique identifier for each record in a table, ensuring no duplicates and fast lookups. Example: An auto-incrementing id in a Users table—enforces data integrity automatically.

4️⃣ What is a Foreign Key?
A: A column in one table that links to the primary key of another, creating relationships (e.g., Orders table's user_id referencing Users). Prevents orphans and maintains referential integrity.

5️⃣ CRUD Operations
⦁ Create: INSERT INTO table_name (col1, col2) VALUES (val1, val2);
⦁ Read: SELECT * FROM table_name WHERE condition;
⦁ Update: UPDATE table_name SET col1 = val1 WHERE id = 1;
⦁ Delete: DELETE FROM table_name WHERE condition;
These are the core for any data manipulation—practice with real datasets!

6️⃣ What is Indexing?
A: A data structure that speeds up queries by creating pointers to rows. Types: B-Tree (for range scans), Hash (exact matches)—but over-indexing can slow writes, so balance for performance.

7️⃣ What is Normalization?
A: Organizing data to eliminate redundancy and anomalies via normal forms: 1NF (atomic values), 2NF (no partial dependencies), 3NF (no transitive), BCNF (stricter key rules). Ideal for OLTP systems.

8️⃣ What is Denormalization?
A: Intentionally adding redundancy (e.g., duplicating fields) to boost read speed in analytics or read-heavy apps, trading storage for query efficiency—common in data warehouses.

9️⃣ ACID Properties
⦁ Atomicity: Transaction fully completes or rolls back.
⦁ Consistency: Enforces rules, leaving DB valid.
⦁ Isolation: Transactions run independently.
⦁ Durability: Committed data survives failures.
Critical for reliable systems like e-commerce.

🔟 Difference between JOIN types
⦁ INNER JOIN: Returns only matching rows from both tables.
⦁ LEFT JOIN: All from left table + matches from right (NULLs for non-matches).
⦁ RIGHT JOIN: All from right + matches from left.
⦁ FULL OUTER JOIN: All rows from both, with NULLs where no match.
Visualize with Venn diagrams for interviews!

1️⃣1️⃣ What is a NoSQL Database?
A: Handles massive, varied data without rigid schemas. Types: Document (MongoDB for JSON-like), Key-Value (Redis for caching), Column (Cassandra for big data), Graph (Neo4j for networks).

1️⃣2️⃣ What is a Transaction?
A: A logical unit of multiple operations that succeed or fail together (e.g., bank transfer: debit then credit). Use BEGIN, COMMIT, ROLLBACK in SQL for control.

1️⃣3️⃣ Difference between DELETE and TRUNCATE
⦁ DELETE: Removes specific rows (with WHERE), logs each for rollback, slower but flexible.
⦁ TRUNCATE: Drops all rows instantly, no logging, resets auto-increment—faster for cleanup.

1️⃣4️⃣ What is a View?
A: Virtual table from a query, not storing data but simplifying access/security (e.g., hide sensitive columns). Materialized views cache results for performance in read-only scenarios.

1️⃣5️⃣ Difference between SQL and ORM
⦁ SQL: Raw queries for direct DB control, powerful but verbose.
⦁ ORM: Abstracts DB as objects (e.g., Sequelize in JS, SQLAlchemy in Python)—easier for devs, but can hide optimization needs.

💬 Tap ❤️ if you found this useful!

✅ Git & GitHub Interview Questions & Answers 🧑‍💻🌐

1️⃣ What is Git?
A: Git is a distributed version control system to track changes in source code during development—it's local-first, so you work offline and sync later. Pro tip: Unlike SVN, it snapshots entire repos for faster history rewinds.

2️⃣ What is GitHub?
A: GitHub is a cloud-based platform that hosts Git repositories and supports collaboration, issue tracking, and CI/CD via Actions. Example: Use it for pull requests to review code before merging—essential for open-source contribs.

3️⃣ Git vs GitHub
⦁ Git: Version control tool (local) for branching and commits.
⦁ GitHub: Hosting service for Git repositories (cloud-based) with extras like wikis and forks. Key diff: Git's the engine; GitHub's the garage for team parking!

4️⃣ What is a Repository (Repo)?
A: A storage space where your project’s files and history are saved—local or remote. Start one with git init for personal projects or clone from GitHub for teams.

5️⃣ Common Git Commands:
⦁ git init → Initialize a repo
⦁ git clone → Copy a repo
⦁ git add → Stage changes
⦁ git commit → Save changes
⦁ git push → Upload to remote
⦁ git pull → Fetch and merge from remote
⦁ git status → Check current state
⦁ git log → View commit history
Bonus: git branch for listing branches—practice on a sample repo to memorize.

6️⃣ What is a Commit?
A: A snapshot of your changes. Each commit has a unique ID (hash) and message—use descriptive msgs like "Fix login bug" for clear history.

7️⃣ What is a Branch?
A: A separate line of development. The default branch is usually main or master—create feature branches with git checkout -b new-feature to avoid messing up main.

8️⃣ What is Merging?
A: Combining changes from one branch into another—use git merge after switching to target branch. Handles conflicts by prompting edits.

9️⃣ What is a Pull Request (PR)?
A: A GitHub feature to propose changes, request reviews, and merge code into the main branch—great for code quality checks and discussions.

🔟 What is Forking?
A: Creating a personal copy of someone else’s repo to make changes independently—then submit a PR back to original. Common in open-source like contributing to React.

1️⃣1️⃣ What is.gitignore?
A: A file that tells Git which files/folders to ignore (e.g., logs, temp files, env variables)—add node_modules/ or.env to keep secrets safe.

1️⃣2️⃣ What is Staging Area?
A: A space where changes are held before committing—git add moves files there for selective commits, like prepping a snapshot.

1️⃣3️⃣ Difference between Merge and Rebase
⦁ Merge: Keeps all history, creates a merge commit—preserves timeline but can clutter logs.
⦁ Rebase: Rewrites history, makes it linear—cleaner but riskier for shared branches; use git rebase main on features.

1️⃣4️⃣ What is Git Workflow?
A: A set of rules like Git Flow (with develop/release branches) or GitHub Flow (simple feature branches to main)—pick based on team size for efficient releases.

1️⃣5️⃣ How to Resolve Merge Conflicts?
A: Manually edit the conflicted files (look for <<<< markers), then git add resolved ones and git commit—use tools like VS Code's merger for ease. Always communicate with team!

💬 Tap ❤️ if you found this useful!