I85PREP
⌘ K
Certified Open Source Developer for Enterprise study materials
Certified Open Source Developer for Enterprise study resources

Certified Open Source Developer for Enterprise practice questions

One question at a time. Build your Certified Open Source Developer for Enterprise understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Fundamentals of Open Source Software Development

Under the Open Source Definition, which characteristic must a license grant to qualify as open source?

  1. The obligation to pay a royalty to the original author for commercial deployment
  2. The restriction that binaries may be distributed only alongside the original unmodified source
  3. The right to modify the source code and distribute derived works under the same terms Correct answer.
  4. The requirement that all derivative works be reviewed by the original author before release

Explanation

The Open Source Definition requires free redistribution and permission for derived works, so modification and redistribution of modified versions must be allowed. Royalties and mandatory author review would violate the freedom to redistribute and to create derived works.

Question 2Fundamentals of Open Source Software Development

A company releases a project under the MIT License. Which statement best describes the obligations imposed on downstream redistributors?

  1. They must include the original copyright notice and permission notice in all copies or substantial portions Correct answer.
  2. They must relicense their combined work under the MIT License only
  3. They must provide a written warranty to all end users of the software
  4. They must publish any modifications they make to the source code publicly

Explanation

The MIT License is permissive and its only real condition is retaining the copyright and permission notice in redistributions. It does not require publishing modifications, does not force relicensing of combined works, and explicitly disclaims warranty rather than requiring one.

Question 3Fundamentals of Open Source Software Development

Which license is a strong copyleft license that requires derivative works distributed to the public to be licensed under the same terms?

  1. Apache License 2.0
  2. BSD 3-Clause License
  3. MIT License
  4. GNU General Public License version 3 Correct answer.

Explanation

The GNU GPL is the canonical strong copyleft license: distributing a derivative work triggers the obligation to license it under the GPL. Apache 2.0, BSD 3-Clause, and MIT are permissive licenses that do not impose that reciprocity.

Question 4Fundamentals of Open Source Software Development

What is the primary purpose of a Contributor License Agreement (CLA) in an open source project?

  1. To guarantee that contributors will be paid for their accepted pull requests
  2. To define the terms under which contributions are licensed or assigned to the project, often granting rights needed for relicensing Correct answer.
  3. To transfer ownership of the project's trademark to every contributor
  4. To prevent contributors from ever forking the project's repository

Explanation

A CLA is a legal agreement that clarifies the rights the project receives over contributed code, frequently including a copyright or patent grant that supports future relicensing. It does not transfer trademarks to contributors, provide payment, or restrict forking.

Question 5Fundamentals of Open Source Software Development

In a Git-based contribution workflow, what does a maintainer typically do with a pull request before merging it?

  1. Delete the contributor's fork to avoid duplicate repositories
  2. Rebase it onto an unrelated branch to hide the commit history
  3. Review the changes, run automated checks, and request revisions if needed Correct answer.
  4. Convert the commits into a patch file and email it to the mailing list only

Explanation

The pull request model centers on review: maintainers examine the diff, rely on CI checks, and may request changes before merging. Rebasing onto unrelated branches, deleting forks, or forcing email-only patches do not describe standard pull request handling.

Question 6Fundamentals of Open Source Software Development

Which artifact in a typical open source repository states the terms under which the software may be used, modified, and redistributed?

  1. The README.md file
  2. The LICENSE file Correct answer.
  3. The CHANGELOG.md file
  4. The CONTRIBUTING.md file

Explanation

The LICENSE file contains the actual legal terms governing use, modification, and redistribution. README, CONTRIBUTING, and CHANGELOG files serve documentation, process, and history purposes rather than granting rights.

Question 7Fundamentals of Open Source Software Development

What distinguishes an open source project's governance from a purely informal arrangement?

  1. Decisions are documented through defined roles, processes, and decision-making rules that participants can rely on Correct answer.
  2. Governance exists only after a foundation purchases the project
  3. All decisions are made by whoever has commit access at the moment
  4. The project must adopt a single commercial vendor's roadmap

Explanation

Governance is about explicit, documented structures: roles such as maintainer or committer, escalation paths, and rules for how decisions are made. Ad hoc commit-access authority, foundation purchase, or vendor control do not constitute documented governance.

Question 8Fundamentals of Open Source Software Development

