packaged enterprise solutions Online Quiz - 72

SAP Java Dispatcher uses the formula 50000+100*instance_number for the base port, with different offsets for different protocols. HTTP with SSL adds +1 to the base. For instance number 00, this would be port 50001. Options B (+3) and C (+4) represent other SAP protocols like P4 and telnet respectively, while option A (+2) is for HTTP without SSL.

The SAP AS Java Dispatcher telnet port is calculated as base (50000+100*instance_number) +8. Telnet administration access requires this specific offset. Options B (+3), C (+9), and D (+4) represent other SAP protocols: P4, HTTP SSL admin, and a different telnet variant respectively.

The SAP Central Services Instance Enqueue Server uses port format 32NN, where NN is the instance number. For instance 00, this is port 3200. The Enqueue Server handles lock table management for SAP applications. Option B reverses the digits, option C has NN at the start, and option D uses 2 instead of 3.

The HTTP Message Server port for SAP Central Services at instance number NN is 81NN. For instance 00, this is port 8100. The Message Server handles load balancing and client connection requests. Options A (8NN1), C (82NN), and D (8NN2) have incorrect digit placement.

SAP AS Java with Development Infrastructure (DI) type uses port 5NN15 for Design Time Repository (DTR) connections. DTR stores version-controlled development objects. For instance 00, this is port 50015. Options A (5NN10), B (51NN5), and C (515NN) have incorrect digit arrangements.

SAP reserves port range 63000-65535 as 'Will Not Be Used' for standard SAP applications. This range is kept free for non-SAP applications or custom use. Options A, B, and D all fall within SAP's standard port range (50000-59999) which SAP actively uses for various services.

In SAP environments using an Oracle database, the default listener port is often configured as 1527. This differs from the standard Oracle default of 1521 to avoid conflicts and follow SAP's specific installation standards.

HP Quality Center is a web-based test management tool used to manage requirements, plan and schedule tests, execute test suites, and track defects throughout the software development lifecycle.

HP Quality Center 9.2 was designed primarily to run on Microsoft Internet Explorer (IE) due to its heavy reliance on ActiveX controls, which were not natively supported by other browsers like Firefox or Safari.

HP Quality Center features 5 core modules: Requirements, Test Plan, Test Lab, Defects, and Dashboard, which together cover the entire application lifecycle management workflow.

Tests are linked to requirements within the Requirements module using the Test Coverage tab, allowing users to map specific test cases to individual requirements.

When a defect is valid but cannot be fixed immediately due to a gap in requirements or lack of code/resources, its status is set to 'Deferred' to be addressed in a future release.

Establishing a Traceability Matrix in Quality Center involves linking requirements to tests (Requirements-Test coverage) and analyzing how requirements cover the test plan (Test Plan-Requirement coverage) to ensure full alignment.

In Quality Center (now HP ALM), test cases are executed in the Test Lab module. The Test Lab is specifically designed for test execution, where test sets are created and run. Test Plan is for design, Defects for tracking issues, and Releases for managing release cycles.

A test plan tree can be created by defining test folders and tests manually in the Test Plan module. This hierarchical organization allows grouping tests by subject area, feature, or other criteria. Converting releases or saving automated tests are different workflows.

Requirement traceability is the mechanism used in Quality Center to relate requirements to one another, establishing parent-child or peer relationships to track dependencies.

In the Test Lab module of Quality Center, you use the 'Select Tests' button to open the test plan tree pane, allowing you to select and add test cases from the Test Plan to your execution test sets.

HP Quality Center 9.2 officially supports enterprise-grade databases, specifically Microsoft SQL Server and Oracle, for storing project repository data. Access, Sybase, and Paradox are not supported databases for this version.

The Quality Center Dashboard provides a high-level, executive view of the entire quality assurance and testing process across projects, aggregating metrics and reports into visual graphs.

A live analysis graph in the Test Plan module of HP Quality Center provides a visual overview illustrating all the tests within a specified folder, helping users analyze test coverage and status dynamically.