Option B is correct because DISTSTYLE ALL means the entire table is copied to every node, but within each node, the data is stored on a single slice. Redshift slices are determined by the number of cores per node; for dc2.large nodes, there are 2 slices per node. However, with DISTSTYLE ALL, each node stores a full copy of the table, but the table is not distributed across slices; it is replicated to each node, and queries may not parallelize across slices efficiently.
Actually, with DISTSTYLE ALL, the table is replicated to all nodes, but within each node, the data is stored on a single slice (the leader node assigns the table to one slice per node). So queries that scan the entire table may only use one slice per node, leading to underutilization. Option A is wrong because the sort key affects data ordering, not slice utilization.
Option C is wrong because WLM queues affect concurrency, not slice usage. Option D is wrong because the query is not using a single node but multiple nodes, but only one slice per node.