Software Engineering › Key terms › Y12 Secure Software Architecture › Session management
Session management
Term Key terms bank Y12 Secure Software Architecture
Definition
Creating, tracking and ending a user's session securely (session ID or token, timeouts, logout), which supports both security and a smooth user experience.
Example: 2025 Q20 marker note: relate session management to code efficiency and to user experience; describe, don't just identify.
Found in: syllabus, 2025 HSC marking guidelines, school notes.
Tracking a user's state across requests with a session ID.
Where it is used in the test
Syllabus area: Y12 Secure Software Architecture.
Question types it can appear in
- Short answer: Describe session management and efficiency (2025 Q20)
- Multiple choice: Pick the option that matches the definition or example.
Where it has appeared in the paper
Secure Software Architecture (Part A). Part letters follow each paper’s own layout.
Related past questions
- 2025 HSC Q20 (3 marks): Session management Secure Software Architecture (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: Session management in Secure Software Architecture (Year 12) · study that set
- Memorise: Defensive data input handling: validation, sanitisation, error handling
- Key terms bank entry: Session management
- Master answer: hsc2025-q20 (3 marks, short answer (describe)) (Master model answers: Secure Software Architecture)
- Notes: Design, develop, and implement code that considers efficient execution for the user,… (Secure Software Architecture (Year 12))
- Notes: Design, develop and implement secure code to minimise vulnerabilities in user action… (Secure Software Architecture (Year 12))
- Notes: Efficient execution: memory, session and exception management (Secure Software Architecture (Year 12))
How to use it in an answer
A model sentence
“Creating, tracking and ending a user's session securely (session ID or token, timeouts, logout), which supports both security and a smooth user experience.” Then apply it: 2025 Q20 marker note: relate session management to code efficiency and to user experience; describe, don't just identify.
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
- Describe: Provide characteristics and features. (2025 HSC Q20 (3 marks): Session management)
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.
What the marking guidelines and feedback say
Answers could include: reducing database and network bottlenecks (frequent access to session stores, especially distributed, causes latency); preventing memory leaks (poor server-side session handling triggers more garbage collection and degrades performance); enabling scalable, responsive systems (asynchronous or lazy cleanup). Marker feedback: DESCRIBE features rather than just identifying them; relate to code efficiency AND user experience.
Worked answers from the marking guidelines
2025 HSC Q20 (3 marks): Session management (3 marks): criteria and sample answer
Criteria
3: Describes how session management can affect code execution efficiency. 2: Identifies some features of session management. 1: Some relevant information.
Sample answer
Efficient session management limits memory consumption by restricting session data size and lifetime. Excessive reading, writing or storing large objects increases input/output operations and slows code execution for the user. Removing sessions when they are no longer required is essential to prevent unnecessary resource consumption.
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: Defensive data input handling · Input validation · Sanitisation · Error handling · Application programming interface (API) · Excessive data exposure · Memory management · Exception management