Software Development and Management

Metric Studio is the IBM Cognos component specifically designed for creating scorecards and monitoring KPIs over time. It provides the framework for defining metrics, setting thresholds, and visualizing performance trends. Cognos Planning is for budgeting and forecasting, TM1 is for multidimensional analysis, and Analysis Studio is for ad-hoc data exploration.

Event Studio (formerly Event Management Service) is designed for event lifecycle management - creating, managing, and monitoring event-based tasks and alerts. Report Studio is for reports, Query Studio for ad-hoc queries, Metric Studio for scorecards.

JDBC connection failures during server startup are logged at ERROR level because they prevent proper initialization of the application server. ERROR messages indicate problems that affect system functionality. CRITICAL is not a standard WebLogic logging level.

The -verbose:gc JVM flag causes the Java Virtual Machine to output detailed information about each garbage collection event, including timing statistics and memory reclaimed. This is a standard JVM feature independent of any WebLogic-specific tools or utilities - the GC information appears in the JVM's stdout/stderr, not WebLogic logs.

Production mode uses conservative default settings to protect database and system resources. A default connection pool size of 25 provides reasonable throughput for production workloads while preventing resource exhaustion - much lower than development defaults, which typically allow more aggressive pooling for testing convenience.

Continuous Integration is a software development practice where developers integrate code frequently, often daily. Each integration is verified by automated builds and tests to detect integration errors early. It is a practice, not a tool (A) or a lifecycle phase (C).

The main objectives of Continuous Integration are reducing integration problems and enabling faster delivery of software. By integrating frequently and automating builds/tests, teams catch bugs early and release more quickly. Both decreasing integration time and speeding up delivery are core goals.

Luntbuild, Gump, and CruiseControl are all CI/CD tools that automate build and test processes. Ant is a build tool (like Make) but not specifically a Continuous Integration tool - it's used by CI tools but isn't one itself. CI tools orchestrate builds, tests, and reporting.

CI automates application builds, testing (including white box testing), and deployment. Configuration management (C) is typically handled separately - while related, it's not a core CI automation target. CI focuses on the integration-build-test-deploy pipeline.

Package overloading in PL/SQL allows multiple subprograms with the same name to coexist if they differ in their parameter signatures. Only local subprograms or packaged subprograms can be overloaded - standalone procedures cannot use overloading (A is true). Overloading requires that subprograms differ in the number, type, or order of parameters - having the same parameter signature is not allowed (E is true). Option B is false because overloading based solely on return type is not permitted. Option C is false because overloading requires differences in parameters. Option D is false because subprograms with identical parameters cannot be overloaded.

PL/SQL packages cannot be nested, nor can they accept parameters directly (though their subprograms can). They are loaded into memory once, not on every invocation. The true statements are that package contents can be shared and information hiding is achieved by making constructs private.

Identifiers defined only in the package body (not in the package specification) are PRIVATE constructs, not public. They are invisible outside the package body and can only be used by other subprograms within the same package body. To make identifiers public and visible outside the package, they must be declared in the package specification. Therefore, the statement in the question is false, making option B the correct answer.

Private constructs defined in the package body are completely hidden from external access. This enforces information hiding and encapsulation, which is a major advantage of PL/SQL packages.

TIBCO Runtime Agent (TRA) is the foundational requirement for installing TIBCO BusinessWorks. TRA provides the runtime environment, Java_HOME configuration, and service infrastructure. TIBCO Administrator and Active Database Adapter are optional components installed separately for specific needs.