Computer File Systems

.apk (Android Package Kit) is the official file format for Android application distribution and installation. Similar to how .exe files work on Windows, .apk files contain the app's code, resources, assets, and manifest file. .jad files are for Java apps, .jar is a Java archive format, and .and is not a standard Android file extension.

Both the Scripts and Data folders contain Applications and Common sub-folders. The Scripts folder organizes test scripts into Applications (app-specific tests) and Common (shared/reusable scripts). Similarly, the Data folder organizes test data files into Applications and Common sub-folders for corresponding scripts. Reports has a different structure without these sub-folders.

The Object Repository Manager handles both Local Object Repositories (test-specific .tsr files) and Shared Object Repositories (reusable .tsr files across multiple tests). This dual capability supports different test object management strategies.

In Informatica's bad file (which contains rejected rows), the first column is the Row Indicator. This column shows why the row was rejected (e.g., D = deleted, I = insert, O = original, T = truncated). Options B and C incorrectly suggest column or file indicators exist.

For externally-described input files in IBM i, the F-spec format uses IF (Input file, Externally-described). The record length is defined in the external file description, not in the F-spec, so no length parameter is needed. Option C includes an unnecessary 41 byte parameter, and option D incorrectly uses F (fixed-length) instead of E (externally-described).

For externally-described input files in IBM i, the F-spec format uses IF (Input file, Externally-described). The record length is defined in the external file description, not in the F-spec, so no length parameter is needed. Option C includes an unnecessary 41 byte parameter, and option D incorrectly uses F (fixed-length) instead of E (externally-described).

Output queues (*OUTQ) are IBM i objects that store spooled files waiting to be printed on output devices like printers. *PRTF is a printer file definition, not a queue object. *SPLQ and *PRTQ are not valid IBM i object types for this purpose.

In RPG programming, /INCLUDE and /COPY directives have specific differences. The key distinction is that /INCLUDE files cannot contain embedded SQL statements (C is correct). This is a documented limitation in RPG compilers where SQL preprocessor cannot handle /INCLUDE directives. Options A, B, and D are incorrect - there are functional differences between the directives, both can be conditional, and /INCLUDE can be nested.

In RPG programming, /INCLUDE and /COPY directives have specific differences. The key distinction is that /INCLUDE files cannot contain embedded SQL statements (C is correct). This is a documented limitation in RPG compilers where SQL preprocessor cannot handle /INCLUDE directives. Options A, B, and D are incorrect - there are functional differences between the directives, both can be conditional, and /INCLUDE can be nested.

In RPG programming, /INCLUDE and /COPY directives have specific differences. The key distinction is that /INCLUDE files cannot contain embedded SQL statements (C is correct). This is a documented limitation in RPG compilers where SQL preprocessor cannot handle /INCLUDE directives. Options A, B, and D are incorrect - there are functional differences between the directives, both can be conditional, and /INCLUDE can be nested.

In RPG programming, /INCLUDE and /COPY directives have specific differences. The key distinction is that /INCLUDE files cannot contain embedded SQL statements (C is correct). This is a documented limitation in RPG compilers where SQL preprocessor cannot handle /INCLUDE directives. Options A, B, and D are incorrect - there are functional differences between the directives, both can be conditional, and /INCLUDE can be nested.

In RPG programming, /INCLUDE and /COPY directives have specific differences. The key distinction is that /INCLUDE files cannot contain embedded SQL statements (C is correct). This is a documented limitation in RPG compilers where SQL preprocessor cannot handle /INCLUDE directives. Options A, B, and D are incorrect - there are functional differences between the directives, both can be conditional, and /INCLUDE can be nested.

In RPG programming, /INCLUDE and /COPY directives have specific differences. The key distinction is that /INCLUDE files cannot contain embedded SQL statements (C is correct). This is a documented limitation in RPG compilers where SQL preprocessor cannot handle /INCLUDE directives. Options A, B, and D are incorrect - there are functional differences between the directives, both can be conditional, and /INCLUDE can be nested.

PINE is a text-based email client for Unix systems, not an FTP tool. FTP (File Transfer Protocol) uses different tools like ftp, sftp, or wget/curl for file transfers. PINE was specifically designed for reading and composing email.

NUL is a reserved device name in Windows and cannot be used for files or folders. Other reserved names include CON, PRN, AUX, and COM1-9. These names date back to MS-DOS and are reserved for backward compatibility with legacy device drivers. CON1 and AUX1 work fine because they're not exact matches to the reserved names.