I85PREP
⌘ K
HubSpot Reporting study materials
HubSpot Reporting study resources

HubSpot Reporting practice questions

One question at a time. Build your HubSpot Reporting understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1The Anatomy of Your CRM

In HubSpot CRM, which object is designed to store information about an individual person you interact with?

  1. Deal
  2. Contact Correct answer.
  3. Company
  4. Ticket

Explanation

Contacts are the standard CRM object for individual people. Companies store organization-level data, deals track sales opportunities, and tickets track support requests, so none of those is the record for a person.

Question 2The Anatomy of Your CRM

What is a property in the HubSpot CRM data model?

  1. A field on a record that holds a value Correct answer.
  2. A scheduled email sent to a contact owner automatically
  3. A saved view of records that match filter conditions
  4. A relationship linking two records together

Explanation

A property is a field attached to a CRM object that holds a value for each record. Filters, associations, and workflow emails use records or properties but are not themselves fields on the record.

Question 3The Anatomy of Your CRM

Which CRM element defines the ordered stages a deal moves through, such as Appointment Scheduled and Closed Won?

  1. A contact lifecycle stage
  2. A ticket pipeline
  3. A company property group
  4. A deal pipeline Correct answer.

Explanation

Deal pipelines define the ordered stages a deal moves through, such as Appointment Scheduled and Closed Won. Lifecycle stages describe a contact's journey, ticket pipelines handle support, and property groups only organize fields.

Question 4The Anatomy of Your CRM

An analyst wants a report of closed-won deal revenue grouped by the associated company's industry. Which CRM anatomy must the report use?

  1. Contact lifecycle stage, contact owner, and company association
  2. Deal pipeline, deal owner, and the deal-contact relationship
  3. Deal amount, deal stage, company industry, and deal-company association Correct answer.
  4. Ticket pipeline, ticket priority, and the ticket-contact relationship

Explanation

Revenue by company industry requires the deal Amount and Stage to identify closed-won revenue, the company Industry property for grouping, and the association that links each deal to its company. Other listed combinations use the wrong object or omit one of those required elements.

Question 5The Anatomy of Your CRM

Which statement correctly distinguishes a contact's lifecycle stage from a deal's pipeline stage?

  1. Lifecycle stage tracks a deal's revenue; deal stage tracks a contact's marketing status.
  2. Lifecycle stage tracks a contact's journey; deal stage tracks opportunity progress. Correct answer.
  3. Lifecycle stage and deal stage are the same field shown on different records.
  4. Lifecycle stage is set only by workflows; deal stage is set only by forms.

Explanation

Lifecycle stage is a contact-level property that reflects where a person sits in the marketing and sales journey. Deal stage is a separate deal-level property reflecting progress through a pipeline, and the two can move independently.

Question 6The Anatomy of Your CRM

A company wants to report on each deal's assigned sales rep. Which CRM element supplies this information for reporting?

  1. The company's industry property
  2. The contact's lifecycle stage
  3. The deal owner property Correct answer.
  4. The ticket's pipeline

Explanation

Owner properties identify the HubSpot user assigned to a record. The deal owner property therefore supplies the assigned sales rep for each deal, while industry, lifecycle stage, and pipeline describe other attributes.

Question 7The Anatomy of Your CRM

When should an admin create a custom object instead of adding another property to an existing object?

  1. When storing a record type beyond standard objects Correct answer.
  2. When changing the stages inside a deal pipeline
  3. When renaming a standard contact property in settings
  4. When building a dashboard that charts deal revenue

Explanation

Custom objects extend the CRM schema for entity types that the standard contacts, companies, deals, and tickets objects do not represent. Renaming properties, editing pipelines, and building dashboards are configuration or reporting tasks, not reasons to create a new object.

Question 8The Anatomy of Your CRM

An admin wants a deal property that limits users to a fixed list of sources such as Organic Search, Paid Search, and Referral. Which property field type fits best?

  1. Single-line text
  2. Dropdown select Correct answer.
  3. Number
  4. Date picker

Explanation

A dropdown select property limits users to a controlled list of options, which fits a fixed set of deal sources. Text fields allow arbitrary values, while number and date picker fields store different data types.

Question 9The Anatomy of Your CRM

