Q: 8
A developer is creating a set of SPA components, half of which do not require a custom component exporter. The developer needs to override the default exporter for the remaining components. How can the developer meet this goal?
Options
Discussion
B , since ComponentExporter lets you set a custom exporter just for the components that need it. A would be overkill for the question as written. Pretty sure that's what Adobe expects here!
Option B works here. ComponentExporter lets you override the default for specific SPA components, just like the question says. ImplementationPicker (A) is for broader use, not per-component overrides. Seen similar in practice sets, but let me know if anyone found exceptions.
B seen similar wording on practice. Only need to override for some components so ComponentExporter service fits.
It’s A, this question is so poorly worded on the official exam. Seen similar in other dumps too.
B , ComponentExporter is what you use when you need to override the default exporter for SPA components in AEM. The other options don't deal with export logic. There's a trap with A since ImplementationPicker sounds generic, but it's not for this use case. Pretty sure it's B based on exam practice and Adobe docs.
Is there any official Adobe doc that clearly shows why B is preferred over A for per-component exporter overrides? Official guide or hands-on labs might help clarify the logic here.
Probably B
Its B here. A is tempting but that's for global logic, not per-component overrides like the question wants.
Had something like this in a mock, pretty sure B is spot on. ComponentExporter lets you override exporters per component, exactly what's needed here instead of a global override. Agree with other posts here.
Not A, it's B. ImplementationPicker is a trap since it's not for SPA component exporter overrides.
Be respectful. No spam.