Choosing slow storage like tape or optical for caching
Ignoring speed differences between storage types
Assuming magnetic drives are fastest
3. Consider a system that stores user photos and metadata. Which storage combination best balances cost and performance?
medium
A. Store photos in tape drives and metadata in in-memory storage
B. Store photos and metadata both in relational database
C. Store photos in in-memory storage and metadata in flat files
D. Store photos in object storage and metadata in a relational database
Solution
Step 1: Analyze storage needs for photos and metadata
Photos are large files suited for object storage; metadata is structured data suited for databases.
Step 2: Evaluate cost and performance trade-offs
Object storage is cost-effective for large files; relational DB offers fast queries for metadata.
Final Answer:
Store photos in object storage and metadata in a relational database -> Option D
Quick Check:
Photos = object storage, Metadata = DB [OK]
Hint: Large files in object storage, metadata in DB [OK]
Common Mistakes:
Storing large files in relational DB (costly and slow)
Using in-memory for large photos (expensive, volatile)
Using tape drives for active data (slow access)
4. A system uses a NoSQL database for all data storage but faces slow complex queries. What is the likely cause?
medium
A. NoSQL databases are not optimized for complex relational queries
B. NoSQL databases always have slow writes
C. NoSQL databases cannot store large data
D. NoSQL databases require more network bandwidth
Solution
Step 1: Understand NoSQL database strengths and weaknesses
NoSQL excels at flexible, scalable storage but is not optimized for complex joins or relational queries.
Step 2: Identify cause of slow complex queries
Using NoSQL for relational queries causes slow performance due to lack of join optimizations.
Final Answer:
NoSQL databases are not optimized for complex relational queries -> Option A
Quick Check:
NoSQL + complex queries = slow [OK]
Hint: NoSQL is weak for complex joins [OK]
Common Mistakes:
Assuming NoSQL is slow for all operations
Thinking NoSQL can't store large data
Blaming network bandwidth for query slowness
5. You are designing a system expected to handle millions of user transactions daily with strict latency requirements. Which storage strategy best fits this scenario?
hard
A. Use distributed in-memory cache for active data and persistent NoSQL for durability
B. Use a single relational database for all transactions
C. Store all data on slow cold storage to save cost
D. Use flat files on local disk for all transaction data
Solution
Step 1: Analyze system requirements for high volume and low latency
Millions of transactions require fast access and scalable storage to meet latency needs.
Step 2: Choose storage types that balance speed and durability
Distributed in-memory cache offers fast access; NoSQL provides scalable, durable storage for persistence.
Step 3: Evaluate other options for suitability
Single DB may bottleneck; cold storage is too slow; flat files lack scalability and reliability.
Final Answer:
Use distributed in-memory cache for active data and persistent NoSQL for durability -> Option A
Quick Check:
High volume + low latency = cache + NoSQL [OK]
Hint: Combine fast cache with durable NoSQL storage [OK]
Common Mistakes:
Relying on single DB for high load
Using slow cold storage for active data
Storing transactions in flat files
Recommended
Ready to prove it?
Pass the test and this pattern moves unknownstrongwhile earning +1 Grip toward your certificate.