Salesforce CRT-403 Exam - Topic 8 Question 41 Discussion

Actual exam question for Salesforce's CRT-403 exam

Question #: 41
Topic #: 8

[All CRT-403 Questions]

Northern Trail Outfitters wants to change a master-detail relationship on

Account to a lookup relationship with a custom object Park. The app builder tries to

reconfigure this but is unable to do so.

What could be causing this?

AThe Account is included in a flow process on the Park object.

BThe Park object needs at least one Master-Detail field for reporting.

CThe Account record includes Parks roll-up summary fields.

DThe park records have existing formulas on the Account.

Show Suggested Answer

Suggested Answer: C

When attempting to change a master-detail relationship to a lookup relationship, Salesforce imposes specific restrictions to maintain data integrity:

C . The Account record includes Parks roll-up summary fields. Master-detail relationships allow roll-up summary fields to aggregate data from child records onto the parent record. If any roll-up summary fields are present on the master object (Account in this case) that depend on the detail records (Parks), the relationship cannot be changed to lookup until these roll-up summary fields are removed.

To resolve this, follow these steps:

Identify and delete all roll-up summary fields on the Account object that reference the Park object.

Convert the master-detail relationship to a lookup relationship.

Recreate any necessary roll-ups using declarative tools like Process Builder or Flow if needed, as lookups do not support native roll-up summaries.

For more guidance, review Salesforce's documentation on Changing Field Types.

by Verda at May 09, 2024, 11:10 PM

Limited Time Offer

25%

Off

Get Premium CRT-403 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel

Carmela

3 months ago

Not so sure about D, formulas shouldn't affect relationship types like that.

upvoted 0 times

...

Stephen

3 months ago

B is wrong, the Park object doesn't need a Master-Detail field for reporting.

upvoted 0 times

...

Devon

3 months ago

Wait, can you really not change it if there are roll-ups? That's surprising!

upvoted 0 times

...

Ressie

4 months ago

Agreed, C makes the most sense here!

upvoted 0 times

...

Leonida

4 months ago

I think it's definitely C, roll-up summary fields can block changes.

upvoted 0 times

...

Adela

4 months ago

I feel like formulas on the Account might not be a reason for this issue, so I'm leaning away from option D.

upvoted 0 times

...

Geoffrey

4 months ago

I practiced a similar question where the object needed a master-detail for reporting, but I can't recall if that's the case here.

upvoted 0 times

...

Maricela

4 months ago

I'm not entirely sure, but I think if the Account is part of a flow, that could cause issues too. Could be option A?

upvoted 0 times

...

Novella

5 months ago

I remember something about how roll-up summary fields can prevent changing relationships, so maybe it's option C?

upvoted 0 times

...

Krystina

5 months ago

I'm a bit confused by this question. I'm not sure I fully understand the implications of the different relationship types and how they might impact the ability to make this change. I'll need to review my notes on object relationships before attempting to answer.

upvoted 0 times

...

Jesusita

5 months ago

I've seen this type of issue before. My guess is that the Account object has some existing functionality, like a flow or roll-up summary fields, that's preventing the change to a lookup relationship.

upvoted 0 times

...

Simona

5 months ago

Okay, let's see. I'm pretty sure it has something to do with the existing setup on the Account object, but I'm not sure which of these options is the correct answer.

upvoted 0 times

...

Lashawna

5 months ago

Hmm, this is a tricky one. I'll need to think carefully about the relationships between the objects and any potential dependencies or constraints.

upvoted 0 times

...

Dick

5 months ago

I'm feeling confident about this one. Based on the information provided, I think the correct answer is C - the Account record includes Parks roll-up summary fields, which would block the change to a lookup relationship.

upvoted 0 times

...

Sharmaine

5 months ago

I'm a bit confused on this one. I know hashes are important for security, but I'm not sure which specific property they guarantee.

upvoted 0 times

...

Leonor

5 months ago

I think the answer is A. The question specifically mentions disabling an Epipe service, and the command "config>service# epipe service-id shutdown" looks like the right one to do that.

upvoted 0 times

...

Lindy

2 years ago

Wait, hold up. Is option B even a real thing? 'The Park object needs at least one Master-Detail field for reporting?' That's like saying you need a unicorn to ride a bicycle. Seriously, Salesforce?

upvoted 0 times

Lawrence

2 years ago

I think we should double-check the other options to see if any of them could be causing the issue.

upvoted 0 times

...

Crista

2 years ago

I agree with Virgie, it does sound like a valid reason for the issue.

upvoted 0 times

...

Merilyn

2 years ago

I agree, it doesn't make much sense. Maybe there's another reason why the app builder can't reconfigure the relationship.

upvoted 0 times

...

Virgie

2 years ago

I'm not sure about that. Maybe it's just a requirement in this specific case.

upvoted 0 times

...

Dylan

2 years ago

Yeah, that does sound strange. I've never heard of that requirement before.

upvoted 0 times

...

Ollie

2 years ago

I think option B is a real thing. It's necessary for reporting.

upvoted 0 times

...

Allene

2 years ago

Haha, this is a classic Salesforce problem. I bet it's option A - the Account is included in a flow process on the Park object, and that's causing the issue. Good one, Salesforce!

upvoted 0 times

...

Ariel

2 years ago

I'm unsure. Those formulas on Account mentioned in D could mess it up too.

upvoted 0 times

...

Paul

2 years ago

Option D seems the most likely to me. If there are existing formulas on the Park records that reference the Account, that would definitely make it difficult to change the relationship.

upvoted 0 times

...

Lauran

2 years ago

Hmm, I'm not sure. Could it be option B? The Park object needs at least one Master-Detail field for reporting, so that might be preventing the change.

upvoted 0 times

Noe

2 years ago

Maybe, but it could also be option C, if the Account record includes Parks roll-up summary fields.

upvoted 0 times

...

Aretha

2 years ago

It could be option B, the Park object needs a Master-Detail field for reporting.

upvoted 0 times

...

Trinidad

2 years ago

C) The Account record includes Parks roll-up summary fields.

upvoted 0 times

...

Jesusita

2 years ago

I think you might be right, that could be causing the issue.

upvoted 0 times

...

Milly

2 years ago

It could be option B, the Park object needs a Master-Detail field for reporting.

upvoted 0 times

...

Barney

2 years ago

B) The Park object needs at least one Master-Detail field for reporting.

upvoted 0 times

...

Sean

2 years ago

A) The Account is included in a flow process on the Park object.

upvoted 0 times

...

Izetta

2 years ago

I think C. Roll-up summaries can't be on lookup relationships.

upvoted 0 times

...

Chantell

2 years ago

But A could also be valid with a flow process inclusion, don't you think?

upvoted 0 times

...

Antonette

2 years ago

Why not? C makes sense because of roll-up summary fields.

upvoted 0 times

...

King

2 years ago

I think it's option C. The Park records have existing roll-up summary fields on the Account, which is why the app builder can't reconfigure the relationship.

upvoted 0 times