Computer File Systems

In Informatica PowerCenter, folders can be copied both within the same repository and from one repository to another. Within a repository, you can create copies of folders for versioning or organizational purposes. Across repositories, you can copy folders for migration between development, testing, and production environments. The 'All the above' option correctly captures both scenarios.

Informatica PowerCenter allows creating header and footer rows in target flat files. This can be configured through session properties and the target flat file definition, enabling you to output header rows at the beginning and footer rows at the end of the file.

In Sybase, the physical storage file used to store database data is called a 'device.' A device is the actual operating system file or disk partition allocated to Sybase for data storage. The other options are incorrect: 'Datafile' is not standard Sybase terminology, 'Data Object' refers to logical structures, and 'Material' is not a Sybase storage term.

Multiple document uploads are supported in SharePoint document libraries but not in regular lists. Document libraries have built-in support for uploading multiple files simultaneously through the 'Upload Multiple Documents' option. Lists store structured data and don't have this bulk upload capability.

File type restrictions in SharePoint are configured through Central Administration under Operations > Blocked File Types. This global setting allows administrators to block specific file extensions (like .exe or .bat) from being uploaded anywhere in the farm. Option D is incorrect because Site Settings don't control this farm-level feature.

Test results can be stored in multiple formats, including simple flat files (like CSV or plain text) for basic reporting, and XML files for structured, hierarchical data that can be parsed and transformed easily. Both formats are commonly used depending on complexity and integration needs. XML provides better structure for detailed results, while flat files offer simplicity for basic logging and requirements.

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.