GUI and Web Frameworks

When Android starts up, it scans for activities that have the CATEGORY_LAUNCHER intent filter in their manifest. These activities are the app's entry points. Android displays their icons and names on the home screen (launcher), allowing users to tap them to launch the application. This is correct behavior.

Android's native content providers include Browser (for bookmarks/history), MediaStore (for audio/video/images), and Contacts (for contact information). CallIndex is not a standard Android content provider. Option F correctly identifies these three native providers.

Content providers in Android must be declared within the application's manifest file using the provider tag so the system knows about their existence and permissions.

Both ContentUris.withAppendedId() and Uri.withAppendedPath() are static helper methods that can append an ID to a ContentProvider URI. ContentUris.withAppendedId() is specifically designed for content URIs and is the preferred approach.

Overlays in Android Maps API allow you to draw graphical layers on top of a MapView. You can create custom overlays by extending the Overlay class to display items like markers, shapes, routes, or other visual elements. The MyLocationOverlay is a specific built-in overlay for showing device position.

MyLocationOverlay is a built-in Android Maps overlay class that displays the user's current location and orientation on the map. It shows a compass indicator for direction and can animate to the current position. This is the correct native overlay for location display.

MapActivity is the base Activity class that provides access to a MapView. When you extend MapActivity, you can call getMapView() or access the map through layout inflation. The Activity hosts the map and provides the context in which the MapView operates. MapController is for controlling the map, Overlay is for drawing on it, but MapActivity provides the MapView itself.

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.

GeoPoint represents a geographical position on a map using integer values for latitude and longitude in microdegrees. It's the fundamental class used in Android Maps API to mark specific coordinates.

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.