Android Application Development Fundamentals

In Android, a ContentProvider is the standard component designed to securely share and expose an application's private data to other applications. Central Provider and Data Provider are incorrect terminology and do not exist in the Android SDK components.

The command-line tool sqlite3 is shipped with Android (or accessible via adb shell) and allows developers to inspect, query, and debug SQLite databases directly. The options dbdebug and Sqldebug are not official Android SDK database debugging tools.

In Android, openFileOutput() is the standard Context method used to open and write a private file associated with the application's internal storage. getSharedPreferences() and getPreferences() access preference files, while putBoolean() writes boolean preferences.

Android's SharedPreferences API provides a lightweight framework to save and retrieve persistent key-value pairs of primitive data types. Internal Storage and SQLite Databases are used for raw files and structured relational data, respectively, rather than simple primitive key-value pairs.

Canvas is the correct answer because it provides a direct drawing surface for applications that need frequent redraws. View Objects are for UI hierarchy, Sandboxes are for security isolation, and Paper is not a standard graphics component. Canvas allows immediate mode rendering where the application controls when and what gets drawn.

The statement is True. For applications that don't require intensive processing or high frame rates (like static forms or simple UIs), using a View is appropriate and more efficient. Views handle invalidation and redraws automatically when content changes, making them suitable for low-frequency updates.

OpenGL API is designed for high-performance 3D graphics rendering. It provides hardware-accelerated graphics capabilities for complex 3D scenes, not low-performance 2D or basic mapping graphics. The 'L' in OpenGL originally stood for 'Library' (now dropped), and it's the industry standard for 3D graphics programming.

In the Android framework, the MediaPlayer class is the primary API used to control the playback of audio/video files and streams. VideoPlayer, AudioPlayer, and SoundPlayer are not the standard Android SDK classes designed for comprehensive playback control of both media types.

To access camera hardware in Android, the application manifest must declare the android.permission.CAMERA permission. The permissions android.permission.VIDEO and android.permission.MEDIA do not exist or do not directly grant direct access to the camera hardware.

The statement is True. Android's sandbox model ensures each application runs in its own isolated process with unique user ID, enforcing inter-application separation. This sandbox, combined with permissions declared in the manifest, controls access to device resources like camera, location, or contacts.

The AndroidManifest.xml file is where applications declare permissions needed to access resources from other applications or device features. Default file, random file, and access file are not standard Android manifest components. The manifest is read at install time to grant requested permissions.

In Android, each application is assigned a unique Linux user ID at install time, which identifies the application (not an individual user). This UID-based isolation is part of Android's security model. Linux user IDs typically identify human users, while Android's UIDs identify applications.

keytool is the Java utility used to generate cryptographic keys and key pairs for Android application signing. openkey doesn't exist, zipalign is for APK optimization (not key generation), and jarsigner is for signing existing JAR/APK files with an already-generated key.

The statement is True. All Android APK files must be signed with a certificate held by the developer. This is a fundamental security requirement - the Android system will not install an unsigned APK. Debug builds use a debug certificate, while release builds use a developer's production certificate.

In Android, test applications can run in the same process as the application under test using the android:targetProcess attribute or by not specifying a separate process. This is useful for faster testing and direct access to application components, though running in a separate process provides better isolation.

Eclipse with ADT was the primary IDE for Android development before Android Studio, providing integrated testing capabilities. The Android Debug Bridge (adb) tool enables command-line testing, debugging, and device interaction. Ant build system includes targets for running tests and building test APKs. These are all valid approaches to Android testing.

Android test applications can verify functional correctness (business logic), Activity lifecycle behavior (onCreate, onResume, etc.), database CRUD operations, and UI behavior across different screen sizes and resolutions using instrumentation and test frameworks like Espresso or UI Automator. All listed areas are valid test targets.

Android test applications extend the standard Android Application class and include a test runner in their manifest. They have access to Android APIs, can declare their own components, and are APKs like any other Android app, with the addition of test-specific manifest entries and dependencies on the app under test.

The Device Administration API provides the DevicePolicyManager.wipeData() method which device admin apps can call to perform a factory reset of the device, wiping all user data and applications. This requires the device admin to have wipe permission granted by the user.

Android's Device Administration API supports policies including minimum password length, maximum inactivity timeout (after which the device locks), password quality requirements like alphanumeric content, and requesting/prompting the user to reset or set a new password. Thus, all listed policies are correct.