At Broome Marine, an administrator opens an existing Account Lightning record page that still uses the standard Record Detail component and wants to adopt Dynamic Forms so that individual fields can be arranged and given their own visibility rules. What is the correct starting action within the Lightning App Builder?
- ASelect the Record Detail component and use its Dynamic Forms upgrade option, then arrange fields using the Fields tab. Correct
- BDelete the current record page and rebuild it from a blank App Page template before adding fields.
- COpen the object's page layout in Object Manager and switch on a Dynamic Forms setting there.
- DAdd a second Record Detail component to the page and hide the original with a visibility filter.
Why A is correct: The Lightning App Builder offers an in-place upgrade on the Record Detail component that converts it to Dynamic Forms, after which the administrator drags individual fields and field sections from the Fields tab onto the page.
Why B is wrong: Rebuilding from a blank template discards the existing configuration and, worse, an app page is record-independent, so it cannot host the Account record's Dynamic Forms fields at all.
Why C is wrong: Dynamic Forms is configured entirely inside the Lightning App Builder, not on the classic page layout, so there is no such toggle in Object Manager; the layout link makes it plausible.
Why D is wrong: Stacking Record Detail components never produces individually placeable fields, so this fails the goal even though it superficially involves components and visibility.