1D0-720 · Question #105
What feature does SASS provide that standard CSS does not?
The correct answer is A. Variables. SASS introduces variables (e.g., $primary-color: #333;), allowing values to be defined once and reused throughout a stylesheet - something standard CSS historically lacked (though CSS custom properties came later, SASS variables predate them and offer compile-time features CSS…
Question
What feature does SASS provide that standard CSS does not?
Options
- AVariables
- BSelectors
- CColor names
- DPseudo-classes
How the community answered
(18 responses)- A89% (16)
- B6% (1)
- D6% (1)
Explanation
SASS introduces variables (e.g., $primary-color: #333;), allowing values to be defined once and reused throughout a stylesheet - something standard CSS historically lacked (though CSS custom properties came later, SASS variables predate them and offer compile-time features CSS variables don't). Options B, C, and D are all native CSS features: selectors (.class, #id, element) and pseudo-classes (:hover, :focus) have been part of CSS since its early versions, and named color values like red or cornflowerblue are built into the CSS spec. A useful memory tip: think of SASS as adding programming concepts to CSS - variables are a programming fundamental, so if the question asks what makes SASS more "programmatic," variables is your answer.
Topics
Community Discussion
9The answer is A, Variables. Standard CSS did not have variables when SASS was created, and that was one of the main reasons SASS became so popular. With SASS you can write something like $primary-color: #3366ff and reuse that value everywhere in your stylesheet. If you need to change it later, you change it in one place and it updates everywhere, instead of doing a find-and-replace across hundreds of lines. Options B, C, and D are all native CSS features that existed long before SASS came along, so those are easy eliminations.
A is correct. Standard CSS did not originally include a native variable system, so SASS introduced variables as a preprocessor feature, letting developers define a value once (like a brand color or font size) and reuse it across the entire stylesheet, which directly prevents the kind of inconsistency that opens the door to maintenance errors and style drift. Selectors, color names, and pseudo-classes all exist in plain CSS without any preprocessor.
Quincy nailed the core reasoning, though it is worth noting that CSS custom properties (variables) did eventually land in the spec around 2017, so the historical framing matters here, since SASS solved this problem well before native CSS caught up.
Honestly the word "variables" here feels a little dated now that CSS custom properties have been around for a while, so I get why some folks in our group second-guessed this, but for the purposes of the 1D0-720 exam scope the answer they are looking for is A. The other options (selectors, color names, pseudo-classes) all exist natively in standard CSS, so those eliminate themselves pretty fast.
Saw this exact question, picked A without blinking, variables are the whole reason SASS exists.
Variables are the obvious standout but I always double-check whether the question says "Sass variables" specifically or just "variables," because some questions try to slip in CSS custom properties as a distractor and those two behave differently at compile time.
SASS variables existed before CSS custom properties, so A still holds, even though CSS has them now.
A is right. SASS lets you define variables like $primary-color or $font-size so you can reuse values across your stylesheet without hunting down every hardcoded hex or pixel value when something changes, which is something plain CSS did not support until custom properties came along much later.
Carlos is right that SASS variables were a game-changer before CSS custom properties, but one important difference worth noting is that SASS variables are compiled away at build time and have no runtime value, while CSS custom properties (like --primary-color) can be changed dynamically with JavaScript or overridden in media queries, which makes them more powerful for theming today.