Git Deployment and Rollback Quiz for Web Design Students

📚 Quick Study Guide

• 🌍 Git Deployment: The process of transferring code changes from a local Git repository to a live server or production environment.
• 🔑 Key Steps:
  • 🧪 Commit changes locally.
  • 📡 Push changes to a remote repository (e.g., GitHub, GitLab).
  • 🧰 Deploy changes from the remote repository to the server.
• ↩️ Rollback: Reverting to a previous state of the application or website.
• ⏱️ Why Rollback? To fix broken deployments, bugs, or unexpected issues.
• 💡 Methods:
  • 🔑 Reverting commits.
  • 🔑 Deploying a previous release tag.
• 🧰 Best Practices:
  • 📝 Use version control (Git).
  • ✅ Automate deployments.
  • 🧪 Test deployments in a staging environment.

Practice Quiz

1. Question 1: What is Git deployment?
   1. A. Deleting code from the repository.
   2. B. Transferring code changes to a live server.
   3. C. Ignoring code changes.
   4. D. Writing documentation.
2. Question 2: Why is Git rollback important?
   1. A. To introduce new bugs.
   2. B. To fix broken deployments and bugs.
   3. C. To increase server load.
   4. D. To confuse developers.
3. Question 3: Which of the following is NOT a key step in Git deployment?
   1. A. Commit changes locally.
   2. B. Push changes to a remote repository.
   3. C. Deploy changes to the server.
   4. D. Ignore all warnings.
4. Question 4: What is one method of performing a Git rollback?
   1. A. Creating new bugs.
   2. B. Reverting commits.
   3. C. Deleting the entire repository.
   4. D. Increasing server costs.
5. Question 5: What is a staging environment used for?
   1. A. To store production data.
   2. B. To test deployments before going live.
   3. C. To confuse users.
   4. D. To increase website loading times.
6. Question 6: Why is automation important in Git deployments?
   1. A. It makes the process slower.
   2. B. It reduces the risk of human error.
   3. C. It increases the number of bugs.
   4. D. It makes deployments more difficult.
7. Question 7: What should you do before deploying changes to a live server?
   1. A. Skip testing.
   2. B. Test in a staging environment.
   3. C. Introduce new features without review.
   4. D. Delete the database.