A proprietary EULA states: "This license is granted on a per-seat basis." What does this mean for a team of 12 developers?
Per-seat licensing means each individual user requires their own license. For 12 developers: 12 seats = 12 licenses needed. Common variations:
Named user — license tied to specific named individuals (non-transferable within a billing period)
Concurrent user — only N users can be logged in simultaneously, regardless of total user count
Device/node — licensed per machine, not per person
Exceeding seat count is a license violation, even if "nobody is actually checking." Audits do happen, and penalties can include back-payment plus fines.
2 / 10
An EULA contains the clause: "Licensee shall not use the Software to perform benchmark tests or publish the results of any benchmark tests." What is this clause called and why does it exist?
Benchmark restriction clauses prohibit publishing performance test results. Vendors include them because:
Performance benchmarks could reveal weaknesses compared to competitors
Benchmarks run on non-production configurations might not represent real-world performance fairly
They prevent "unfair" comparisons in competitor marketing
These clauses are controversial — many security researchers and developers consider them anti-competitive. Notable examples: Oracle, Microsoft SQL Server, and some VMware EULAs historically contained these. When evaluating enterprise software, check for benchmark clauses before publishing internal performance tests.
3 / 10
An EULA states: "Licensee may not reverse engineer, decompile, or disassemble the Software." Under which circumstance might this clause be legally unenforceable in the EU?
EU Directive 2009/24/EC (the Software Directive) preserves the right to decompile software for interoperability — even if the EULA says otherwise. Article 6 allows decompilation when: the information is necessary to achieve interoperability with independently created software, the information is not already available, and the decompilation is limited to the parts necessary. This is why anti-reverse-engineering EULA clauses are more enforceable in the US (where DMCA governs) than in the EU. In the US, courts have sometimes upheld these clauses; in the EU, the statutory right generally prevails.
4 / 10
A SaaS EULA states: "Vendor reserves the right to modify or discontinue the Service with 30 days' notice." What risk does this create for enterprise customers?
Data portability — enterprise migrations can take months; 30 days is rarely enough
No guaranteed refund — the clause does not imply refunds; check the subscription/payment terms separately
Applies regardless of tier — the clause says "the Service," not "free tier"
When reviewing SaaS contracts, negotiate for: longer notice periods (90-180 days minimum for enterprise), explicit data export provisions before termination, and SLA credits or refunds if service is discontinued. The EULA is the floor, not the ceiling — most vendors will negotiate these terms.
5 / 10
A vendor offers software under both a commercial license and the AGPL-3.0. Under the AGPL version, your company built a SaaS product. What obligation does this create?
AGPL-3.0 (Affero GPL) extends the copyleft requirement to network use. Under regular GPL, if you do not distribute the software, you have no obligation to share source. Under AGPL: if users interact with the software over a network (i.e., your SaaS product), you must make the complete corresponding source code available under AGPL. This is exactly why vendors offer AGPL + commercial license dual-licensing: companies that don't want to open-source their SaaS must buy the commercial license. This is the MongoDB, Elastic, and Grafana dual-licensing model.
6 / 10
Review Comment: 'Sarah, I've flagged this code block for review. The documentation mentions a proprietary license restriction regarding access to the compute_resource function. It appears you're bypassing the standard authentication flow and directly calling it. Could you explain why?'
This question tests understanding of how proprietary license restrictions are communicated and addressed within a code review context. The key here is recognizing that Sarah's comment isn't just about a vulnerability; it's about *how* access to the licensed component is governed, specifically bypassing authentication. Option 3 correctly identifies this core concern.
7 / 10
Slack Message: 'Mark: Just confirming – our team's license for ProjectPhoenix is strictly limited to development and testing. We can't use it in production without a separate commercial agreement. Just wanted to avoid any surprises.'
The core of this question is understanding the implications of a 'development and testing' license. It isn't simply about availability; it's about *where* usage is permitted. Option 2 accurately explains that the message emphasizes the limitations on production use, which is crucial for avoiding legal issues.
8 / 10
PR Description: 'Adding a new feature to integrate with the DataStream API. This utilizes a proprietary license component (version 2.1) – please ensure all code changes adhere to the terms outlined in the licensing agreement regarding data export restrictions.'
This scenario tests recognizing that even when adding a new feature, the underlying license terms still apply. Option 2 correctly emphasizes that the PR's development is subject to compliance with the licensing agreement, specifically regarding data export restrictions – a common restriction in proprietary licenses.
9 / 10
Standup Update: 'David: We're continuing to refine our integration with the QuantumEngine. The license dictates that we can only use it for internal research and development; no client-facing applications are permitted.'
This question focuses on understanding limitations imposed by proprietary licenses. David's statement clarifies that usage is confined to internal research and development, prohibiting client-facing applications – a typical restriction to control commercial use. Option 2 correctly identifies this scope limitation.
10 / 10
API Response (Partial): `{"status": "error", "code": 403, "message": "Access Denied: License Violation - Attempt to utilize SecureVault for external data processing."}`
This question tests interpreting an error response that directly relates to a proprietary license violation. The 'Access Denied' message and specific reference to unauthorized use of the `SecureVault` component clearly indicate a breach of licensing terms. Option 2 accurately explains this critical implication.
What will I learn from the "Proprietary License Reading | Coders Lingo" exercise?Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Software Licensing exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss software licensing topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Software Licensing exercises?
See the full Software Licensing exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.