Background Concept

A logic circuit can be written as a Boolean expression by tracing each signal from the inputs to the output. Each gate has a direct logical meaning:

• NOT inverts a single input.
• AND is true only when both inputs are true.
• OR is true when at least one input is true.
• NOR means OR followed by NOT.
• XOR is true when the two inputs are different.

When a circuit has several stages, you write the expression one gate at a time. Brackets are important because they show which operation happens first.

Understanding the Question

The question gives one circuit with inputs P, Q, R and S, and asks for the expressions for the two outputs X and Y.

So the task is not to simplify anything. It is just to read the circuit correctly and convert what each branch does into a logic expression.

For X, the top half of the circuit must be followed.
For Y, the lower half of the circuit must be followed.

Approach

Start at the left and move right.

For each output:

1. Find the first gate fed by the input lines.
2. Write the expression produced by that gate.
3. If that result goes into another gate, wrap it in brackets and continue.
4. Stop when you reach the labelled output.

This method prevents missed inversions and missed brackets.

Step-by-Step Reasoning

For X:

1. Input P passes through a NOT gate, so this becomes NOT P.
2. That result and input R go into an OR gate, giving:
   ((NOT P) OR R)
3. That output and input Q go into an AND gate, so:
   X = ((NOT P) OR R) AND Q

For Y:

1. Inputs Q and R go into a NOR gate.
2. A NOR gate means OR first, then NOT, so this gives:
   NOT(Q OR R)
3. That result and input S go into an XOR gate, so:
   Y = (NOT(Q OR R)) XOR S

That is all the question needs. No extra simplification is required.

Key Takeaways

• Convert a circuit into an expression by following the signal path gate by gate.
• A NOR gate is NOT( ... OR ... ), not just NOT ... OR ....
• Brackets matter in multi-stage expressions.
• XOR means the two inputs must be different.

Common Mistakes

• Writing NOT P OR R AND Q without brackets, which makes the order unclear.
• Treating NOR as just OR, and forgetting the inversion.
• Using the wrong variable at a gate input by tracing the wire incorrectly.
• Writing NOT Q OR R instead of NOT(Q OR R) for the NOR gate.

Things to Be Careful About

• Follow the wires, not just the vertical position of the inputs.
• Put brackets around any intermediate result that feeds another gate.
• Distinguish carefully between OR and XOR symbols.
• For NOR, the inversion applies to the whole OR result.

Background Concept

A truth table shows the output of a logic circuit for every possible combination of its inputs.

With three inputs A, B and C, there are:

possible rows.

This circuit contains:

• an XOR gate on A and B
• a NOT gate after that XOR
• an AND gate on B and C
• an OR gate combining those two branch outputs

Useful gate rules:

• A XOR B is 1 when A and B are different.
• NOT flips 0 to 1 and 1 to 0.
• B AND C is 1 only when both are 1.
• OR gives 1 if either input is 1.

Understanding the Question

The question asks you to complete the truth table for the circuit in Fig. 1.2.

That means you must work through all 8 input combinations and decide the output X each time. The table includes one Working space column, so it is sensible to use that for one intermediate value. A natural choice is NOT(A XOR B), because that is one whole branch of the circuit.

The final output is:

X = NOT(A XOR B) OR (B AND C)

Approach

For each row:

1. Work out A XOR B.
2. Invert it to get NOT(A XOR B).
3. Work out B AND C.
4. OR those two results to get X.

Even though the printed table has only one working column, while learning it is best to think in terms of both branches of the circuit.

Step-by-Step Reasoning

First write the expression represented by the circuit:

• top branch: A XOR B, then NOT, so NOT(A XOR B)
• bottom branch: B AND C
• final gate: OR

So:

X = NOT(A XOR B) OR (B AND C)

Now evaluate row by row.

If we use the printed Working space column for NOT(A XOR B), the completed table becomes:

You can check the pattern:

• whenever A and B are equal, the XOR is 0, so the NOT gives 1, which makes X equal to 1 regardless of the bottom branch
• when A and B are different, the top branch gives 0, so X depends entirely on whether B AND C is 1

Key Takeaways

• Build the truth table by following each branch of the circuit separately.
• XOR is often the gate students misread, so check whether the inputs are equal or different.
• An intermediate working column helps avoid mistakes in the final output column.
• The final output of a multi-stage circuit is easiest to find from the full Boolean expression.

Common Mistakes

• Confusing XOR with OR. XOR is 1 only when the inputs differ.
• Forgetting to apply the NOT after the XOR.
• Calculating B AND C incorrectly and giving 1 when only one input is 1.
• Filling the final X column directly without working systematically, which often causes row errors.

Things to Be Careful About

• Use all 8 input combinations exactly once.
• Keep the row order consistent with the table given.
• If you choose a value for Working space, keep it the same meaning on every row.
• Remember that the final gate is OR, so only one branch needs to be 1 for X to be 1.

Background Concept

Real-time bit streaming is used when media such as audio or video must be delivered continuously as it is being watched or listened to. Instead of sending a whole file first and making the user wait, the data is transmitted in a steady flow.

A buffer is normally used at the receiving device. This is a small temporary storage area that holds a short section of the stream before playback starts. The purpose of the buffer is to smooth out small delays in transmission.

