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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Salesforce Accredited Agentforce Financial Services Professional (AP-208) Exam - Topic 2 Question 57 Discussion

An insurance company needs to ensure the record rollups aggregate information from related records for several objects in the Financial Services Cloud at a client or group level.What should the administrator configure to meet the requirement?
C) When the administrator enables record rollups at the group level, all corresponding records are stamped with the Primary Group in the Rallup_c lookup field
A) To show all Primary Group member cases on a related list at the group level, the administrator should add Cases as a picklist value to the Rollup__c field on Account Contact Relationship.
B) Client-level records are aggregated by setting up client-level rollups to all primary group members.
D) To show all Primary Group member opportunities on a related list at the group level, the administrator should add Opportunities as a picklist value to the Household__c field on Account Contact Relationship.

Salesforce Accredited Agentforce Financial Services Professional (AP-208) Exam - Topic 2 Question 57 Discussion

Actual exam question for Salesforce's Salesforce Accredited Agentforce Financial Services Professional (AP-208) exam
Question #: 57
Topic #: 2
[All Salesforce Accredited Agentforce Financial Services Professional (AP-208) Questions]

An insurance company needs to ensure the record rollups aggregate information from related records for several objects in the Financial Services Cloud at a client or group level.

What should the administrator configure to meet the requirement?

Show Suggested Answer Hide Answer
Suggested Answer: C

The architect at Cumulus Insurance should be aware of the limitation that the administrator can define up to 300 total sharing rules for each object when using the Role Hierarchy and sharing rules to implement the franchise business model. Sharing rules are a way of granting additional access to records based on criteria, such as record owner, role, or field values. The Role Hierarchy is a way of organizing users into a hierarchy that reflects the reporting structure of the company. The Role Hierarchy and sharing rules can be used together to control the access and visibility of records for different users in Financial Services Cloud. However, there is a limit of 300 sharing rules per object, which means that the administrator may need to use other methods, such as public groups or manual sharing, to grant access to records beyond this limit.


[Sharing Rules]

[Role Hierarchy]

[Sharing Rule Limits]

by Lawanda at Feb 10, 2025, 06:04 PM

Limited Time Offer

25%

Off

Get Premium Salesforce Accredited Agentforce Financial Services Professional (AP-208) Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Lenita
9 months ago
C seems right, but I’m not sure about the lookup field part.
upvoted 0 times
...
Kiley
10 months ago
A is just confusing, why would you use a picklist for cases?
upvoted 0 times
...
Anjelica
10 months ago
Wait, can you really stamp records with Primary Group like that? Sounds odd.
upvoted 0 times
...
Jolene
10 months ago
Definitely agree with B, it’s straightforward!
upvoted 0 times
...
Mozell
10 months ago
I think option B makes the most sense for client-level rollups.
upvoted 0 times
...
Theola
10 months ago
I vaguely remember something about opportunities and related lists, so option D might be a possibility, but I can't quite connect it to the group level requirement.
upvoted 0 times
...
Linette
11 months ago
I practiced a similar question about showing related lists, and I feel like option A could be relevant, but I'm not entirely confident about the picklist values.
upvoted 0 times
...
Corrinne
11 months ago
I think option C sounds familiar, but I can't recall if enabling rollups automatically stamps records with the Primary Group. I might need to double-check that.
upvoted 0 times
...
Brigette
11 months ago
I remember we discussed rollups in class, but I'm not sure if the client-level records are specifically aggregated by option B. It seems like it could be right, though.
upvoted 0 times
...
Ona
11 months ago
I'm pretty confident I know the answer here. The administrator needs to add the appropriate object types as picklist values to the Rollup__c field on the Account Contact Relationship object.
upvoted 0 times
...
Son
11 months ago
Okay, I think I've got this. The key is to configure the right rollup fields on the Account Contact Relationship object to aggregate the relevant records at the group level.
upvoted 0 times
...
Jestine
11 months ago
Hmm, I'm a bit confused about the difference between client-level and group-level record rollups. I'll need to review that concept again.
upvoted 0 times
...
Quentin
11 months ago
This question seems straightforward, but I want to make sure I understand the requirements correctly before answering.
upvoted 0 times
...
Carli
1 year ago
Option A - adding Cases to the Rollup__c field? Sounds like someone's been mixing up their insurance policies and their Salesforce fields.
upvoted 0 times
Xenia
1 year ago
Exactly. It will help ensure the record rollups aggregate information at the client or group level.
upvoted 0 times
...
Yvette
1 year ago
Oh, I see. So, we should use Rollup Summaries to aggregate the information.
upvoted 0 times
...
Halina
1 year ago
No, that won't work. You need to configure Rollup Summaries on the objects.
upvoted 0 times
...
Tamesha
1 year ago
Option A - adding Cases to the Rollup__c field?
upvoted 0 times
...
...
Niesha
1 year ago
C looks good, but I'm not sure about the 'Rallup_c' field. Is that a new Salesforce feature or just a typo?
upvoted 0 times
...
Rebeca
1 year ago
D? Really? Opportunities on the Household__c field? That's about as useful as a chocolate teapot.
upvoted 0 times
Glory
1 year ago
I think the administrator should look into creating a custom formula field to aggregate the information at the client or group level.
upvoted 0 times
...
Francesco
1 year ago
I agree, using Opportunities on the Household__c field doesn't seem like the best solution for aggregating information.
upvoted 0 times
...
Barrett
1 year ago
Yeah, that doesn't sound right. Maybe they should consider using a custom rollup summary field instead.
upvoted 0 times
...
...
Marnie
1 year ago
Hmm, I'm not sure about adding Cases to the Rollup__c field. Seems like that would just create more confusion.
upvoted 0 times
Sherron
1 year ago
User1: Agreed, it could create more confusion.
upvoted 0 times
...
Mozell
1 year ago
Adding Cases to the Rollup__c field might not be the best approach, it could indeed create confusion.
upvoted 0 times
...
Alfred
1 year ago
User3: Adding Cases to the Rollup__c field might not be the best solution.
upvoted 0 times
...
Miss
1 year ago
User2: Yeah, that would help aggregate information from related records.
upvoted 0 times
...
Lillian
1 year ago
Aggregating information from related records would definitely help with reporting at a higher level.
upvoted 0 times
...
Lyda
1 year ago
User1: I think the administrator should configure a Rollup Summary Field.
upvoted 0 times
...
Rueben
1 year ago
I think the administrator should configure a Rollup Summary Field on the related objects.
upvoted 0 times
...
...
Annmarie
1 year ago
Option B seems like the most logical choice here. Client-level aggregation is exactly what the requirement calls for.
upvoted 0 times
...
Alberta
1 year ago
Hmm, that makes sense too. It's important to ensure the record rollups aggregate information accurately.
upvoted 0 times
...
Roy
1 year ago
I disagree, I believe the correct answer is D, adding Opportunities as a picklist value to the Household__c field.
upvoted 0 times
...
Alberta
1 year ago
I think the answer is B, setting up client-level rollups to all primary group members.
upvoted 0 times
...

Save Cancel