GUI and Web Frameworks

CSS3 Media Queries allow applying different styles based on device characteristics like screen size, orientation, and resolution. They are the core of responsive web design. Media queries do NOT handle business logic (A), master pages (B), or device capability detection (D) - those are server-side or JavaScript concerns.

ASP.NET Mobile Controls were deprecated by Microsoft and are NOT recommended for ASP.NET 4.0 development. Microsoft recommends using CSS media queries, responsive design, and standard web controls instead. The Mobile Controls namespace was designed for older devices and doesn't align with modern web standards.

When an activity doesn't appear in the SmartPrompt for a Utility shape, the most common cause is that the activity hasn't been designated as a Utility activity in its rule configuration. Activities must be specifically set up as Utility-type activities to appear in the Utility shape's activity selector. This is a configuration issue, not a class or initialization problem.

In Pega flows, activities create work objects using the Call Add method, which properly initializes the work object and adds it to the database. The Flow-New method and Utility shape serve different purposes, and activities can indeed start flows.

Documentum's core architecture consists of three main components: Content Server (the backend engine storing and managing content), Client Applications (interfaces like D2, Webtop for users), and WDK (Web Development Kit for building custom applications). All three are essential components of the Documentum platform.

Documentum Foundation Services (DFS) replaced the Web Services Framework starting with D5.3, providing a modern SOA-based services layer for building documentum applications.

Adaptive rendering refers to a web development technique where content and layout are dynamically adjusted based on the device and browser capabilities accessing the content. It specifically targets browser/device combinations rather than platform/browser combinations, as the focus is on the rendering engine and device characteristics (screen size, input method, etc.) rather than the underlying operating platform.

In QTP/UFT, actions can be made reusable through the Action Properties dialog. This setting allows the action to be called from other tests, making it modular and reusable across multiple test scripts.

The Watch tab in QTP/UFT allows users to monitor specific variables and object properties during execution. It is not limited to simple variables, nor does it automatically display every variable in the script (which is the role of the Variables/Locals tab).

FREE_SELECTIONS_INIT is the correct function module used for creating dynamic selection screens in SAP ABAP. This FM initializes and provides functionality for free selection screens where users can dynamically define selection criteria. The other options are not valid FMs for this purpose - they appear to be made-up names.

AWT stands for Abstract Window Toolkit, not Abstract Window Tools. AWT is Java's original platform-independent windowing, graphics, and user-interface toolkit. The word 'Toolkit' is the correct term, not 'Tools'. Option B correctly identifies this as false.

Substitute components are configured in the Substitute Components window, which is accessed by selecting a component in the Bill of Materials window and clicking the Substitutes button. The Bill Details tab and Revisions window do not support setting up substitutes.

The 'Build in WIP' item attribute determines whether an item can be manufactured in WIP as a discrete job or a repetitive assembly. The other options describe default subinventories or generic component definition attributes.

A Prompt is the MicroStrategy object that allows users to select specific elements or values during report execution, enabling interactive filtering. Filters restrict data but don't offer user selection, Consolidations group elements, and Metrics perform calculations.