Software Engineering › Key terms › Y12 Secure Software Architecture › Proactive not reactive
Proactive not reactive
Term Y12 Secure Software Architecture
Definition
A privacy by design principle: anticipate and prevent privacy problems before they happen instead of fixing them after a breach.
Example: Run a privacy impact check during design.
Found in: syllabus, sample exam and familiarisation guidelines, school notes.
Where it is used in the test
Syllabus area: Y12 Secure Software Architecture.
Question types it can appear in
- Multiple choice: Pick the option that matches the definition or example.
- Fill in the blanks: Choose this term to complete a statement or table.
- Short answer: Define, outline or explain it and tie it to the scenario.
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 Q16c (3 marks): Privacy by design 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: Proactive not reactive in Secure Software Architecture (Year 12) · study that set
- Memorise: Cryptography and sandboxing in 'security by design'
- Notes: Privacy by design (syllabus: three parts) (Secure Software Architecture (Year 12))
- Notes: Use and explain the 'privacy by design' approach in the development of software… (Secure Software Architecture (Year 12))
- Master answer: hsc2025-q16c (3 marks, short answer (describe)) (Master model answers: Secure Software Architecture)
How to use it in an answer
A model sentence
“A privacy by design principle: anticipate and prevent privacy problems before they happen instead of fixing them after a breach.” Then apply it: Run a privacy impact check during design.
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 Q16c (3 marks): Privacy by design)
Technique for the question types
- 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.
- Short answer: One clear point per mark, use the stimulus and course terms, and answer the command word.
What the marking guidelines and feedback say
Marker feedback: understand privacy by design (proactive not reactive; embed privacy into design; respect for user privacy) rather than generalising about privacy techniques; link to the scenario, e.g. live location data.
Worked answers from the marking guidelines
2025 HSC Q16c (3 marks): Privacy by design (3 marks): criteria and sample answer
Criteria
3: Describes ONE way privacy by design could be implemented in the weather app. 2: Outlines ONE feature of privacy by design. 1: Identifies a feature of privacy by design.
Sample answer
Embedded within the design of the weather app would be a process for regularly deleting identifiable data. For example, the app would likely record a person's live location to deliver relevant weather details. The privacy by design approach would incorporate a regular process to delete these locations from cache.
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: Security by design · Cryptography · Sandboxing · Privacy by design · Embed privacy into design · Respect for user privacy