Choose 1 option.

The correct answer is B because this is a global mobile consent-capture behavior that should be configured in Consent Administration , not enforced through a custom validation rule or permission workaround. Salesforce Life Sciences Consent Management is used to capture, manage, and track HCP consent for communication channels and subscription preferences. Salesforce’s setup guidance for Consent Management directs administrators to the Life Sciences Commercial app, then Admin Console , and then Consent setup areas, which is where consent behavior is configured for the Customer Engagement experience.

The scenario requires that every consent captured on a mobile device include an HCP signature. The appropriate admin configuration is to locate the Signature Section in Consent Administration and set it to Required . This makes the signature pad mandatory during the consent flow and ensures reps cannot submit consent records without capturing the required signature.

Option A is not the best answer because a validation rule on Communication Subscription Consent may block saves after the user attempts submission, but it does not configure the guided mobile consent experience or make the signature pad properly required in the flow. Option C is also incorrect because a custom permission would control access or behavior by profile, but the requirement is global enforcement in the mobile consent flow. Therefore, the consultant should configure the Signature Section as Required in Consent Administration.

=========