1.WIP Limits provide a boundary/container in which the Scrum Team self-manages (Option B):
WIP Limits establish clear boundaries within which the Scrum Team can make decisions about how much work they take on. This framework allows the team to self-manage their workflow more effectively, as they must decide collectively how to stay within these limits while delivering value.
2.As part of self-managing, Scrum Teams figure out their own WIP Limits (Option D):
A fundamental principle of Scrum is self-management. The team collectively decides its WIP limits, adjusting them based on empirical evidence and ongoing learning about their capacity, flow, and delivery capabilities.
This decision-making process is a key aspect of the team's autonomy and self-management( Options A and C are incorrect because WIP limits do not inhibit self-management (A); instead, they enable it.
Additionally, a Scrum Master does not define WIP limits (C); the Scrum Team decides them.

Little's Law states:
*Average Cycle Time = Average Work in Progress (WIP) / Average Throughput.
Little's Law is used to understand and forecast the performance of a workflow system. It implies that if you know two of these three variables (Cycle Time, WIP, Throughput), you can calculate the third. The correct formula is Option A( Options B, C, and D do not correctly state Little's Law.