CodeHS Communication and Collaboration 3 — Questions and Answers
Question 1: Which file format is MOST commonly used to document project requirements so the entire team can reference them?
- .exe
- .md (Markdown) (Correct answer)
- .py
- .css
Correct answer: .md (Markdown)
Markdown (.md) files are widely used for project documentation because they are human-readable, version-controllable, and render cleanly on platforms like GitHub.
Question 2: What is the main advantage of using a shared online repository like GitHub for a team project?
- It eliminates the need for any written communication
- It allows all team members to access, track, and contribute to code from anywhere (Correct answer)
- It automatically fixes bugs in submitted code
- It prevents any two people from editing the same project
Correct answer: It allows all team members to access, track, and contribute to code from anywhere
Shared repositories enable distributed teams to collaborate on code, track history, and manage contributions from different locations.
Question 3: In a code review, a reviewer leaves a comment that says 'nit: extra space here.' What does 'nit' signal?
- A critical security vulnerability that must be fixed immediately
- A minor, low-priority style issue that is optional to fix (Correct answer)
- A missing feature that breaks core functionality
- A request to completely rewrite the function
Correct answer: A minor, low-priority style issue that is optional to fix
'Nit' (short for nitpick) signals a small stylistic or formatting issue that reviewers flag but typically do not block merging over.
Question 4: Which of the following BEST describes 'psychological safety' in a collaborative coding team?
- Keeping passwords and credentials private from teammates
- Team members feel safe to ask questions, share ideas, and admit mistakes without fear of judgment (Correct answer)
- Using two-factor authentication on all shared accounts
- Running code in a sandboxed test environment before deploying
Correct answer: Team members feel safe to ask questions, share ideas, and admit mistakes without fear of judgment
Psychological safety means team members can take interpersonal risks—like asking 'dumb' questions or flagging errors—without fearing negative consequences.
Question 5: A project uses labels like 'bug,' 'enhancement,' and 'help wanted' on its issue tracker. What purpose do these labels serve?
- They automatically assign tasks to specific team members
- They categorize and prioritize issues so contributors can find relevant work quickly (Correct answer)
- They replace the need for written issue descriptions
- They mark issues as complete once a pull request is merged
Correct answer: They categorize and prioritize issues so contributors can find relevant work quickly
Labels organize and classify issues, making it easier for contributors to filter, prioritize, and pick up work that matches their skills or interests.
Question 6: When presenting a technical solution to a non-technical audience, which communication strategy is MOST effective?
- Use as much technical jargon as possible to appear credible
- Focus on the business impact and use analogies instead of implementation details (Correct answer)
- Skip the presentation and share the raw code directly
- Present only the most complex parts to show effort
Correct answer: Focus on the business impact and use analogies instead of implementation details
Non-technical audiences understand outcomes and analogies better than implementation details, so focusing on impact and clear analogies improves comprehension.
Question 7: Which Git workflow practice MOST directly supports smooth collaboration between multiple developers?
- All developers commit directly to the main branch without review
- Each developer works on a separate feature branch and merges via pull request (Correct answer)
- One developer writes all code while others test only
- Developers email code files to each other instead of using branches
Correct answer: Each developer works on a separate feature branch and merges via pull request
Feature branches isolate individual work, and pull requests provide a structured review process before changes reach the main codebase.
CodeHS Communication and Collaboration 3
Which file format is MOST commonly used to document project requirements so the entire team can reference them?