Which statement accurately describes the relationship between open source and open standards?

  1. Open standards and open source are synonyms for the same governance model
  2. An open standard legally requires all implementations to be copyleft licensed
  3. Open standards define interoperable specifications, while open source provides implementations that may or may not conform Correct answer.
  4. Open source implementations automatically become open standards once released

Explanation

Open standards are published specifications with transparent processes, whereas open source concerns the licensing and availability of implementing code. Implementations can conform to standards without the standard mandating any particular license.

Question 9Fundamentals of Open Source Software Development

A developer wants to use a library licensed under GPLv3 inside a proprietary product that will be distributed to customers. What is the key legal consideration?

  1. The developer only needs to add the GPL notice to the product's documentation
  2. The library can be used freely because GPL only applies to server-side software
  3. Distributing the combined work likely triggers GPL obligations to provide source under GPL terms, so the architecture or licensing must change Correct answer.
  4. GPLv3 permits proprietary distribution as long as the library is dynamically linked

Explanation

Combining GPLv3 code into a distributed proprietary product generally creates a derivative work that must be licensed under the GPL, including source availability. The distinction between linking styles is contested and does not automatically permit proprietary distribution.

Question 10Fundamentals of Open Source Software Development

A company modifies an MIT-licensed library and ships it inside a closed-source desktop application. Which obligation applies?

  1. Pay a per-seat fee to the original project maintainers
  2. Release the modified library source under the MIT License
  3. Remove the original authors' names from the source files
  4. Include the original copyright and permission notice in the distribution Correct answer.

Explanation

MIT's condition is notice retention: the copyright and permission text must accompany copies or substantial portions of the software. It does not compel source release, payment, or removal of attribution.

Question 11Fundamentals of Open Source Software Development

An enterprise adopts a policy of tracking Software Bill of Materials (SBOM) data for its applications. What is the main benefit in an open source context?

  1. It replaces the need to review license obligations for each component
  2. It provides an inventory of components and versions, enabling faster identification of affected dependencies when vulnerabilities are disclosed Correct answer.
  3. It automatically upgrades all transitive dependencies to secure versions
  4. It guarantees that no dependency has a known vulnerability

Explanation

An SBOM records the components and versions in a product, which lets teams quickly determine exposure when a vulnerability is announced. It is an inventory mechanism, not a guarantee of security, a license review substitute, or an automated upgrade tool.

Question 12Fundamentals of Open Source Software Development

A project uses the Developer Certificate of Origin (DCO) instead of a CLA. What does a contributor affirm by signing off on a commit?

  1. That they have obtained a patent license from all prior employers
  2. That they will maintain the contributed code indefinitely
  3. That they transfer all copyright ownership to the project's foundation
  4. That they have the right to submit the contribution under the project's license and agree to the sign-off requirements Correct answer.

Explanation

The DCO is a lightweight attestation that the contributor has the right to submit the code under the project's license and understands the sign-off. It does not assign copyright, impose maintenance duties, or require employer patent clearances.

Question 13Fundamentals of Open Source Software Development

Which practice best supports a healthy, sustainable open source community in a corporate-sponsored project?

  1. Closing the issue tracker so that discussions happen only in internal channels
  2. Restricting issue triage and review duties to employees of the sponsoring company
  3. Requiring contributors to sign a non-disclosure agreement before filing bug reports
  4. Publishing clear contribution guidelines, recognizing non-employee contributors, and documenting decision processes Correct answer.

Explanation

Sustainability depends on transparent processes and inclusive recognition so that contributors outside the sponsor can participate meaningfully. Concentrating duties internally, gating reports behind NDAs, or hiding discussion undermines community growth.

Question 14Fundamentals of Open Source Software Development

In the context of open source licensing, what does a patent grant clause such as the one in Apache 2.0 accomplish?

  1. It requires all users to file patents on their modifications
  2. It invalidates the patents of downstream competitors
  3. It converts the software license into a trademark license
  4. It ensures contributors grant users a license to patents they hold that are necessary to use their contributions Correct answer.

Explanation

Apache 2.0 includes an express patent grant from contributors covering patent claims necessarily infringed by their contributions. This protects users from patent ambush; it does not compel patent filing, invalidate third-party patents, or function as a trademark license.

Question 15Fundamentals of Open Source Software Development

