B is correct. After further testing, I can verify. None of the other answers make sense. But this question is still missing an important step: You have to create the twin field on Product Option as well.

A is 100% WRONG. You can't create a Price Rule tot injects a Quote Line field value back to a Product Option field (at least, no way I could figure out, without some wacky additional formula fields or automations).

C make no sense either, neither does D since you can't automate updating CPQ Product Options when the Configurator is launched using WF/Flow (afaik).

I also assume they're talking about a single Product here, since there is no mention of a bundle.

So I guess they're looking for B here, but another confusing and poorly worded question seems just designed to confuse you. There is nothing required except creating twin fields on Product Option and Quote Line, creating the CA, and setting Configuration Type=Allowed/Required to make sure the user is prompted to enter it in the first place. Then it will be mapped back whenever you click the wrench or Edit Lines again (tested and confirmed).

Can someone explain this question? None of the answers seem to make any sense. What's missing here is to create a Product Option twin field (NOT Product twin field), then the mapping and field population will happen automatically from what's already on the Product Configuration Attribute when you hit Edit Lines again (just tested and confirmed it works fine). So how are any of these answers correct?

B. The value is auto-mapped back to the Product option field when the user enters configurations.