MENU
You need to create a relationship between the Weekly_Returns table and the Date table to meet the reporting requirements of the regional managers. What should you do?
Suggested Answer: A
Get Premium PL-300 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
CA
Caprice
11 months ago
Wait, can a calculated column really handle that? Seems risky.
KA
Katlyn
11 months ago
Totally agree with A, it keeps things straightforward!
SH
Sherita
11 months ago
C sounds complicated, why create a new table?
KE
Kenda
12 months ago
I think B might be better, related DAX functions can simplify things.
CH
Chun
12 months ago
A is the way to go, calculated columns are super useful!
KA
Kaitlyn
1 year ago
I feel like option A is the most straightforward solution, but I wonder if there are any performance issues with calculated columns.
LE
Lennie
1 year ago
I practiced a similar question where we had to link tables using DAX functions, but I can't recall if option B is the right approach here.
RE
Rene
1 year ago
I'm not entirely sure about option C; creating a new table sounds complicated. I remember something about many-to-many relationships being tricky.
BE
Bev
1 year ago
I think option A makes sense since creating a calculated column for date-id could help establish a direct relationship with the Date table.
JU
Julio
1 year ago
This seems pretty straightforward to me. I'd go with option A - it's the most direct way to connect the two tables and meet the requirements. I'm confident that's the right approach here.
FR
France
1 year ago
Okay, I've got a strategy for this. I'll create the calculated date-id column in Weekly_Returns, then use that to establish the relationship to the Date table. That should give me the reporting capabilities the managers need.
VE
Verlene
1 year ago
I'm a bit confused by this question. Do we need to create a new table or can we just use the existing Date table? I'm not sure which option is the best approach here.
JO
Josefa
1 year ago
Hmm, this looks like a tricky one. I think I'll go with option A - creating a calculated column in the Weekly_Returns table to use as a date ID. That seems like the most straightforward approach.
EU
Eulah
1 year ago
Responsive design is definitely the way to go here. It's the industry standard for making websites that work well across a variety of devices and screen sizes.
MA
Maryln
1 year ago
I'm hesitating between core service logic and redundantly deployed services; both seem plausible based on what we reviewed!
NA
Nan
1 year ago
PaaS sounds like the best fit to me. It should provide the platform-level services to support the custom application requirements.
HE
Hershel
1 year ago
This question reminds me of a practice one about service attributes. I think I selected similar answers but I can't recall the details.
EV
Evangelina
1 year ago
Option A is the clear winner here. Ain't nobody got time for all that extra table creating and DAX function nonsense. Keep it simple, stupid!
AZ
Azalee
1 year ago
I think we can all agree that option A is the best choice here. Let's keep it simple.
RO
Ronnie
1 year ago
Yeah, creating a new table seems like overkill. Option A is much more straightforward.
YV
Yvonne
1 year ago
I agree, option A is definitely the way to go. Simple and effective.
SH
Shaunna
1 year ago
I like the simplicity of option A. No need to reinvent the wheel here. Sometimes the obvious solution is the best one.
ST
Stephaine
2 years ago
Ooh, a many-to-many relationship, fancy! But I'm not sure it's necessary for this use case. Seems a bit overkill.
DW
Dwight
1 year ago
Yeah, a many-to-many relationship might be too complex for this scenario. Let's keep it simple.
TY
Tyisha
1 year ago
C) Create a new table based on the Date table where date-id is unique, and then create a many-to-many relationship to Weekly_Return.
CH
Chana
1 year ago
A) In the Weekly_Returns table, create a new calculated column named date-id in a format of yyyymmdd and use the calculated column to create a relationship to the Date table.
LO
Lorean
2 years ago
Ugh, option B is just adding more complexity. Why bring in the Sales table when we can handle this with the Date table directly?
CH
Chanel
2 years ago
Creating a calculated column in the Weekly_Returns table is the way to go. It's a simple and straightforward solution that should get the job done.
CA
Cassie
1 year ago
A) In the Weekly_Returns table, create a new calculated column named date-id in a format of yyyymmdd and use the calculated column to create a relationship to the Date table.
DA
Dan
1 year ago
C) Create a new table based on the Date table where date-id is unique, and then create a many-to-many relationship to Weekly_Return.
PA
Paris
1 year ago
A) In the Weekly_Returns table, create a new calculated column named date-id in a format of yyyymmdd and use the calculated column to create a relationship to the Date table.
BL
Blair
2 years ago
I'm not sure, but I think option B could also work if we use the DAX functions correctly.
HO
Hoa
2 years ago
I disagree, I believe option C is better because it allows for more flexibility in the relationship.
CA
Carri
2 years ago
I think option A is the best choice because it creates a direct relationship between the two tables.