Computer File Systems

When expanding a filesystem using chfs, AIX requires space in /tmp for temporary files. If /tmp is 100% full, the chfs command will fail even if the target filesystem (/home) has space issues. This is a common AIX filesystem administration gotcha.

The mount point directory /fstest must exist before mounting. The error explicitly states a path component doesn't exist, which directly points to a missing directory. Out of space would return different errors (ENOSPC), and a logged-in user wouldn't block mounting.

Hibernate mapping files use the .hbm.xml extension by convention. The configuration file uses .cfg.xml. Options C and D are typos or non-existent formats.

Branching preserves the complete history of files and folders because when you create a branch, TFS maintains the entire version history up to that branch point. You can view the full historical context in the new branch. Merging combines changes but doesn't create the historical record, Annotate shows per-line history, and History is a view command.

Proper information handling requires: (i) sharing files only with authorized personnel using proper rights management (RMS ensures this), and (ii) declaring media before moving it in/out of office premises for audit purposes. Option iii is incorrect because confidential printed files must be disposed securely (shredding or secure bins), NOT in regular trash where they could be retrieved. The claimed answer B (I and ii only) correctly excludes the incorrect option iii.

File type validation ensures only allowed formats are uploaded. Size limits prevent storage exhaustion and DoS attacks. Virus scanning detects malware. File name validation is less critical since the real security concern is file content and type.

The find -mtime -1 command finds files modified less than 1 day ago (within the last 24 hours). The -mtime option uses days, where negative values mean less than and positive values mean more than. Option A is incorrect because -mtime uses days not hours. Option B uses the non-existent -mday option. Option C with +1 would find files modified MORE than 1 day ago.

The kernel uses the 'type' field in the file's inode to distinguish between ordinary files and device files. Each inode contains a type field that identifies whether the file is a regular file, directory, character device, block device, symbolic link, etc. Option A (temp field) and B (id field) don't exist for this purpose. Option D is wrong because the type is in the file's inode, not the directory's.

TIFF (Tagged Image File Format) is the standard format for document scanning in enterprise environments because it supports lossless compression, multi-page documents, and is widely compatible with archival systems. JPEG and PNG are more commonly used for photos and web graphics, not document archival.

Linux and UNIX filesystems are case-sensitive, meaning 'File.txt', 'file.txt', and 'FILE.TXT' are treated as three distinct files. This is a fundamental characteristic of Unix-like operating systems, inherited from their design philosophy.

In Informatica PowerCenter and similar ETL tools, parameter names for file handling follow the convention of starting with $ followed by the parameter name without spaces or special characters (except underscore at the end for some metadata parameters). $InputFile is the correct convention. $Input_File uses an underscore in the middle which is not standard for file parameter naming. $Input$File has a dollar sign in the middle which is invalid. $Input File contains a space which is not allowed in parameter names.

Error logs in Informatica can be written to different storage types. Relational error logs store error information in database tables for structured querying and analysis. File-based error logs write errors to flat files (text, CSV) for portability and external processing. XML (C) and Binary (D) are not standard error log types - error logs are typically written in readable formats for debugging.

Events are categorized into pre-defined events (built into the system) and user-defined events (created by developers). 'Event raise' and 'File watch' are not event types but operations or mechanisms, not categories.

The .msi (Microsoft Installer) extension is the standard file format for Windows Installer setup packages. These files contain installation information and are used by the Windows Installer service to install applications. .mst files are transform files used to modify installations, .zap is for Windows Installer patches, and .aas is not a standard Windows Installer extension.

Unix files do NOT have an end-of-file mark stored in the file itself. EOF is detected by the operating system when a read operation returns no more data (0 bytes read). Unlike some other systems that used special characters (like CP/M's Ctrl-Z), Unix simply tracks file size and detects EOF conditionally.