This portion holds the top level WPF elements like Windows, panels, controls, styles, etc.

It implements the end-user presentation features.

It provides a managed wrapper for MIL and implements the core services for WPF such as UI Element and visual from.

It holds basic elements to be reused outside the WPF environment like Dispatcher objects and Dependency objects.

Both (2) and (3)

This portion holds the top level WPF elements like Windows, panels, controls, styles, etc.

It implements the end-user presentation features.

It provides a managed wrapper for MIL and implements the core services for WPF such as UI Element and visual from.

It holds basic elements to be reused outside the WPF environment like Dispatcher objects and Dependency objects.

Both (1) and (2)

This portion holds the top level WPF elements like Windows, panels, controls, styles, etc.

It implements the end-user presentation features.

It provides a managed wrapper for MIL and implements the core services for WPF such as UI Element and visual from.

It holds basic elements to be reused outside the WPF environment like Dispatcher objects and Dependency objects.

None of the above

It provides low development and maintenance cost.

Multiple design tools can be used to implement and share XAML mark-up.

It provides, clear separation between the UI and logic.

It provides easier understanding of Silverlight.

All of the above

It is a set of tools, documentation, samples and templates for the web developers.

It is a plug-in for browsers to support Silverlight enabled applications.

Silverlight SDK is not really mandatory to develop Silverlight applications.

Both (1) and (2)

Both (1) and (3)

This layer comes under the category of unmanaged layer in WPF architecture.

It is used for imaging support in WPF applications like image processing.

It holds the top level WPF elements.

This layer is used to provide interface directly with DirectX and provide basic support for 2D and 3D surface.

Both (1) and (2)

This file is the loader of Silverlight Application.

In this file, we can declare your shared/global resources, styles and templates.

The Application_Exit event can occur in App.xaml.cs file.

All of the above

Both (1) and (2)

Silverlight provides a simple user interface for developers.

It provides high Compatibility.

Silverlight offers cross-domain support for applications.

All of the above

Both (1) and (2)

WPF is based on XAML.

WPF is a Graphical subsystem which provides visually stunning user interfaces in Windows based applications.

WPF can be used for data manipulation.

All of the above

Both (1) and (3)

Silverlight is a subset of WPF.

WPF is used to develop enhanced graphics applications for desktop platform.

WPF supports 3D graphics.

WPF uses cross platform .Net runtimes.

None of the above

milCore.dll layer comes under the category of managed layer in WPF architecture.

This layer is used to provide interface directly with DirectX.

It is used for imaging support in WPF applications like image processing.

It holds the top level WPF elements.

All of the above

It supports manage code.

.NET runtime is mandatory to run the Silverlight 2 applications.

Silverlight 2 is only based on JavaScript and XAML.

Silverlight 2 uses Dynamic Language Runtime (DLR) for compilation and execution of the dynamic scripting languages.

Both (2) and (3)

It holds all other UI elements in a .xaml file.

It is used as a layout panel.

All UI elements in a .xaml control must be placed within a layout panel in User control.

All of the above

Both (1) and (3)

WinForms does not provide better binding capabilities.

WPF provides better UI customization and graphics.

WPF provides clear separation between the UI and logic.

All of the above

Both (1) and (3)

Resource

Site of origin

Application code

Content

None of the above

In this navigation, it changes the content and location URL of a browser itself.

In this navigation, it can be identified with a pack URI.

Safe navigation is based on browser and application level.

Safe navigation is not possible in WPF security.

(1), (2) and (3) are correct

The default xaml file page.xaml is created on creating the new Silverlight project.

The default content of page.xaml file does not have User control.

The compiled assembly file of Silverlight application has the .xap extension.

The compiled assembly file of Silverlight application does not have any .xap extension.

Both (2) and (4)

It describes the Windows Workflow Foundation content.

WPF XAML is used for Silverlight applications.

WPF XAML also have XPS XAML which defines an XML representation of electronic documents.

All of the above

Both (1) and (3)

Silverlight applications are delivered to browsers in a text-based mark-up language.

XAML is a compiled application.

Silverlight supports video, audio and animations.

Silverlight allows web developers to handle events from web pages.

None of the above

It is a compressed output file.

In .xap file, the AppManifest.xaml is responsible for compilation of output assembly of the Silverlight project.

The .xap file is used to declaratively specify the user interface for Silverlight or WPF applications.

All of the above

Both (1) and (2)