MENU
[Data Prep and Transformation]
A Prism data writer has to create an intermediary Prism calculated field A, used only to achieve a final result in Prism calculated field B and they only need to publish out field B. What should they do?
Suggested Answer: B
Get Premium Workday Prism Analytics Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
26 comments · newest first
CR
Cristy
10 months ago
Not sure about this, can we really just ignore field A?
LA
Lashanda
10 months ago
Wait, why would you delete field A? That seems risky.
CO
Cordie
10 months ago
Hiding field A is a solid choice too.
DA
Dan
10 months ago
I agree, that makes the most sense!
AB
Abel
11 months ago
Field A should definitely be marked as intermediate.
MA
Mary
11 months ago
Hiding field B seems odd since it's the final output. I think we should focus on field A, but I can't remember the exact steps from my notes.
HE
Henriette
11 months ago
I feel like deleting field A could simplify things, but then I worry if that would mess up the calculation for field B.
RA
Ranee
11 months ago
I remember a practice question where we had to manage fields in a similar way. Adding a Manage Fields stage sounds familiar, but I can't recall if we should hide field A or B.
KA
Kanisha
12 months ago
I think marking field A as an intermediate calculation might be the right choice, but I'm not entirely sure how that affects the final output.
EL
Eladia
12 months ago
I think option A is the way to go here. Marking field A as an intermediate calculation is the cleanest solution and ensures that only the final field B gets published out, which is what we need. Seems like the most efficient way to handle this.
JE
Jeannine
12 months ago
Option D seems like the easiest solution - just delete field A and only publish out field B. That way, I don't have to worry about any intermediate calculations or hiding fields. Might be the most straightforward approach.
LY
Lyla
1 year ago
Hmm, I'm a bit unsure about this one. I was thinking option B might work, but I'm not 100% sure if that's the best approach. I'll have to double-check the details on hiding fields in the Manage Fields stage.
KA
Karan
1 year ago
This seems straightforward - I'd go with option A and mark field A as an intermediate calculation. That way, it won't get published out, but I can still use it to calculate field B.
VO
Von
1 year ago
You know, I'm feeling a bit mischievous today. I think I'd choose C, just to see the look on the examiner's face. 'Wait, you want me to hide the output field? Brilliant!'
KA
Kati
1 year ago
User 2: That's a good choice. It keeps things organized and clear.
GL
Glory
1 year ago
User 1: I think I'll go with option A, marking field A as intermediate calculation.
TO
Torie
1 year ago
Hmm, I'd say D is the way to go. Why bother with an intermediary field if you don't need it? Just delete A and let B shine on its own. Efficiency is key, my friend.
SH
Sherill
1 year ago
Agreed, deleting field A and focusing on field B is definitely the most efficient choice.
FE
Felicitas
1 year ago
I think D is the best option too. No need for extra steps if you don't need field A.
VI
Vicky
1 year ago
Ah, the age-old dilemma of intermediary fields. I'd go with option B - hide that pesky field A and just publish field B. Keep it simple, you know?
LY
Lynsey
1 year ago
Definitely, no need to clutter things up with unnecessary intermediary fields.
HE
Helene
1 year ago
Yeah, that's what I would do too. Keeping it simple is key in data transformation.
AN
Anglea
1 year ago
Option B sounds like the best choice. Just hide field A and focus on publishing field B.
EV
Eveline
1 year ago
But wouldn't it be better to just delete field A and leave field B?
FE
Felix
1 year ago
I agree with Stephanie, marking field A as intermediate calculation makes sense.
ST
Stephanie
1 year ago
I think they should mark field A as intermediate calculation.