Two contact records can both have the value "Acme" in a custom text property. What does this illustrate about CRM record identifiers?

  1. Record IDs are editable, while custom property values are read-only.
  2. Record IDs are stored only on deals, while custom properties are stored on contacts.
  3. Record IDs are unique and system-generated; custom property values can repeat. Correct answer.
  4. Record IDs change whenever a custom property is updated.

Explanation

Record IDs are system-generated and unique, so they remain reliable identifiers even when users enter duplicate values in custom properties. Custom property values can repeat unless validation or deduplication rules prevent it.

Question 10The Anatomy of Your CRM

A report must count only deals associated with a company through a specific relationship such as "Parent Company." What must the reporting setup account for?

  1. The association label linking deal and company Correct answer.
  2. The priority assigned to the ticket
  3. The contact's current lifecycle stage
  4. The order of stages in the deal pipeline

Explanation

Association labels describe the nature of a relationship between two records, such as a parent company link. A report that must count only a specific relationship type needs to filter on that association label, not on pipeline or lifecycle fields.

Question 11The Anatomy of Your CRM

Which standard HubSpot object is designed to track a customer support request through its resolution, including properties such as status and priority?

  1. Ticket Correct answer.
  2. Deal
  3. Contact
  4. Company

Explanation

Tickets are the standard object for support inquiries: each ticket carries its own properties such as status and priority, sits in a pipeline, and can be associated with contacts and companies. Deals, companies, and contacts model revenue, accounts, and people respectively.

Question 12The Anatomy of Your CRM

In the HubSpot CRM data model, how does an object differ from a record?

  1. An object defines a type of CRM item and its property schema, while a record is one specific instance of that object. Correct answer.
  2. An object is a single contact, while a record is the complete list of every contact in the portal.
  3. An object can only hold custom data created by an admin, while a record holds only the default standard data.
  4. An object is a filtered view that displays a subset of records, while a record is the full underlying database table that stores them.

Explanation

An object is the schema: it defines which properties and associations a category of CRM item has. A record is a single instance of that schema with its own record ID and its own property values, such as one specific contact.

Question 13The Anatomy of Your CRM

Which element gives a HubSpot record a permanent internal identifier that stays the same even when its property values are edited or its associations change?

  1. The record's name or title property
  2. The pipeline ID of the object
  3. The record ID Correct answer.
  4. The email address property

Explanation

The record ID is assigned when a record is created and is independent of any editable property, so renaming a record or changing its email leaves the identifier intact. That is why integrations and APIs rely on it rather than on names or addresses.

Question 14The Anatomy of Your CRM

Two contacts are associated to the same deal: one negotiates the pricing and the other signs the contract. Which CRM feature lets the team record these two distinct roles so reports and workflows can treat them differently?

  1. Association labels on the deal-to-contact association Correct answer.
  2. A contact property group named after each role
  3. A deal pipeline with an extra stage for each role
  4. A second deal record created for the signer

Explanation

Association labels describe the role that a specific associated record plays in the relationship, so a report or workflow can target only the signer or only the negotiator. The role belongs to the link between the two records, not to a stage, a layout grouping, or a duplicate deal.

Question 15The Anatomy of Your CRM

An admin is creating a custom deal property to hold the estimated implementation fee so that an analyst can sum it across deals in a report. Which property field type should be used?

  1. Number Correct answer.
  2. Multiple checkboxes
  3. File
  4. Single-line text

Explanation

Report calculations such as sum and average require a numeric field type, so a fee intended for aggregation should be a number or currency property. Text, checkbox, and file fields cannot be totaled in a report.

Question 16The Anatomy of Your CRM

A company sells two product lines with different sales processes: one follows a five-stage enterprise cycle and the other a three-stage self-serve cycle. What is the most appropriate CRM structure on the deal object?

  1. One pipeline whose stages combine all eight steps in sequence
  2. A single stage property where reps type the current step as free text
  3. A separate custom object created for each product line's deals
  4. Two separate pipelines, each with its own stages, on the same deal object Correct answer.

Explanation

Pipelines let one object hold multiple independent stage sets; each deal belongs to exactly one pipeline, and reports can filter or group by pipeline. This keeps stage progression accurate for each process instead of forcing every deal through steps it will never reach.