Real-time streaming is different from downloading a file. With a download, the complete file is usually received before it is used. With real-time streaming, playback begins before the whole data has arrived.

Understanding the Question

The question says the programmers are using live video conferences. The important clue is the word live and the phrase real-time bit streaming. So this is not about saving a video file first; it is about how the video is transferred so that people can watch and hear it immediately during the conference.

To answer well, you need to explain the transfer process itself: continuous sending, receiving while still transmitting, buffering, and immediate playback.

Approach

A good way to answer is to describe the sequence:

1. The live video is captured and sent continuously.
2. The receiving device starts receiving data before the transmission has finished.
3. A buffer temporarily stores a small amount.
4. Playback begins from the buffer while more data continues to arrive.
5. If transmission cannot keep up, the stream may pause or lose quality.

That gives a complete explanation rather than just defining streaming in one short sentence.

Step-by-Step Reasoning

The conference video is being generated live by cameras and microphones. Because it is real-time, the sender does not wait until the meeting ends and then send one complete file. Instead, the media data is transmitted continuously across the network.

At the receiving end, the computer or device begins to accept this incoming stream straight away. The whole video does not need to be present before anything can be shown.

Before playback starts, a small amount of the incoming stream is placed into a buffer. This buffer is important because network transmission is not perfectly regular. Some packets may arrive slightly later than others. The buffer gives the device a small reserve of data so the video can continue playing smoothly.

Once enough data is in the buffer, the receiver starts decoding and displaying the video and playing the audio. While this is happening, new data is still arriving. So receiving and playback happen at the same time.

If the network speed drops too much, the buffer may empty faster than it is refilled. When that happens, the video may freeze, pause, or become distorted. That is why a stable connection matters for real-time streaming.

Key Takeaways

• Real-time streaming sends media continuously while it is being used.
• The whole file is not received first.
• A buffer helps smooth out small delays.
• Playback depends on the incoming data arriving fast enough.

Common Mistakes

• Saying it is just downloading a file. Streaming is different because playback begins before the whole data has arrived.
• Forgetting to mention buffering. Buffering is a key part of how streaming works reliably.
• Describing on-demand streaming instead of real-time streaming. Real-time means the data is being delivered live.
• Saying the data is stored permanently first. That is not the normal point of real-time streaming.

Things to Be Careful About

• Use the idea of continuous transfer, not one complete file transfer.
• Make clear that playback starts before the whole video arrives.
• Mention the buffer as temporary storage, not long-term storage.
• Link poor connection speed to interruption in playback, because this is often a scoring point in streaming questions.

Background Concept

Internet communication depends on different hardware devices and communication links.

A modem is short for modulator-demodulator. Its job is to convert digital data from a computer or router into a form suitable for transmission over a communication line, and then convert incoming signals back into digital data.

A dedicated line is a permanent communication link reserved for network traffic. Unlike a temporary connection, it is always available and is commonly used where reliable, continuous data transfer is needed.

Understanding the Question

This part gives a small table with two hardware items: modems and dedicated lines. It asks how each is used when data is transmitted over the internet.

So this is not asking for definitions alone. It is asking for the function or role of each in internet transmission.

Approach

Answer each row with one clear use:

• For modems, focus on signal conversion.
• For dedicated lines, focus on the permanent connection used to carry internet traffic.

Because there are only 2 marks, one correct use for each item is enough.

Step-by-Step Reasoning

A computer processes data digitally. Some communication systems require the signal to be changed so it can travel across the transmission medium being used. A modem performs this conversion when sending and reverses it when receiving. That is why modems are associated with internet access over communication lines.

Dedicated lines are different. They are not about signal conversion; they are about the type of connection. A dedicated line is permanently in place and can be used continuously for internet traffic. This makes it suitable for reliable, high-speed transmission between network points.

So the correct table entries focus on:

• modem: convert digital to analogue and back
• dedicated line: provide a permanent high-speed path for internet data

Key Takeaways

• A modem converts signals for transmission and reception.
• A dedicated line is a permanent communication link.
• In internet infrastructure, different hardware has different roles: conversion versus connection.

Common Mistakes

• Saying a modem stores data. It does not; its role is conversion.
• Describing a dedicated line as a device. It is a type of communication connection.
• Mixing up router and modem functions. A router directs packets; a modem converts signals.
• Saying the World Wide Web instead of the internet. The question is about internet transmission hardware.

Things to Be Careful About

• Keep the modem answer focused on conversion between signal forms.
• Keep the dedicated line answer focused on a permanent or always-available connection.
• Do not overcomplicate a 2-mark table; one precise use per item is enough.
• Use communication terminology accurately: transmission, conversion, permanent connection, high speed.

Background Concept

A bitmapped image is made from tiny individual picture elements called pixels. Each pixel stores colour information.

Two important properties of a bitmap are:

• colour depth (bit depth): how many bits are used to store the colour of one pixel
• resolution: how much detail the image has, often described using measurements such as dots per inch (dpi) or pixels per inch

The number of colours available from a bit depth is found using:

• number of colours = 2^(number of bits)

So with 8 bits, the image can represent 2^8 = 256 different colours.

Understanding the Question

This part gives three short statements about a bitmapped image and asks for the correct technical term or value for each one.

You are expected to know:

• what the smallest unit of a bitmap is
• how to work out the maximum number of colours from a bit depth
• the term used for dpi when discussing displayed image detail

Because it is a table-completion question, each answer should be short and exact.

Approach

Match each statement to the standard bitmap term:

1. smallest element of an image -> identify the correct component name
2. 8-bit depth -> calculate 2^8
3. dpi when displayed -> give the term used for image detail on display

This is mainly recall, with just one very simple calculation.

Step-by-Step Reasoning

First statement:

• A bitmap is made of many tiny picture elements.
• The correct term for one of these elements is pixel.

Second statement:

• Bit depth tells us how many binary combinations are possible.
• With 8 bits, the number of combinations is 2^8.
• 2^8 = 256.
• So the largest number of different colours is 256.

Third statement:

• Dots per inch is a measure of how much detail is shown.
• The general term for this is resolution.

Key Takeaways

• A bitmap image is built from pixels.
• Maximum colours from a bit depth are found using 2^n.
• Resolution describes image detail and may be measured in dpi.

Common Mistakes

• Writing "bit" or "byte" instead of pixel. A bit stores data, but it is not the image element itself.
• Giving 255 instead of 256 for 8-bit colour depth. The count is 2^8, not the highest value only.
• Confusing resolution with colour depth. Resolution is about detail; colour depth is about colour range.

Things to Be Careful About

• Read exactly what is being asked: the term, not a description.
• For bit depth questions, use the number of possible combinations, not the denary range endpoints.
• Use the accepted technical word resolution rather than a vague phrase such as "quality".

Background Concept

A common AI technique for identifying people from camera images is facial recognition. This is a pattern-recognition task. The system does not simply store a photograph and look for an identical picture; instead, it looks for important features of the face, such as the distances and relationships between eyes, nose, mouth, jawline, and other measurable characteristics.

In AI terms, the system has usually been trained using many labelled examples. That means it has seen many face images already associated with the correct person. From this, it learns how to recognise patterns that belong to the same person even if lighting, angle, expression, or hairstyle changes slightly.

The result of the analysis is often a facial template or feature vector rather than the raw image itself. This template is then compared against stored templates in a database. If the similarity is high enough, the person is treated as a match.

Understanding the Question

The question says the shop uses digital cameras and AI to identify customers as they enter. So this is asking for the process of AI-based identification, not just the name of the technology.

The important clues are:

• digital cameras provide the input image
• AI is used to identify each customer
• the system must match the person to their account

So the answer needs to explain the stages from image capture, through AI analysis, to matching with a stored account.

Approach

A good way to answer this is to describe the facial-recognition pipeline in order:

1. capture the customer’s face
2. analyse it to find unique features
3. compare those features with stored data
4. choose the matching customer account or reject if there is no match

That gives clear, mark-worthy steps and directly answers how AI is being used.

Step-by-Step Reasoning

First, the camera must collect data. The system needs an image or video frame of the customer entering the shop. Without that input, the AI has nothing to analyse.

Next, the AI processes the image. It detects where the face is in the image and measures important facial characteristics. These are the parts that help distinguish one person from another. For example, the AI might analyse the shape of the face or the relative positions of facial features. The exact internal method is not needed in the exam, but the key idea is that the AI extracts distinguishing patterns.

Then the system compares the extracted pattern with stored patterns in its database. These stored patterns belong to customers who already have accounts. In many real systems, the AI model has also been trained on many examples so that it can make reliable matches even when the face is not shown in exactly the same way as before.

Finally, if one stored record is sufficiently similar, the system identifies that person and links them to the correct customer account. If no acceptable match is found, the system cannot identify the person, so they would not be allowed through the barrier.

That sequence is exactly what the question is looking for: input image, AI analysis, comparison, then identification.

Key Takeaways

• AI can be used for facial recognition by finding patterns in images.
• The camera captures the raw input, but the AI performs the recognition.
• Identification normally involves comparing extracted features with stored templates or trained data.
• A successful match can then be used to link the person to an account.

Common Mistakes

• Saying only "it uses face recognition". That names the method but does not explain how it works.
• Describing a human operator checking the image. The question is specifically about AI, so the process must be automated.
• Saying the system matches the whole image exactly pixel by pixel. Real AI recognition depends on features or patterns, not an identical photograph.
• Forgetting the final step of linking the recognised person to their account.

Things to Be Careful About

• Keep the answer focused on identification, not on payment or barriers unless it helps explain what happens after matching.
• Make it clear that the system compares the captured face with stored customer data.
• If you mention training data, do not let that replace the matching stage; both ideas are useful, but the actual identification still needs comparison with stored records.
• Avoid vague statements like "the computer knows who it is" without describing the matching process.

Background Concept

A sensor is an input device that detects a physical property or reads data automatically so that a computer system can respond. In a retail system, sensors can be used to detect that an item has been moved, removed, or passed a certain point.

One suitable technology is RFID, which stands for Radio Frequency Identification. An RFID system usually has two parts:

• an RFID tag attached to the item
• an RFID reader that detects and reads the tag

The tag stores identifying data, such as a product code. When the reader detects the tag, the system can look up that code in a database and determine exactly which item it is.

Understanding the Question

The question asks for two things:

1. one type of sensor that could be used
2. how that sensor would identify items taken from a shelf