A maintainer wants to change a project's license from GPLv2 to GPLv3. Which factor most directly determines whether this is permissible?

  1. The number of stars the repository has received
  2. The programming language used by the project
  3. Whether the project holds or has secured rights from all copyright holders, or the existing license permits 'or later' versions Correct answer.
  4. Whether the project has a code of conduct

Explanation

Relicensing requires authority over the relevant copyrights, either through ownership, contributor agreements, or a license that allows use of later versions. Popularity, language choice, and community policies do not confer the legal right to relicense.

Question 16Fundamentals of Open Source Software Development

What is the role of a foundation such as those that host large open source projects?

  1. It replaces maintainers with foundation employees for all technical decisions
  2. It guarantees commercial support contracts for every hosted project
  3. It holds assets such as trademarks and copyrights and provides neutral governance for multiple projects Correct answer.
  4. It owns the source code of all projects and can relicense them at will

Explanation

Foundations typically act as neutral stewards holding trademarks, sometimes copyrights, and providing governance and legal infrastructure. They do not guarantee support contracts, unilaterally relicense code, or take over technical decision-making from maintainers.

Question 17Fundamentals of Open Source Software Development

A team consumes an open source component under a license requiring attribution in documentation. Where should the team record this obligation to remain compliant over time?

  1. In the product's marketing website footer only
  2. In a maintained third-party notices file shipped with the product and reviewed during dependency updates Correct answer.
  3. In the personal notes of the engineer who first added the dependency
  4. In an ephemeral chat message that is deleted after the release

Explanation

Attribution obligations persist across releases, so they belong in a durable, version-controlled notices artifact that ships with the product and is updated when dependencies change. Ephemeral messages, individual notes, or unrelated web pages do not reliably satisfy the obligation.

Question 18Fundamentals of Open Source Software Development

Which statement best captures the difference between a permissive license and a weak copyleft license such as the LGPL?

  1. Weak copyleft allows linking with proprietary code under conditions but requires sharing changes to the licensed library itself Correct answer.
  2. Permissive licenses forbid commercial use, while weak copyleft permits it
  3. Permissive licenses require source disclosure of the whole application, while weak copyleft does not
  4. Weak copyleft prohibits any redistribution of binaries

Explanation

Weak copyleft like the LGPL targets the library itself: modifications to it must be shared, while larger proprietary works may link to it under specified conditions. Permissive licenses impose no source-sharing at all, and neither license type bans commercial use or binary redistribution.

Question 19Fundamentals of Open Source Software Development

A contributor submits a patch containing code copied from a project with an incompatible license. What is the most appropriate maintainer response?

  1. Merge it quickly to reward the contributor's enthusiasm
  2. Reject or request a rewrite and document the provenance concern in the review Correct answer.
  3. Merge it but remove all comments to obscure the origin
  4. Accept it and change the project's license to match the copied code

Explanation

Accepting incompatible code would create a licensing violation for the whole project, so maintainers should reject or require a clean-room rewrite and record the provenance issue. Hiding origin, rushing the merge, or unilaterally relicensing do not resolve the legal problem.

Question 20Fundamentals of Open Source Software Development

Why do many projects adopt a Code of Conduct alongside their contribution guidelines?

  1. To replace the project's software license
  2. To define expected behavior and enforcement so participation is safe and predictable for a diverse community Correct answer.
  3. To establish legally binding employment relationships with contributors
  4. To restrict contributions to a single geographic region

Explanation

A Code of Conduct sets behavioral expectations and describes enforcement, which supports constructive participation across a diverse contributor base. It is not an employment contract, does not supersede the license, and must not discriminate by geography.

Question 21Fundamentals of Open Source Software Development

An organization wants to contribute an internally developed tool to the open source community. Which sequence best reflects sound practice?

  1. Publish the code first, then audit it for secrets and third-party license issues afterward
  2. Choose the most restrictive license available to deter all commercial use
  3. Retain all trademarks and forbid any forks in the license text
  4. Audit for sensitive data and license compatibility, choose a license, add governance and contribution docs, then publish Correct answer.

Explanation

Releasing code requires pre-publication diligence on secrets, provenance, and license compatibility, followed by selecting a license and providing governance and contribution documentation. Publishing before auditing, choosing deliberately restrictive terms, or banning forks conflicts with open source practice.

Question 22Fundamentals of Open Source Software Development

