Computer File Systems

The INVALID_FILEHANDLE exception is raised by UTL_FILE procedures like FCLOSE and GET_LINE when they receive an invalid or uninitialized file handle. Conversely, the IS_OPEN function evaluates whether a handle is open and returns a boolean value instead of raising this exception, making the combination 1,2 correct.

INVALID_MAXLINE_SIZE is a valid UTL_FILE exception raised when the MAX_LINESIZE parameter in FOPEN or FOPEN_NCHAR exceeds implementation limits. Other valid exceptions include INVALID_PATH, INVALID_MODE, INVALID_FILEHANDLE, and WRITE_ERROR, but INVALID_OFFSET, VALUE_ERROR, and ACCESS_DENIED are not standard UTL_FILE exceptions.

UTL_FILE can read files on Windows systems, but only if the Oracle database server is running on Windows and the directory is properly configured in the DIRECTORY object and utl_file_dir parameter. The question likely tests whether you understand UTL_FILE operates server-side, not client-side, so it depends on the server OS, not the client environment.

SFT outbox retention period is set to 30 days as a standard configuration. This balances the need for audit trails with storage management - keeping files long enough for troubleshooting but not indefinitely. The other options (10, 15, 40) are not standard SFT retention values.

For binary mode file transmission via SFT (Secure File Transfer), you must disable translation (&TXLATE=NO) and specify the data type as binary (&TDATTYP=BINARY). Translation converts data between character sets (e.g., EBCDIC to ASCII), which would corrupt binary files. The other combinations either enable translation when binary is needed or specify TEXT type incorrectly.

Secure File Transfer (SFT) protocols and automated scripts typically restrict spaces in filenames. Spaces cause parsing errors, unexpected truncation, or command execution failures in script arguments. Lower case characters, numbers, and semicolons are generally allowed or handled more safely, making spaces the primary prohibited character here.

Perl programs need execute permission to run directly. The common permission scheme is 755 (rwxr-xr-x): owner can read/write/execute, group/others can read/execute. 777 gives write permission to everyone which is a security risk. 666 is read/write for all with no execute permission - not executable. 766 is unusual and gives write to group/others.

In Genesys applications, the config folder conventionally contains configuration files including properties files that define system behavior, database connections, and environment settings. The xmlstore folder stores XML templates, com contains Java packages, and sites typically holds site-specific configurations.

Browse mode is designed for read-only access to files, allowing users to view content without making modifications. Edit and save operations are restricted in this mode to prevent accidental changes.

chmod 644 sets permissions as: owner gets read (4) + write (2) = 6, group gets read (4) = 4, others get read (4) = 4. This results in read/write for owner and read-only for everyone else. Execute permission would require adding 1 to the octal value.

The gunzip command is used to decompress gzip files. Applying the -f or --force option forces decompression and overwrites any existing uncompressed files with the same name without prompting, whereas the other options incorrectly suggest that this command performs file compression.

ls -ltr *.zip directly lists files ending in .zip. ls -ltr | grep "zip$" lists all files, then filters for lines ending in 'zip'. Both achieve the same result for .zip files - the shell glob matches the pattern, and the regex anchors to the end.

POST is designed for larger form submissions because it sends data in the request body without size limitations imposed by URLs. GET has length restrictions due to URL limits. Option A is wrong because GET isn't suitable for large data. Option C is incorrect because POST is specifically suitable. Option D is unnecessary - POST handles this directly.

The 'a' mode in fopen() opens a file for writing only, positions the pointer at the end, and creates the file if it doesn't exist. 'w' truncates the file, not append. 'w+' allows both read and write but truncates. 'a+' allows both reading and writing without truncating, starting at the end. Therefore 'a' matches the description exactly.

allow_url_fopen is the php.ini directive that enables PHP to open remote files using functions like fopen() with URLs. allow_remote_files is not a valid PHP directive. Option A is the correct configuration setting. Option B doesn't exist. Option C is incorrect because 'allow_remote_files' is not a real setting.