New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Microsoft DP-300 Exam - Topic 6 Question 26 Discussion

Actual exam question for Microsoft's DP-300 exam
Question #: 26
Topic #: 6
[All DP-300 Questions]

You have an Azure SQL database that contains a table named factSales. FactSales contains the columns shown in the following table.

FactSales has 6 billion rows and is loaded nightly by using a batch process.

Which type of compression provides the greatest space reduction for the database?

Show Suggested Answer Hide Answer
Suggested Answer: D

Columnstore tables and indexes are always stored with columnstore compression. You can further reduce the size of columnstore data by configuring an additional compression called archival compression.

Note: Columnstore --- The columnstore index is also logically organized as a table with rows and columns, but the data is physically stored in a column-wise data format.

Incorrect Answers:

B: Rowstore --- The rowstore index is the traditional style that has been around since the initial release of SQL Server.

For rowstore tables and indexes, use the data compression feature to help reduce the size of the database.


https://docs.microsoft.com/en-us/sql/relational-databases/data-compression/data-compression

Contribute your Thoughts:

0/2000 characters
Charlene
4 months ago
Page compression is decent, but columnstore is the way to go!
upvoted 0 times
...
Veronika
4 months ago
Wait, are you sure about that? Sounds too good to be true.
upvoted 0 times
...
Leah
4 months ago
Definitely columnstore archival compression for max space savings!
upvoted 0 times
...
Rocco
5 months ago
I think row compression could work too, but not as well.
upvoted 0 times
...
Noemi
5 months ago
Columnstore compression is the best for large datasets!
upvoted 0 times
...
Alison
5 months ago
I’m a bit confused about the differences between row and page compression. I hope I remember the right details during the exam!
upvoted 0 times
...
Shannon
5 months ago
I practiced a similar question where columnstore archival compression was highlighted for its efficiency with large tables.
upvoted 0 times
...
Quentin
5 months ago
I’m not entirely sure, but I remember something about page compression being effective for reducing space too.
upvoted 0 times
...
Rosio
5 months ago
I think columnstore compression might be the best option here since it’s designed for large datasets like this one.
upvoted 0 times
...
Carol
5 months ago
Hmm, I'm a bit confused by some of these options. I know ESS is used for scheduling jobs, but I'm not sure about the specifics of how the job request processor and dispatcher work. I'll need to review my notes on that.
upvoted 0 times
...
Apolonia
5 months ago
Hmm, this seems straightforward. I think the two objects are application and package.
upvoted 0 times
...
Elli
5 months ago
I'm not sure about this one. Option C looks interesting with the `PipelineParameter`, but I'm not sure if that's the right approach for this specific question. I'll have to review the Azure ML documentation to see if that's the appropriate solution.
upvoted 0 times
...

Save Cancel