platforms and products Online Quiz - 70

PARAM 8000 was India's first supercomputer, developed in 1991 by the Centre for Development of Advanced Computing (C-DAC). Aryabhata was India's first satellite, not supercomputer. Druva is a supercomputer but not the first.

Roadrunner, built by IBM for Los Alamos National Laboratory, was a supercomputer that first broke the 1 petaflop barrier in 2008. It held the title of world's fastest supercomputer before being surpassed, making it the second fastest at certain points in the TOP500 rankings timeline. Loadrunner is a performance testing tool, BlueGene/L and JUGENE are different IBM supercomputer architectures.

The Tianhe-1 ( Milky Way-1) supercomputer at the National Supercomputer Center in Tianjin achieved 1.75 petaflops in 2009, making it briefly the fastest in the world. Roadrunner reached 1.45 petaflops and Jaguar reached 1.75 petaflops at different times, so 1.75 petaflops is historically accurate for certain periods. The 890 and 974 tflops figures represent earlier generation supercomputers that were slower.

EKA ( PARAM padma-1), India's fastest supercomputer at Computational Research Laboratories in Pune, achieved approximately 117.9 teraflops at peak performance. This made it among the world's top supercomputers when launched. The 75 tflops figure likely refers to earlier PARAM systems, while 345 tflops is too high for India's fastest at the time this question was written.

Druva-ac (also known as Aaditya) at the Indian Institute of Tropical Meteorology, Pune, was India's second fastest supercomputer with approximately 47-50 teraflops performance. PARAM is the series name for multiple Indian supercomputers, not a specific one. BlueGene/L is an IBM architecture used worldwide. Arundhati is another Indian supercomputer but was typically ranked lower.

Dr. Vijay Bhatkar, founder of C-DAC, led the development of the PARAM series of supercomputers in the 1990s, establishing India as a supercomputing nation. Vijay Bhaskar is incorrect. Bhaskaracharya was an ancient Indian mathematician. Aryabhatta was also an ancient mathematician, not related to modern supercomputing.

After-job subroutines in DataStage execute regardless of job completion status - they run when the job finishes successfully, finishes with warnings, or aborts. This ensures cleanup and post-processing logic always executes.

In IBM DataStage, Parallel Containers are designed specifically for parallel jobs to encapsulate a reusable set of stages and links. They cannot be used in server jobs, which are legacy non-parallel jobs. Therefore, the statement is false.

Sparse lookup is used when reference data DOES change frequently - it performs a direct database lookup each time rather than caching, which is expensive but necessary for dynamic data. For stable/infrequently changing data, you would use a cached lookup (not sparse) for better performance.

A DataStage dataset descriptor file (.ds) contains the metadata, dataset header, creation details, a copy of the configuration file used to generate it, and paths to the actual data files, making 'All' the correct option.

The dsjob command with -run and -mode RESET is the correct syntax for resetting a Datastage job from outside the Director client. Option A is incomplete - it lacks the -run flag. Option C incorrectly uses SET instead of RESET. Option D uses SET which is for different purposes.

The cleanup resources option in Director stops the running job and releases allocated system resources. Reset is used after a job stops abnormally to prepare it for rerun. Clear log removes log entries but does not stop the job. Clear status file is not a standard Director option.

In IBM InfoSphere DataStage, the environment variable APT_COMPILEOPT is used to specify compiler options/flags when compiling parallel routines. APT_CONFIG specifies the configuration file path, and the others are incorrect or misspelled.

Notification Activity is the specific TIBCO activity designed for sending email notifications. Notify Activity is not the correct name for this component. SendMail Activity and Mail Activity are not standard TIBCO BW activity names.

Server routines in Datastage are developed using BASIC programming language, which is the proprietary scripting language for Datastage server routines. PERL, Shell Script, and C++ are not used for developing server routines within the Datastage environment.

Business Objects Universes contain three primary object types: Dimensions (descriptive attributes like names or categories), Measures (numeric aggregations like revenue or count), and Details (additional context objects like descriptions).

A Universe serves as a semantic layer that abstracts the underlying database schema. It translates technical table and column names into business terminology, making data accessible to non-technical users through familiar business concepts.

In SAP BusinessObjects, aggregate projection is a metadata feature defined on measure objects within a Universe. It dictates how the BusinessObjects reporting engine (like Web Intelligence) automatically aggregates measure values locally when dimensions are changed or removed from a report. Distractors like database features refer to physical database settings, not BO configuration.

Journal search in enterprise email systems is used to list all emails with specified details for compliance and auditing purposes. It does not list SMTP addresses or sent emails specifically, and 'All are above' is incorrect.