A company distributes a product that statically links a GPLv2 library and also ships a separate proprietary plugin loaded at runtime. Which analysis is most defensible?

  1. Shipping components on the same medium never creates any licensing relationship
  2. The GPLv2 library can be relicensed by the distributor to avoid obligations
  3. The statically linked combination is likely a derivative work subject to GPL, while the plugin's status depends on whether it forms a single combined work with the GPL code Correct answer.
  4. The entire product, including the plugin, must always be GPL because it ships on the same medium

Explanation

Static linking generally produces a derivative work requiring GPL compliance for the combined program, whereas mere aggregation on the same medium is not itself decisive. The plugin's status turns on whether it communicates at arm's length or forms a single combined work, so the distributor cannot relicense the library.

Question 23Fundamentals of Open Source Software Development

A project's governance document grants committers merge rights but reserves license changes and trademark use to a steering committee. A committer merges a change that quietly switches the project from Apache 2.0 to a proprietary license. What is the most accurate assessment?

  1. The change is valid because license files are not code and fall outside governance
  2. The change is valid if at least one steering committee member approved the pull request informally
  3. The change exceeds the committer's authority and is invalid under the documented governance, requiring reversal and process review Correct answer.
  4. The change is valid because committers hold merge rights over the repository

Explanation

Merge rights are bounded by the governance document, which explicitly reserves licensing decisions to the steering committee. A committer acting outside that scope produces an unauthorized change that should be reverted and addressed through process, regardless of informal approval or the file type involved.

Question 24Fundamentals of Open Source Software Development

An enterprise's legal team must evaluate an open source component whose license includes a 'commons clause'-style restriction on selling the software. How should this be treated relative to the Open Source Definition?

  1. It likely fails the Open Source Definition because it discriminates against fields of endeavor and restricts commercial use Correct answer.
  2. It qualifies as open source because it permits modification
  3. It qualifies as open source if the restriction applies only to large enterprises
  4. It qualifies as open source because the source code is publicly available

Explanation

Public availability of source and permission to modify are necessary but not sufficient; the Open Source Definition forbids discrimination against fields of endeavor and restrictions on selling the software. A restriction on selling therefore generally disqualifies the license as open source, regardless of who is targeted.

Question 25Fundamentals of Open Source Software Development

A maintainer receives a security report for a vulnerability in a dependency and must coordinate disclosure. Which approach best reflects responsible open source practice?

  1. Patch only the local fork silently and never inform upstream
  2. Work privately with the dependency maintainers on a fix, agree on a disclosure timeline, and credit the reporter Correct answer.
  3. Publish full exploit details immediately without notifying the dependency maintainers
  4. Ignore the report until a user complains publicly

Explanation

Coordinated disclosure gives maintainers time to prepare a fix while keeping reporters informed and credited, reducing harm to users. Immediate publication, indefinite silence, or forking without upstream notification all increase risk or leave others exposed.

Question 26Fundamentals of Open Source Software Development

Which file in a source repository conventionally records the human-readable history of notable changes for each released version of an open source project?

  1. LICENSE
  2. CODEOWNERS
  3. CHANGELOG Correct answer.
  4. AUTHORS

Explanation

A CHANGELOG file lists notable changes per release so downstream consumers can judge upgrade impact without reading every commit. LICENSE states legal terms, CODEOWNERS assigns review ownership, and AUTHORS credits contributors, so none of them records release history.

Question 27Fundamentals of Open Source Software Development

What is the primary purpose of a CONTRIBUTING file in an open source repository?

  1. To explain how to build, test, and submit changes to the project Correct answer.
  2. To define the license under which the code is distributed
  3. To list the names of everyone who has ever submitted a patch
  4. To record the security vulnerabilities found in each release

Explanation

A CONTRIBUTING guide tells newcomers the workflow: how to set up the build, run tests, follow style rules, and open a pull request. It reduces maintainer burden by making expectations explicit before a patch arrives.

Question 28Fundamentals of Open Source Software Development

A contributor forks a repository, creates a branch, commits a fix, and opens a pull request. Which term describes the upstream maintainer's action of integrating that work into the project's main branch?

  1. Forking the branch
  2. Merging the pull request Correct answer.
  3. Rebasing the fork
  4. Cloning the repository

Explanation

Merging the pull request is the step that brings the reviewed commits into the target branch of the upstream repository. Cloning and forking create copies, and rebasing rewrites the contributor's branch history rather than integrating it upstream.

