Salesforce Certified Platform Developer II — Question 278

The Account edit button must be overridden in an org where a subset of users still use Salesforce Classic. The org already has a Lightning Component that will do the work necessary for the override, and the client wants to be able to reuse it.
How should a developer implement this?

Answer options

• A. Override the edit button for both Lightning and Classic with a Lightning Component
• B. Override the edit button for both Lightning and Classic with a new Visualforce page
• C. Override the edit button for Lightning with a Lightning Page, and Classic with a Visualforce page that contains the Lightning Component
• D. Override the edit button for Lightning with a Lightning Component, and Classic with a Visualforce page that contains the Lightning Component

Correct answer: C

Explanation

The correct answer is C because it allows the reuse of the Lightning Component specifically for Classic users by embedding it within a Visualforce page, while also providing a tailored experience for Lightning users with a dedicated Lightning Page. Option A is incorrect as it does not accommodate the Classic users properly, and option B fails to leverage the existing Lightning Component. Option D is misleading, as it suggests using the Lightning Component for Lightning but doesn't specify the proper use for Classic.