Software Engineering › Key terms › Y12 Programming for the Web › Server-side (back-end) programming
Server-side (back-end) programming
Term Y12 Programming for the Web
Definition
Code that runs on the server (Python, PHP, Node) to process requests, access databases, apply business rules and keep data secure.
Example: 2025 Q23b marker note: identify features of server-side programming, use the stimulus, and link back end to front end.
Found in: syllabus, 2025 HSC marking guidelines, school notes.
Where it is used in the test
Syllabus area: Y12 Programming for the Web.
Question types it can appear in
- Short answer: Explain why server-side programming is needed (2025 Q23b)
- Multiple choice: Pick the option that matches the definition or example.
- Fill in the blanks: Choose this term to complete a statement or table.
Where it has appeared in the paper
Programming for the Web (Part A). Part letters follow each paper’s own layout.
Related past questions
- 2025 HSC Q23b (3 marks): Server-side web programming Programming for the Web (Part A) · 3 marks
These are the questions the flashcard set links to this term. Open each one and compare your answer with its marking criteria.
Study links
- Flashcard: Server-side (back-end) programming in Programming for the Web (Year 12) · study that set
- Memorise: Web development system: front end, back end, databases
- Notes: Web development system: front end, back end, databases (Programming for the Web (Year 12))
- Notes: The back-end process of a web request (Programming for the Web (Year 12))
- Notes: Skeleton: Explain why server-side programming/back end is needed (3 marks) (Programming for the Web (Year 12))
- Master answer: hsc2025-q23b (3 marks, short answer (explain)) (Master model answers: Programming for the Web)
How to use it in an answer
A model sentence
“Code that runs on the server (Python, PHP, Node) to process requests, access databases, apply business rules and keep data secure.” Then apply it: 2025 Q23b marker note: identify features of server-side programming, use the stimulus, and link back end to front end.
In a short answer, give the definition in your own words first, then tie it to the situation in the question. Do not copy the example above unless it fits the scenario.
Command words used with it
- Explain: Relate cause and effect; make the relationship between things evident; provide why and/or how. (2025 HSC Q23b (3 marks): Server-side web programming)
Technique for the question types
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
- Multiple choice: Read all four options, rule out wrong ones, pick one; no penalty for guessing so never leave blank.
- Fill in the blanks: Choose the right word from a list; use exact syllabus terms.
What the marking guidelines and feedback say
Marker feedback: key features of server-side programming plus stimulus examples; 'draw on the circular nature of data to link the backend to the front end'.
Worked answers from the marking guidelines
2025 HSC Q23b (3 marks): Server-side web programming (3 marks): criteria and sample answer
Criteria
3: Explains why server-side web programming is needed, with examples from the scenario. 2: Outlines some features, with examples. 1: Identifies a feature and/or relevant examples.
Sample answer
Server-side development will need to be used to provide dynamic information to the front-end (website). There are many dynamic aspects to the website, including the menu which changes along with subscription information and order tracking information. Server-side scripting will need to be written to read the relevant information from storage (most likely, a database) and then provide this information to the front-end.
Common mistakes
- Use the term exactly as the syllabus words it, then link it to the scenario in the question; the 2025 feedback repeatedly rewards using the stimulus.
- Answer the command word: outline gives main points only, explain gives a reason or cause, discuss gives both sides.
Related terms
Same group in the syllabus: W3C and WAI · Client-side (front-end) programming · SQL and non-SQL databases · Web browser and developer (dev) tools · Cascading style sheets (CSS) · CSS selectors (id v class) · CSS maintenance tools · Code libraries and frameworks (front end) · Open-source software · Version control · Load times · Minification · Lazy loading · Caching