Question 17The Anatomy of Your CRM

Which contact property does HubSpot use as the primary identifier when detecting and merging duplicate contact records?

  1. Full name
  2. Phone number
  3. Lifecycle stage
  4. Email address Correct answer.

Explanation

HubSpot treats email address as the primary unique identifier for contacts and uses it when flagging and merging duplicates. Names and phone numbers are frequently shared, missing, or inconsistently formatted, so they cannot serve as the matching key.

Question 18The Anatomy of Your CRM

What is the purpose of a property group in HubSpot?

  1. It organizes related properties together on a record's layout so users can find them easily. Correct answer.
  2. It bundles records that share a common value into one list so they can be enrolled together in a workflow.
  3. It defines the ordered stages that a record passes through as it progresses.
  4. It restricts which users are allowed to view a defined set of properties.

Explanation

Property groups are a layout and organization device: they cluster related properties on record pages and in the property editor. They do not change who can see a property, how records are enrolled, or how stages work.

Question 19The Anatomy of Your CRM

An analyst wants a report showing the individual products, quantities, and discounted prices on each closed-won deal. Which part of the CRM anatomy supplies those line-level details?

  1. The deal's current pipeline stage
  2. The company record associated to the deal
  3. A multi-line text property on the deal that lists the products
  4. The line items object, associated to deals Correct answer.

Explanation

Line items are a separate object that stores the product, quantity, and price for each item on a deal, and they are associated to the deal so they can be reported individually or rolled up into deal amount. The other options hold process position, account data, or unstructured text rather than line-level product detail.

Question 20The Anatomy of Your CRM

An admin must ensure every company record carries a distinct external ERP account number and that HubSpot rejects a save when the value already exists on another company. Which property setting accomplishes this?

  1. Making the property read-only for all users
  2. Turning on the requirement for unique values on that property Correct answer.
  3. Adding the property to a property group
  4. Marking the property as the primary display property

Explanation

The unique-value setting enforces a constraint at the data layer, so a save fails when another record already holds the same value; this is the standard approach for external system identifiers. Read-only status, display settings, and groups affect editing or layout rather than duplication.

Question 21The Anatomy of Your CRM

An admin creates a custom object for warranty registrations. Which setting controls the value that identifies each registration in search results and association pickers?

  1. Unique value property
  2. Pipeline stage
  3. Primary display property Correct answer.
  4. Property group

Explanation

HubSpot uses the custom object's primary display property to label each record in search results, association pickers, and record headers. It is a display choice and does not by itself enforce uniqueness across records.

Question 22The Anatomy of Your CRM

A support team needs a ticket property that records the exact date and time a customer first replied, so reports can distinguish morning from afternoon replies. Which HubSpot property field type should the admin choose?

  1. Date and time Correct answer.
  2. Number
  3. Single-line text
  4. Date picker

Explanation

The date and time field type stores both a calendar date and a time of day, which is necessary when reporting on hour-level timing. A date picker stores only the date and would lose the time component.

Question 23The Anatomy of Your CRM

An admin wants a deal property that automatically calculates the number of days between the deal's create date and close date so analysts can report average sales cycle length. Which CRM property capability should be used?

  1. A pipeline stage property
  2. A calculation property Correct answer.
  3. A property group
  4. A unique value property

Explanation

Calculation properties derive values from other properties and can compute time between two date properties. That gives a reportable numeric value without requiring manual entry or workflows to copy dates.

Question 24The Anatomy of Your CRM

An admin must prevent users from saving a new deal record unless the Deal amount field contains a value. Which property configuration enforces this requirement?

  1. Making the property required Correct answer.
  2. Adding the property to a property group
  3. Setting the property as the primary display property
  4. Marking the property as unique

Explanation

A required property blocks record creation or saving when the field is empty, which enforces data completeness at the point of entry. This is separate from uniqueness, which only prevents duplicate values.

Question 25The Anatomy of Your CRM

A report counts deals grouped by a contact property. One deal is associated with three contacts, so the same deal contributes three rows and is counted three times. Which CRM anatomy concept explains this result?

  1. Lifecycle stage synchronization
  2. Property group inheritance
  3. Association cardinality fan-out Correct answer.
  4. Record ID deduplication

