Build fluency in the vocabulary of Android Activity lifecycle.
0 / 5 completed
1 / 5
A teammate explains that the Android system calls a well-defined sequence of methods, onCreate, onStart, onResume, onPause, onStop, onDestroy, on an app's Activity as the user navigates to it, backgrounds it, or the system reclaims its memory, and the app must save and restore its state at the right points in that sequence. What is being described?
The Android Activity lifecycle is exactly what is described here. A DNS zone transfer is an unrelated concept about replicating name server records. Understanding the Activity lifecycle is exactly why it comes up so often in real engineering discussions of this kind of problem.
2 / 5
During a design review, the team adopts proper Activity lifecycle handling, specifically to gain a concrete benefit. Which capability does this provide?
Proper lifecycle handling here provides an app that survives being backgrounded or reclaimed without losing user data. Assuming the Activity simply stays alive indefinitely is the alternative this avoids. This behavior is exactly why lifecycle handling is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a system relies on assuming an Activity simply stays alive with all of its in-memory state intact for as long as the user has the app installed, instead of handling the Activity lifecycle properly. What does this represent?
This is a missed lifecycle-handling-opportunity, since saving and restoring state at the correct callbacks would prevent data loss when the system reclaims the Activity. A cache eviction policy is an unrelated concept about discarded cache entries. This pattern is exactly the kind of gap a reviewer flags once the tradeoffs are understood.
4 / 5
An incident report shows a user lost unsaved form input because the app assumed its Activity would simply stay alive in the background, and the system silently destroyed and later recreated the Activity to reclaim memory, discarding the in-memory state. What practice would prevent this?
Saving critical state in onSaveInstanceState and restoring it in onCreate or onRestoreInstanceState, so a system-initiated destroy and recreate doesn't lose user data. Continuing the prior approach regardless of the risk it has already caused is exactly what led to the incident described here. This fix is the standard remedy once the root cause is confirmed.
5 / 5
During a PR review, a teammate asks why the team handles the Activity lifecycle carefully instead of assuming the Activity simply stays alive for as long as the app is installed. What is the reasoning?
Respecting the Activity lifecycle trades the extra work of saving and restoring state at the right callbacks for an app that survives being backgrounded or reclaimed, while assuming it just stays alive loses data the moment the system needs memory. This is exactly why lifecycle handling is favored in scenarios that call for it, while the alternative remains acceptable in simpler cases that don't.
What does the "Android Activity lifecycle Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to android activity lifecycle vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.