How to Survive G1 Computing Paper 1

Independent study guide, October 2026, for the new 2027 K127 G1 Computing SEC syllabus. All digital cases are hypothetical and must be practised only with authorised data and accounts. Confirm exam instructions, lab software and current admissions criteria with the relevant institutions.

How the two compulsory 2027 papers work

Component	Official task	Duration / marks / weight
Paper 1 Section A	20 four-option MCQs across relevant Computing concepts	20 of 60 marks
Paper 1 Section B	Structured questions testing knowledge, comprehension and application	40 of 60 marks
Paper 1 e-Examination	All seven modules, electronic assessment	1 hour 15 minutes; 60 marks; 40%
Paper 2 lab	Media software, document processing and spreadsheets, and programming	2 hours; 90 marks; 60%

Paper 2’s approximate task allocations are Media Software 30 marks; Document Processing and Spreadsheets 35; and Programming 25. This article focuses on Paper 1, where the student interprets systems, explains results and answers questions electronically. The numbers help parents avoid treating Computing as only a coding subject or only an office-software qualification.

An approach that prevents rote learning

For any Computing question, identify the input, the system or rule, the output and evidence that the result meets the requirement. If the question concerns a document, ask what information should be easier for the intended reader to understand. If it concerns a formula, ask how a changed cell affects the answer. If it concerns a network, ask what communication is occurring, who may access it and what might go wrong. These relationships survive software interface changes better than memorised clicks.

Detailed syllabus explanations with realistic examples

1. Understand input, processing and output

A computer accepts inputs, processes data according to programs and produces outputs. It may also store information for later use. The student should be able to separate these functions instead of treating every computer part as an all-purpose device. A keyboard input is not the same as the processor’s decision or the screen’s displayed result.

In a fictional library checkout, a barcode reader supplies an identifier, software checks a record and a display shows the loan result. Ask which part is input, which is processing and which is output. Then change the input to an invalid code and predict the responsible system response. The goal is causal explanation, not brand knowledge.

2. Distinguish hardware from software

Hardware consists of physical computer components, while software consists of instructions and data that run through the system. A student’s answer should identify the role in context. A printer is hardware; the program that formats the print job is software. A smartphone contains both.

Compare a laptop running a word processor with an empty powered-off laptop. Which part handles the letters and layout? Which physical devices display and accept commands? Students should not confuse an app icon with a storage device simply because both can be seen on a screen.

3. Recognise input devices by function

Keyboards, pointing devices, microphones, cameras and scanners can provide different forms of input. A sensor may report a condition rather than a person’s deliberate instruction. Questions can describe a task and ask for an appropriate input device.

A fictional museum kiosk lets visitors choose a language. A touchscreen selection is an input. If the kiosk also records sound for permitted accessibility functions, the microphone plays a different role. The learner should choose by what information must enter the system rather than by visual attractiveness.

4. Recognise useful output devices

Displays, speakers and printers present digital results in different forms. A suitable output depends on the person, setting and purpose. An audio alert may support attention, while a printed receipt provides a physical record. More outputs do not necessarily make the product better.

An imaginary helpdesk system must give a visitor directions. Would a map display, spoken response or printout be appropriate? The question’s requirements determine the answer. A student should explain one advantage and limitation, avoiding the assumption that a speaker replaces visual information for every user.

5. Understand central processing

A processor executes instructions and coordinates operations, while other components provide memory, storage, input and output. Students should understand the basic functional distinction without claiming that CPU clock speed alone determines every computer’s performance.

In an invented spreadsheet task, the processor performs calculations, but data must also be available from memory or storage and the result displayed. Ask why a broken file or insufficient data cannot be repaired merely by using a faster processor. Systems thinking discourages one-component guesses.

6. Distinguish RAM from secondary storage

RAM is working memory used during program operation; secondary storage holds files more persistently. Saving a document writes it to an appropriate storage location. Students must not assume leaving a file open means that every change has been safely stored.

A learner edits a presentation, closes the program without saving and assumes the next session will contain the changes. Discuss what saving does and why checking a reopened file helps. This is a practical digital habit that also supports the two-hour lab examination.

7. Understand file types and extensions

File formats identify how digital content is represented and which applications can work with it. A filename extension may indicate a document, spreadsheet, image or another format, but renaming the extension alone does not actually convert content correctly.

In a fictional assignment, the required file is a spreadsheet with functioning formulas. Exporting an image of the spreadsheet may lose the needed calculation behaviour. Ask what the examiner or recipient must be able to do with the file, not only what it looks like.

8. Organise files with meaningful names

A useful filename and folder structure help someone locate the correct version and avoid submitting an obsolete file. The syllabus connects file operations with dependable computing. A file labelled ‘final-final-new’ may be less helpful than a clear name complying with task instructions.

