Internet and Web

Web 2.0 applications rely on user participation and network effects, meaning their utility and database of content grow and improve as the user base expands. They do not require scheduled sequential usage, are focused on user-generated content rather than static delivery, and represent a paradigm shift in web utilization rather than a simple software version upgrade.

Quality Center is accessed through a web browser and can be deployed over either the public Internet or a corporate intranet, depending on organizational security requirements. Option D correctly captures both deployment models. Options A, B, and C are individually incomplete.

HTML (HyperText Markup Language) is the standard markup language for creating web pages. It defines the structure and content of web documents using tags and elements, forming the foundation of the World Wide Web alongside CSS and JavaScript.

HTML forms provide input areas (text boxes, checkboxes, radio buttons, dropdowns, etc.) that allow users to enter and submit data to a web server. Forms are the primary mechanism for user interaction on the web, enabling everything from search boxes to checkout processes.

In portal architecture (specifically BEA/Oracle WebLogic Portal), a 'desktop' is the top-level container that defines a collection of books, pages, and portlets - essentially defining the service collection for a user. Books organize pages, pages contain portlets, and portlets are the actual service components. Option A is correct.

Quality Center 9.2 was an HP testing tool from the early 2000s. At that time, enterprise web applications primarily supported Internet Explorer. This is historical knowledge about legacy HP software ecosystem.

Adding web servers increases system availability (redundancy means if one fails, others continue serving), performance (load distribution across more servers), and reliability (redundancy reduces single points of failure). It does not inherently improve extensibility (ability to add features), maintainability (ease of modification), or manageability (ease of administration) - these would require architectural or process changes beyond just adding hardware.

The Sales user details page specifically displays a user's access configurations, including associated Sales Access Profiles and permissions. The Visibility page shows territory associations, not access information.

The GET method sends form input data through the URL query string, visible in the browser address bar. POST sends data in the HTTP request body and doesn't expose parameters in the URL. Therefore, GET is the method that sends input via URL.

JavaScript has three built-in popup boxes: Alert (displays a message), Confirm (asks for OK/Cancel confirmation), and Prompt (requests user input). Radio buttons are form input elements, not popup boxes.

In a GET request, the query string (the key=value pairs after the ? in the URL) is logged by the web server in access logs. Hidden tags are in the HTML body and not sent separately. Headers are logged but are server metadata, not request content. Cookies are sent in headers.

Flex breaks free of the traditional web's link-and-page metaphor by enabling single-page applications with dynamic content without full page refreshes. It does NOT have slow page refreshes (that's traditional web) or progressively loading content (that's progressive enhancement). Option A correctly describes Flex's architectural advantage.

In a multitiered application architecture, the browser runs on the client side and handles user interface presentation. This is known as the presentation tier or first tier. The other tiers (application logic tier and data tier) typically run on servers.

The Requestor page holds session information including access roles, RuleSet list, and HTTP parameters. Process pages track work objects, Thread pages hold execution context, and User Pages is not a standard clipboard page.

All HTTP headers (Host, Cookie, Referrer) are user-controlled and can be manipulated by attackers. Every header must be validated before use to prevent injection attacks, cache poisoning, or authentication bypass.