Quiz for File operations fclose

Q1: What is the purpose of the fclose() function?

A. To close an opened file and release resources B. To open a file C. To read data from a file D. To write data to a file

Q2: What happens if fclose() is not called after fopen()?

A. Resources may not be freed properly, leading to leaks B. File is automatically closed immediately C. Program will crash D. Data is always lost

Q3: What is the return type of fclose()?

A. int B. void C. FILE * D. char

Q4: What does fclose() return on successful file close?

A. 0 B. 1 C. -1 D. NULL

Q5: What does fclose() return if an error occurs?

A. EOF B. 0 C. 1 D. NULL

Q6: Is it safe to call fclose() on a NULL file pointer?

A. No, causes undefined behavior B. Yes, safely ignored C. Depends on compiler D. It closes all files

Q7: Can fclose() flush the buffer before closing a file?

A. Yes, it flushes buffered data B. No, you must call fflush() manually C. Only for read mode files D. Only for write mode files

Q8: Which header file declares fclose()?

A. <stdio.h> B. <stdlib.h> C. <string.h> D. <fcntl.h>

Q9: What happens if fclose() fails?

A. Returns EOF and sets errno B. Returns 0 silently C. Program aborts D. File remains open

Q10: Can fclose() be used to close files opened with fopen() in any mode?

A. Yes, for all fopen() modes B. Only read mode C. Only write mode D. Only append mode

Q11: Is fclose() a blocking call?

A. Generally yes, it waits for operation completion B. No, it is asynchronous C. Depends on OS D. It never blocks

Q12: Why is it important to close files promptly?

A. To free system resources and flush data B. To delete the file C. To prevent file creation D. To compress file

Q13: Can multiple fclose() calls be made on the same FILE pointer?

A. No, second call causes undefined behavior B. Yes, safe to do C. It closes multiple files D. It resets file pointer

Q14: How does fclose() handle errors during flushing?

A. Returns EOF indicating error B. Ignores errors C. Throws exception D. Closes file anyway

Q15: Can fclose() close files opened with low-level system calls?

A. No, only FILE * streams B. Yes, all file descriptors C. Depends on OS D. Only on Windows

Q16: Which function should be called before fclose() to flush buffers?

A. fflush() B. fopen() C. fread() D. fwrite()

Q17: What happens if program terminates without fclose()?

A. Buffered data may be lost B. File auto-closed and flushed C. File content unchanged D. File deleted

Q18: Is fclose() required to close stdin, stdout, stderr?

A. Usually no, system handles them B. Yes, always C. No, they never close D. They close automatically only in Linux

Q19: What is a common error when forgetting fclose()?

A. Resource leak and data loss B. Syntax error C. Compiler error D. File creation error