Create a hypothetical folder for a poster, a spreadsheet and a simple program. Ask how the candidate would recognise the authorised final file. Then change one document and explain how they can verify that the revised copy, not an earlier version, was saved.

9. Back up work rather than hope

A backup is a separate recoverable copy or version according to a suitable policy. Students should distinguish a real backup from merely creating another shortcut to the same file. Data can be lost through hardware failure, mistakes or unexpected corruption.

A classroom project is saved only on one computer’s desktop and the machine is unavailable next week. Ask what a permissible backup method would have protected, and which school policies govern storage. Do not upload assessed files to unauthorised external accounts.

10. Understand local area networks

A local area network connects devices within a limited area, such as a school or office, to share data or resources. It is not identical to the entire internet. Students should describe what is being shared and which devices participate.

Imagine several library computers using a school-authorised shared printer. Which network relationship enables access, and which permission might be needed? The student should not assume that connecting to a Wi-Fi signal authorises access to every connected device.

11. Distinguish internet from intranet

The internet is a global system of interconnected networks, while an intranet is a restricted network resource intended for an organisation’s authorised users. A school’s internal notice service can remain distinct from a public website.

A fictional school stores staff scheduling information on an internal portal, while students can read public announcements on its ordinary website. Ask which information should require permission. Access design is about intended audiences, not just technical convenience.

12. Recognise basic network equipment roles

Routers, switches and wireless access points have different purposes in connecting devices and forwarding traffic. A router links networks, while a switch typically helps connect devices within a local network. Students should connect the equipment with the required communication.

In an imaginary small office, several computers need to share local data and reach an external service. Ask what relationships each device supports. Avoid turning this into an unauthorised network-configuration exercise; the skill is functional understanding.

13. Understand the client-server relationship

A client may request information or a service from a server, such as a browser requesting a web page. That does not mean every computer always has one fixed role in every system. Students should identify the roles within the specific interaction.

An invented online library page receives a book-search request and returns results from an authorised database. Which side makes the request, and which side provides the service? Then change the request to a non-existent book and discuss how the system could respond accurately.

14. Recognise the value and limits of the cloud

Cloud-based services can allow access to files or applications across suitable devices, subject to permissions, connectivity and provider availability. Storing something online does not automatically make it private, permanently available or exempt from backup needs.

A student saves a group project to an approved shared account. Who should have editing access, and what happens if the service is unavailable during class? The correct response uses school policy, appropriate permissions and version awareness instead of optimistic assumptions.

15. Avoid phishing and impersonation

Phishing attempts to trick people into revealing credentials or performing unsafe actions by appearing trustworthy. A student should inspect context, sender claims, links and requests instead of treating logos or urgency as proof of authenticity.

An invented message claims the school must receive a password within ten minutes. Ask why the request is suspicious and how a learner should verify it through the school’s known legitimate channel. Never enter credentials into an unknown form to test whether a suspected scam works.

16. Use strong authentication responsibly

Passwords and other authentication methods help establish authorised access. Students should understand why reusing the same weak password across accounts raises risk and why a second factor can add protection. Authentication does not make every uploaded file appropriate to share.

A fictional student account contains submitted assessment work. Ask which controls should prevent other people from editing it and what to do if access appears compromised. Refer to authorised account recovery, not unsanctioned testing.

17. Respect personal data and privacy

Computing can collect names, contact information and other personal details. The responsible question is whether data are genuinely needed, who can access them and how they should be handled. Permission to use one service does not grant access to unrelated personal records.

A school club’s poster needs event details but does not need to publish every member’s telephone number. Ask what should be visible and what should remain controlled. A thoughtful design serves communication while minimising unnecessary exposure.

18. Understand responsible digital communication

Messages, images and online posts can spread quickly and persist. The Impact of Computing module involves understanding benefits, risks and social effects. Students should distinguish permitted use, misleading content and respectful behaviour.

An imagined group shares a screenshot of another student’s private message. Ask what consent and purpose would be needed before sharing. A simple rule is to avoid circulating someone else’s private information without appropriate authorisation.

19. Examine information credibility

Search results and social posts vary in reliability. Students should check author, date, evidence and whether the source actually supports a claim. An attractive graphic is not proof that the statistics behind it are genuine.

A fictional post claims every computer will stop working next month. What official or technically credible source could verify the statement? Teach the learner to distinguish a direct source from a repeated rumour before acting on it.

20. Understand intellectual property

Images, code, music and writing can be subject to copyright and licence conditions. A student should use appropriate materials and acknowledgement rather than assume everything found online may be copied into a project.

For a school poster, a photo may have usage restrictions. Compare using an original photograph, a properly licensed image and a random download with unknown rights. The safest answer recognises that educational use does not automatically permit every form of redistribution.

