Ruankao Database Systems Engineer (Intermediate) study materials
Ruankao Database Systems Engineer (Intermediate) study resources

Ruankao Database Systems Engineer (Intermediate) case studies

Ruankao Database Systems Engineer (Intermediate) · Put your knowledge to work in context.

This independent study page provides practice for Ruankao Database Systems Engineer (Intermediate). Its editorial learning areas include Data, Databases, and Information Retrieval; SQL models, types and constraints; SQL retrieval, joins and transaction semantics; Database theory, administration and recovery; Computational Thinking and Problem Solving; Computer architecture, logic and data representation; Operating systems, translation and concurrency; Computer Network Fundamentals and Architecture; Security foundations, governance and Chinese context. The Ruankao Database Systems Engineer (Intermediate) case studies are 5 cases and about 2,845 words.

1

The Slow Catalog Query

A public library's catalog database has 2.4 million rows in a table with columns id, title, author, year, subject, and checked out. The web catalog runs this query about 40 times per second: SELECT id, title FROM books WHERE author = ?

613 words, about 3 min
2

Candidate Records at East Mercia Examinations Board

East Mercia Examinations Board stores records for 25,000 candidates. Each record contains an 8-digit candidate number, a 60-character name, and nine paper marks that are integers from 0 to 100.

805 words, about 4 min
3

The Memory Hierarchy Upgrade Committee

A high school robotics team runs a simulation on 40 single-board computers. Each board has a 32 KB L 1 cache with a 1-cycle hit time, a unified L 2 cache with a 10-cycle hit time, and 100-cycle main memory.

633 words, about 3 min
4

The Attendance App Breach

A district's attendance web app has 12,000 student and staff accounts. Passwords are stored as unsalted SHA-256 hashes.

571 words, about 3 min
5

A recovery target does not prescribe one universal architecture

A fictional order service has a recovery-point objective of fifteen minutes and a recovery-time objective of four hours. A tested option creates consistent recovery points every ten minutes and restores the service in three hours after the declared recovery procedure begins.

223 words, about 1 min