We exported data from our on-premise relational database to a cloud-based non-relational database. After the export, we noticed that the size of the cloud-based database was significantly larger than our on-premise database. What is the likely reason that the database size increased?
Select the correct answer.
Suggested Answer: B
Get Premium C90.02 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
12 comments · newest first
OL
Olive
3 months ago
I’m with C. The state data for scalability could add a lot of size.
AL
Alberta
3 months ago
I lean towards A. Extra metadata from HTTP headers makes sense.
GO
Golda
3 months ago
I think it's definitely B. Normalization to denormalization can really bloat size.
AV
Avery
4 months ago
All of the above? That sounds a bit too convenient, doesn't it?
CH
Chuck
4 months ago
C makes sense too, especially with cloud scalability needs.
MA
Malcom
4 months ago
Wait, isn't it possible that A could also contribute? More metadata could add up.
BA
Barb
5 months ago
Totally agree with B! Non-relational databases usually store more data.
GL
Glory
6 months ago
I think B is the main reason. Normalization vs. denormalization really affects size.
LY
Lynelle
6 months ago
I’m leaning towards D, thinking that all these factors could contribute to the size increase. It feels like a combination of issues we’ve seen in practice questions.
HO
Honey
6 months ago
I feel like option C makes sense too, especially with cloud databases needing to manage state data. But does that really apply to all non-relational databases?
EL
Ellen
7 months ago
I think we covered something about metadata in our last class. Option A could be a factor, but I wonder if it's significant enough to cause such a large increase.
MA
Matilda
7 months ago
I remember discussing how normalization affects database size, so option B seems plausible. But I'm not entirely sure if denormalization always leads to a size increase.