The study guide identifies C. The color palette is auto-generated based on the brand color to be WCAG compliant as the correct answer. Salesforce's current theming architecture reinforces this principle. Administrators define a primary brand color, and Salesforce generates complementary palette values for the interface. With SLDS 2 themes, Salesforce specifically generates accent, container-accent, and border-accent colors that meet applicable WCAG color-contrast requirements. Salesforce explicitly discourages overriding those generated accessible colors because manually selected replacements may no longer provide adequate contrast. This is important because a company brand color selected in isolation does not guarantee accessible text, controls, borders, or component states. A design system must derive related colors with sufficient perceptual separation and contrast across the interface.

Option A reverses the recommended practice: accessible generated values should generally not be overridden merely for visual preference. Option B is too restrictive; Salesforce branding supports considerably more customization than changing only a single brand color.

The UX principle is to preserve organizational identity while allowing the design system to generate accessible supporting values. This makes branding scalable across components without requiring designers to manually calculate every UI color combination.

Study Guide reference/topics: Themes and Branding, WCAG, accessible color palettes, brand colors, Declarative Design.

==================================