A candidate answers "I'd use Kafka to decouple the services, Redis to cache the hot reads, and Cassandra for the write-heavy table." What's wrong with this answer even if every technology choice is defensible, and what would fix it?

It's a stack, not a design — naming Kafka, Redis and Cassandra says nothing about what each one solves that the alternative couldn't, or what it costs to add. A real trade-off has a fixed shape: we will X, it costs Y (with a number and a unit), we accept that because Z (grounded in a stated requirement), and we would revisit if W. Rewriting just the Kafka piece: "we'll decouple order creation from the confirmation email using a queue; it costs us eventual delivery instead of an immediate guarantee, and consumers now need to tolerate duplicates; we accept that because the customer only needs the order confirmed within their session, not the email sent; we'd revisit if consumer lag regularly grows past a few minutes." The stack-listing version and this version can describe the identical architecture — only one of them is a design.