Styling, Theming, and Configuration
Styling in Site Studio is token-driven. Style guides centralize colors, typography, spacing, and other design tokens. Components reference these tokens so a change in the style guide propagates consistently. Expect questions on the relationship between the style guide, base styles, and component styles.
Base styles apply globally (element defaults like body typography). Component styles are scoped to a component. Custom CSS can be added, but the exam rewards knowing when to use tokens versus raw CSS. Breakpoints define responsive behavior; styles can differ per breakpoint.
Configuration management is heavily tested. Site Studio settings, components, templates, and style guides are exported as config and moved between environments via Site Studio Sync. A frequent trap: assuming a style guide change is automatically live everywhere - it must be synced. Another: confusing theme (the Drupal theme layer providing templates and assets) with style guide (design tokens consumed by Site Studio).
Worked example
A brand changes its primary color. The correct path: update the color token in the style guide, so every component referencing that token updates - then sync config to other environments. If a component hard-coded the color as a static style, it would not update; that's the trap. Rule of thumb: reference tokens, don't hard-code, so global changes stay global.
Also know that permissions govern who can edit components/templates versus author content, and that configuration should be version-controlled and deployed, not hand-edited per environment.