Explanation

When a report traverses a one-to-many association from deal to contacts, each associated contact can produce a separate result row for the same deal. Analysts must account for that cardinality, often by counting distinct deal IDs rather than rows.

Question 26Designing Compelling HubSpot Dashboards

A marketing manager wants a single HubSpot view that groups several saved reports so the team can monitor campaign performance at a glance. Which HubSpot feature is designed for this?

  1. A dashboard that contains multiple reports Correct answer.
  2. A property group that organizes contact fields
  3. A workflow that enrolls contacts from campaign lists
  4. A form that captures campaign landing page submissions

Explanation

A HubSpot dashboard is a collection of reports arranged together for quick monitoring. Workflows automate actions, property groups organize fields, and forms collect submissions, so none of those provides a multi-report monitoring view.

Question 27Designing Compelling HubSpot Dashboards

You created a custom HubSpot dashboard and want specific teammates to view it without editing its layout. Which sharing approach fits?

  1. Export the dashboard as a CSV and email it daily
  2. Make every teammate a super admin so they can open the dashboard without any sharing steps
  3. Add each teammate as an owner on every report in the dashboard
  4. Share the dashboard with those users or teams and assign view-only access Correct answer.

Explanation

Dashboard sharing lets you grant access to selected users or teams and choose a permission level. View-only access lets teammates see the dashboard without changing its layout or reports.

Question 28Designing Compelling HubSpot Dashboards

A revenue team wants one dashboard to show marketing email engagement and sales pipeline value. What is the most appropriate HubSpot dashboard design?

  1. Add relevant email and deal reports to one dashboard with compatible filters Correct answer.
  2. Convert email performance into deal properties so every report uses deals
  3. Add every report from the report library to one dashboard so nothing is missed
  4. Create two separate dashboards and ask users to switch between them

Explanation

A dashboard can display reports built on different objects, so email and deal reports can coexist in one view. Dashboard filters apply only where the underlying report data sources share the filtered property, so compatibility should guide the filter setup.

Question 29Designing Compelling HubSpot Dashboards

An analyst needs a HubSpot report that shows deal revenue alongside associated contact job titles. Which reporting tool should they use?

  1. A dashboard filter on contact job title
  2. The custom report builder with deals and contacts as data sources Correct answer.
  3. The single-object deal report builder, because it already includes contact fields
  4. A workflow report based on contact enrollment

Explanation

The custom report builder supports multiple data sources, so deal revenue and associated contact fields can appear in one report. A single-object deal report does not natively include contact properties as report columns.

Question 30Designing Compelling HubSpot Dashboards

A dashboard includes a deal report and a ticket report. You add a dashboard filter for deal pipeline. The ticket report does not change. What is the most likely reason?

  1. The ticket report must first be converted into a deal report
  2. The ticket report's data source lacks the deal pipeline property Correct answer.
  3. Only a super admin can apply dashboard filters to ticket reports
  4. Dashboard filters only apply to reports created in the last 30 days

Explanation

Dashboard filters are property-based and apply only to reports whose data sources include the filtered property. A deal pipeline filter therefore affects deal-based reports, while a ticket report lacks that property and remains unchanged.

Question 31Designing Compelling HubSpot Dashboards

A dashboard should show how monthly closed-won revenue has changed over the past 12 months. Which HubSpot report visualization is most suitable?

  1. A gauge showing only the current month's revenue
  2. A line chart with month on the x-axis and revenue on the y-axis Correct answer.
  3. A pie chart that shows each individual deal as its own slice so no deal is hidden
  4. A single table listing every deal record

Explanation

A line chart is designed to show change over time, making monthly revenue trends easy to compare. Pie charts show part-to-whole relationships, tables provide detail, and gauges show a single value rather than a trend.

Question 32Designing Compelling HubSpot Dashboards

A lifecycle marketing team wants a dashboard widget that shows how contacts progress from lead to customer and where the largest drop-off occurs. Which HubSpot report type fits best?

  1. A revenue attribution report
  2. A funnel report with lifecycle stages as the steps Correct answer.
  3. A custom report that lists every contact property for each contact record
  4. A dashboard filter on contact owner