So the answer must not stop after naming a sensor. It also needs a practical explanation of how the system uses the sensor reading to work out which item was taken.

Approach

Choose a sensor that can do more than just detect movement. Since the shop needs to identify the item, not only notice that something changed, RFID is a strong answer because it can read an item-specific code.

Then explain the process clearly:

• item has a tag
• reader detects the tag
• code is read
• code is matched to the product record

Step-by-Step Reasoning

The best answer here is to name an RFID reader or RFID sensor.

Why is RFID appropriate? Because the system needs to identify items automatically. If every item has an RFID tag, that tag can store a unique product code or identifier.

When the customer takes the item from the shelf, the RFID reader near the shelf detects the tag. The reader reads the code stored on it.

The computer system then uses that code to search its database. Once the code matches a record, it knows which product was taken. That product can then be added to the customer’s account.

This is stronger than simply saying "it detects an item" because the question specifically asks how the item is identified.

Key Takeaways

• A sensor question usually needs both the device name and what data it provides.
• RFID is useful when individual items must be recognised automatically.
• Identification normally happens by reading a code and matching it with a database record.

Common Mistakes

• Naming a sensor but not explaining how it identifies the item.
• Choosing a sensor that only detects presence, such as a basic motion sensor, without saying how the exact product is recognised.
• Saying "barcode scanner" without explaining that the code is read and matched to a database. Also, a barcode scanner is less realistic for automatic shelf removal unless specifically positioned and used.
• Describing charging the account instead of explaining identification.

Things to Be Careful About

• The question asks for one type of sensor, so one clear valid example is enough.
• Make sure your explanation includes the data being read, such as a product code.
• Keep the wording linked to the shelf system: the item is taken, the tag is read, and the product is identified.
• Avoid giving a sensor that cannot reasonably identify the item by itself unless you explain the wider setup very carefully.

Background Concept

An entity-relationship (E-R) diagram shows how tables in a relational database are linked. Each entity represents a table, and the relationship line between entities shows how many records in one table can be linked to records in another table.

A common way to work out the relationships is to look at the foreign keys:

• a primary key uniquely identifies a record in its own table
• a foreign key stores the primary key value from another table
• if a table contains a foreign key, many records in that table can usually refer to one record in the parent table

So a foreign key usually indicates a one-to-many relationship from the parent table to the table containing the foreign key.

Understanding the Question

You are given four tables:

• CUSTOMER
• CUSTOMER_CARD_DATA
• ORDER
• ORDER_ITEM

You need to complete the E-R diagram by adding the correct relationship lines and cardinalities between these tables.

The important clues are in the table structures:

• CUSTOMER_CARD_DATA contains CustomerID
• ORDER contains CustomerID
• ORDER_ITEM contains OrderID

Those attributes show which table each one depends on.

Approach

Start from the foreign keys.

1. Find which table owns the original primary key.
2. Find which table stores that key as a foreign key.
3. Draw a one-to-many relationship from the parent table to the child table.

That gives:

• one CUSTOMER can have many card records
• one CUSTOMER can have many orders
• one ORDER can have many order items

Step-by-Step Reasoning

CUSTOMER_CARD_DATA has the attribute CustomerID.
That means each card record belongs to one customer, but a customer may have several cards stored. So the relationship is:

• CUSTOMER 1 : many CUSTOMER_CARD_DATA

ORDER also has the attribute CustomerID.
That means each order belongs to one customer, but a customer may place many orders. So the relationship is:

• CUSTOMER 1 : many ORDER

ORDER_ITEM has the attribute OrderID.
That means each order item belongs to one order, but one order can contain many items. So the relationship is:

• ORDER 1 : many ORDER_ITEM

That is exactly what must be shown in the completed diagram.

Key Takeaways

• Foreign keys are the main clue for building E-R relationships.
• A table containing a foreign key is usually on the many side of the relationship.
• A parent table whose primary key is referenced is usually on the one side.

Common Mistakes

• Reversing the relationship direction, for example showing many customers for one order. Each order belongs to one customer, not the other way round.
• Missing one of the links, especially ORDER to ORDER_ITEM.
• Drawing a direct relationship between CUSTOMER and ORDER_ITEM, even though the link is through ORDER.

Things to Be Careful About

• Use the table names exactly as given.
• Put the many end on CUSTOMER_CARD_DATA, ORDER, and ORDER_ITEM.
• Do not invent extra relationships that are not supported by the foreign keys.

Background Concept

A candidate key is an attribute, or set of attributes, that could uniquely identify each record in a table. Any candidate key is suitable to become the primary key, although only one is chosen as the actual primary key.

For a single attribute to be a candidate key, its value must be unique for every record and it should not be null.

Understanding the Question

The table is CUSTOMER_CARD_DATA with attributes:

• CardID
• CustomerID
• CardType
• CardNumber
• EndDate

You are asked for one attribute that could be a candidate key. That means you need an attribute that could uniquely identify each card record.

Approach

Check which attributes are likely to be unique.

• CustomerID cannot be unique because one customer may have more than one card.
• CardType cannot be unique because many people can have the same card type.
• EndDate cannot be unique because many cards can expire on the same date.
• CardNumber is expected to be unique for each card.

Step-by-Step Reasoning

CardNumber is the best choice because each payment card should have a different card number.

