GUI and Web Frameworks

This question tests understanding of MVC relationships. Options A, B, and C all describe genuine MVC concepts: A acknowledges the pattern introduces more classes due to separation, B correctly states views access data through models, and C accurately states application logic should not reside in UI methods. Option D claims Model-View separation minimizes interface changes' impact on the controller layer, which is misleading. Model-View separation primarily isolates business logic from presentation. The controller layer sits between them and handles input, but the principle specifically addresses decoupling Model from View, not interface-to-controller relationships.

In Java's AWT and Swing, the default layout manager for Frame and JFrame is BorderLayout. Other options like FlowLayout (default for Panel/Applet), GridLayout, and CardLayout must be explicitly set using the setLayout method.

TStaticText descends from TWinControl and has its own window handle, which allows it to have more control over its appearance and behavior. TLabel descends from TGraphicControl, NOT TWinControl, and does NOT have its own window handle - it's drawn directly on its parent's surface for better performance. The statement claims B says 'TLabel descends from TWinControl but does not have window handle' which is FALSE because TLabel doesn't descend from TWinControl at all. Therefore 'A True and B False' is correct.

ValidationSummary does not validate a specific input control itself, but instead displays a summary of errors from all page validators; hence, it lacks the ControlToValidate property. Other options validate individual inputs and require it.

In HP QTP/UFT, the "Expand All" option in the View menu recursively expands all steps and nodes in the Keyword View hierarchy. Other options like "Expand" or "Expand Rows" do not perform a full expansion of all levels.

In Pega PRPC, the NewDefaults rule type is where you specify the default harness for new work objects of a class. The harness defines the user interface structure and layout for work object forms. This setting determines which UI template is used when creating new instances.

In ASP.NET, configuration hierarchy applies settings from most specific to most general: root Web.config (3) → application-specific Web.config (1) → Machine.config (2). The root Web.config overrides application Web.config, which overrides Machine.config. This allows specific settings to take precedence over broader system-wide defaults.

The default value for background-repeat is 'repeat', which means the background image repeats both horizontally and vertically. Option D correctly describes this behavior. Options A (repeat-x) and B (repeat-y) repeat only in one direction, while option C (no-repeat) prevents repetition entirely.

An HTML Server control maps directly to standard HTML tags while remaining accessible on the server. However, Web Server controls can also render pure HTML based layouts (e.g., Literal, Repeater). Additionally, HTML Server controls require the 'runat=server' attribute, making the question somewhat subjective. But since HTML Server controls preserve HTML structure directly, the stored answer is acceptable.

In Flex/MXML development, the Application tag is the required root element that every MXML file must have. Other components like Box, Button, and Panel are child elements used within the Application tag.

Flex and ActionScript support creating custom components through inheritance and composition. This is a fundamental feature of the framework for building reusable UI elements.

Application is correct. In MXML (Flex framework), the tag is the root container required for compilation. It represents the main entry point of the application. Box, Button, and Panel are UI components but cannot serve as the root element - an MXML file must have Application as its top-level tag to compile.

Yes, developers can create custom components using native Web Components APIs (such as Custom Elements) or within modern frontend frameworks like React, Angular, and Vue to build reusable, encapsulated UI blocks. The other options are incorrect as custom component creation is a standard, widely supported feature.

The question asks which is NOT a valid way to express frameworks. Options A, B, and D all describe frameworks correctly - as abstractions with override points, as specialized libraries with APIs, and as templates for consistency. Option C is wrong because frameworks don't 'generate code' - they provide code that you extend or configure.

Option A is correct because when choosing a framework, the coding standard used in its development is typically the least relevant factor - frameworks are used as compiled binaries or libraries, not modified source code. What matters is the framework's architecture, modularity (B), development rules (C), and your team's ability to learn it (D). The internal coding conventions of framework developers don't affect how you use or integrate the framework.