Question 29Fundamentals of Open Source Software Development

Which version control system model became dominant for open source collaboration because it gives every contributor a full local copy of the repository history?

  1. Centralized version control
  2. Proprietary file locking
  3. Distributed version control Correct answer.
  4. Single-branch snapshotting

Explanation

Distributed version control, exemplified by Git, gives each clone the complete history, so contributors can commit, branch, and inspect history offline and share work through remotes. Centralized systems require a network connection to the single server for most history operations.

Question 30Fundamentals of Open Source Software Development

What does an SPDX license identifier such as 'Apache-2.0' provide when placed in a source file header?

  1. A cryptographic signature proving the file was not modified
  2. A machine-readable standard tag naming the license that applies to the file Correct answer.
  3. A build instruction telling the compiler which flags to use
  4. A pointer to the contributor's employer for copyright purposes

Explanation

SPDX identifiers are standardized short strings that tools can scan to determine which license governs a file, supporting automated compliance checks. They are metadata about licensing, not signatures, employer records, or build directives.

Question 31Fundamentals of Open Source Software Development

In open source terminology, what is a 'downstream' consumer of a project?

  1. A foundation that owns the project's trademark
  2. A project or organization that builds on or redistributes the upstream project's code Correct answer.
  3. A maintainer who holds merge rights on the main branch
  4. A contributor who reports issues but never submits code

Explanation

Downstream refers to the direction of dependency flow: projects and products that consume or redistribute code from an upstream project. Maintainers, issue reporters, and foundations occupy other roles and are not defined by consuming the code.

Question 32Fundamentals of Open Source Software Development

Which metric best indicates that an open source project has a healthy bus factor rather than depending on one person?

  1. A single maintainer has authored the majority of commits in the last year
  2. The project releases a new version on a fixed calendar schedule
  3. The repository has a very large number of stars and forks
  4. Several maintainers routinely review and merge changes across different areas Correct answer.

Explanation

Bus factor measures how many people could disappear before the project stalls, so distributed review and merge authority across areas signals resilience. Stars, forks, and release cadence can look healthy while decision-making still rests with one individual.

Question 33Fundamentals of Open Source Software Development

A team wants to depend on an open source library and needs to judge whether the project is actively maintained. Which combination of signals is most informative?

  1. Recent commits, responsive issue triage, and releases addressing security fixes Correct answer.
  2. The license text length and the number of files in the repository
  3. The programming language used and the size of the README
  4. The number of forks and the age of the original commit

Explanation

Maintenance health shows up in ongoing activity that affects consumers: commits, timely issue handling, and releases that ship security fixes. Repository size, language choice, and fork counts do not demonstrate that someone is responding to problems.

Question 34Fundamentals of Open Source Software Development

What is the function of a project's security policy file, commonly named SECURITY.md?

  1. It grants committers permission to merge security patches without review
  2. It replaces the need for coordinated disclosure timelines
  3. It tells researchers how to report vulnerabilities privately and what response to expect Correct answer.
  4. It lists every known vulnerability in the project's dependency tree

Explanation

A security policy directs reporters to a private channel and sets expectations about acknowledgment and fix timelines, which prevents premature public disclosure. It is a process document, not a vulnerability inventory or a permission grant.

Question 35Fundamentals of Open Source Software Development

An enterprise contributor is asked to sign a Contributor License Agreement before a pull request can be merged. What does the CLA typically accomplish?

  1. It certifies that the contributor has run the project's test suite
  2. It waives the project's license obligations for the contributor's employer
  3. It records a grant of copyright or patent rights from the contributor to the project entity Correct answer.
  4. It transfers ownership of the contributor's personal fork to the foundation

Explanation

A CLA is a legal agreement in which the contributor grants the project entity rights, often including a copyright license and patent grant, so the project can distribute the contribution under its chosen license. It does not move repository ownership, certify testing, or exempt anyone from the project license.

Question 36Fundamentals of Open Source Software Development

Why do many open source projects require contributors to sign off commits with a line such as 'Signed-off-by: Name <email>'?

  1. To encrypt the commit contents so only maintainers can read them
  2. To trigger a license change for the affected files
  3. To create a traceable attestation that the contributor has the right to submit the code Correct answer.
  4. To automatically assign the contributor a maintainer role

Explanation

