Module 3 Quiz :Android App Components – Intents, Activities, and Broadcast Receivers (Android App Development Specialization) Answers 2025
Question 1 — What an Intent Is
✔️ A message that describes an action to perform or an event that has occurred
❌ An event handler for system broadcasts
❌ A background-running component
❌ A message that provides an interactive screen
Question 2 — Benefits of Intents
✔️ An intent is the “glue” that helps integrate Android apps
❌ Defines the smallest unit of execution
✔️ Simplifies development via reusable black-box components
❌ Manages secure access to structured data (ContentProvider does this)
Question 3 — Intent is a Passive Data Structure
❌ Cannot be used concurrently
❌ Contains only static getters/setters
✔️ Consists of fields + accessors/mutators (data-only structure)
❌ Only contains public fields
Question 4 — Intent Enables Late Runtime Binding
❌ Components started by intents are slow
✔️ Components can be discovered/used at runtime
❌ Discovered at compile-time
❌ Must run in separate processes
Question 5 — Benefits of Runtime Discovery
✔️ Enables systematic reuse of components
❌ Enhances security by disallowing trojans
❌ Ensures compile-time knowledge of components
✔️ Enables loosely coupled, dynamically extendable components
Question 6 — Elements of an Intent
✔️ Data
✔️ Flags
❌ URL
❌ Service
❌ Name
❌ Stack
✔️ Action
✔️ Extras
Question 7 — Characteristics of Implicit Intents
✔️ The name must not be specified
❌ The data must not be specified (data is optional, not forbidden)
❌ The category must not be specified (optional)
❌ The action must not be specified (action is usually required)
Question 8 — Implicit vs Explicit Intents
❌ Implicit = tightly coupled
✔️ Implicit delivered only if it matches an intent filter
✔️ Implicit often used for other apps’ components
✔️ Explicit delivered without consulting filters
❌ Explicit used for other apps’ components (that’s implicit)
✔️ Explicit important when starting/binding services
Question 9 — Elements That Must Match for Implicit Intent Filtering
❌ Flags
❌ Extras
✔️ Data
❌ Name
✔️ Category
✔️ Action
Question 10 — What IntentService Does
✔️ Expresses requests as intents & passes them between threads/processes
❌ Provides user-interactive screens
✔️ Handles asynchronous requests on demand
❌ Responds to broadcast announcements
📌 SUMMARY TABLE
| Q | Correct Answers (✔️) |
|---|---|
| 1 | Message describing action/event |
| 2 | Glue for apps, simplifies reuse |
| 3 | Fields + getters/setters only |
| 4 | Runtime discovery of components |
| 5 | Systematic reuse, loosely coupled |
| 6 | Data, Flags, Action, Extras |
| 7 | Name must not be specified |
| 8 | Implicit→filter match, cross-app; Explicit→no filter, services |
| 9 | Data, Category, Action |
| 10 | Asynchronous service, intent-based worker |