SF-PD2 User Interface Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✓

  Declare a public property with @api recordId and reference it in the component.

  Why this is correct

  When a Lightning Web Component is placed on a record page, the platform automatically populates the @api recordId property with the id of the record being viewed. No query or Apex is needed. This is the documented, supported way to obtain the current record id in an LWC.

• ✗

  Query the record id in Apex using ApexPages.currentPage().getParameters().

  Why it's wrong here

  ApexPages.currentPage() is available only in Visualforce controller contexts, not in Lightning Web Components running in Lightning Experience. Calling it from an LWC-adjacent Apex method returns null. The scenario also explicitly forbids Apex, so this fails both technically and by requirement.

• ✗

  Call the getUserInfo wire adapter and read the currentRecordId field from the result.

  Why it's wrong here

  The getUserInfo adapter returns information about the logged-in user, such as id, name, and locale, not the record being viewed. There is no currentRecordId field on its result. Using it here would return undefined for the record id, so it cannot satisfy the requirement.

• ✗

  Read the value from the page state by calling NavigationMixin.Navigate with a state object.

  Why it's wrong here

  NavigationMixin.Navigate is used to move to a URL and optionally pass state; it does not read the current record id. Calling it would trigger navigation rather than return data. The record page already provides the id through the recordId property, so this approach is both incorrect and disruptive.