21. Understand accessible document design

Document Processing involves communicating with a reader, not merely applying decorative fonts. Headings, consistent layout, meaningful spacing and understandable information order help a person navigate a document.

In a fictional school event handout, the registration deadline is hidden in a dense paragraph. Which formatting change would help the target reader? The student should explain the purpose of styles and hierarchy rather than recommend the maximum number of colours.

22. Use document formatting purposefully

Bold, headings, lists, tables and page layout can distinguish different kinds of information. A document can look polished but still mislead if dates, amounts or content are wrong. Accurate structure and data are part of good digital work.

Compare two fictional notices: one uses a clear title, date and action line; the other uses mixed font sizes without a hierarchy. Explain what the reader would find more easily and why. The reasoning transfers across office software interfaces.

23. Recognise useful tables and mail merge concepts

Documents can arrange repeated information in tables or use appropriate automated features for standardised communication. The goal is to reduce errors and present information meaningfully, not to distribute personal data carelessly.

Imagine a fictitious school supplies list with item, quantity and cost. A table may make comparisons easier than a long sentence. If a templated letter uses names from records, students should consider accuracy and privacy rather than assume every record may be shared.

24. Understand spreadsheet cells and references

A spreadsheet stores values and formulas in a grid with named cells. A formula refers to the current data and can recalculate when a value changes. This is more useful than typing a result once and hoping it remains correct.

An invented cost sheet uses quantity in B2 and unit price in C2. A formula such as =B2*C2 gives total cost. Change the quantity and ask which result should update. If a number stays unchanged after the input changes, the computation may not be implemented as intended.

25. Distinguish relative and absolute references

Relative references can adjust when formulas are copied to a new cell; absolute references identify a fixed row or column where appropriate. A correct initial formula may become wrong when copied if the reference behaviour was not intended.

Imagine a list of item prices multiplied by a tax rate stored in one fixed cell. Ask which reference should remain unchanged across rows and why. Use a non-assessed fictional worksheet and check the copied formulas rather than memorise a click sequence.

26. Understand simple spreadsheet functions

Functions such as SUM, AVERAGE, MIN and MAX perform different operations. Students need to understand which question is being answered, what range of cells is used and whether values are suitable to include. A function name alone is not a justified result.

In a fictional weekly sales sheet, SUM reports a total while AVERAGE reports a mean. A learner who selects MAX for an average question has identified the wrong task even if the spreadsheet displays a correct number for something else.

27. Distinguish sorting from filtering

Sorting changes the order of records according to a selected field, while filtering shows a subset meeting criteria. Both can help analyse information, but neither inherently changes the underlying truth of the records.

A classroom table contains stock quantities for three departments. Sort descending by quantity, then filter to one category. Ask what the student sees after each action and why a hidden row is not necessarily a deleted record.

28. Choose charts that support comparisons

Charts can represent values or changes visually, but the type and labels must suit the question. A misleading axis or missing units can create a false impression even when the numerical data are accurate.

For monthly class attendance, a column chart may help compare months. A pie chart may be less suited to showing a sequence of changes over time. Ask what the intended reader needs to decide before choosing visual decoration.

29. Recognise principles of media design

Media Software tasks may involve slide presentations, images or other digital compositions. Visual hierarchy, contrast and readable text support communication. The electronic theory paper can still test why a particular design decision is useful.

In a fictional awareness slide, five equally large headlines compete for attention. Ask which single message the audience should see first, and how space, size and colour could improve clarity without changing the factual content.

30. Understand image resolution and size

Digital images are composed of pixels, and resolution affects how a graphic may appear at different sizes. Enlarging a low-quality image does not manufacture missing real detail. Students should distinguish file size from visual usefulness.

A poster uses a tiny thumbnail stretched across a page and appears blurred. What is the problem, and why might selecting a suitable legitimate source image be better than applying more sharpening? The correct explanation uses evidence from the result.

31. Learn Scratch sprites and stage coordinates

Visual programming uses objects or sprites operating within a stage. Their positions can be represented through coordinates, and events trigger actions. Students should explain movement relative to the coordinate system rather than guess the result from the picture alone.

A fictional sprite starts at a given coordinate and receives a command to change x by a positive amount. Ask which direction it moves under the stated stage convention. Then change the starting point and predict the new location.

32. Understand program variables as changing state

A variable stores a value a program can read or update. In a simple game, a score variable might increase after a valid event. Students should know when it is initialised and which event changes it.

A practice game begins with score zero and adds one per collected token. If the code resets score inside the repeated event, what unexpected result occurs? Trace the sequence on paper before editing an actual project.

33. Distinguish if and if–else logic

