When would you wrap layers in a Frame versus a Group?

WHAT THIS TESTS: This question checks if you know that Frames are bound-bearing parent containers with specific layout and prototype behaviors, while Groups are not described as supporting these same features. The interviewer wants to hear that you rely on Frames when you need clipping, scroll overflow, or constraint-based resizing, not just visual grouping.

A GOOD ANSWER COVERS: First, Frames have independent bounds, so you choose a Frame when content must extend beyond visible edges and you need to hide overflow with Clip content or enable vertical, horizontal, or bidirectional scrolling. Second, Constraints define how child objects behave when you resize the parent Frame, which matters for responsive layouts. Third, child objects nest beneath their parent Frame in the Layers panel, establishing clear hierarchy. Fourth, you choose a Group when you only need loose organization without bounds-based clipping, scroll overflow, or constraint logic, since the reference does not attribute these behaviors to Groups.

COMMON WRONG ANSWERS: A red flag is saying Groups and Frames both support Clip content or scroll overflow identically. Another mistake is claiming Constraints only apply to Frames without explaining that they govern how nested children resize. Some candidates also forget that a Frame must have content exceeding its bounds before scroll overflow works, or they suggest clipping is automatic rather than a checkbox in the Layout section.

LIKELY FOLLOW-UPS: An interviewer might ask how Constraints interact with Auto Layout, or when to use Fix position instead of scroll overflow. They may also ask how to temporarily ignore Constraints and Auto Layout resizing when dragging a Frame edge, which you do by holding Command on Mac or Control on Windows. Another follow-up is how preserving scroll position works when navigating between prototype frames.

ONE CONCRETE EXAMPLE: Imagine a mobile screen with a vertical list of cards. You would wrap the list in a Frame sized to the phone viewport, enable Clip content so cards disappear at the edges, and set scroll overflow to vertical. The cards inside would use Constraints to pin or stretch as the Frame resizes. You would not use a Group here because the reference does not describe Groups as supporting clipping or scroll overflow; the Group would simply bundle layers without boundary control.