Salesforce Certified Marketing Cloud Engagement Consultant free question 1 / 10 · Domain 1: Discovery and Architecture
A nonprofit collects sign-ups through a public Web Collect form and wants the new subscribers to land in the data model without extra integration work. Which model does the Email Studio list versus data extension article point to?
- A data extension, as it takes more steps to create and so offers more flexibility for web forms
- A list, as the comparison shows Web Collect supported for lists and not for data extensions
- A data extension that is filled through the API, as lists are limited to 500,000 members
- Either model, as Web Collect writes to lists and data extensions in the same way
Show the answer and explanation
Answer: B
Why this is correct
The comparison table in the article shows Web Collect as supported for lists and not supported for data extensions. A team that depends on a Web Collect form therefore fits the list model. Data extensions are the better fit when you need more than 500,000 subscribers, fast imports, triggered sends, or API use, but none of those is the requirement in this case.
Why the other options are wrong
"A data extension, as it takes more steps to create and so offers more flexibility for web forms" … More creation steps do not make a data extension work with Web Collect. The table lists Web Collect as not supported for data extensions.
"Either model, as Web Collect writes to lists and data extensions in the same way" … The two models differ here. Web Collect is supported for lists and is not supported for data extensions.
"A data extension that is filled through the API, as lists are limited to 500,000 members" … The 500,000 figure is a guideline for choosing a model at scale. The scenario does not mention that scale, and the API route does not replace Web Collect.
Key point
A Web Collect requirement points to a list.