1. In a scenario where team members need to brainstorm new ideas for a project, which GitHub feature should they use and why? GitHub Issues, because they allow tracking tasks and ideas Pull requests, because they facilitate collaboration on code changes GitHub Discussions, because they provide a platform for open conversations

2. A team member reports that their changes in a branch are not visible in the main branch after the merge. What is the likely cause? The branch containing the changes was deleted before the merge. The merge was performed on a branch, not on the main branch. The repository settings do not allow merging into the main branch.

3. Your team is preparing to deploy a new feature using GitHub branches. What should be done to ensure the feature branch is ready for deployment? Make sure all changes are reviewed and approved through a pull request before merging into the main branch. Delete the feature branch to finalize the deployment process. Commit all changes directly to the main branch without review.

4. Your team wants to improve collaboration by using GitHub Discussions. What is a key feature of Discussions that promotes open communication? They allow smooth and open conversation accessible to anyone with access to the repository. They automatically generate tasks for team members. They are limited to topics related to code only.

5. What is the main reason for using branches in the GitHub flow? Create backups of the entire repository. Isolate changes and work on features without affecting the main branch. Automatically update the main branch with new changes.

6. How do pull requests contribute to the GitHub flow during collaboration? They create a development backup. They provide a structured way to propose and review changes before merging them into the main branch. They automatically resolve conflicts between different branches.

7. In which scenario would GitHub Issues be more effective than Discussions? When seeking ideas and project improvements from the community. When tracking specific tasks and bugs that need resolution. When making announcements and sharing news with teams.

8. When should you use a GitHub issue instead of a discussion? When it’s about tracking specific tasks or bugs related to a project. When seeking open feedback on a project idea. When announcing important project milestones to the team.