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

The correct answer is C.

The Lightning record page already supports both mobile and desktop, but the downloaded custom component is not visible on mobile. That points to the component itself, not the page activation. Lightning components must be configured to support the required form factors. Salesforce developer documentation explains that components can be configured for desktop form factor Large, phone form factor Small, or both.

So, if the AppExchange component was built only for desktop pages or only supports the large form factor, users cannot view it in the Salesforce mobile app.

A and D are incorrect because the issue is not page activation if the page already supports mobile and desktop. B is incorrect because the scenario states the record page supports both mobile app and desktop.

===========

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.

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