GUI and Web Frameworks

The Google Maps library is NOT part of the standard Android SDK - it's an optional add-on library that must be explicitly declared in AndroidManifest.xml using the tag. This declaration tells the system that the app requires the Google Maps API to function. Without this declaration, the app won't have access to Maps classes.

Workspace Profile utility is the SDIS feature that enables developers to capture plug-in selections in a profile, eliminating the need to repeatedly select the same options. The other options (Workspace setup utility, Profile management utility, Profile reminder utility) are descriptive but not the actual feature name.

Android projects can be created using various IDEs and editors. Eclipse with ADT plugin and IntelliJ IDEA with Android plugin provide integrated development experiences. However, any text editor can be used with Android's command-line tools, making all these options technically valid.

Content Provider is part of the Android Application Framework, enabling data sharing between applications. It provides a standardized interface for accessing and modifying data stored by other apps. Media Library, WebKit, and FreeType are middleware libraries, not framework components.

Activities are the essential building blocks of Android applications, representing single screens with a user interface. The Android system instantiates activities as needed to navigate through an app. Managers like Surface, Package, and Location are system services, not core application components.

AndroidManifest.xml is the correct answer because it's the most important file in an Android app, declaring all components (activities, services, receivers), permissions, app metadata, and other essential information the Android system needs to know before running the application. Without it, the system cannot launch or understand the app.

MVC (Model-View-Controller) is a design pattern separating application logic into three interconnected components. Model handles data and business logic. View handles display and user interface. Controller handles user input and updates Model/View. 'Viewer' and 'Control' are not the standard terminology.

ASP.NET MVC 2.0 introduced multiple significant features including asynchronous controllers for better scalability, enhanced model validation support, and Html.RenderAction for progressive rendering/partial views. All three listed features were indeed new in MVC 2.0, making 'All of the above' the correct choice.

MVC Framework explicitly does NOT use view state (that's a Web Forms feature), which is one of its advantages for cleaner markup and better performance. MVC does support TDD, provides separation of concerns, and supports RESTful URLs - these are all benefits/usages, not things it doesn't do.

ASP.NET MVC 2.0 provides greater control over application behavior through improved separation of concerns, enhanced routing, and better abstraction over WebForms. While it gives some control over client IDs and reduces view state issues, its primary benefit is behavioral control.

ASP.NET MVC 2.0 runs on top of the ASP.NET runtime, meaning it fully supports existing ASP.NET features like Master Pages, User Controls, Caching, and built-in Authentication/Authorization mechanisms.

Strongly-typed view scaffolding in MVC includes multiple content template options: Create, Edit, Delete, Details, and List. All of these are standard scaffold templates available when generating strongly-typed views.

In ASP.NET MVC 2.0, Html Helper methods are the primary mechanism for rendering views. These helper methods generate HTML markup programmatically and are the standard way views are rendered. Page Events are a WebForms concept, not MVC.