The sign-off is a lightweight attestation, matching the Developer Certificate of Origin, that the contributor is legally entitled to submit the code under the project license. It provides an auditable trail without the overhead of a formal CLA.

Question 37Fundamentals of Open Source Software Development

A project's maintainers want to make triage faster for new contributors. Which change most directly reduces the time before a first-time contributor's pull request receives feedback?

  1. Adding a pull request template with a checklist and labeling new contributions for maintainer attention Correct answer.
  2. Increasing the number of stars on the repository
  3. Removing continuous integration checks from the pipeline
  4. Adding more permissive license terms to the project

Explanation

A structured template collects the information reviewers need up front, and labeling routes new contributions to someone who will respond. Popularity and licensing do not affect response latency, and removing CI checks trades speed for quality risk.

Question 38Fundamentals of Open Source Software Development

An engineer notices that a widely used open source library is missing documentation for a feature they just learned to use. Which action best reflects the norms of open source collaboration?

  1. File a demand that maintainers document the feature within a deadline
  2. Open a pull request that adds the documentation and offers to revise it based on review Correct answer.
  3. Rewrite the library from scratch to avoid depending on its maintainers
  4. Publish a private fork with the documentation and stop contributing upstream

Explanation

Open source collaboration favors contributing improvements upstream so everyone benefits, and a documentation pull request is a low-risk way to start. Private forks and demands shift work onto others or fragment the community, and a rewrite discards existing effort.

Question 39Fundamentals of Open Source Software Development

What distinguishes a project's 'main' branch from a feature branch in a typical Git-based open source workflow?

  1. The main branch is rewritten on every release to remove old commits
  2. The main branch is the only branch that can contain merge commits
  3. The main branch is owned by the foundation rather than by contributors
  4. The main branch is the integration line whose history releases are built from Correct answer.

Explanation

The main branch serves as the integration point that releases are cut from, while feature branches hold work in progress that is reviewed before merging. Ownership and merge-commit policy vary by project, and rewriting history on every release is not a standard practice.

Question 40Fundamentals of Open Source Software Development

A company wants to depend on a project whose last commit was three years ago but which still receives occasional security patches from a single volunteer. Which assessment is most accurate?

  1. The project is safe because any security patch proves it is actively maintained
  2. The project carries elevated sustainability risk because fixes depend on one person's availability Correct answer.
  3. The project should be forked immediately because a single maintainer is disallowed
  4. The project's age guarantees stability, so no further evaluation is needed

Explanation

A long gap in activity plus a single volunteer indicates a low bus factor and uncertain response capacity, which is a sustainability risk for dependents. One occasional patch does not establish active maintenance, and forking is a heavy remedy rather than an automatic rule.

Question 41Fundamentals of Open Source Software Development

Why is a public issue tracker valuable to an open source project beyond simply recording bug reports?

  1. It provides legal protection against license violations
  2. It replaces the need for a code review process
  3. It guarantees that every reported issue will be fixed by a maintainer
  4. It creates a searchable record of design discussions and decisions that newcomers can learn from Correct answer.

Explanation

Issue trackers preserve the reasoning behind changes, so future contributors can understand prior decisions and avoid reopening settled debates. They do not obligate maintainers to fix everything, substitute for code review, or provide legal protection.

Question 42Fundamentals of Open Source Software Development

A maintainer wants to signal which parts of a repository require review from specific experts. Which mechanism is designed for this purpose?

  1. A CODEOWNERS file mapping paths to responsible reviewers Correct answer.
  2. A .gitignore file listing generated artifacts
  3. A README badge showing build status
  4. A CHANGELOG entry describing the release

Explanation

CODEOWNERS associates file paths with individuals or teams so hosting platforms can request the right reviewers automatically. Build badges, ignore rules, and changelog entries serve unrelated purposes.

Question 43Fundamentals of Open Source Software Development

Which practice most directly helps an open source project satisfy the provenance expectations of enterprise consumers?

  1. Allowing commits to be pushed directly to main without review
  2. Renaming the project for each major release
  3. Requiring sign-off on every commit and publishing signed release tags Correct answer.
  4. Keeping the project's dependency list out of the repository

Explanation

Sign-offs and signed tags create verifiable records of who contributed what and which artifact corresponds to a release, which is what enterprise consumers need for provenance. Unreviewed pushes and hidden dependencies undermine traceability, and renaming releases adds confusion.

