Enterprise Software Fundamentals Quiz - 1

Clients interact with session beans to access application business logic. Session beans serve as the client-facing business interface. Entity beans (in EJB 2.x) are for persistence and not directly invoked by clients. Message-driven beans process asynchronous messages and are also not directly invoked by clients.

Session beans are categorized into exactly two types: stateless session beans (no conversational state maintained between calls, can be pooled) and stateful session beans (maintain client-specific state across method invocations). BMP (Bean-Managed Persistence) and CMP (Container-Managed Persistence) are persistence mechanisms for entity beans, not session bean types.

Stateless session beans are used when business operations don't require maintaining client-specific data between method calls. They're more efficient as they can be pooled and shared across clients. Option D correctly describes this scenario. Options A and B suggest scenarios where state might be needed (better for stateful beans). Option C is irrelevant.

Stateful session beans are specifically designed to maintain conversational state with a specific client across multiple method invocations. This makes them ideal for multi-step workflows like shopping carts or wizard-style processes. Option B correctly describes this use case. Option A describes stateless beans. Options C and D are misleading.

Entity beans are designed to represent business objects that need persistent storage - data that survives beyond application sessions. Option A correctly states this purpose. Entity beans map to database tables and handle CRUD operations. Options B, C, and D describe other concerns (communication, review, validation) not related to persistence.

EJB specifications, particularly for stateless session beans, state that these beans do not maintain conversational client state and should not contain custom instance variables. Instead, they are deployed as simple instances managed by the container's pool to execute stateless business methods.

Message-driven beans (MDBs) do not expose remote or local client interfaces. Instead, they act as asynchronous message listeners that the EJB container invokes when messages arrive at their designated queue or topic. Session and entity beans require interfaces for clients to invoke their business methods.

Entity beans in EJB 2.x support two persistence mechanisms: BMP (Bean-Managed Persistence) where the developer writes all database code, and CMP (Container-Managed Persistence) where the container handles persistence automatically. Options C and D correctly identify these. JMS and JAXM (A and B) are messaging technologies unrelated to entity bean persistence.

Algorithm efficiency is measured by counting the number of key operations (like comparisons, assignments, etc.). Counting microseconds is machine-dependent, making it unreliable for comparing algorithms across different platforms.

RSISET is the standard SAP transaction code used to create, change, and adjust InfoSets. When structural changes are made to an InfoSet, it must be adjusted and regenerated using this transaction to ensure system consistency.

Compounded InfoObjects require all parent compounding objects to be included in the InfoCube to maintain referential integrity. An InfoObject cannot be a compounding parent if it is defined as an attribute-only, and the cumulative key length of compounded objects cannot exceed 60 characters.

Once an InfoCube is compressed, its individual requests are aggregated, meaning request-based deletion is no longer possible. Similarly, if aggregates are not compressed, deleting a request from the InfoCube automatically propagates the deletion to the corresponding aggregate data.

In SAP BW, transaction code RSBBS is used to maintain sender-receiver assignments, enabling the Report-to-Report Interface (RRI) to navigate between queries or targets. It does not list users, reload InfoCubes, or create bulletin boards.

The Web Application Designer (WAD) is a flexible tool for creating web-based reporting interfaces. It supports multiple content types simultaneously: tabular query results for structured data, corporate logos for branding, graphical elements like bar charts for visual analysis, and hyperlinked navigation to related reports. This versatility allows creating comprehensive, professional dashboards that combine various visualization and navigation elements in a single browser-based interface.

In SAP BW, table ROIDOCPRMS stores the control parameters for data transfer from source systems. 'Max lines' actually sets the maximum number of records per data package, and 'Max Size' defines the memory size limit rather than direct record count, making only the first statement true.

Test comparator tools are used to compare actual outputs with expected outputs during test execution, making them part of test execution and logging support. They compare files, data, or screens. Option A (performance monitoring) is wrong - that's for load/performance tools. Option B (static testing) is wrong - comparators work on runtime outputs. Option D (management of testing tools) is wrong - comparators aren't meta-tools.