An if condition executes an action when the relevant test is true; an if–else can select between two branches. Students should follow the actual logical expression and consider what happens when the condition is false.

In a fictional quiz, a correct answer adds a point while an incorrect answer displays feedback. A student should show which branch handles each response. Then change the initial score and re-run the logic as a dry trace.

34. Understand repeat and repeat-until loops

Loops let a program perform a sequence repeatedly under a defined count or condition. A repeat-until loop depends on the stopping condition becoming true, whereas a fixed repeat executes a specified number of times. They should not be treated as identical.

Imagine a sprite moving until it reaches a boundary. If the boundary test is never satisfied, the loop may continue unexpectedly. Ask the learner what stopping information is missing rather than copy another student’s code.

35. Understand AND, OR and NOT in program decisions

Logical operators combine or invert conditions. AND generally requires both conditions, OR at least one, and NOT reverses a Boolean state. A beginner should represent each condition in ordinary language before applying it to a game.

A fictional collection event should count only when the sprite touches a token and the round is active. Writing the rule as OR instead of AND could award points outside active play. Use a four-row truth table to expose the difference.

36. Recognise events, messages and broadcasts

An event-driven program responds to actions such as a click, key press or broadcast. A broadcast can communicate to another sprite that a stage has changed. The student should distinguish what causes an event from what the responding code does.

In a fictional game, an opening screen sends a start-round message and several objects respond. What happens if one receiver has no matching event handler? A correct explanation traces the communication without assuming the whole project automatically changes.

37. Identify debugging as evidence-based repair

Debugging means finding and correcting a difference between intended and actual program behaviour. Randomly changing many blocks may accidentally produce a good run without revealing the cause. Better practice begins with the exact input and observed output.

A sprite gains two points when only one token should count. Ask which event could fire twice or which condition might not prevent repeated scoring. Change one relevant part in an authorised practice copy, then retest with a different starting state.

38. Understand the value of testing several cases

One successful run does not establish that a spreadsheet or program is correct for every input. Tests should include normal conditions, boundary cases and changed starting values where relevant. Students need to learn what result is expected before looking at the screen.

In a fictional quiz program, try one correct answer, one incorrect answer and the final question transition. A student should record expected and actual behaviour for each, then explain discrepancies. This habit transfers to real digital work.

39. Know what information is missing

Computing questions sometimes omit a necessary detail, such as a network permission, spreadsheet reference or program starting value. An accurate student states what cannot be concluded rather than inventing the missing fact.

A screen reports that a file was saved, but the student does not know the folder or filename. Has the required submission been verified? Not yet. They should seek the authorised location and check the correct version.

40. Make exam-time reasoning manageable

Paper 1 gives seventy-five minutes for 60 marks. Some recognition questions may be quick while applied items require interpreting text, diagrams or small programs. A student should practise sensible pacing, but no arbitrary universal seconds-per-mark rule replaces task reading.

Review a timed attempt by classifying errors: concept, reading, arithmetic, code-tracing or misunderstanding the response format. Repair the first repeated cause, then practise changed questions. A slightly slower accurate answer can be more useful than rushed guessing.

41. Connect theory and lab skills responsibly

Paper 2 uses a controlled two-hour lab with specific software and file-saving requirements. Theoretical understanding should support practical choices, but merely naming a formula does not show the file works. Conversely, following clicks once does not prove conceptual understanding.

A student can explain why a spreadsheet needs cell references and then demonstrate it on a practice file, saving and reopening as instructed. Authentic digital work and permissions matter in both examinations.

42. Prepare across the seven modules in six weeks

Week 1 can check computer fundamentals, storage and file organisation. Week 2 covers networking, privacy and digital risks. Week 3 addresses document communication and media choices. Week 4 develops spreadsheets and data; Week 5 teaches conditions, loops and state in programming.

Week 6 combines unfamiliar Paper 1 questions and a distinct authorised Paper 2 rehearsal. The schedule is a framework, not a promised grade increase. Adjust according to the school’s syllabus pacing and the first identifiable learning gap.

43. Keep post-secondary choices realistic

Digital literacy is useful in administration, logistics, retail technology, marketing, data entry, programming, media production and many technical domains. A learner may discover a genuine preference for careful data work over coding or vice versa.

K127 is one new SEC subject and is not an IT professional qualification. Course admission depends on the complete subject results and current receiving-institution criteria. Families should explore interests without turning one G1 grade into a career verdict.

Twelve practice cases to test transfer

1. The saved file is not the submitted file

An assignment appears correct on screen, but only an older copy is saved in the required folder. The final output must be checked against actual task instructions. Explain how filename, location and version are related.

For a reliable revision check, change one input or requirement and ask for a fresh answer. The learner should explain the result through relevant evidence rather than recite the previous correct option.

