Architecture & System Design Flashcards
7 cards from real HCT practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Architecture & System Design flashcards as text
When designing a HubSpot portal for a B2B company with multiple business units, which architecture best prevents data cross-contamination between units?
Answer: Create separate Business Units with distinct branding and user permissions
Business Units in HubSpot allow one portal to serve multiple brands with separate assets, users, and reporting without data leakage.
A client wants to sync ERP order data to HubSpot deals in near real-time. Which integration pattern minimizes API rate limit exposure?
Answer: Use webhooks from the ERP to push changes to a middleware queue that batches HubSpot API calls
A webhook-driven middleware queue decouples the ERP from HubSpot, enabling batching and retry logic that respects HubSpot's rate limits.
Which HubSpot object relationship type should be used when a single Contact can be associated with multiple Companies and vice versa?
Answer: Many-to-many association using the native Associations API
HubSpot's Associations API natively supports many-to-many relationships between Contacts and Companies with association labels.
When should a HubSpot trainer recommend using Custom Objects instead of standard CRM objects?
Answer: When a client needs to store data that has no logical fit within Contacts, Companies, Deals, or Tickets
Custom Objects are appropriate when the data entity (e.g., Subscriptions, Vehicles) cannot be accurately represented by any existing standard CRM object.
A trainer is evaluating a client's workflow architecture and finds 47 active contact-based workflows firing on the same enrollment trigger. What is the primary risk?
Answer: Conflicting actions across workflows can create race conditions and unpredictable contact property states
Multiple concurrent workflows acting on the same contact properties can overwrite each other's changes depending on execution order, producing inconsistent data.
Which approach correctly handles a scenario where a HubSpot form submission should create a deal only when the contact does NOT already have an open deal in a specific pipeline?
Answer: Use a form submission workflow with an 'if/then' branch checking deal association count in that pipeline
An if/then branch inside a workflow can check the associated deal count or stage before conditionally creating a new deal.
When architecting HubSpot's data model for a SaaS company tracking product usage, where should recurring subscription MRR data best reside?
Answer: In a Custom Object called 'Subscription' associated to the Company
A Subscription custom object keeps recurring billing data normalized and associated to the correct Company without polluting Deal pipeline semantics.