Explanation

A funnel report visualizes stage-by-stage progression and makes drop-off between steps visible. Attribution reports assign credit, property listings show record detail, and filters narrow data rather than display conversion.

Question 33Designing Compelling HubSpot Dashboards

A sales director needs a weekly dashboard for executives. Which design choice best supports quick decision-making?

  1. Use a few high-level KPIs with one date range and prior-period comparisons Correct answer.
  2. Include every available sales report so executives can explore the underlying details themselves
  3. Rely on individual deal records so executives can review each opportunity
  4. Use different date ranges for each report to show more variety

Explanation

Executive dashboards work best when they focus on a small number of high-level indicators and use a consistent time frame with comparisons. Too much detail or inconsistent date ranges slows interpretation and can mislead comparisons.

Question 34Designing Compelling HubSpot Dashboards

Two sales pipelines have different stage counts. A dashboard must let leaders compare stage conversion fairly. Which design is best?

  1. Show only the final closed-won total for each pipeline
  2. Use a pie chart of deal count by pipeline
  3. Combine both pipelines into one funnel with all stages in sequence so leaders see one chart
  4. Build separate funnel reports per pipeline and align stage definitions before comparing Correct answer.

Explanation

Separate funnels preserve each pipeline's own stage process and avoid implying false drop-off between mismatched stages. Aligning stage definitions before comparison keeps conversion rates meaningful across pipelines.

Question 35Designing Compelling HubSpot Dashboards

Before sharing a new executive HubSpot dashboard, which validation step best protects against misleading conclusions?

  1. Set all report colors to the company palette
  2. Reconcile each report's totals against a trusted source and confirm filters and date ranges Correct answer.
  3. Add more reports until every property in the account is represented somewhere on the dashboard
  4. Give every viewer edit access so they can fix errors

Explanation

Validation should compare dashboard totals with trusted lists or reports and confirm that every report uses the intended filters and date range. Visual polish and broader access do not establish data accuracy, so reconciliation is the key safeguard.

Question 36Designing Compelling HubSpot Dashboards

A newly formed marketing team needs a starting HubSpot dashboard with prebuilt marketing performance reports rather than building every card from scratch. Where should they begin?

  1. Start from a template in the HubSpot dashboard library. Correct answer.
  2. Import a spreadsheet of report definitions into the dashboard during setup.
  3. Build a workflow that emails report snapshots to the team each week.
  4. Create a blank custom dashboard and add every report manually from the report library.

Explanation

The HubSpot dashboard library provides prebuilt dashboard templates for common use cases, including marketing performance. Starting from a template gives the team a structured set of report cards that can then be adjusted to fit their data and audience. Building every card manually is slower and does not provide a prebuilt starting point.

Question 37Designing Compelling HubSpot Dashboards

An operations lead wants the same HubSpot dashboard delivered as a scheduled snapshot to five executives every Monday morning. Which HubSpot capability should be used?

  1. A saved report added to the report library
  2. A contact-based list enrollment that sends a marketing email
  3. Dashboard sharing set to view-only for each executive
  4. A dashboard subscription with a recurring email schedule Correct answer.

Explanation

Dashboard subscriptions send a scheduled email version of a dashboard to selected recipients on a recurring basis. This fits the requirement for an automatic Monday snapshot without requiring executives to open HubSpot. Sharing and report library features control access and organization, not recurring delivery.

Question 38Designing Compelling HubSpot Dashboards

In HubSpot, what is the purpose of a dashboard-level filter such as a date range or pipeline selector?

  1. It permanently rewrites each report's saved filter settings.
  2. It changes only the dashboard title and description.
  3. It controls which HubSpot users can open the dashboard.
  4. It filters compatible report cards across the dashboard. Correct answer.

Explanation

A dashboard-level filter applies a shared selection, such as a date range or pipeline, to the report cards on that dashboard that support it. It lets viewers change the dashboard's view without editing each saved report individually. Reports that do not support the filter keep their own settings.

Question 39Designing Compelling HubSpot Dashboards

