Computer Memory and Storage

The -Xmx parameter sets the maximum heap size that the JVM can use. -Xms sets the initial heap size, while -Xmn configures the size of the young generation. There is no -Xmax parameter in standard JVM options.

Archived CVM feed files are stored in the /home/apps/cvm_live/cvm/data/archive/ directory. The other directories serve different purposes: failed/ holds rejected files, logs/ contains processing logs, and incoming/ is for new files awaiting processing.

In ITIL and service management frameworks, Capacity Management is a key IT infrastructure architecture or design-related process. While Process, Memory, File, and Device Management are low-level operating system functions, Capacity Management is a strategic, architectural framework planning process, making it the correct match here.

SAP systems require at least 2GB of swap memory to handle memory overflow situations and prevent system crashes during peak loads. Less than 2GB risks insufficient paging space. Setting swap to twice main memory is excessive and not a standard requirement.

Garbage Collection is .NET's automatic memory management system that reclaims memory from objects that are no longer in use. It runs periodically in the background, removing the need for manual memory management. Serialization is for object persistence, Assemblies are deployment units, and Overriding is an OOP concept.

Informatica Lookup transformation supports three cache types: Static cache (built once and reused), Dynamic cache (cache updated during session - used for lookups that change), and Shared cache (shared across multiple transformations). Since all three are valid types, 'All the above' is the correct answer. Static is default and fastest. Dynamic is slower but needed when lookup data changes during session. Shared allows multiple lookups to share the same cache to save memory.

Memory fragmentation occurs when free memory is split into many small, non-contiguous blocks (holes). As processes allocate and deallocate memory of varying sizes, the free space becomes fragmented. This creates a situation where there's sufficient total free memory but no single block large enough to satisfy a new allocation request. The 'large number of free holes' directly causes this problem.

A dirty bit indicates whether a page has been modified since being loaded from disk. If the dirty bit is 0 (clean), the page can be discarded without writing it back to the paging device, saving unnecessary I/O operations.

DASD stands for Direct Access Storage Device, a mainframe terminology for secondary storage devices (such as hard disks) where data can be accessed directly. The other options are incorrect or humorous fabrications.

In JProbe memory analysis, the Runtime Summary view provides high-level diagnostics via the Memory, Heap, and GC tabs. Distractors are incorrect because Thread profiling belongs to performance/thread analysis, and Data Tab is not a standard JProbe memory summary panel.

Windows Azure (now Microsoft Azure) provides three primary storage options: Blob storage for unstructured data, Table storage for NoSQL-like structured storage, and relational database via SQL Azure.

ARM processors support multiple addressing modes. Unlike some microcontrollers that are strictly byte-addressable, ARM can address bytes (8-bit), half-words (16-bit), and words (32-bit). The term 'Half-word or Full-word Addressable' refers to this ability to efficiently access different data sizes. ARM is byte-addressable at its core but supports aligned accesses to half-words and full-words. The claimed answer captures this multi-width addressing capability.

Paging allocates memory in fixed-size blocks, causing internal fragmentation when process size is not a multiple of page size. Segmentation uses variable-sized blocks matching logical units, leading to external fragmentation as free memory becomes scattered. Both statements accurately describe the key trade-offs between these memory management techniques.

Garbage Collection is correct because it is the automatic memory management technique in .NET that reclaims memory from objects that are no longer in use. Serialization (A) is for object persistence, Assemblies (C) are deployment units, and Overriding (D) is an object-oriented programming concept.