Deal of The Day! 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 12 Question 94 Discussion

Posted by Lenny on Jun 29, 2024 at 01:57 AM

You have an Azure SQL database named DB1.

You have a table name Table1 that has 20 columns of type CHAR(400). Row compression for Table1 is enabled.

During a database audit, you discover that none of the fields contain more than 150 characters.

You need to ensure that you can apply page compression to Table1.

What should you do?

Suggested Answer: D, E

Get Premium DP-300 Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test
27 comments · newest first
ST
Stefan 12 months ago
Sparse columns? Really? I thought that was for different use cases!
VI
Vivienne 12 months ago
Changing to varchar (200) could work too, but not sure if it's the best choice.
DO
Dorsey 12 months ago
Wait, why not just use nvarchar? Seems like a better option.
FR
Frank 1 year ago
I agree, varchar (MAX) is the way to go!
MA
Magda 1 year ago
You need to change the column type to varchar for page compression.
NU
Nu 1 year ago
I feel like nvarchar(MAX) is not the right choice here since we only need to store up to 150 characters. It seems like overkill.
CA
Carolynn 1 year ago
I practiced a similar question where we had to optimize storage. I think changing to varchar(200) could be a good option since it limits the size.
JO
Johanna 1 year ago
I'm not entirely sure, but I think sparse columns are more about saving space for NULL values. Not sure if that helps with page compression.
BR
Brock 1 year ago
I remember reading that page compression requires the data types to be variable-length, so I think changing to varchar might be the right move.
ST
Stephania 1 year ago
Ah, I see what they're getting at. Changing the column type should do the trick.
SH
Sharika 1 year ago
Page compression, huh? I'm a bit unsure about the specifics, but I'll give it my best shot.
BE
Belen 1 year ago
Hmm, this looks like a tricky one. I'll need to think through the options carefully.
GL
Gladys 1 year ago
Okay, I think I know the answer here. Let me double-check the details.
PE
Pearly 1 year ago
This looks like a classic network access control issue. I think the key is to identify the problem - clients are getting the correct IP address but can't access the internet, so it's likely an ACL or firewall rule blocking the traffic.
IV
Ivette 1 year ago
I'm a bit confused by this question. Regulation T is not my strongest area, so I'll need to review the key points before making a decision. Hopefully, I can eliminate a few options and narrow it down.
MA
Marci 2 years ago
I'm no database expert, but I'm pretty sure option A, configuring the columns as sparse, is a completely different feature. Someone's trying to trick us here!
ON
Ona 2 years ago
Hold up, why are we even using CHAR in the first place? Shouldn't we be using VARCHAR to begin with? I'd go with option C and change it to varchar (MAX).
TA
Tammy 2 years ago
Woah, 400 characters for a CHAR field? That's overkill! I'd go with option D and change it to varchar (200). Less memory usage, and it still covers the 150 character limit.
SO
Son 1 year ago
↳ replying to Tammy
Agreed, it's a more efficient choice.
CR
Cristy 1 year ago
↳ replying to Tammy
Good point! That would definitely save on memory.
SH
Sharita 1 year ago
↳ replying to Tammy
Option D) Change the column type to varchar (200).
SO
Sophia 2 years ago
Hmm, I'm thinking option B. Changing the column type to nvarchar (MAX) seems like the way to go. That'll allow for the page compression to work its magic.
AM
Amie 2 years ago
↳ replying to Sophia
I think option D might be better, changing the column type to varchar (200) could also work.
AR
Arminda 2 years ago
↳ replying to Sophia
I agree with you, option B seems like the best choice here.
LO
Lorita 2 years ago
I'm not sure, maybe we should consider configuring the columns as sparse instead.
AR
Arthur 2 years ago
I agree with Chantell, changing the column type to varchar (200) seems like the right choice.
CH
Chantell 2 years ago
I think we should change the column type to varchar (200) to apply page compression.
0/2000 characters

Save Cancel