Question 44Fundamentals of Open Source Software Development

A project receives a large pull request that mixes a bug fix, a refactor, and a new feature. What is the most effective maintainer response consistent with common open source practice?

  1. Close the pull request without comment to keep the queue short
  2. Merge the whole change immediately to reward the contributor's effort
  3. Reassign the pull request to the contributor's employer for approval
  4. Ask the contributor to split the work into focused pull requests that can be reviewed and merged separately Correct answer.

Explanation

Small, focused changes are easier to review, test, and revert, so maintainers commonly request that mixed work be split. Merging unreviewed code risks quality, and silent closure discourages contributors without explaining the path forward.

Question 45Fundamentals of Open Source Software Development

What is the main reason open source projects document their release process, including version numbering and support windows?

  1. It lets consumers plan upgrades and know which versions still receive fixes Correct answer.
  2. It transfers maintenance responsibility to downstream users
  3. It removes the need to publish changelogs for each release
  4. It guarantees backward compatibility across all future versions

Explanation

A documented release process tells consumers how versions are numbered and how long each line is supported, which is essential for planning upgrades and security patching. It does not shift maintenance to users or guarantee compatibility.

Question 46Fundamentals of Open Source Software Development

In a project that uses semantic versioning, a library publishes version 2.0.0 after 1.9.4. What should a dependent team expect?

  1. The release may contain breaking API changes requiring code updates Correct answer.
  2. The release is guaranteed to be backward compatible
  3. The release is a pre-release that should not be used in production
  4. The release contains only documentation fixes

Explanation

Under semantic versioning the major number increments when incompatible API changes are introduced, so 2.0.0 signals a possible breaking change. Patch releases cover fixes, minor releases add compatible functionality, and pre-releases are marked with suffixes such as -rc.

Question 47Fundamentals of Open Source Software Development

A contributor wants to propose a significant architectural change to a project that uses a formal RFC or enhancement-proposal process. What is the appropriate first step?

  1. Commit the change directly to the main branch to demonstrate feasibility
  2. Implement the full change locally and open a large pull request without prior discussion
  3. Write a proposal document describing the problem, design, and alternatives, then seek review before coding Correct answer.
  4. Open an issue asking maintainers to implement the idea themselves

Explanation

Enhancement-proposal processes exist so design questions and trade-offs are settled with maintainers before significant implementation effort is spent. Coding first or pushing directly to main bypasses that review and often results in rejected work.

Question 48Fundamentals of Open Source Software Development

Which statement best explains why a project might adopt a 'good first issue' label?

  1. It indicates the issue has already been resolved in a later release
  2. It marks issues that maintainers consider unimportant and will never fix
  3. It restricts the issue to contributors from a specific company
  4. It points newcomers to scoped tasks that build familiarity while giving maintainers useful help Correct answer.

Explanation

Labeling newcomer-friendly tasks lowers the barrier to a first contribution and gives maintainers help with work that does not require deep project knowledge. The label does not deprioritize the issue, restrict who may work on it, or mean it is already fixed.

Question 49Open Source Licensing and Usage Guidelines

An enterprise engineering team wants to adopt a permissive license that requires preservation of copyright notices and grants an express patent license. Which license best fits this requirement?

  1. Apache License 2.0 Correct answer.
  2. GNU General Public License v3.0
  3. MIT License
  4. BSD 2-Clause License

Explanation

Apache License 2.0 is a permissive license that includes an express contributor patent grant and requires retention of notices and a NOTICE file where present. MIT and BSD 2-Clause are permissive but do not contain an express patent grant. GPLv3 is copyleft, not permissive.

Question 50Open Source Licensing and Usage Guidelines

A developer copies GPLv3-licensed source code into a proprietary internal service and distributes the compiled binary to a customer. What obligation does GPLv3 impose?

  1. The developer must provide the corresponding source code to the recipient under GPLv3 terms. Correct answer.
  2. The developer must pay a royalty to the Free Software Foundation before distribution.
  3. The developer may distribute the binary if the copyright notice is retained in the documentation.
  4. The developer must relicense the entire service under the MIT License.

Explanation

GPLv3 is a strong copyleft license: when a covered work is conveyed, the distributor must offer the corresponding source code under GPLv3. There is no royalty obligation to the FSF. Retaining notices alone does not satisfy the source-provision requirement.