2. The formula is replaced with a number

A spreadsheet displays a correct total today, but after an input changes the result does not update. Ask whether a functioning formula or only a typed value is present and why that matters.

3. The copied formula uses a shifting tax reference

A fixed rate is stored in one cell, but the reference changes when a formula is copied downward. Which kind of reference would serve the intended calculation and how could a changed-row test reveal the problem?

4. An average is mistaken for a total

The question asks for mean attendance but the student selects SUM. Which function answers the stated decision? Explain why a mathematically valid total is still irrelevant.

5. An image is stretched until blurred

A tiny picture is enlarged for a poster. Why can its appearance deteriorate even though the file still opens? Identify resolution and source suitability.

6. A suspicious message looks official

An email with a copied school logo demands a password through an unknown link. What verification and protective behaviour is appropriate without visiting the supplied URL?

7. A client is mistaken for the server

A browser requests a page from a web service. Which side requests, which provides, and why is internet access different from an organisation’s intranet permissions?

8. The Scratch score resets after every collision

A game briefly shows a correct score but never rises beyond one. Which code event may be initialising the variable at the wrong time? Trace the updates before changing several blocks.

9. OR is used where AND was required

A score should change only when a round is active and a token is touched. A different logical operator changes behaviour. Use a truth table and name the unsupported cases.

10. A loop does not stop

A repeat-until structure has a condition that cannot become true in the current model. Explain the likely symptom and which relationship the student should inspect.

11. A beautiful document lacks necessary information

A school notice uses fancy fonts but omits the deadline. Explain why a design that looks polished does not satisfy the reader’s need.

12. One strong coding mark is treated as guaranteed admission

The student enjoys programming and expects a particular course place. Which full qualifications and current programme-specific criteria must still be checked?

Common questions about G1 Computing Paper 1

Is Computing K127 new in 2027?

Yes. It is a new G1 Singapore–Cambridge SEC subject with its first examination in 2027.

How long is Paper 1?

One hour and fifteen minutes, with 60 raw marks and 40% weighting.

How are Paper 1 marks divided?

Section A has 20 four-option MCQs worth 20 marks, and Section B structured questions worth 40.

What modules can Paper 1 assess?

All seven: Computer Fundamentals, Networking, Impact of Computing, Document Processing, Spreadsheets, Media Software and Programming.

Is G1 Computing only Scratch?

No. Programming is one module, alongside other digital systems, ethics, networking and productivity skills.

What happens in Paper 2?

A two-hour lab worth 60%, including media, documents/spreadsheets and programming practical tasks.

Does a displayed correct value prove a spreadsheet works?

No. Check that the formula responds correctly to changed inputs and that the required file was saved.

May a student practise by probing accounts or networks?

No. Use authorised school or personal accounts and never test unrelated systems without permission.

Does this replace admissions requirements for IT programmes?

No. Later eligibility depends on the complete qualification profile and the receiving course’s current criteria.

How should revision begin?

Diagnose one weak module using a real school question, teach the underlying idea and retest it on changed data.

Official documents and connected eduKateSG articles

Confirm the correct 2027 subject code K127 instead of using old Computer Applications materials as though the schemes were identical.
Create a seven-module checklist and identify which one is currently weakest in a school question.
Explain each computer component through what it receives, stores, processes or outputs.
Use a spreadsheet to predict the result of a changed cell before checking the formula, and explain the effect of a relative or absolute reference.
Trace a Scratch-style conditional or loop with two different starting values rather than relying on one lucky game run.
Practise Section B answers in short clear steps and reserve preparation for the separate practical saving requirements.

How the two compulsory 2027 papers work

Component	Official task	Duration / marks / weight
Paper 1 Section A	20 four-option MCQs across relevant Computing concepts	20 of 60 marks
Paper 1 Section B	Structured questions testing knowledge, comprehension and application	40 of 60 marks
Paper 1 e-Examination	All seven modules, electronic assessment	1 hour 15 minutes; 60 marks; 40%
Paper 2 lab	Media software, document processing and spreadsheets, and programming	2 hours; 90 marks; 60%

An approach that prevents rote learning

Detailed syllabus explanations with realistic examples

1. Understand input, processing and output

2. Distinguish hardware from software

3. Recognise input devices by function

4. Recognise useful output devices

5. Understand central processing

6. Distinguish RAM from secondary storage

7. Understand file types and extensions

8. Organise files with meaningful names

9. Back up work rather than hope

10. Understand local area networks

11. Distinguish internet from intranet

12. Recognise basic network equipment roles

13. Understand the client-server relationship

14. Recognise the value and limits of the cloud

15. Avoid phishing and impersonation

16. Use strong authentication responsibly

17. Respect personal data and privacy

18. Understand responsible digital communication