A viewer clicks a segment on a chart card in a HubSpot dashboard. What does drill-down typically allow in this context?

  1. It opens the detailed data behind that segment. Correct answer.
  2. It changes the dashboard's sharing permissions.
  3. It edits the saved report definition for every dashboard viewer.
  4. It converts the card into a workflow enrollment trigger.

Explanation

Drill-down lets a viewer move from an aggregated chart segment to the underlying report details so they can investigate what makes up the number. It is a navigation and analysis aid, not an edit or permission action. The saved report and dashboard configuration remain unchanged unless someone explicitly edits them.

Question 40Designing Compelling HubSpot Dashboards

A revenue dashboard mixes cards with different date ranges, unrelated color schemes, and no clear section order. Which redesign choice best improves executive readability?

  1. Apply one dashboard date filter and order related cards logically. Correct answer.
  2. Use a different color for every card to separate the metrics.
  3. Add more cards so every metric appears at once.
  4. Remove all card titles so the charts have more space.

Explanation

Executives need a dashboard that reads consistently: a shared date filter removes misleading time-window differences, and logical ordering helps viewers move from summary metrics to supporting detail. Limiting visual variation also reduces cognitive load. More cards or distinct colors per card add noise rather than clarity.

Question 41Designing Compelling HubSpot Dashboards

An analyst opens a saved report from a dashboard card, changes its filters, and saves the report. What is the effect on the dashboard?

  1. The dashboard-level filter permanently overrides the report.
  2. Only the analyst's personal dashboard view changes.
  3. The saved report changes, so the card updates for all viewers. Correct answer.
  4. HubSpot automatically creates a separate copy of the report for the dashboard.

Explanation

A dashboard card displays a saved report, so editing and saving that report changes what the card shows for everyone who can view it. Dashboard-level filters may adjust the displayed view, but they do not prevent a saved report edit from affecting all placements. Analysts should treat dashboard-originated report edits as account-wide changes.

Question 42Designing Compelling HubSpot Dashboards

Two sales managers view the same shared HubSpot dashboard but see different pipeline totals. Which explanation is most consistent with HubSpot reporting permissions?

  1. Each viewer sees only records their permissions allow. Correct answer.
  2. Dashboards cache data per viewer and must be refreshed manually.
  3. Dashboard filters are saved per user and cannot be shared.
  4. Shared dashboards always show account-wide totals to every viewer.

Explanation

HubSpot reporting respects the viewer's permissions, so a shared dashboard can show different totals when users have different access to records or objects. This is expected behavior and is important to explain when dashboard numbers are compared across teams. Sharing a dashboard does not necessarily grant access to all underlying records.

Question 43Designing Compelling HubSpot Dashboards

A dashboard has a date-range filter, but one card ignores it and keeps showing the report's own date range. What is the most likely cause?

  1. That report type or data source does not support the filter. Correct answer.
  2. The dashboard is shared with a team instead of individuals.
  3. The report was created by a super admin.
  4. The dashboard has too many cards for filters to apply.

Explanation

Dashboard filters only affect report cards that support the specific filter and its underlying data. Some report types or data sources do not accept a given dashboard filter, so their cards continue to use report-level settings. The fix is to confirm compatibility or use a report configuration that responds to the dashboard filter.

Question 44Designing Compelling HubSpot Dashboards

A dashboard card shows a single KPI such as total open deal amount, but it is displayed as a pie chart with one slice. Which HubSpot report display adjustment is most appropriate?

  1. Convert the card to a table with every deal record listed.
  2. Remove the card title and legend to save space.
  3. Switch the card to a single-number visualization. Correct answer.
  4. Add a second pie chart with the same metric.

Explanation

A single aggregate value is best communicated as a number or KPI-style visualization, not as a pie chart with one category. This makes the metric immediately readable and avoids implying a part-to-whole comparison that does not exist. Tables of individual records would add detail that the audience does not need for a summary KPI.

Question 45Designing Compelling HubSpot Dashboards

A company wants one dashboard to serve both sales development representatives and account executives, but each group needs different pipeline stages and date ranges. What is the best HubSpot dashboard design choice?

  1. Build separate dashboards for each audience and share each with the right team. Correct answer.
  2. Use only account-wide totals so neither group needs different stages.
  3. Give both teams edit access so each group can rearrange the dashboard daily.
  4. Put every report for both roles on one dashboard and let each viewer apply personal filters.

