SQL & Databases Transactions, Concurrency, and Administration Flashcards

24 sample cards from the Transactions, Concurrency, and Administration deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. Contrast optimistic and pessimistic concurrency control.

   Pessimistic locks data upfront to prevent conflicts, best under high contention; optimistic lets transactions proceed and checks for conflicts at commit, best under low contention.

2. How does optimistic locking typically detect a conflict?

   By checking a version number or timestamp column at commit time; if the row's version changed since it was read, the update is rejected and retried.

3. What is the difference between authentication and authorization?

   Authentication verifies who a user is (login/identity); authorization determines what an authenticated user is allowed to do (privileges).

4. What is a role in database security?

   A named collection of privileges that can be granted to users or other roles, simplifying permission management by grouping access rights.

5. What is the difference between a system privilege and an object privilege?

   A system privilege allows a database-wide action (e.g., CREATE TABLE); an object privilege allows an action on a specific object (e.g., SELECT on a table).

6. Write the SQL to give user 'app' read access to the table 'orders'.

   GRANT SELECT ON orders TO app;

7. What does the WITH GRANT OPTION clause do in a GRANT statement?

   It allows the recipient to further grant the same privilege to other users.

8. Write the SQL to remove UPDATE permission on 'orders' from user 'app'.

   REVOKE UPDATE ON orders FROM app;

9. What is the principle of least privilege?

   Granting each user or process only the minimum permissions needed to perform its function, reducing the attack surface and blast radius of compromise.

10. What is Row-Level Security (RLS)?

    A mechanism that restricts which rows a user can see or modify by attaching security policies (predicates) that filter rows based on the user's identity or attributes.

11. How does a Row-Level Security policy enforce access at query time?

    The DBMS transparently appends the policy's predicate to every query's WHERE clause, so users only see rows satisfying that condition.

12. What is SQL injection?

    An attack where malicious input is concatenated into a SQL query, altering its logic to read, modify, or destroy data or bypass authentication.

13. What is the primary defense against SQL injection?

    Parameterized queries (prepared statements), which send SQL structure and user data separately so input can never be interpreted as code.

14. Why is input escaping alone an insufficient defense against SQL injection?

    Escaping is error-prone and context-dependent; missed cases or type mismatches still allow injection, whereas parameterized queries are structurally safe.

15. Distinguish encryption at rest from encryption in transit.

    At rest protects stored data on disk/backups (e.g., TDE/AES); in transit protects data moving over the network (e.g., TLS/SSL) from eavesdropping.

16. What is Transparent Data Encryption (TDE)?

    Encryption of database files at rest performed automatically by the DBMS, so data on disk and in backups is encrypted without changing the application.

17. Compare full, differential, and incremental backups.

    Full copies all data; differential copies all changes since the last full backup; incremental copies only changes since the last backup of any type — smallest but slowest to restore.

18. Define RPO and RTO in backup and recovery planning.

    RPO (Recovery Point Objective) is the maximum tolerable data loss measured in time; RTO (Recovery Time Objective) is the maximum tolerable downtime to restore service.

19. What is Point-in-Time Recovery (PITR)?

    Restoring a database to a specific past moment by loading a base backup and replaying archived transaction logs up to the chosen timestamp.

20. What database components are required to perform Point-in-Time Recovery?

    A full base backup plus a continuous archive of write-ahead/transaction logs covering the period up to the target recovery time.

21. What is Write-Ahead Logging (WAL) and its core rule?

    A durability technique that records changes to a log before applying them to data pages; the rule is that the log record must reach durable storage before the corresponding data change.

22. Contrast synchronous and asynchronous replication.

    Synchronous replication confirms a commit only after replicas acknowledge, ensuring zero data loss but higher latency; asynchronous commits on the primary first, giving lower latency but risking loss on failover.

23. What key performance metrics indicate database health?

    Throughput (transactions/queries per second), latency/response time, cache/buffer hit ratio, replication lag, lock wait time, and active connection count.

24. Give the formula for cache (buffer) hit ratio and explain why it matters.

    $\text{Hit Ratio} = \frac{\text{cache hits}}{\text{cache hits} + \text{cache misses}}$; a high ratio means most reads are served from memory, reducing slow disk I/O.

What this deck covers

Transactions, Concurrency, and Administration flashcards FAQ