Computer Knowledge
Computer File Systems
1,249 Questions
Computer file systems dictate how data is stored, organized, and retrieved on storage devices. Important concepts include file allocation tables, access mechanisms, and various formats like sequential and video files. Candidates preparing for banking and government exams should practice these fundamentals thoroughly.
File access mechanismsVideo and password filesFile extensionsFile allocation tableSystem metadata
Computer File Systems Questions
-
zipplus
-
winrar
-
winzip
-
gzip
D
Correct answer
Explanation
Gzip is the standard compression utility for Unix/Linux systems. Unlike Windows-centric tools like WinRAR or WinZip, gzip is natively integrated into Unix environments and is the go-to tool for compressing and decompressing files in the Unix ecosystem.
-
file name : process name : timestamp : line : trace group : logged message
-
timestamp : file name : process name : line : trace group : logged message
-
timestamp : process name : file name : line : logged message : trace group
-
timestamp : process name : file name : line : trace group : logged message
C
Correct answer
Explanation
The standard Trace & Error log format begins with timestamp for chronological ordering, followed by process name for multi-process systems, then the file name and line number for precise source location, the trace group for categorization, and finally the actual logged message. Options A and B are incorrect because they don't start with timestamp. Option D incorrectly places trace group before the message.
-
file name : process name : timestamp : line : trace group : logged message
-
timestamp : file name : process name : line : trace group : logged message
-
timestamp : process name : file name : line : logged message : trace group
-
timestamp : process name : file name : line : trace group : logged message
B
Correct answer
Explanation
The TPF Trace & Error log format structures entries chronologically starting with timestamp, followed by file name, process name, line number, trace group, and finally the logged message. This standardized format allows for systematic parsing and analysis of diagnostic information. Option B correctly presents this sequence: timestamp:file name:process name:line:trace group:logged message.
-
File status indicator
-
It is stored in both disk and memory and tracts file status
-
There is one inode for each file on the system
-
All the above
-
None of the above
D
Correct answer
Explanation
An inode is a data structure that stores file metadata (permissions, size, timestamps, location). Every file has exactly one inode. Inodes exist both on disk (persistent storage) and in memory (when files are accessed). Therefore all descriptions A, B, and C are correct aspects of inodes.
-
uuencode coomand
-
attach command
-
compress command
-
Its not possilble to send attachment from unix
A
Correct answer
Explanation
The uuencode command converts binary files to ASCII format, allowing them to be sent as email attachments through the mailx utility. When piped to mailx, it properly formats the file as an attachment rather than inline text, which is the traditional Unix method for email attachments.
-
The +x right is meaningless for directory
-
To give permission to other users
-
To move into that directory
-
None of these
C
Correct answer
Explanation
The execute (+x) permission on a directory grants the ability to enter (cd into) that directory and access files within it by name. Without +x on a directory, even if you have read/write permissions on files inside, you cannot traverse the directory path to reach those files. It does not grant permissions to other users specifically.
B
Correct answer
Explanation
Unix does allow spaces in file and directory names, though they require special handling with quotes or escaping. The statement claims Unix cannot use spaces, which is false. Option B is correct because Unix filenames can contain spaces, unlike the statement suggests.
-
name.doc
-
name.tsr
-
name.qrs
-
name.trs
B
Correct answer
Explanation
In QTP (QuickTest Professional), object repository files use the .tsr extension. This is the Test Shared Repository file format. Option D (.trs) is similar but incorrect - .tsr is the standard extension. The question tests knowledge of QTP file conventions.
-
name.tsr
-
name.prs
-
name.qrs
-
name.trs
C
Correct answer
Explanation
Recovery Scenario files in QTP (QuickTest Professional) use the .qrs file extension. QTP is a functional testing automation tool, and Recovery Scenarios are used to handle unexpected errors or events during test execution. The .qrs extension specifically identifies these recovery configuration files. The other extensions (.tsr, .prs, .trs) are not associated with QTP Recovery Scenarios.
-
stock.sdf
-
stock.fdf
-
stock
-
stock.sds
A
Correct answer
Explanation
The .sdf (SQL Database File) extension is used for storing structured data, including stock information in handheld systems. Other extensions like .fdf, .sds, or no extension are not standard database file formats used for this purpose in the context.
A
Correct answer
Explanation
In Unix filesystems, directories ARE stored as special files on disk containing filename-to-inode mappings. They have file metadata (permissions, timestamps, ownership) just like regular files, with a special 'd'irectory bit set. This is a core Unix design principle.
-
File is opened for input and an attempt is made To write to it (or Logic error).
-
Mismatch in LRECL or BLOCKSIZE or RECFM between your COBOL pgn and the JCL ( or the dataset label).
-
Attempted to open a file that is already open.
-
File not found.
A
Correct answer
Explanation
File status 92 indicates that the file was opened for input and a write operation was attempted, which is a logic error. The first option correctly describes this condition, so the stored answer is right.
C
Correct answer
Explanation
File status code 35 in COBOL indicates 'File not found' when attempting to open a file that doesn't exist. Other common file status codes include 00 (success), 04 (wrong length record), 06 (record duplicate key), 13 (file not found), and 30 (permanent error). The specific code 35 is the standard COBOL file status for a non-existent file on OPEN. This is a fundamental concept in COBOL file handling.
-
Password failure
-
Resource not available
-
Logic error
-
No DD statement specified for this file
C
Correct answer
Explanation
In COBOL file status codes, 92 indicates a logic error occurred during file processing. This is a catch-all error code for problems that stem from programming logic rather than physical file issues or resource constraints.
-
An OPEN statement was attempted for a file in the open mode
-
A CLOSE statement was attempted for a file not in the open mode
-
An OPEN statement was attempted on a file previously closed with lock
-
The execution of a WRITE statement was attempted on a file not open in the I-O, output, or extend mode
A
Correct answer
Explanation
File status 41 indicates that an OPEN statement was attempted for a file that is already in the open mode. This is a logical error because a file cannot be opened again while it's already open - it must be closed first before being reopened.