To answer this question, the user needs to have a basic understanding of buffering techniques used in database management systems.
Full buffering is a buffering technique in which the entire table is read into the buffer pool. This technique is appropriate for tables that are small and static, as well as tables that are accessed frequently and require fast access times.
Now, let's go through each option and explain why it is right or wrong:
A. Transaction Tables: Transaction tables are large and frequently updated, so full buffering is not appropriate for them. Instead, partial buffering or no buffering may be more appropriate.
B. Small Static tables: Small static tables are ideal for full buffering, as they are easy to load into memory and can be accessed quickly.
C. Internal Tables: Internal tables are usually small and accessed frequently, so full buffering may be appropriate for them.
D. Tables with generic Keys: Whether or not full buffering is appropriate for tables with generic keys depends on the size and usage patterns of the table.
Therefore, the answer is:
The Answer is: B. Small Static tables