Salesforce Updated Platform-App-Builder Exam Questions and Answers by lennie

Queues are represented through Salesforce Group records, and their stable programmatic identifier is the DeveloperName , or API name. A flow that determines a regional queue dynamically can first calculate the appropriate queue API name in a text or formula resource and then use Get Records against the Group object, filtering DeveloperName to that value and Type to Queue. Salesforce ' s current Flow guidance provides this exact architecture for dynamically resolving queues rather than hard-coding IDs. Hard-coded user or queue IDs are brittle across environments and conflict with the dynamic-routing requirement. An asynchronous path changes execution timing but does not resolve the assignee. A custom Task text field likewise does not establish an actual queue assignment. Therefore, the formula-resource plus Get Records pattern is the correct declarative solution.

================

Salesforce imposes a daily limit on mass and list email sent to external recipients. Current Salesforce documentation specifies a limit of 5,000 external email addresses per day per licensed org , meaning a recurring campaign to 7,000 contacts cannot be completed using standard Salesforce mass-email functionality in one day. Salesforce recommends considering a third-party mass-email solution from its marketplace when higher-volume sending is required. This corresponds to option B in the question. Requesting an arbitrary increase does not remove the standard product limitation. Exporting contacts to an external email client creates additional data-management and compliance concerns, while developing Apex and an LWC does not bypass Salesforce ' s applicable email limits. A purpose-built marketplace solution is therefore the appropriate scalable approach. Salesforce

================

A Screen Flow is specifically designed for interactive processes that display information, ask users questions, and capture user input across one or more screens. Salesforce states that Screen elements can collect text, choices, dates, lookup values, and other inputs, and multiple Screen elements can create a guided multi-page experience. Screen flows can also be embedded directly on Lightning record pages, which precisely matches the requirement to guide customer care agents from the Case page. A record-triggered flow runs automatically when record data changes and does not provide an interactive wizard. An autolaunched flow normally runs without screens, while a schedule-triggered flow executes at defined times for batches of records. Because agents must actively provide information at several stages of the return process, Screen Flow is the correct declarative solution.

The correct answer is A because Salesforce provides the Establish upper bound on existing picklists option to protect picklist performance by limiting inactive picklist values. Salesforce documentation states that this setting runs a query to identify picklists with fewer than 4,000 inactive values and enforce the limit.

Why others are incorrect:

B is for reusing picklist values across fields, not reducing inactive picklist performance impact.

C would worsen the issue because it removes limits on inactive values.

D is too drastic and not the recommended Salesforce feature for this issue.

===========