HAC DevOps & Deployment 2 — Questions and Answers
Question 1: When deploying a HubSpot CMS theme update, what is the safest approach to avoid breaking a live site?
- Deploy directly to the live domain and monitor logs
- Use a staging environment or sandbox portal first (Correct answer)
- Update the theme files via FTP overwrite
- Disable the CDN before deploying
Correct answer: Use a staging environment or sandbox portal first
A sandbox or staging portal lets you validate theme changes without risking the production site.
Question 2: Which HubSpot CLI command syncs local project files to your HubSpot portal?
- hs upload (Correct answer)
- hs push
- hs deploy
- hs sync
Correct answer: hs upload
`hs upload` transfers local CMS assets (templates, modules, CSS) up to the connected HubSpot portal.
Question 3: A developer wants to watch local file changes and automatically sync them to HubSpot during development. Which CLI command enables this workflow?
- hs watch (Correct answer)
- hs live
- hs auto-sync
- hs fetch --watch
Correct answer: hs watch
`hs watch` monitors a local directory for changes and uploads them to the portal in real time.
Question 4: What file in a HubSpot CMS project defines the theme's metadata, labels, and screenshot preview?
- theme.json (Correct answer)
- hubspot.config.yml
- package.json
- fields.json
Correct answer: theme.json
The `theme.json` file contains theme name, version, author, preview image, and label configurations.
Question 5: In HubSpot's deployment model, what is the purpose of the `hubspot.config.yml` file?
- It defines page template layouts
- It stores portal ID and authentication tokens for CLI connections (Correct answer)
- It configures CDN caching rules
- It lists required npm dependencies for the project
Correct answer: It stores portal ID and authentication tokens for CLI connections
`hubspot.config.yml` maps portal IDs to their corresponding personal access keys used by the CLI.
Question 6: A HubSpot admin needs to revert a recently deployed CMS file to a previous version. Where can this be done?
- Design Manager > File History (Correct answer)
- Settings > Integrations > Version Control
- Developer File System > Revisions panel
- Content > Pages > Rollback
Correct answer: Design Manager > File History
Design Manager maintains a version history for CMS files and allows admins to restore previous versions.
Question 7: Which environment isolation strategy does HubSpot recommend for testing CRM customizations such as custom objects and workflows before production release?
- Using a cloned live portal with read-only API access
- Developer sandbox account (Correct answer)
- A separate HubSpot Starter account
- Deploying to production with feature flags disabled
Correct answer: Developer sandbox account
HubSpot's developer sandbox provides a full-featured isolated environment for testing CRM configurations without affecting production data.
HAC DevOps & Deployment 2
When deploying a HubSpot CMS theme update, what is the safest approach to avoid breaking a live site?