DataSys+ case studies
DataSys+ · Put your knowledge to work in context.
This independent study page provides practice for DataSys+. 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; Database deployment, performance and recovery lifecycle; Identity, access and cryptographic protection; Security operations, monitoring and response; Continuity, backup and technical recovery. The DataSys+ case studies are 6 cases and about 2,258 words.
1The 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 min2Candidate 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 min3Successful backup job without a verified restore chain
A fictional database service reports successful nightly base backups and frequent log backups. The recovery requirement names a particular point during the afternoon.
177 words, under 1 min4SaaS access after a role change
A fictional organization uses a managed collaboration service for internal planning documents. The provider maintains the application and underlying servers, while the organization configures users, groups and sharing settings.
221 words, about 1 min5An incident review with an action that can be checked
A fictional delivery team restores service after a release encounters an undocumented database dependency. The initial meeting ends with the statement that the engineer should be more careful, but no owner, test or review date is recorded.
219 words, about 1 min6A 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