19. Examine information credibility

20. Understand intellectual property

21. Understand accessible document design

22. Use document formatting purposefully

23. Recognise useful tables and mail merge concepts

24. Understand spreadsheet cells and references

25. Distinguish relative and absolute references

26. Understand simple spreadsheet functions

27. Distinguish sorting from filtering

28. Choose charts that support comparisons

29. Recognise principles of media design

30. Understand image resolution and size

31. Learn Scratch sprites and stage coordinates

32. Understand program variables as changing state

A variable stores a value a program can read or update. In a simple game, a score variable might increase after a valid event. Students should know when it is initialised and which event changes it.

33. Distinguish if and if–else logic

34. Understand repeat and repeat-until loops

35. Understand AND, OR and NOT in program decisions

36. Recognise events, messages and broadcasts

37. Identify debugging as evidence-based repair

38. Understand the value of testing several cases

39. Know what information is missing

40. Make exam-time reasoning manageable

41. Connect theory and lab skills responsibly

42. Prepare across the seven modules in six weeks

43. Keep post-secondary choices realistic

Twelve practice cases to test transfer

1. The saved file is not the submitted file

2. The formula is replaced with a number

A spreadsheet displays a correct total today, but after an input changes the result does not update. Ask whether a functioning formula or only a typed value is present and why that matters.

3. The copied formula uses a shifting tax reference

4. An average is mistaken for a total

The question asks for mean attendance but the student selects SUM. Which function answers the stated decision? Explain why a mathematically valid total is still irrelevant.

5. An image is stretched until blurred

A tiny picture is enlarged for a poster. Why can its appearance deteriorate even though the file still opens? Identify resolution and source suitability.

6. A suspicious message looks official

An email with a copied school logo demands a password through an unknown link. What verification and protective behaviour is appropriate without visiting the supplied URL?

7. A client is mistaken for the server

A browser requests a page from a web service. Which side requests, which provides, and why is internet access different from an organisation’s intranet permissions?

8. The Scratch score resets after every collision

A game briefly shows a correct score but never rises beyond one. Which code event may be initialising the variable at the wrong time? Trace the updates before changing several blocks.

9. OR is used where AND was required

A score should change only when a round is active and a token is touched. A different logical operator changes behaviour. Use a truth table and name the unsupported cases.

10. A loop does not stop

A repeat-until structure has a condition that cannot become true in the current model. Explain the likely symptom and which relationship the student should inspect.

11. A beautiful document lacks necessary information

A school notice uses fancy fonts but omits the deadline. Explain why a design that looks polished does not satisfy the reader’s need.

12. One strong coding mark is treated as guaranteed admission

The student enjoys programming and expects a particular course place. Which full qualifications and current programme-specific criteria must still be checked?

Common questions about G1 Computing Paper 1

Is Computing K127 new in 2027?

Yes. It is a new G1 Singapore–Cambridge SEC subject with its first examination in 2027.

How long is Paper 1?

One hour and fifteen minutes, with 60 raw marks and 40% weighting.

How are Paper 1 marks divided?

Section A has 20 four-option MCQs worth 20 marks, and Section B structured questions worth 40.

What modules can Paper 1 assess?

All seven: Computer Fundamentals, Networking, Impact of Computing, Document Processing, Spreadsheets, Media Software and Programming.

Is G1 Computing only Scratch?

No. Programming is one module, alongside other digital systems, ethics, networking and productivity skills.

What happens in Paper 2?

A two-hour lab worth 60%, including media, documents/spreadsheets and programming practical tasks.

Does a displayed correct value prove a spreadsheet works?

No. Check that the formula responds correctly to changed inputs and that the required file was saved.

May a student practise by probing accounts or networks?

No. Use authorised school or personal accounts and never test unrelated systems without permission.

Does this replace admissions requirements for IT programmes?

No. Later eligibility depends on the complete qualification profile and the receiving course’s current criteria.

How should revision begin?

Diagnose one weak module using a real school question, teach the underlying idea and retest it on changed data.

Official documents and connected eduKateSG articles

To survive G1 Computing Paper 1, learn to explain how a digital system works rather than memorising only where software buttons are located. The 2027 Singapore–Cambridge SEC G1 Computing syllabus is K127, a new subject with its first examination in 2027. Paper 1 is a 1-hour-15-minute electronic examination carrying 60 marks and 40% of the subject. Its Section A contains 20 four-option multiple-choice questions, worth 20 marks, and Section B contains short structured questions worth 40 marks. Both can draw from all seven syllabus modules.