Explanation

When audiences need materially different filters, stages, or date ranges, separate dashboards keep each view focused and reduce the chance of misreading another team's metrics. Each dashboard can be shared with the appropriate team and maintained with the right default filters. One crowded dashboard or shared editing access creates confusion and inconsistent viewing experiences.

Question 46Designing Compelling HubSpot Dashboards

You already have a saved report in HubSpot's report library and want it to appear as a card on an existing custom dashboard. Which action adds it without rebuilding anything?

  1. Export the report as a CSV file and upload the file into the dashboard's settings.
  2. Open the report's actions menu in the report library and select Add to dashboard. Correct answer.
  3. Add the report's owner as a dashboard viewer so the card is generated automatically.
  4. Create a new blank dashboard and re-enter the report's filters and metrics by hand.

Explanation

Saved reports can be attached to any dashboard you are allowed to edit, and HubSpot reuses the saved report rather than copying its logic into the dashboard. This is why one report can sit on several dashboards at once. Because the card points at the saved report, later edits to that report are reflected wherever the card appears.

Question 47Designing Compelling HubSpot Dashboards

A dashboard has one headline metric, total open pipeline value, plus eight supporting breakdown cards. Which layout best reflects that hierarchy for viewers?

  1. Split the headline metric across eight cards, one card per supporting breakdown.
  2. Place the headline metric alone in a full-width card at the top of the dashboard. Correct answer.
  3. Place the headline card last, on the bottom row, so viewers reach it after the detail.
  4. Give every card the same size so no metric appears to matter more.

Explanation

Viewers scan a dashboard from the top down, so the single most important number should own the most prominent position and the largest surface area. Uniform sizing flattens the hierarchy and forces people to hunt for the number that matters. Keeping the supporting breakdowns grouped below the summary preserves detail without competing with it.

Question 48Designing Compelling HubSpot Dashboards

A sales manager wants a dashboard card that ranks ten account executives from highest to lowest close rate, with each rep's name readable. Which visualization should the card use?

  1. A single-number card showing the team-average close rate.
  2. A horizontal bar chart sorted by close rate. Correct answer.
  3. A line chart plotting close rate over the last ten quarters.
  4. A pie chart with one slice per account executive.

Explanation

A ranked comparison of named categories reads best as bars sorted by the measure, because bar length gives an immediate ordering and horizontal labels stay legible for long names. A line chart implies movement over time rather than a ranking across people. A pie with ten similar slices is hard to compare, and a team average erases the per-rep differences the manager asked to see.

Question 49Designing Compelling HubSpot Dashboards

A card groups closed-won revenue by a custom property that holds more than 150 distinct values, and viewers cannot read the resulting chart. Which design change best makes the card usable?

  1. Remove the group-by entirely and show only total closed-won revenue.
  2. Show all 150 values, shrink the labels, and switch the card to a pie chart.
  3. Group by the property's record ID instead, since IDs use fewer characters.
  4. Show the top values by revenue and group the rest as Other. Correct answer.

Explanation

A breakdown stops being readable once there are far more categories than a viewer can scan, so the standard fix is to rank categories and consolidate the long tail. A top-values-plus-Other card keeps the meaningful differences in view and lets viewers investigate the remainder separately. Reducing label size or changing chart type does not reduce the number of categories competing for attention.

Question 50Designing Compelling HubSpot Dashboards

A dashboard card's report is saved with a filter restricting it to deals in the Enterprise pipeline. A viewer then selects a deal owner on the dashboard's owner filter, and that owner has no Enterprise deals. What does the card display?

  1. Zero results, because the dashboard filter is combined with the report's saved filter. Correct answer.
  2. The owner's deals from every pipeline, because dashboard filters override report filters.
  3. The Enterprise pipeline total, because the owner filter is ignored on already-filtered reports.
  4. An error state, because a dashboard filter cannot be applied to a filtered report.

Explanation

Dashboard filters narrow the data a card shows; they do not replace the conditions stored in the underlying report. Both conditions are applied together, so the card returns only records that are in the Enterprise pipeline and owned by the selected person. When nothing satisfies both conditions the card shows no data rather than silently widening the scope.