A developer Is asked to create a Visualforce page that lists the contacts owned by the current user. This component will be embedded In a Lightning page. Without writing unnecessary code, which…

A 'Standard list controller' (i.e., `StandardSetController`) typically requires custom Apex code to implement dynamic filtering like 'owned by the current user' unless a specific list view is referenced, which goes against the 'without writing unnecessary code' constraint.

A Visualforce page can use a standard controller for the User object and then leverage the `<apex:relatedList>` component to display contact records where the User is the owner, effectively listing contacts owned by the current user without custom Apex code.

A Lightning controller is used for Lightning Web Components or Aura Components, not for Visualforce pages.

A custom controller would require writing Apex code to query and filter the contacts, which the question explicitly seeks to avoid.