The seven modules are Computer Fundamentals, Networking, Impact of Computing, Document Processing, Spreadsheets, Media Software and Programming. That means a student who can make a Scratch game but does not understand file storage, cyber risks, spreadsheet references or the purpose of document formatting is not yet prepared for Paper 1. Equally, knowing software definitions alone is insufficient for Paper 2, the separate two-hour practical lab worth 60%. The best preparation connects a technical concept to a small task and asks what would happen if an input or constraint changed.

Computing develops digital literacy that can help in administration, logistics, retail systems, data work, digital media and wider technical study. It can reveal interests in coding, creative production or business systems without guaranteeing a course or job. G1 is the level of this one subject, not a judgement on the learner’s future. Admission decisions depend on the whole qualification record and current course requirements.

The official source is SEAB’s 2027 K127 G1 Computing syllabus and the 2027 G1 directory. The examples in this guide are independent, fictional exercises rather than specimen-paper questions. School rules govern the electronic examination platform, authorised computer access and any submitted practical files. Never practise digital security by accessing accounts or systems without permission.

Quick actions for the next study session

Confirm the correct 2027 subject code K127 instead of using old Computer Applications materials as though the schemes were identical.
Create a seven-module checklist and identify which one is currently weakest in a school question.
Explain each computer component through what it receives, stores, processes or outputs.
Use a spreadsheet to predict the result of a changed cell before checking the formula, and explain the effect of a relative or absolute reference.
Trace a Scratch-style conditional or loop with two different starting values rather than relying on one lucky game run.
Practise Section B answers in short clear steps and reserve preparation for the separate practical saving requirements.

How the two compulsory 2027 papers work

Component	Official task	Duration / marks / weight
Paper 1 Section A	20 four-option MCQs across relevant Computing concepts	20 of 60 marks
Paper 1 Section B	Structured questions testing knowledge, comprehension and application	40 of 60 marks
Paper 1 e-Examination	All seven modules, electronic assessment	1 hour 15 minutes; 60 marks; 40%
Paper 2 lab	Media software, document processing and spreadsheets, and programming	2 hours; 90 marks; 60%

An approach that prevents rote learning

Detailed syllabus explanations with realistic examples

1. Understand input, processing and output

2. Distinguish hardware from software

3. Recognise input devices by function

4. Recognise useful output devices

5. Understand central processing

6. Distinguish RAM from secondary storage

7. Understand file types and extensions

8. Organise files with meaningful names

9. Back up work rather than hope

10. Understand local area networks

11. Distinguish internet from intranet

12. Recognise basic network equipment roles

13. Understand the client-server relationship

14. Recognise the value and limits of the cloud

15. Avoid phishing and impersonation

16. Use strong authentication responsibly

17. Respect personal data and privacy

18. Understand responsible digital communication

19. Examine information credibility

20. Understand intellectual property

21. Understand accessible document design

22. Use document formatting purposefully

23. Recognise useful tables and mail merge concepts

24. Understand spreadsheet cells and references

25. Distinguish relative and absolute references

26. Understand simple spreadsheet functions

27. Distinguish sorting from filtering

28. Choose charts that support comparisons

29. Recognise principles of media design

30. Understand image resolution and size

31. Learn Scratch sprites and stage coordinates

32. Understand program variables as changing state

A variable stores a value a program can read or update. In a simple game, a score variable might increase after a valid event. Students should know when it is initialised and which event changes it.

33. Distinguish if and if–else logic

34. Understand repeat and repeat-until loops

35. Understand AND, OR and NOT in program decisions

36. Recognise events, messages and broadcasts

37. Identify debugging as evidence-based repair

38. Understand the value of testing several cases

39. Know what information is missing

40. Make exam-time reasoning manageable

41. Connect theory and lab skills responsibly

42. Prepare across the seven modules in six weeks

43. Keep post-secondary choices realistic

Twelve practice cases to test transfer

1. The saved file is not the submitted file

2. The formula is replaced with a number

A spreadsheet displays a correct total today, but after an input changes the result does not update. Ask whether a functioning formula or only a typed value is present and why that matters.

3. The copied formula uses a shifting tax reference

4. An average is mistaken for a total

The question asks for mean attendance but the student selects SUM. Which function answers the stated decision? Explain why a mathematically valid total is still irrelevant.

5. An image is stretched until blurred

A tiny picture is enlarged for a poster. Why can its appearance deteriorate even though the file still opens? Identify resolution and source suitability.

6. A suspicious message looks official

An email with a copied school logo demands a password through an unknown link. What verification and protective behaviour is appropriate without visiting the supplied URL?

7. A client is mistaken for the server

A browser requests a page from a web service. Which side requests, which provides, and why is internet access different from an organisation’s intranet permissions?

8. The Scratch score resets after every collision

A game briefly shows a correct score but never rises beyond one. Which code event may be initialising the variable at the wrong time? Trace the updates before changing several blocks.

9. OR is used where AND was required