CustomerID is a foreign key, so it can repeat for customers who store more than one card.

CardType and EndDate are clearly not unique enough to identify one record each.

So CardNumber is a valid candidate key.

Key Takeaways

• A candidate key must uniquely identify each row.
• Foreign keys often repeat, so they are usually not candidate keys for that table.
• Real-world meaning helps: card numbers are intended to be unique.

Common Mistakes

• Giving CustomerID. That would not work if one customer has several cards.
• Giving CardType or EndDate, which are not unique.
• Confusing the existing primary key with the idea of a different possible candidate key.

Things to Be Careful About

• The question asks for an attribute in CUSTOMER_CARD_DATA, not from another table.
• A candidate key must be unique, not just useful or descriptive.
• In exam questions like this, choose the most clearly unique single attribute.

Background Concept

A foreign key is an attribute in one table that refers to the primary key of another table. Foreign keys create links between tables and support relationships such as one-to-many.

For example:

• a customer ID in another table points back to a customer record
• an order ID in another table points back to an order record

Understanding the Question

You need to name two tables that contain at least one foreign key, and for each of those tables give one foreign-key attribute.

From the database structure:

• CUSTOMER_CARD_DATA contains CustomerID
• ORDER contains CustomerID
• ORDER_ITEM contains OrderID

All of those are foreign keys.

Approach

Look for attributes that repeat the name of a primary key from another table.

• CustomerID is the primary key of CUSTOMER
• OrderID is the primary key of ORDER

Any table containing one of those as a non-primary attribute contains a foreign key.

Step-by-Step Reasoning

In CUSTOMER_CARD_DATA, the attribute CustomerID links each card record to a customer in CUSTOMER. So that is a foreign key.

In ORDER_ITEM, the attribute OrderID links each item to an order in ORDER. So that is a foreign key.

ORDER also contains the foreign key CustomerID, so that table would also have been acceptable.

Key Takeaways

• A foreign key repeats the primary key of another table.
• Foreign keys are what connect related tables in a relational database.
• More than one correct answer is often possible when a database has several linked tables.

Common Mistakes

• Naming a primary key instead of a foreign key in the same table.
• Giving CUSTOMER as a table with a foreign key when it does not contain one here.
• Choosing an attribute like CardType or Paid, which does not reference another table.

Things to Be Careful About

• The foreign key must be named in the same table you choose.
• Do not list the same table twice with different attributes unless the question allows it clearly.
• If several answers are possible, any correct pair is acceptable.

Background Concept

Normalisation is the process of organising data into tables so that data is stored efficiently and without unnecessary duplication. One of the first problems normalisation removes is repeating groups, where a single record would need multiple copies of the same type of field.

In a relational database:

• one table should represent one type of entity
• a one-to-many relationship is usually handled by using two tables
• repeating data should be separated so each row stores one fact at one level

This improves consistency and reduces redundancy.

Understanding the Question

The question asks why the attributes in ORDER_ITEM should not be placed directly inside the ORDER table.

ORDER stores information about the whole order, such as:

• OrderID
• CustomerID
• TotalCost
• Paid
• OrderDate
• Complete

ORDER_ITEM stores details of each individual item within an order, such as:

• Type
• Height
• Width
• Depth
• Details

So the key issue is that one order can include several items.

Approach

Explain the database-design problem from three angles:

1. the relationship is one order to many items
2. storing many items in one ORDER record creates repeating groups
3. storing them as multiple ORDER rows duplicates order-level data and causes anomalies

That gives the full reasoning the examiner wants.

Step-by-Step Reasoning

Each record in ORDER represents one order.

But one order may contain several separate furniture items. For example, a customer might order a table and four chairs. Those are multiple items belonging to the same order.

If you tried to store item data inside ORDER, one of two bad designs would happen.

First possibility: put several item fields into the same row, such as Type1, Type2, Type3, and so on. That creates repeating groups. Relational tables should not be designed that way because the number of items per order varies.

Second possibility: store one row per item in ORDER. Then the same order information such as CustomerID, Paid, OrderDate, and Complete would have to be repeated for every item in that order.

That duplication wastes space and can cause inconsistency. For example, if Paid were changed in one repeated row but missed in another, the database would disagree about the same order.

So ORDER_ITEM must be kept as a separate table linked to ORDER by OrderID.

Key Takeaways

• Use separate tables for one-to-many relationships.
• Repeating groups are a sign that a table is not properly normalised.
• Splitting tables reduces redundancy and avoids update anomalies.

Common Mistakes

• Saying only that the table would be too large. Size is not the main database-design reason.
• Forgetting to mention that one order can have many items.
• Describing ORDER_ITEM as many-to-many with ORDER, which is incorrect here.

Things to Be Careful About

• Focus on structure, not just storage space.
• Use database terms such as one-to-many, repeating groups, redundancy, and inconsistency.
• Make it clear that ORDER stores order-level data while ORDER_ITEM stores item-level data.

Background Concept

A SELECT query is used to retrieve data from one or more tables. When the required fields are in different tables, the tables must be joined using their matching key fields.

Important SQL ideas used here are:

• SELECT chooses the columns to display
• FROM names the table or tables used
• WHERE sets the conditions
• a join condition matches related rows across tables
• AS gives a column heading or alias in the output

Understanding the Question

You must output:

• the customer ID
• the customer's name
• the total cost of orders that have not been paid

The data comes from two tables:

• CUSTOMER for CustomerID and Name
• ORDER for TotalCost and Paid

Because the two tables are related by CustomerID, you must join them.

The phrase "have not been paid" means only rows where Paid = FALSE should be included.

The phrase "must have an appropriate title" means the TotalCost column should be given an alias.

Approach

Build the query in four parts:

1. select the three required fields
2. read from both CUSTOMER and ORDER
3. join the two tables using CustomerID
4. filter for unpaid orders with Paid = FALSE
5. rename TotalCost with AS

Step-by-Step Reasoning

The output needs CustomerID and Name, so those must be selected from CUSTOMER.

The output also needs TotalCost, so that must be selected from ORDER.

Since both tables are involved, the query must read from both:

• FROM CUSTOMER, ORDER

But simply naming both tables is not enough. You must say how rows match:

• CUSTOMER.CustomerID = ORDER.CustomerID

That join condition links each order to the correct customer.

Now apply the filter for unpaid orders:

• ORDER.Paid = FALSE

Finally, give TotalCost a suitable output heading using AS, for example:

• AS UnpaidTotalCost

That satisfies the requirement for an appropriate title.

Key Takeaways

• When fields come from different tables, you need a join.
• The join usually matches a primary key to a foreign key.
• Use AS to control the output heading of a column.
• Boolean conditions in SQL can be tested directly with TRUE or FALSE.

Common Mistakes

• Forgetting the join condition, which would create a Cartesian product.
• Selecting the wrong fields, such as Phone instead of Name.
• Missing the Paid = FALSE condition.
• Forgetting to rename TotalCost when the question asks for an appropriate title.

Things to Be Careful About

• Use the exact table and field names given in the question.
• Make sure the join is on CustomerID, not OrderID.
• Keep the Boolean test correct: unpaid means FALSE, not TRUE.
• The question asks for the total cost already stored in the table, not a calculated SUM().

Background Concept

An operating system is system software that controls the basic operation of a computer. It sits between the hardware and the user or application programs. Without an operating system, a user would not have a practical way to run programs, manage files or control devices easily.

The OS is responsible for managing resources such as the CPU, memory, storage and peripherals. It makes the computer usable by coordinating all of these parts.

Understanding the Question

The question asks for the purpose of an OS in a computer. That means you should describe what the operating system is there to do, not just name an example such as Windows or Linux.

For a 5-mark answer, one brief statement is not enough. You need several distinct functions that show the OS's role in the system.

Approach

A strong answer starts with the overall purpose, then gives key management tasks. A good structure is:

1. interface role
2. processor management
3. memory management
4. file or storage management
5. device or I/O management

This covers the main responsibilities expected in Cambridge answers.

Step-by-Step Reasoning

First, the operating system provides the interface between the user and the hardware. This means users and application programs do not need to control hardware directly.

Second, it manages the processor. If several programs or processes need CPU time, the OS decides which one runs and when. This is often called scheduling.

Third, it manages memory. Programs need RAM while they are running, so the OS allocates memory to them and frees it when it is no longer needed.

Fourth, it manages files and secondary storage. This includes organising how files are stored, found, opened, saved and deleted.

Fifth, it manages input, output and peripheral devices. Keyboards, printers, disks and other devices need controlling, and the OS coordinates this, often using device drivers.

These functions together explain the purpose of the OS: to make the computer usable and to manage its resources efficiently.

Key Takeaways

• The OS is system software, not application software.
• Its main purpose is to act as the interface and resource manager.
• Key resources managed by the OS include CPU time, memory, storage and devices.

Common Mistakes

• Naming operating systems instead of describing their purpose.
• Giving only one vague point such as "it runs the computer" without detail.
• Confusing utility software with the operating system.
• Describing application software functions instead of OS functions.

Things to Be Careful About

For "describe" questions, give separate clear functions rather than one long general sentence. Also keep the answer focused on the OS itself: managing files, memory, processor time and peripherals are classic creditworthy points.

Background Concept

When confidential data is sent across the internet, the main risk is that someone may intercept it while it is travelling between sender and receiver. This is a security problem, specifically a problem of confidentiality.

A common way to protect confidentiality is encryption. Encryption takes readable data, called plaintext, and converts it into an unreadable form, called ciphertext. A key is used in this process. Without the correct key, the intercepted data should not be understandable.

In exam questions like this, the important idea is not just naming encryption, but linking it clearly to the risk: interception becomes much less dangerous because the attacker cannot read the content.

Understanding the Question

The question says the banker needs to transfer confidential data across the internet and asks for one method of restricting the risks if an unauthorised person intercepts it.

That wording points directly to a protection used during transmission, not a storage method and not a staff training policy. The key clue is the phrase intercepting the data whilst it is being transferred. So the answer should focus on making intercepted data useless or unreadable.

Approach

The safest exam approach is:

1. Name a valid method.
2. Describe how it works.
3. Link it back to the stated risk.

The clearest method here is encryption because it directly addresses interception in transit.

Step-by-Step Reasoning

A full-mark answer needs a method and a description of why it reduces the risk.

• First, state the method: encryption.
• Then explain that before transmission, the original readable data is changed into ciphertext.
• If someone intercepts the transmitted data, they do not see the original message in readable form.
• Finally, explain that only someone with the correct decryption key can turn it back into plaintext.

