GUI and Web Frameworks

Pega alerts and their threshold configurations are traditionally managed within the prconfig.xml file. The other options are incorrect: prlogging.xml controls logging configurations, prweb.xml handles web deployment descriptors, and System Settings rules are not the standard location for these configuration parameters.

Activities (Rule-Obj-Activity) contain complex logic and code that should not be delegated to business users. Decision tables, decision trees, and map values are designed for business user delegation as they provide visual, rule-based interfaces without code.

To pass parameters to a ListView in an Activity, you use a Property-Set step BEFORE calling Obj-List-View to place values onto the parameter page. The Obj-List-View method then reads from this parameter page. You don't pass parameters directly in the Obj-List-View method call, and ListView rules DO accept parameters.

Summary View rules in PEGA can generate graphical reports. List View rules display tabular data and do not create graphs. The Obj-Graph method is not the correct approach for Summary View-based graphing. Summary View is the mechanism for creating report visualizations and graphs.

Properties with the px prefix are system-maintained and read-only. Pega prevents modifying them using standard methods like Property-Set. Developers must use the specialized Property-Set-Special method to force-write values to these system properties, making other options incorrect.

Properties on the primary page can be accessed using dot notation (.myProperty) or by explicitly prefixing the page name as Primary.myProperty or primary.myProperty. The keyword Primary is case-insensitive, but local variables use the local prefix, and case-sensitive property naming conventions must be matched.

The primary page of an activity does not always need to be defined on the Pages & Classes tab - it can be set programmatically within the activity itself or inherited. The absolute constraint 'must always' makes this statement false.

When the same data is served to desktop and mobile with only CSS changes, the best MVC approach is to use the same controllers and views but switch Razor layouts dynamically. This avoids code duplication while allowing device-specific styling through different layout files. Option A creates unnecessary duplication, option D duplicates views unnecessarily, and option C is not a viable solution.

When multiple MVC areas have different HomeController classes, ambiguity is resolved in the RegisterRoutes method in Global.asax.cs. This is where you configure route constraints and namespaces to specify which HomeController should handle requests. Options A and D refer to specific controller methods, and option B references a view file, not routing logic.

In MVC3, the _ViewStart.cshtml file is used to specify which layout file to render. To associate a different layout for mobile devices, you would add code in _ViewStart.cshtml to check the request browser and conditionally set a different layout file. Options A and B are configuration files not used for view logic, and option C is a layout file itself, not the place to assign layouts.

The MVC framework is NOT built on top of ASP.NET framework - it's an alternative pattern built directly on the ASP.NET core runtime, alongside traditional Web Forms. ASP.NET MVC and ASP.NET Web Forms are both built on ASP.NET, but neither is built on the other. The statement 'built on top of ASP.NET framework' is false.

In MVC applications, it is NOT mandatory that different areas share the same controllers. Each area can have its own set of controllers with the same names without conflict, thanks to area-based routing and namespace separation. Areas are designed specifically to allow modular, independent controller sets.

In ASP.NET MVC, mobile area registration is handled by the MobileAreaRegistration class in the App_Start folder. This class inherits from AreaRegistration and is specifically designed to register mobile-specific areas. The HomeController (C) handles routing logic within an area, while ViewStart (B) manages view layouts and RazorLayout (A) is a layout file - none of these specify the area registration itself.

To answer this question, the user needs to be familiar with the concept of building blocks in software engineering.

All of the options (A, B, C, and D) describe generic building blocks in software engineering.

A. A building block is a package of functionality defined to meet the business needs. This statement is true because building blocks are designed to provide specific functionality that meets the requirements of a particular business or application.

B. A building block has published interfaces to access the functionality. This statement is also true because building blocks typically have well-defined interfaces that allow other components to interact with them.

C. A building block may be assembled from other building blocks. This statement is true because building blocks can be combined and nested to create more complex systems.

D. A building block may have multiple implementations. This statement is also true because building blocks can be implemented in different ways to meet different requirements or to take advantage of different technologies.

Therefore, the correct answer is: E) All of the above.