Q: 9
Sales reps at UC were facing governor limits while configuring certain large bundles, theadmin at UC
has set the ‘enable large configurations package settings to TRUE now theusers are experiencing
longer loading times between saving a bundle configuration andreturning to the quote line
editor,even for smaller bundles.what should the admin do toresolve this issue?
Options
Discussion
Option A Good question, similar logic came up in some practice sets. Selectively enabling on only the needed bundles makes total sense.
C or D maybe. Splitting bundles (C) is something I’ve seen in practice tests as a fix for governor limits, and disabling the large config setting (D) might help speed up smaller bundles. Haven’t found a clear answer in the official guide though, so someone correct me if I missed something.
Nah, C is a bit of a trap since splitting bundles isn't always needed. A.
Yeah, makes sense to only enable it on specific parent bundles. A
C/D? This setting always causes headaches, wish Salesforce made it clearer. A is correct since you should only enable large config where needed, not globally. Pretty sure that matches recent exam practice.
C tbh, but not totally sure. Splitting big bundles into smaller ones is a known way to dodge governor limits-have seen that advised before. Maybe not the "best practice" compared to A, but if the main issue is complexity, C seems logical. Open to being wrong if I'm missing some platform nuance here.
A imo. Selectively enabling the Large Configuration setting at the bundle parent level keeps small bundles from being impacted by extra processing, so you get better performance for most users. Blanket enabling this feature causes slowdowns even where it's not needed. Pretty sure that's the usual Salesforce approach, but open to other takes.
Selective enabling is the way to go, so A is right. Turning large config on everywhere slows down even small bundles, and you only need it for those with high product counts anyway. Pretty sure that's Salesforce best practice, but happy if someone disagrees.
A is wrong, it's B only if you want full redesign, but the question wants a targeted fix. Selective enabling (A) helps avoid penalizing smaller bundles. Unless asked for global impact, you shouldn't flip D. Seen similar logic in exam reports.
I’d say D. Disabling the large configurations setting feels less risky than splitting bundles everywhere, though I'm not 100% convinced.
Be respectful. No spam.
