HAC System Architecture & Design 3 — Questions and Answers
Question 1: A HubSpot portal has overlapping workflow enrollment criteria causing contacts to enroll in multiple conflicting workflows. What is the best architectural fix?
- Add suppression lists or enrollment conditions to prevent overlap (Correct answer)
- Delete all workflows and rebuild from scratch
- Increase workflow re-enrollment settings
- Use a single mega-workflow for all scenarios
Correct answer: Add suppression lists or enrollment conditions to prevent overlap
Suppression lists and refined enrollment criteria prevent conflicting workflows from processing the same contact simultaneously.
Question 2: Which HubSpot feature allows administrators to control which users can view or edit specific records based on team hierarchy?
- HubSpot Teams with hierarchical permissions (Correct answer)
- Custom contact properties with access tags
- Workflow-based field locking
- Record cloning restrictions
Correct answer: HubSpot Teams with hierarchical permissions
HubSpot Teams support parent-child hierarchy so managers can see their team's records while reps see only their own.
Question 3: When integrating a third-party ERP with HubSpot, what is the safest strategy to avoid duplicate contact creation?
- Use email address as the unique identifier and enable deduplication in the integration (Correct answer)
- Rely on HubSpot's default auto-merge feature
- Import contacts manually each week
- Create a new property called 'ERP ID' and do not set deduplication rules
Correct answer: Use email address as the unique identifier and enable deduplication in the integration
Using a consistent unique identifier like email ensures the integration can match existing records rather than creating duplicates.
Question 4: A HubSpot administrator wants to ensure that marketing emails are only sent to contacts who have explicitly opted in. Which setting enforces this at the portal level?
- Enabling GDPR settings and requiring legal basis for marketing emails (Correct answer)
- Adding a required property called 'Consent' to all contact forms
- Creating a suppression list of non-opted-in contacts
- Using double opt-in on all forms
Correct answer: Enabling GDPR settings and requiring legal basis for marketing emails
HubSpot's GDPR settings enforce legal basis tracking and opt-in requirements at the portal level, restricting sends to consented contacts.
Question 5: What is the key difference between a HubSpot 'pipeline' and a HubSpot 'lifecycle stage' in terms of architectural purpose?
- Pipelines track deal/ticket progression while lifecycle stages track overall buyer journey status (Correct answer)
- Pipelines are for contacts only; lifecycle stages are for deals only
- Both track the same data but pipelines are visible to sales and lifecycle stages to marketing
- Lifecycle stages are customizable; pipelines have fixed stages
Correct answer: Pipelines track deal/ticket progression while lifecycle stages track overall buyer journey status
Pipelines manage the stages of a specific deal or ticket, while lifecycle stages represent where a contact is in the broader buyer journey.
Question 6: A company needs to store multiple addresses (billing, shipping, headquarters) for a single company record in HubSpot. What is the recommended approach?
- Create custom properties for each address type on the company object (Correct answer)
- Use the default address field and append all addresses in one text block
- Create separate company records for each address
- Use line item properties to store address data
Correct answer: Create custom properties for each address type on the company object
Custom properties allow you to create distinct fields for each address type without polluting the default address field or creating duplicate records.
Question 7: When using HubSpot's sandbox environment, which type of data is automatically synced from the production portal?
- CRM schema, custom properties, and pipeline configurations (Correct answer)
- Live contact records and deal data
- Email send history and engagement data
- Billing and subscription information
Correct answer: CRM schema, custom properties, and pipeline configurations
Sandboxes mirror the production portal's schema (properties, pipelines, object structure) but do not sync live contact or deal records.
A HubSpot portal has overlapping workflow enrollment criteria causing contacts to enroll in multiple conflicting workflows.
What is the best architectural fix?