vmartinez

Consider the following scenario. Your workflow sends a series of marketing emails that include a large discount email. Should you turn the enrollment of merged contacts for this workflow on or off?

• On
• Off

 

Explanation

Keep enrollment of merged contacts disabled for this workflow. HubSpot states that merged contacts do not automatically enroll because of merge-related data changes unless this setting is turned on. That matters for a discount email series because a merge can create qualification changes that would enroll the primary contact after the records combine. In a promotional workflow, that increases the risk of sending duplicate or unintended discount emails. Using the default disabled setting helps prevent merge-driven enrollment from triggering that series. HubSpot Knowledge Base+1

Why the other options are incorrect

On Turning this on allows merged contacts to enroll at the time of the merge, which can trigger a discount workflow from merge-related changes and create unwanted promotional sends. HubSpot Knowledge Base+1

Source for verification

https://knowledge.hubspot.com/workflows/manage-workflow-enrollment-settings

https://knowledge.hubspot.com/records/merge-records

 

True or false? The primary uses of marketing automation are lead nurturing, data hygiene maintenance, and routing support tickets.

• True
• False

 

Explanation

HubSpot documents workflows as automation for marketing, sales, and service processes, but its core marketing use cases focus on keeping prospects engaged, assigning leads, creating records, and maintaining record data. Lead nurturing clearly fits marketing automation because HubSpot describes using automation to continue nurturing contacts after they engage with forms or marketing emails. Data maintenance also fits because workflow actions can update records and add or manage information automatically. Routing support tickets, however, belongs to service or pipeline automation rather than the primary marketing automation use case in HubSpot Marketing Software. HubSpot Knowledge Base+1

Why the other options are incorrect

A) This would incorrectly treat ticket routing as a primary marketing automation use, even though HubSpot documents it under service and pipeline automation. HubSpot Knowledge Base

Source for verification

https://knowledge.hubspot.com/get-started/automate-your-processes

https://knowledge.hubspot.com/workflows/choose-your-workflow-actions

 

Which enrollment trigger allows you to re-enroll contacts every time the trigger occurs?

• Event-based
• Schedule-based
• Trigger-based
• Filter-based

 

Explanation

In HubSpot workflows, event-based enrollment triggers are the trigger type that supports re-enrollment every time the defined event happens. HubSpot’s event enrollment setup includes the option to re-enroll records “every time the trigger occurs,” which is tied directly to repeated event activity such as form submissions or custom events. By contrast, standard re-enrollment for criteria-based triggers depends on a record changing from not meeting criteria to meeting criteria again. That makes event-based enrollment triggers the correct choice when repeated occurrence of the same trigger should enroll the record again. HubSpot Knowledge Base+2HubSpot Knowledge Base+2

Why the other options are incorrect

Schedule-based This enrolls records on a defined recurring frequency, not each time a tracked event happens. HubSpot Knowledge Base

Trigger-based This is not an official HubSpot enrollment trigger type. HubSpot Knowledge Base

Filter-based This depends on criteria being met and re-met, not on re-enrolling every time an event occurs. HubSpot Knowledge Base+1

Source for verification

https://knowledge.hubspot.com/workflows/set-event-enrollment-triggers

https://knowledge.hubspot.com/workflows/add-re-enrollment-triggers-to-a-workflow

 

What are the different types of enrollment triggers in workflows?

• Event-based, list-based, and data-based
• List-based, re-enrollment-based, and date-based
• Event-based, filter-based, and schedule-based
• Re-enrollment-based, branch-based, and internal-based

 

Explanation

HubSpot documents three workflow enrollment trigger types: When an event occurs, When filter criteria is met, and Based on a schedule. HubSpot Knowledge Base+3HubSpot Knowledge Base+3HubSpot Knowledge Base+3

These are the official ways records automatically enter a workflow based on activity, property-based conditions, or scheduled timing. HubSpot Knowledge Base+1

That is why the correct set includes event-based, filter-based, and schedule-based triggers. HubSpot Knowledge Base+3HubSpot Knowledge Base+3HubSpot Knowledge Base+3

HubSpot treats other terms such as re-enrollment as settings related to enrollment behavior, not as one of the primary trigger types. HubSpot Knowledge Base+1

Why the other options are incorrect

Event-based, list-based, and data-based HubSpot uses filter criteria and Based on a schedule as official trigger categories, while list membership is handled through criteria rather than as a separate primary trigger type. HubSpot Knowledge Base+2HubSpot Knowledge Base+2

List-based, re-enrollment-based, and date-based Re-enrollment is a workflow setting, and HubSpot now uses Based on a schedule instead of treating date-based enrollment as a standalone trigger category. HubSpot Knowledge Base+2HubSpot Knowledge Base+2

Re-enrollment-based, branch-based, and internal-based These are not HubSpot enrollment trigger types, and branches belong to workflow actions rather than enrollment setup. HubSpot Knowledge Base+2HubSpot Knowledge Base+2

Source for verification

https://knowledge.hubspot.com/workflows/set-your-workflow-enrollment-triggers

https://knowledge.hubspot.com/workflows/use-based-on-a-schedule-workflow-enrollment-triggers

 

Which of the following is NOT a component of a topic cluster?

• Core topics, which will take the shape of your pillar page
• Subtopics, such as blog posts or videos
• Distribution channels, such as YouTube or X
• Internal hyperlinks

 

Explanation

A topic cluster in HubSpot is built around a main topic that is connected to a pillar page. Supporting content is organized through subtopic keywords and attached content such as blog posts, landing pages, or website pages. Internal links connect subtopic content back to the pillar page to show the relationship between the content pieces. Distribution platforms are used to share content, but they are not part of the HubSpot topic cluster structure.

Why the other options are incorrect

Core topics are part of the topic cluster model because they define the main subject connected to the pillar page.

Subtopics are part of the cluster because they support the main topic with related content.

Internal hyperlinks are part of the cluster because they connect subtopic content to the pillar page.

Source for verification

https://knowledge.hubspot.com/content-strategy/pillar-pages-topics-and-subtopics

https://knowledge.hubspot.com/seo/create-topics-for-your-seo-strategy

You want to send a series of targeted emails to contacts who haven’t engaged with any of your previous emails in the last month. Which of the following would help you achieve this?

 

• Set up a contact-based workflow with an enrollment trigger based on email engagement criteria.
• Create a company-based workflow with a goal to increase overall website traffic.
• Use the “Send internal email notification” action to alert the marketing team about unengaged contacts.
• Manually create a static list of unengaged contacts and sending a one-time regular email.

 

Explanation

A contact-based workflow is designed to automate actions for individual contact records based on defined enrollment criteria. Email engagement properties can be used as enrollment triggers to identify contacts who have not interacted with marketing emails within a specific time period. Once enrolled, those contacts can receive a targeted series of follow-up emails through workflow actions. This supports re-engagement because the automation is based on contact behavior, not manual selection.

Why the other options are incorrect

Company-based workflow acts on company records, so it is not the correct workflow type for sending emails to individual contacts.

Send internal email notification alerts users inside the account but does not send a re-engagement email series to contacts.

Static list requires manual maintenance and supports a one-time send rather than automated behavior-based nurturing.

Source for verification

https://knowledge.hubspot.com/workflows/create-workflows

https://knowledge.hubspot.com/workflows/set-your-workflow-enrollment-triggers