Databases — OTHM Qualifications Vocationally-Related Qualification Computer Science Revision
This topic covers fundamental database concepts, relational database design based on user specifications, and using SQL for data interaction. It includes u
Topic Synopsis
This topic covers fundamental database concepts, relational database design based on user specifications, and using SQL for data interaction. It includes understanding data models, normalization, and querying.
Key Concepts & Core Principles
- Defence in Depth: A layered security strategy combining physical, technical, and administrative controls to protect assets. For example, using firewalls, antivirus, and access controls together to mitigate single points of failure.
- Risk Management: The process of identifying, assessing, and prioritising risks (e.g., using qualitative risk matrices) followed by applying controls to reduce risk to an acceptable level, as per ISO 31000.
- Cryptography: Techniques like AES (symmetric) and RSA (asymmetric) for encrypting data at rest and in transit. Students must understand key management, hashing (SHA-256), and digital signatures.
- Incident Response: A structured approach (NIST framework) involving preparation, detection, containment, eradication, recovery, and lessons learned. Key metrics include Mean Time to Detect (MTTD) and Mean Time to Respond (MTTR).
- Ethical Hacking: Authorised penetration testing using tools like Nmap, Metasploit, and Wireshark to find vulnerabilities. It follows a methodology: reconnaissance, scanning, exploitation, and reporting.
Exam Tips & Revision Strategies
- Practice writing SQL queries for common scenarios.
- Use entity-relationship diagrams to plan designs.
- Check for referential integrity in your design.
- For design tasks, always start by analyzing user specifications and mapping nouns to potential entities, then identify relationships and constraints before drawing the ERD.
- In SQL practicals, test queries on sample data first and use EXPLAIN or equivalent to understand query performance; be mindful of security by using parameterised queries or prepared statements.
- When explaining concepts, link them directly to cybersecurity scenarios, e.g., discuss how indexing can support faster threat detection or how views can restrict sensitive data exposure.
Common Misconceptions & Mistakes to Avoid
- Ignoring normalization, leading to data redundancy.
- Using incorrect SQL syntax for joins or subqueries.
- Failing to define primary and foreign keys correctly.
- Assuming that a database is always secure by default without considering encryption, access controls, or audit trails.
- Designing tables without proper normalization, leading to data redundancy and update anomalies.
- Writing SQL queries vulnerable to SQL injection attacks, especially when concatenating user input directly into statements.
Examiner Marking Points
- Define key database concepts like tables, keys, and relationships.
- Design a normalized relational database from user requirements.
- Use SQL to create, read, update, and delete data.
- Explain the purpose of constraints and indexes.
- Award credit for correctly identifying and explaining database concepts such as ACID properties, normalization, and referential integrity in context of cyber security.
- Expect a well-structured entity-relationship diagram (ERD) that translates user specifications into tables, relationships, and constraints with clear justification of design choices.
- Assess SQL proficiency by verifying ability to write syntactically correct Data Definition Language (DDL) and Data Manipulation Language (DML) statements, including joins, subqueries, and aggregation.