A score should change only when a round is active and a token is touched. A different logical operator changes behaviour. Use a truth table and name the unsupported cases.

10. A loop does not stop

A repeat-until structure has a condition that cannot become true in the current model. Explain the likely symptom and which relationship the student should inspect.

11. A beautiful document lacks necessary information

A school notice uses fancy fonts but omits the deadline. Explain why a design that looks polished does not satisfy the reader’s need.

12. One strong coding mark is treated as guaranteed admission

The student enjoys programming and expects a particular course place. Which full qualifications and current programme-specific criteria must still be checked?

Common questions about G1 Computing Paper 1

Is Computing K127 new in 2027?

Yes. It is a new G1 Singapore–Cambridge SEC subject with its first examination in 2027.

How long is Paper 1?

One hour and fifteen minutes, with 60 raw marks and 40% weighting.

How are Paper 1 marks divided?

Section A has 20 four-option MCQs worth 20 marks, and Section B structured questions worth 40.

What modules can Paper 1 assess?

All seven: Computer Fundamentals, Networking, Impact of Computing, Document Processing, Spreadsheets, Media Software and Programming.

Is G1 Computing only Scratch?

No. Programming is one module, alongside other digital systems, ethics, networking and productivity skills.

What happens in Paper 2?

A two-hour lab worth 60%, including media, documents/spreadsheets and programming practical tasks.

Does a displayed correct value prove a spreadsheet works?

No. Check that the formula responds correctly to changed inputs and that the required file was saved.

May a student practise by probing accounts or networks?

No. Use authorised school or personal accounts and never test unrelated systems without permission.

Does this replace admissions requirements for IT programmes?

No. Later eligibility depends on the complete qualification profile and the receiving course’s current criteria.

How should revision begin?

Diagnose one weak module using a real school question, teach the underlying idea and retest it on changed data.

How to survive G1 Computing Paper 1? | 2027 e-Exam, Seven Modules and Digital Reasoning

How the two compulsory 2027 papers work

An approach that prevents rote learning

Detailed syllabus explanations with realistic examples

1. Understand input, processing and output

2. Distinguish hardware from software

3. Recognise input devices by function

4. Recognise useful output devices

5. Understand central processing

6. Distinguish RAM from secondary storage

7. Understand file types and extensions

8. Organise files with meaningful names

9. Back up work rather than hope

10. Understand local area networks

11. Distinguish internet from intranet

12. Recognise basic network equipment roles

13. Understand the client-server relationship

14. Recognise the value and limits of the cloud

15. Avoid phishing and impersonation

16. Use strong authentication responsibly

17. Respect personal data and privacy

18. Understand responsible digital communication

19. Examine information credibility

20. Understand intellectual property

21. Understand accessible document design

22. Use document formatting purposefully

23. Recognise useful tables and mail merge concepts

24. Understand spreadsheet cells and references

25. Distinguish relative and absolute references

26. Understand simple spreadsheet functions

27. Distinguish sorting from filtering

28. Choose charts that support comparisons

29. Recognise principles of media design

30. Understand image resolution and size

31. Learn Scratch sprites and stage coordinates

32. Understand program variables as changing state

33. Distinguish if and if–else logic

34. Understand repeat and repeat-until loops

35. Understand AND, OR and NOT in program decisions

36. Recognise events, messages and broadcasts

37. Identify debugging as evidence-based repair

38. Understand the value of testing several cases

39. Know what information is missing

40. Make exam-time reasoning manageable

41. Connect theory and lab skills responsibly

42. Prepare across the seven modules in six weeks

43. Keep post-secondary choices realistic

Twelve practice cases to test transfer

1. The saved file is not the submitted file

2. The formula is replaced with a number

3. The copied formula uses a shifting tax reference

4. An average is mistaken for a total

5. An image is stretched until blurred

6. A suspicious message looks official

7. A client is mistaken for the server

8. The Scratch score resets after every collision

9. OR is used where AND was required

10. A loop does not stop

11. A beautiful document lacks necessary information

12. One strong coding mark is treated as guaranteed admission

Common questions about G1 Computing Paper 1

Is Computing K127 new in 2027?

How long is Paper 1?

How are Paper 1 marks divided?

What modules can Paper 1 assess?

Is G1 Computing only Scratch?

What happens in Paper 2?

Does a displayed correct value prove a spreadsheet works?

May a student practise by probing accounts or networks?

Does this replace admissions requirements for IT programmes?

How should revision begin?

Official documents and connected eduKateSG articles

How the two compulsory 2027 papers work

An approach that prevents rote learning

Detailed syllabus explanations with realistic examples

1. Understand input, processing and output

2. Distinguish hardware from software

3. Recognise input devices by function

4. Recognise useful output devices

5. Understand central processing