Choose 1 option.

Option B is correct because Salesforce Life Sciences Cloud requires a specific API-name prefix for custom Lightning web components that should render as inline components in the Life Sciences mobile app. Salesforce Help for creating and adding an LWC as an inline component on a record page states that admins must create a custom mobile-ready LWC and add lscMobileInline_ as the prefix for the component’s API name. This exact prefix identifies the component as compatible with the Life Sciences mobile inline rendering framework.

This directly matches the issue in the scenario. The component exists and was added to the Account record page, but it does not render correctly as an inline component in the mobile app. The missing configuration is not the page placement itself, but the required naming convention that allows the Life Sciences mobile app to recognize and render the LWC inline.

Option A, lsc_mobile_, is incorrect because it is not the documented prefix for inline mobile LWCs. Option C, mobileInline_, is also incorrect because it omits the Life Sciences-specific lsc prefix and does not match the Salesforce Help requirement. Therefore, the consultant should rename or recreate the LWC API name using the lscMobileInline_ prefix so it functions correctly as an inline component in the Agentforce Life Sciences mobile app.

=========