GUI and Web Frameworks

Visual Studio 2010 provides drag-and-drop data binding capabilities for UI platforms like WPF and Silverlight, as well as binding to multiple objects. However, WCF is a communication service framework and does not support drag-and-drop data binding directly to UI controls, making it the correct option.

Visual Studio 2010 Report Viewer controls maintain backward compatibility with RDL 2005 reports. The statement claiming you cannot process RDL 2005 reports is false, making option D the correct answer to what is 'not true.' VS 2010 supports multiple export formats (including Word), provides the Report Wizard, and includes enhanced data regions like Tablix and improved charts.

.NET 4.0's embedded interop types feature automatically handles COM reference counting through the runtime callable wrapper (RCW), eliminating the need for developers to manually manage reference counts. This was a significant improvement over pre-4.0 COM interop where developers had to be more conscious of COM lifecycle management.

In-process side-by-side execution primarily enables .NET 4.0 applications to coexist with earlier .NET versions within the same process. However, .NET 1.x, 2.x, and 3.x components cannot generally run side-by-side within the same process - they would run in different processes or require different AppDomains. Option B incorrectly suggests broad cross-version compatibility.

MEF (Managed Extensibility Framework) in .NET 4.0 is part of the System.ComponentModel.Composition namespace, not System.ComponentModel.CompositeApplication. Options A, B, and C correctly describe MEF's purpose and capabilities for building composable applications.

Canvas was already present in WPF before .NET 4.0. DataGrid, Calendar, and DatePicker were new controls added in .NET 4.0.

In web frameworks, pages typically inherit from a base page class that's part of the UI framework's hierarchy. The exact naming varies by framework, but 'web.ui.page' represents a common pattern where page is the base UI component.

ListView and DataPager were new data controls introduced in ASP.NET 3.5 to provide improved data presentation and paging capabilities. The other options existed in earlier versions.

.NET Framework 3.5 builds on the 2.0/3.0 runtime and supports versions 2.0, 3.0, and 3.5. .NET 1.1 was a separate, earlier runtime version not supported by the 3.5 framework.

The ASP.NET Merge Tool (aspnet_merge.exe) was introduced in .NET 3.5 to merge pre-compiled assemblies into a single assembly for deployment. ILDASM is for disassembly, while Remote Spy and Remote File Viewer are unrelated tools.

In a UML deployment diagram, a software component is represented by a rectangle with two small tabs protruding from its left side. A three-dimensional box represents a deployment node, whereas rounded rectangles depict states in state machine diagrams.

In Pega PRPC, standard local actions are predefined actions available on cases. AttachANote, AttacAURL (note: typo in original), and AttachAFile are all standard local actions that allow users to add notes, links, and files to a case. AttachADocument is not a standard local action in this context.

For node-scoped declarative pages, you must explicitly specify which access group(s) can load the declare page instance by entering them in the declare page rule form. This creates explicit scoping at the node level rather than relying on organization/division rulesets or the current user's access group, which apply at broader scopes.

The Newdefaults activity (with 's') is automatically executed when a work object is created, initializing properties with default values. This is a framework-provided activity that runs as part of the object creation process. 'Newdefault' is a common misspelling, and PyDefault is a different mechanism for property initialization.