Welcome to ExamTopics
ExamTopics Logo
- Expert Verified, Online, Free.
exam questions

Exam DP-300 All Questions

View all questions & answers for the DP-300 exam

Exam DP-300 topic 1 question 40 discussion

Actual exam question from Microsoft's DP-300
Question #: 40
Topic #: 1
[All DP-300 Questions]

You have an Azure subscription that contains an Azure SQL database. The database contains a table named tablet that uses partitioned columnstores.

You need to configure table1 to meet the following requirements:

• Each partition must be compressed.
• The compression ratio must be maximized.
• You must be able to index the compressed data.

What should you use?

  • A. page compression
  • B. columnstore compression
  • C. GZIP compression
  • D. columnstore archival compression
Show Suggested Answer Hide Answer
Suggested Answer: D 🗳️

Comments

Chosen Answer:
This is a voting comment (?) , you can switch to a simple comment.
Switch to a voting comment New
fmelendezcr
6 days, 4 hours ago
Selected Answer: D
D correct
upvoted 1 times
...
Davidjsanchez
4 weeks ago
https://learn.microsoft.com/en-us/sql/relational-databases/data-compression/data-compression?view=sql-server-ver16
upvoted 1 times
...
Davidjsanchez
4 weeks ago
• For partitioned columnstore tables and columnstore indexes, you can configure the archival compression option for each partition, and the various partitions don't have to have the same archival compression setting. Archival compression would be correct
upvoted 1 times
...
bingomutant
2 months ago
D -Columnstore archival compression is a feature of Azure SQL Database and SQL Server that allows for maximum compression of columnstore index data. It is specifically designed for large datasets and is ideal for read-heavy workloads where maximizing compression is crucial.
upvoted 2 times
...
tapsAch
3 months, 1 week ago
Selected Answer: B
The correct Answer is B A clustered columnstore index (CCI) will compress your data and maximize the compression ratio. It also allows you to index the compressed data.
upvoted 1 times
...
yousiftech
6 months, 2 weeks ago
I think the B. columnstore compression is better answer, who is sure about this answer ?
upvoted 1 times
...
yyc585
10 months, 3 weeks ago
Selected Answer: B
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. To perform archival compression, SQL Server runs the Microsoft XPRESS compression algorithm on the data ¹. However, it is important to note that archival compression is not an indexing technique. Important (Only when you can afford extra time and CPU) Archival compression is a data compression technique that can be used to further reduce the size of columnstore data for situations when you can afford extra time and CPU resources to store and retrieve the data.
upvoted 1 times
...
kkkiet
1 year, 9 months ago
While columnstore archival compression can be used to compress columnstore data in a way that minimizes storage costs, it is not optimized for query performance, as it is designed for long-term storage of cold data. In this scenario, the requirement is to maximize compression ratio while still being able to perform index operations on the compressed data. Columnstore archival compression is not optimized for indexing, and as such, it would not meet this requirement. Therefore, the correct answer is B. columnstore compression.
upvoted 3 times
victorlie
1 year, 5 months ago
The questions only asks to achieve max compression. It doesn´t ask for any query or index Optimization. So IMHO, it´s Archival.
upvoted 3 times
ofzrgrz
1 year, 2 months ago
Yeah I agree
upvoted 1 times
...
...
...
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.

Upvoting a comment with a selected answer will also increase the vote count towards that answer by one. So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.

SaveCancel
Loading ...