Yes/No field type stores true/false values?

Yes/No field type stores true/false values?

• A. Text values
• B. Date values
• C. Numeric values
• D. Boolean values (true/false)

Answer: (D)

A Yes/No field is meant to represent a binary choice, true or false. This directly aligns with a boolean data type, where true corresponds to Yes and false to No. Using a boolean keeps the data simple, consistent, and easy to query or reason about in logic and conditions. Behind the scenes, many systems store booleans as 1/0 or a true/false flag, even if the user interface displays Yes or No. Text values would allow arbitrary strings, which could be inconsistent (e.g., "yes," "Yes," "Y"), and wouldn’t enforce a binary constraint. Date values are for calendar dates, not binary decisions. Numeric values would store numbers, which can represent more than just a binary state and would complicate comparisons and validation.

A Yes/No field is meant to represent a binary choice, true or false. This directly aligns with a boolean data type, where true corresponds to Yes and false to No. Using a boolean keeps the data simple, consistent, and easy to query or reason about in logic and conditions. Behind the scenes, many systems store booleans as 1/0 or a true/false flag, even if the user interface displays Yes or No.

Text values would allow arbitrary strings, which could be inconsistent (e.g., "yes," "Yes," "Y"), and wouldn’t enforce a binary constraint. Date values are for calendar dates, not binary decisions. Numeric values would store numbers, which can represent more than just a binary state and would complicate comparisons and validation.