Which of the following is an advantage of nesting dataclasses inside of lists?

Select one answer, then check.

• A list of dataclasses can represent complex data like a spreadsheet.
  Correct. The primer compares a list of dataclasses to "a table or spreadsheet," since each element shares the same attributes but holds distinct values.
• Nesting data structures makes code more complex.
  Not quite, this is a cost of nesting, not an advantage.
• Dataclasses are easier to nest inside of lists, compared to nesting lists inside of dataclasses.
  Not quite. The primer never compares the two directions of nesting; both are covered as equally normal combinations.
• Each dataclass instance inside of the list can have different attributes.
  Not quite. The primer says each element "has the same type of attributes," only the values differ between instances.

How does one index a specific element in a nested list?

Select one answer, then check.

• By chaining together two indexes, like spreadsheet[2][3].
  Correct. The primer says indexing a specific element in a nested list "requires chaining together two indexes," as in numbers_2d[1][2].
• By using a string to describe the correct index.
  Not quite. That describes dictionary-style lookup, not list indexing, which uses integer positions.
• With the in operator.
  Not quite. in tests membership (whether a value appears in the list); it does not retrieve an element by position.
• By partitioning the indexes and rotating through them correctly.
  Not quite. Nested-list indexing is just two ordinary indexes in a row, nothing is partitioned or rotated.

What is the main advantage of heavily nested data?

Select one answer, then check.

• Nesting allows us to represent truly complex data.
  Correct. The primer's closing section says "by doing so, we can represent truly complex data," at the cost of more nested control structures and attribute accesses.
• Nested dataclasses can be recursively polled for fractal outcomes.
  Not quite, this is not a real property the primer describes.
• We can iterate over dataclasses.
  Not quite. A dataclass itself is not something you loop over; you iterate over the lists that hold dataclass instances.
• There's a turducken in there somewhere.
  Not quite, this is a joke option, not a stated advantage.