DevOps & Deployment Flashcards

When deploying a HubSpot CMS theme update, what is the safest approach to avoid breaking a live site?

Answer: Use a staging environment or sandbox portal first

A sandbox or staging portal lets you validate theme changes without risking the production site.

Which HubSpot CLI command syncs local project files to your HubSpot portal?

Answer: hs upload

`hs upload` transfers local CMS assets (templates, modules, CSS) up to the connected HubSpot portal.

A developer wants to watch local file changes and automatically sync them to HubSpot during development. Which CLI command enables this workflow?

Answer: hs watch

`hs watch` monitors a local directory for changes and uploads them to the portal in real time.

What file in a HubSpot CMS project defines the theme's metadata, labels, and screenshot preview?

Answer: theme.json

The `theme.json` file contains theme name, version, author, preview image, and label configurations.

In HubSpot's deployment model, what is the purpose of the `hubspot.config.yml` file?

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.

A HubSpot admin needs to revert a recently deployed CMS file to a previous version. Where can this be done?

Answer: Design Manager > File History

Design Manager maintains a version history for CMS files and allows admins to restore previous versions.

Which environment isolation strategy does HubSpot recommend for testing CRM customizations such as custom objects and workflows before production release?

Answer: Developer sandbox account

HubSpot's developer sandbox provides a full-featured isolated environment for testing CRM configurations without affecting production data.