That directly answers the question because the unauthorised interceptor may still capture the data, but they should not be able to understand it.

Key Takeaways

• For intercepted confidential data, the main protection is encryption.
• Good answers must link the method to the risk, not just name the method.
• The key idea is: intercepted data is unreadable without the correct key.

Common Mistakes

• Saying only "use security" or "protect it" without naming a specific method.
• Naming passwords for the computer rather than a method that protects data while it is being transferred.
• Saying the data is hidden rather than explaining that it is encrypted into ciphertext.
• Forgetting to mention that the authorised receiver needs the correct key to decrypt it.

Things to Be Careful About

• The question is about transmission across the internet, so keep the answer focused on protection in transit.
• Do not confuse encryption with compression; compression reduces size, not confidentiality.
• Do not say encryption makes interception impossible; it makes intercepted data unreadable to unauthorised users.
• Make sure your description includes both parts: unreadable data and the need for the correct key.

Background Concept

A digital signature is used to help prove two things:

• integrity: the data has not been changed
• authenticity: the data came from the claimed sender

For this question, the important one is integrity.

A digital signature normally works with:

• a hash function, which converts the data into a fixed-length digest or hash value
• asymmetric encryption, where a sender has a private key and a matching public key

The sender creates a hash from the original message. That hash is then encrypted using the sender's private key. The encrypted hash is the digital signature.

When the receiver gets the data, they decrypt the signature using the sender's public key, giving the original hash. They also hash the received data themselves. If both hash values match, the data is unchanged.

Understanding the Question

The question says the data includes a digital signature and asks how this can make sure the data has not been changed during transmission.

So this is not mainly asking about secrecy or confidentiality. It is asking about checking integrity. The answer therefore needs the comparison process:

1. hash created by sender
2. signature made from that hash
3. receiver gets and decrypts signature
4. receiver calculates own hash
5. compare both values

Approach

To answer well, explain the digital signature as a sequence.

A strong structure is:

• what the sender does
• what the receiver does
• what matching or non-matching results mean

That sequence is important because many students know the key terms but mix up whose key is used and what is being encrypted.

Step-by-Step Reasoning

Here is the full logic:

1. The sender starts with the original confidential data.
2. A hash function is applied to that data. This produces a fixed-size hash value.
   • Even a small change to the data should produce a different hash.
3. The sender encrypts that hash using their private key.
   • This encrypted hash becomes the digital signature.
4. The sender sends both:
   • the data
   • the digital signature
5. The receiver receives the message.
6. The receiver decrypts the digital signature using the sender's public key.
   • This reveals the sender's original hash value.
7. The receiver separately applies the same hash function to the received data.
   • This creates a second hash value.
8. The receiver compares the two hash values.
   • If they are the same, the data has not changed in transit.
   • If they are different, the data has been altered, damaged, or tampered with.

Why does this work? Because the hash depends on the exact contents of the data. If even one bit changes, the new hash should differ, so the comparison fails.

Key Takeaways

• A digital signature checks integrity by comparing hash values.
• The signature is typically an encrypted hash, not the whole message.
• The sender uses the private key to sign.
• The receiver uses the public key to check the signature.
• Matching hashes mean the data has not been changed.

Common Mistakes

• Saying the entire message is encrypted to form the digital signature. Usually the hash is signed, not the whole message.
• Mixing up the keys and saying the sender signs with the public key. Signing uses the private key.
• Forgetting that the receiver must create a new hash from the received data.
• Explaining confidentiality instead of integrity. This question is about detecting changes, not hiding the message.
• Saying the digital signature itself prevents alteration. More precisely, it lets the receiver detect alteration.

Things to Be Careful About

• Use the correct key roles: private key to sign, public key to verify.
• Mention both hashes, not just one.
• State clearly what the comparison result means.
• Avoid vague wording like "it checks the data". Explain exactly how: decrypt signature, hash received data, compare.
• Do not confuse a digital signature with a digital certificate. They are related but not the same thing.

Background Concept

A checksum is a value calculated from a block of data using an agreed method. It is sent along with the data so that the receiver can check whether the data changed during transfer.

This is a verification method, not a validation method.

• Validation checks whether data is sensible or acceptable.
• Verification checks whether data has remained the same.

Checksums are useful for detecting accidental changes caused by noise, interference, or transmission errors.

Understanding the Question

The question asks how transferred data can be verified using a checksum. That means it wants the send-calculate, receive-recalculate, compare process.

Because the word used is verified, the answer should focus on checking whether the received data still matches what was sent.

Approach

The simplest full-mark structure is:

1. sender calculates checksum
2. sender sends data plus checksum
3. receiver recalculates checksum
4. receiver compares values
5. state what matching and non-matching results mean

That covers the whole verification process clearly.

Step-by-Step Reasoning

Here is how checksum verification works:

1. The sender takes the original data.
2. A checksum is calculated from that data using a defined algorithm.
3. The sender transmits:
   • the data
   • the checksum
4. The receiver gets the data and the transmitted checksum.
5. The receiver applies the same checksum method to the received data.
6. This produces a newly calculated checksum.
7. The receiver compares:
   • transmitted checksum
   • newly calculated checksum
