QCM : Understanding Software Licensing and Open Source — 4 questions

Questions et réponses du QCM

1. If a user obtains proprietary software under a license, what action are they typically allowed to perform according to copyright and licensing rules?

Use the software without ownership or rights to share it
Modify and redistribute the software freely
Claim ownership of the software code
Share the software with others without restriction

Use the software without ownership or rights to share it

Explication

Proprietary software licenses allow the user to use the software but do not grant ownership or rights to share it, as copyright grants exclusive control to the author by default. Review: Copyright basics and proprietary software model. Course evidence: "- Copyright is automatic upon software creation, granting exclusive rights to the author by default as 'All Rights Reserved'. - Proprietary software licenses allow use but do not grant ownership or rights to share the software."

2. If you want to release software that ensures any derivative work must remain open source but still allows proprietary extensions in separate files, which license category should you choose?

Permissive licenses that allow proprietary versions
Weak Copyleft licenses that apply copyleft at the file level
Strong Copyleft licenses that require the entire derivative work to be open source
Public Domain with no restrictions

Weak Copyleft licenses that apply copyleft at the file level

Explication

Weak copyleft licenses apply copyleft conditions at a file level, allowing proprietary extensions, thus ensuring derivative works remain open source only at the file level while permitting proprietary additions. Permissive licenses allow proprietary versions without such restrictions, strong copyleft requires the entire derivative work to be open source, and Public Domain imposes no restrictions. Review: License categories and spectrum from permissive to strong copyleft. Course evidence: "- License categories range from Public Domain (no restrictions) through Permissive (e.g., MIT, Apache), Weak Copyleft (e.g., MPL, LGPL), to Strong Copyleft (e.g., GPL). - Permissive licenses allow users to do almost anything including making proprietary…"

3. How do the GPL and MIT licenses differ in their requirements regarding derivative works and source code disclosure?

GPL permits proprietary derivatives without disclosure, MIT requires all derivatives to be open source
Both GPL and MIT require source code disclosure but differ in commercial use permissions
GPL requires derivative works to be GPL and source code disclosure, while MIT allows proprietary derivatives without sharing source code
MIT requires derivative works to be GPL licensed, while GPL allows proprietary derivatives

GPL requires derivative works to be GPL and source code disclosure, while MIT allows proprietary derivatives without sharing source code

Explication

GPL is a strong copyleft license requiring derivative works to also be GPL and source code disclosure, while MIT allows modification and proprietary derivatives without sharing source code, only requiring inclusion of license text and copyright notice. Review: Characteristics and effects of GPL and MIT licenses. Course evidence: "- GPL is a strong copyleft license requiring source code disclosure when distributing binaries and that derivative works must also be GPL. - The 'viral' effect of GPL means that using GPL code forces the entire project to adopt GPL, which can deter some…"

4. What is the primary role of the Mozilla Public License (MPL) in software development?

To restrict any commercial use of the licensed software
To enforce that all code in a project must be distributed under the same license
To require all modifications to be released under a strong copyleft license
To allow proprietary files to coexist with MPL-licensed files enabling hybrid open source and proprietary development

To allow proprietary files to coexist with MPL-licensed files enabling hybrid open source and proprietary development

Explication

The MPL's file-level copyleft allows proprietary files to coexist with MPL-licensed files, enabling hybrid open source and proprietary development, which is its primary role as stated in the source. Review: Real-world license case studies and compatibility challenges. Course evidence: "Mozilla Public License (MPL) : A file-level copyleft license allowing proprietary files alongside MPL-licensed files, enabling hybrid development."

Révisez avec les flashcards

Mémorisez les réponses avec 8 flashcards sur Understanding Software Licensing and Open Source.

Copyright — definition?

Legal rights granted automatically upon creation.

Proprietary software — role?

Allows use but restricts sharing or modification.

License spectrum — range?

From public domain to strong copyleft.

Voir les flashcards →

Approfondir avec la fiche

Consultez la fiche de révision complète sur Understanding Software Licensing and Open Source.

Voir la fiche →

Cours similaires

Introduction à l'Informatique et IA

Introduction aux marchés publics et réglementations du bâtiment

Bases de données

Gestion des imprimantes Windows et PDF

Introduction aux bases de données relationnelles

Bases de données

Maîtrise des Boucles en Programmation

Programmation

Maîtrise des fonctions et paradigmes de programmation

Programmation

Crée tes propres QCM

Importe ton cours et l'IA génère des QCM avec corrections en 30 secondes.

Générateur de QCM