IB COMPUTER SCIENCE | A3 ASSESSMENT
DATABASES: END OF TOPIC REVIEW
Check relational design, normalisation, SQL and the labelled HL material through recall, applied tasks and developed written responses.
BEFORE YOU BEGIN
Split this review into two sessions if needed: first the automatic checks and applied tasks, then the written work. As a flexible guide, allow 75–100 minutes for the common review and additional time for the HL extension; adjust to the detail of your written answers.
Sections A and B award one point for each fully correct automatic item, with no partial credit within an item. Section C has separately suggested content marks. These are original practice questions, not an official IB paper, grade boundary or prediction.
Choose your level below. Write calculations, diagrams and Section C answers in your exercise book before revealing guidance. Answers and selections last while the page remains open.
Automatic total: 36 points. Suggested written total: 72 marks, assessed separately.
C | WRITTEN COMMUNICATION AND SUBJECT KNOWLEDGE
Write in your exercise book before revealing the guidance. The table gives practical guidance based on the IB command terms supplied in the guide; it is not the Cambridge command-word table.
In particular, IB compare focuses on similarities, while distinguish asks for differences. If you need to address both, the question can request each separately. All main commands below are highlighted.
| IB command term | What to provide in this review | Writing approach |
|---|---|---|
| Calculate | A numerical result with relevant working stages | Show the calculation and units |
| Describe | A detailed account | Give features or an ordered process, not only a name |
| Explain | A detailed account including reasons or causes | Link ideas with because, therefore, resulting in or leading to |
| Compare | Similarities, referring to both items throughout | Both…; each…; in both approaches… |
| Compare and contrast | Similarities and differences, referring to both throughout | Use both for similarities and whereas for differences |
| Discuss | A considered, balanced review of relevant arguments or factors | Develop strengths and limits in context and reach a supported judgement |
| Distinguish | Clear differences between the concepts | Whereas…; unlike…; this holds a value while that holds an address… |
| Construct | Information displayed in diagrammatic or logical form | Supply the requested table, map or connected diagram |
| Deduce | A conclusion reached from the supplied information | Use the map or data as evidence |
| Justify | Valid reasons or evidence for a choice | Connect the choice to the stated requirement |
| Evaluate | An appraisal weighing strengths and limitations | Balance relevant factors and reach a supported judgement |
A connective earns no automatic mark by itself: it must express an accurate relationship. For example, “a foreign key rejects the specified missing-parent reference, therefore a stored membership cannot point to a nonexistent student under that rule” explains a mechanism and consequence. Suggested marks reward subject content, not extra unofficial grammar marks.
C1 | SHARED RELATIONAL FACTS
6 suggested marks | COMMON SL/HL
Store each student’s details once under StudentID, then reference that ID in Enrolment. A composite (StudentID,ClubID) key can identify one membership if the rule is one membership per pair. Updating a stored email in Student avoids contradictory copies across memberships, therefore reports can use one maintained fact. Foreign keys reject specified missing-parent references. However, valid-looking values can still describe the wrong person, so constraints do not prove every real-world fact.
SUGGESTED MARKING POINTS
- Identifies one Student row per unique non-null StudentID.
- Uses an Enrolment reference to connect the student.
- Describes the membership pair key under an explicit assumption.
- Explains reduced repeated descriptive data.
- Links reduced duplication to avoiding conflicting updates.
- Explains a valid limit of constraints or the design.
Writing focus: Use because or therefore to connect the structure to the consistency benefit; repeated IDs are not automatically bad redundancy.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC2 | FROM REQUIREMENTS TO ERD
6 suggested marks | COMMON SL/HL
| Relationship | Participation |
|---|---|
| Student to Enrolment | Student: zero or many enrolments; Enrolment: exactly one Student. |
| Club to Enrolment | Club: zero or many enrolments; Enrolment: exactly one Club. |
Draw the three labelled entities connected through Enrolment, with minimum and maximum participation at the correct ends. A conceptual schema captures these business relationships. A logical schema adds attributes, keys and relational structures; a physical schema describes implementation/access choices such as indexes.
SUGGESTED MARKING POINTS
- Draws Student, Club and Enrolment as separate labelled entities.
- Connects Student–Enrolment and Club–Enrolment rather than leaving an unresolved many-to-many link.
- Shows Student/Club zero-to-many participation appropriately.
- Shows each Enrolment’s exactly-one parent participation.
- Distinguishes conceptual business meaning from logical structures/keys.
- Describes physical storage/access implementation choices.
Writing focus: Label both directions and show minimums as well as maximums; a list of entity names is not a complete diagram.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC3 | CONSTRUCT A 3NF DESIGN
6 suggested marks | COMMON SL/HL
| OrderID | ProductID | OrderDate | CustomerID | CustomerName | ProductName | Quantity |
|---|---|---|---|---|---|---|
| 501 | P1 | 2026-09-02 | C1 | Maya | Kit | 2 |
| 501 | P2 | 2026-09-02 | C1 | Maya | Glasses | 1 |
| 502 | P1 | 2026-09-03 | C2 | Leon | Kit | 1 |
| Table | Fields / key roles |
|---|---|
| Customer | CustomerID PK, CustomerName |
| Order | OrderID PK, OrderDate, CustomerID FK → Customer |
| Product | ProductID PK, ProductName |
| OrderLine | OrderID PK/FK → Order, ProductID PK/FK → Product, Quantity |
Order and Product remove partial dependencies from the pair-keyed relation. Customer separates the transitive descriptive dependency from Order. Quantity stays with its complete order-product identity.
SUGGESTED MARKING POINTS
- Constructs Customer with CustomerID PK and CustomerName.
- Constructs Order with OrderID PK, OrderDate and CustomerID reference.
- Constructs Product with ProductID PK and ProductName.
- Constructs OrderLine with the complete composite primary key.
- Shows both OrderLine foreign-key targets and Quantity.
- Explains the dependency-based split or accurately preserves the stated assumptions and associations.
Writing focus: Supply explicit fields and key labels; explain at least one reason for a split rather than only listing four table names.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC4 | NORMAL FORMS AND DEPENDENCIES
6 suggested marks | COMMON SL/HL
1NF avoids repeating groups and gives one domain value per field, but repeated descriptions can still cause anomalies. Non-prime means an attribute in no candidate key. 2NF additionally requires non-prime attributes to depend on the whole of every candidate key, so ProductName is separated from the composite-key line relation. 3NF addresses the remaining transitive CustomerName dependency through CustomerID in this straightforward design. Repeating names can create an update anomaly if one copy changes and another does not. The formal 3NF condition permits each non-trivial X → A only when X is a superkey or A is prime.
SUGGESTED MARKING POINTS
- Describes atomic-domain/no-repeating-group 1NF.
- Defines non-prime relative to all candidate keys.
- Describes whole-candidate-key requirement for 2NF.
- Applies partial dependency to ProductName or Order fields.
- Describes and applies the transitive dependency/3NF rule accurately.
- Explains a specific insertion, update or deletion anomaly.
Writing focus: Use the same example throughout so the differences are clear; avoid treating the words atomicity and transaction atomicity as identical.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC5 | DENORMALISATION FOR REPORTING
6 suggested marks | COMMON SL/HL
A stored total can avoid repeated aggregation for a frequently read dashboard, potentially lowering read work. However, line insertions, changes and deletions must update or invalidate the total, otherwise the report can be inconsistent. It adds storage and write/maintenance cost, including failure and concurrency concerns. Measure the actual bottleneck and consider indexes or a suitable view before adding redundant data. I would use the stored total only if the measured read benefit justifies the maintenance design and its freshness guarantee meets the report’s needs.
SUGGESTED MARKING POINTS
- Explains a concrete read-performance benefit.
- Explains the redundant-total consistency risk.
- Connects line changes to a maintenance/refresh requirement.
- Explains a storage, write, failure or concurrency cost.
- Considers measurement or an appropriate alternative.
- Reaches a supported context-specific judgement.
Writing focus: Balance benefits and costs, then state a conditional judgement; “it is faster” without evidence or maintenance is insufficient.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC6 | CONSTRUCT THE REQUESTED QUERY
6 suggested marks | COMMON SL/HL
| StudentID | StudentName | YearGroup |
|---|---|---|
| 1 | Maya | 12 |
| 2 | Leon | 13 |
| 3 | Aisha | 12 |
| LoanID | StudentID | BookTitle | DaysLoaned |
|---|---|---|---|
| 101 | 1 | Python Basics | 12 |
| 102 | 1 | Robot Design | 8 |
| 103 | 2 | Python Projects | 20 |
| 104 | 3 | Web Design | 12 |
SELECT s.StudentName, l.BookTitle, l.DaysLoaned FROM Student AS s JOIN Loan AS l ON s.StudentID = l.StudentID WHERE s.YearGroup = 12 AND l.DaysLoaned BETWEEN 8 AND 12 AND (l.BookTitle LIKE 'Python%' OR l.BookTitle LIKE '%Design%') ORDER BY l.DaysLoaned DESC, s.StudentName ASC, l.LoanID ASC;
The result is Aisha/Web Design/12, Maya/Python Basics/12 and Maya/Robot Design/8. Equivalent correct aliases or full qualified table references are valid.
SUGGESTED MARKING POINTS
- Selects the three requested output columns from the appropriate sources.
- Joins student key to borrower StudentID.
- Filters YearGroup = 12.
- Uses the inclusive range correctly.
- Groups both complete LIKE alternatives with the correct wildcard positions.
- Specifies descending days, ascending names and a suitable stable tie-breaker.
Writing focus: Construct executable logical structure, not a paragraph saying “use a join”; check that all restrictions apply to both title alternatives.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC7 | MODIFY RECORDS AND MAINTAIN AN INDEX
6 suggested marks | COMMON SL/HL
UPDATE Equipment SET Quantity = Quantity + 2, Category = 'Sensors' WHERE ItemID = 304; DELETE FROM Equipment WHERE ItemID = 305;
The targeted row receives Quantity 8 and Category Sensors. DELETE removes the whole matching 305 record if it exists and the rules permit it. The Category index must reflect the new association, so the modification adds relevant maintenance work. The DBMS normally performs that work automatically; later rebuilding or reorganisation is considered for an actual physical-layout need rather than after every row change.
SUGGESTED MARKING POINTS
- Uses a targeted UPDATE with Quantity = Quantity + 2.
- Correctly assigns Category with comma-separated SET syntax or equivalent separate targeted statement.
- Explains the resulting quantity and target scope.
- Uses/describes DELETE for whole matching record removal.
- Links the indexed Category change to relevant automatic association maintenance and resource work.
- Distinguishes routine maintenance from a possible later justified rebuild/reorganisation.
Writing focus: Link each clause to its effect, then distinguish logical correctness from physical maintenance cost.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC8 | STRUCTURE, VALUES AND TYPES
6 suggested marks | COMMON SL/HL
ALTER TABLE Club ADD Room VARCHAR(30); UPDATE Club SET Room = 'Lab 2' WHERE ClubID = 1;
ALTER changes the definition and is DDL, whereas UPDATE changes values in existing records and is DML. Text can preserve the meaningful leading zeros of code 00127. An appropriate exact decimal type can represent the fee’s required decimal precision. Related identifiers and FK definitions must be compatible. Types still need suitable mandatory, format or range rules where required.
SUGGESTED MARKING POINTS
- Distinguishes structural DDL from record-focused DML.
- Gives a suitable ALTER example for adding Room.
- Gives a targeted UPDATE assigning the room value.
- Justifies text for the meaningful identifier format.
- Justifies an appropriate exact decimal fee representation.
- Explains compatible references or a relevant limit requiring additional constraints.
Writing focus: Use whereas to make the language-type difference explicit and because to justify the type choices.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC9 | HL: AGGREGATES AND VIEW FRESHNESS
6 suggested marks | HL ONLY
COUNT(*) is 3, COUNT(Score) is 2 and AVG(Score) is (80+60)/2 = 70. The NULL is not a third known value. A new virtual summary derives its mean from visible base scores, giving (100+60)/2 = 80. The stored snapshot remains 70 until its maintenance policy updates it. A refresh recomputes/maintains the stored result with storage and processing costs; it does not automatically reload a browser.
SUGGESTED MARKING POINTS
- COUNT(*) = 3.
- COUNT(Score) = 2.
- AVG = 70 with the correct known-value denominator.
- Describes the virtual result as newly derived from visible source data, giving 80.
- Describes the unchanged materialized result as 70 before refresh.
- Explains the refresh role or a correct freshness/maintenance limitation.
Writing focus: Show the denominator, then describe each view separately rather than saying both “update automatically”.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC10 | HL: A RELIABLE TRANSFER
6 suggested marks | HL ONLY
BEGIN starts the related work. The application verifies an eligible debit and intended credit, then commits only the correctly completed transfer. On failure it stops and rolls back pending changes. Atomicity prevents a half-transfer becoming the final committed result; consistency preserves non-negative balances and total 1300 through correct logic and constraints. Isolation governs simultaneous interference under the chosen level. Durability retains confirmed committed work through covered recovery. Zero changed rows may not be an SQL error, so the application must check the outcome.
SUGGESTED MARKING POINTS
- Describes BEGIN, checks the intended affected rows and commits only the successful complete action.
- Describes failure handling with ROLLBACK and original balances retained.
- Describes atomicity using both included transfer steps.
- Describes consistency using correct rules and total 1300.
- Describes isolation with appropriate concurrent-operation qualification.
- Describes durability as retaining confirmed committed work through covered recovery.
Writing focus: Use the scenario for each ACID property and connect the command path to success/failure; a zero-row outcome must not be mistaken for a completed transfer.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC11 | HL: WAREHOUSE AND ANALYTICAL METHODS
6 suggested marks | HL ONLY
The warehouse reconciles source meanings and retains event-time history, therefore reports can compare consistent categories over periods. OLAP lets users slice, dice or drill through monthly category summaries to locate contributors. Association rule discovery examines co-occurring products and can suggest a bundle for investigation, whereas regression estimates numeric delivery duration. These outputs can support planning, but an association is not proof of causation and a numeric prediction has uncertainty that needs evaluation.
SUGGESTED MARKING POINTS
- Explains integration of source meanings.
- Links retained time context to historical comparison.
- Explains an appropriate OLAP operation and its analytical purpose.
- Explains association rule discovery for co-occurring products.
- Explains regression for numeric delivery duration.
- Connects an evidence/evaluation limitation to how a result should be used.
Writing focus: Use therefore to link preparation to comparable reports, and distinguish each analytical output rather than calling every task “AI”.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentC12 | HL: DISTRIBUTED STOCK
6 suggested marks | HL ONLY
North and South are different logical partitions; the additional North copy is a replica of the same five kits. A complete query combines each logical portion once to obtain eight, not thirteen. Routing/coordinating services can hide selected distribution details, and logical names can hide physical location. If South is unavailable with no suitable accessible replica, the complete result is unknown rather than definitely five. Safe continued service needs adequate surviving resources and protocols; authentication, authorisation and protected communications must also cover the nodes and copies.
SUGGESTED MARKING POINTS
- Distinguishes different logical partitions from replica copies.
- Describes the complete logical sum as 8 without double-counting.
- Describes coordinated global query processing across relevant portions.
- Distinguishes broader distribution transparency from hiding physical location.
- Explains that missing South is unavailable/unknown and requires an appropriate failure or partial-result response.
- Describes a valid security or fault-tolerance condition beyond the mere existence of a copy.
Writing focus: Use separate sentences for logical records, physical copies and failure behaviour; never silently replace unknown data with zero.
Equivalent accurate wording and methods can be valid. Use the points as self-assessment guidance, not an official IB markscheme.
Revisit related contentCHECK THE QUALITY OF YOUR WRITING
Did you answer the command? For explain, check the reason or cause; for compare, address both items through similarities; for compare and contrast, include differences too; for discuss, balance relevant factors in context; for distinguish, make the differences explicit; for evaluate, weigh strengths and limitations and support your conclusion.
For construct, check labels, connections and completeness. For calculate, show enough working to follow your method and label units. Select two weak responses and rewrite them after revising. Keep the written total separate from your automatic result.
YOUR NEXT REVISION STEP
Submit the automatic sections for targeted revision links.
Record your own written marks using the suggested points. Choose two weaknesses and attempt new examples after revising. Use the A3 revision page for worked content and a personal flashcard list, or return to the IB course index.