8. If the two values are the same, the data is assumed to have arrived unchanged.
9. If the values differ, the data has changed or been corrupted during transmission.
   • In practice, the receiver may reject the data or request it again.

The key principle is that if the data changes, the calculated checksum should also change, so the mismatch reveals the problem.

Key Takeaways

• A checksum is used to verify integrity during transfer.
• The sender and receiver both calculate a checksum.
• The two checksum values are compared.
• A match suggests no change; a mismatch shows an error or alteration.

Common Mistakes

• Confusing verification with validation.
• Saying only that a checksum is attached without explaining that the receiver must recalculate it.
• Forgetting to mention the comparison step.
• Claiming a matching checksum proves with absolute certainty that no error is possible. It indicates the data is assumed correct, but the main exam point is error detection.

Things to Be Careful About

• Make sure the answer is about data transfer, not data entry.
• Use the word recalculate or calculate again at the receiving end.
• Explain both outcomes: match and mismatch.
• Do not describe encryption here; a checksum checks integrity, not confidentiality.

Background Concept

Tracing assembly language means following the effect of each instruction on registers and memory, one step at a time. In this question the important ideas are:

• ACC stores the current working value.
• LDD <address> uses direct addressing, so it loads the contents stored at that address.
• LDI <address> uses indirect addressing, so you first look in the given address to find a second address, then load from that second address.
• STO <address> copies the current ACC value into memory.
• CMP <address> compares ACC with the contents of the given memory location.
• JPE <address> depends on the previous compare. Here it means jump only if the compare was True.
• JMP <address> always jumps.

When completing a trace table, each row usually shows the machine state after that instruction has executed.

Understanding the Question

You are given:

• the instruction meanings
• the starting contents of memory locations 80, 81, 82 and 83
• a short program stored from address 200 onwards

You must run through the program in order, taking jumps into account, and fill in the trace table with the new values of ACC and the relevant memory locations after each executed instruction.

The main clues are the addressing modes:

• LDD 81 means load the contents of address 81
• LDI 82 means look at address 82, use that as another address, then load from there

So you must be careful not to treat LDD and LDI as the same.

Approach

A reliable method is:

1. Write down the initial memory values.
2. Start at instruction address 200.
3. For each instruction, update ACC or memory exactly as the opcode says.
4. After CMP, decide whether the following conditional jump happens.
5. If a JMP occurs, continue from the target address instead of the next sequential address.
6. Record the complete state after every instruction that is actually executed.

Step-by-Step Reasoning

Initial memory:

• 80 = 10
• 81 = 8
• 82 = 80
• 83 = 81

Now trace the program.

200 LDD 81

• Direct addressing: load contents of address 81.
• Address 81 contains 8.
• So ACC = 8.
• Memory does not change.

201 INC ACC

• Add 1 to ACC.
• ACC goes from 8 to 9.

202 STO 83

• Store ACC into address 83.
• ACC is 9, so address 83 becomes 9.
• This overwrites the old value 81.

203 LDI 82

• Indirect addressing: first inspect address 82.
• Address 82 contains 80.
• So now load from address 80.
• Address 80 contains 10.
• Therefore ACC = 10.

This is the most common place students slip: LDI 82 does not load 80 into ACC; it uses 80 as the next address and loads the contents of that address.

204 CMP 83

• Compare ACC with contents of address 83.
• ACC is 10.
• Address 83 now contains 9.
• 10 = 9 is False.
• ACC itself stays 10.

205 JPE 209

• Jump only if the compare was True.
• The compare was False, so the jump is not taken.
• Execution continues at 206.

206 LDD 83

• Load contents of address 83 into ACC.
• Address 83 contains 9.
• So ACC = 9.

207 ADD #10

• Immediate addressing: add denary 10 to ACC.
• 9 + 10 = 19.
• So ACC = 19.

208 JMP 210

• Unconditional jump.
• Next executed instruction is 210.
• The instruction at 209 is skipped.

210 STO 81

• Store ACC into address 81.
• ACC is 19, so address 81 becomes 19.

211 END

• Program stops.
• No values change.

Final memory state is:

• 80 = 10
• 81 = 19
• 82 = 80
• 83 = 9

Final ACC is 19.

Key Takeaways

• Direct addressing loads from the named address; indirect addressing loads from the address found in the named address.
• CMP affects the next conditional jump decision, even though it does not change ACC here.
• STO changes memory, so later instructions may read a different value from the same address.
• In a trace table, jumps mean some instructions are skipped and should not appear as executed rows.

Common Mistakes

• Treating LDI 82 as if it means ACC = 80. It actually means use 80 as an address, then load contents of address 80, which is 10.
• Forgetting that STO 83 changes address 83 from 81 to 9 before the later compare.
• Making JPE 209 jump even when the compare is False.
• Including address 209 in the executed trace even though JMP 210 skips over it.
• Changing ACC during CMP. In this instruction set, the compare determines True/False; ACC stays the same in the trace.

Things to Be Careful About

• Always distinguish the address itself from the data stored in that address.
• Record the state after each executed instruction, not before.
• When a memory location is updated, use the new value from that point onward.
• For jump instructions, the instruction address column should show only instructions that actually run.
• Do not lose track of overwritten values: address 83 starts as 81, but after STO 83 it is 9.