The correct answer is C because the Life Sciences Cloud mobile app relies on metadata cache configuration to make updated page metadata available in the mobile experience. Salesforce documentation for customizing the Life Sciences Cloud mobile app states that administrators should generate a new metadata cache whenever they update Lightning record pages, page layouts, object or schema changes, new or modified feature settings, or related mobile configuration. The official setup path also references the Life Sciences Commercial app, Admin Console, Mobile, and Object Metadata Cache Configuration.

In this scenario, the Lightning web component was deployed and added correctly to the Lightning page, and the page was activated as the Org Default for Desktop and Phone. That means the desktop Lightning configuration is not the issue. The missing step is refreshing or creating the mobile metadata cache so the Agentforce Life Sciences mobile app can recognize the updated Lightning page structure and component metadata.

Option A is incorrect because activating a trigger handler is not the normal remedy for mobile page metadata visibility. Trigger handlers relate to backend automation behavior, not rendering a newly added component in the mobile UI. Option B is also not the best answer because reinstalling the app is a user-side workaround and does not address the administrator-controlled metadata cache. The correct administrative action is to create a new metadata cache in the Admin Console.

=========