Quiz for Bit fields

Q1: What is a bit field in C?

A. A way to allocate memory at the bit level inside a struct B. A method to define integer arrays C. A pointer to bits D. A special data type

Q2: Which keyword is used to declare a bit field in a struct?

A. unsigned B. bit C. field D. bitfield

Q3: How is a bit field declared in a struct?

A. int fieldName : number_of_bits; B. int fieldName = number_of_bits; C. int : number_of_bits fieldName; D. int fieldName;

Q4: Can bit fields be of type int only?

A. No, any integer type B. Yes, only int C. Only unsigned int D. Only char

Q5: What is the maximum number of bits allowed in a bit field?

A. Depends on the base type size B. Always 8 bits C. Always 16 bits D. No limit

Q6: Are bit fields portable across different compilers?

A. No, behavior may vary B. Yes, always C. Yes, with warnings D. Only on 64-bit systems

Q7: Can bit fields be used for flags?

A. Yes B. No C. Only with macros D. Only with enums

Q8: What happens if bit field width is zero?

A. Forces alignment to next boundary B. Declares an empty field C. Causes compilation error D. Defines 1 bit width

Q9: Can bit fields cross byte boundaries?

A. Yes, but depends on compiler B. No, never C. Only for unsigned D. Only for signed

Q10: How do you access bit fields?

A. Using normal struct member access B. Using bitwise operators C. Only via pointers D. Only via macros

Q11: Can you take the address of a bit field?

A. No B. Yes C. Only if unsigned D. Only if static

Q12: What is a common use case for bit fields?

A. Memory-efficient flags and control bits B. Floating point arithmetic C. String manipulation D. File handling

Q13: Can bit fields be declared as volatile?

A. Yes B. No C. Only if unsigned D. Only if const

Q14: Which type qualifier can be combined with bit fields?

A. const B. static C. extern D. register

Q15: What is a limitation of bit fields?

A. Cannot be arrays B. Cannot be in structs C. Cannot be signed D. Cannot be initialized

Q16: Can bit fields be initialized inside the struct declaration?

A. No B. Yes C. Only with macros D. Only in C++

Q17: What does the following mean: unsigned int flag:1;

A. flag uses 1 bit to store an unsigned integer B. flag is 1 byte unsigned int C. flag is an unsigned int pointer D. flag is an array of 1 bit

Q18: How is padding handled with bit fields?

A. Compiler dependent B. No padding C. Always 1 byte padding D. Always 4 byte padding

Q19: Are bit fields guaranteed to be atomic in access?

A. No B. Yes C. Only for 8 bits D. Only on 64-bit

Q20: Which C standard introduced bit fields?

A. C89 / ANSI C B. C99 C. C11 D. C17