March 8, 2026 • 2 min read

Weekly Engineering Mastery Quiz (2026-03-02 to 2026-03-06)

A 20-question assessment covering fundamentals, implementation best practices, and advanced architecture insights from this week’s learning posts.

#Learning-log#Quiz#Assessment Weekly Quiz

Table of contents

Week Summary (Mar 2–6, 2026, Europe/London)
Interactive Quiz

Week Summary (Mar 2–6, 2026, Europe/London)

This week consolidated Kotlin fundamentals and Jetpack Compose core concepts.

Highlights

Jetpack Compose Core Concepts (Mar 4 & Mar 6): declarative UI, composition tree, recomposition, idempotency, composable lifecycle, positional memoization, pure composables; Slot APIs (single vs named slots), insets-aware design, Scaffold usage, and subcomposition for advanced layouts.
Kotlin Language: Variables & Types (Mar 4, Parts 1–2) + Refresher (Mar 5): val vs var, type inference, strings and templates, numeric/boolean/char types; lattice cornerstones Any, Unit, Nothing and their correct use.

What you should now be able to do

Structure UIs declaratively in Compose, reason about composition/recomposition, and keep composables idempotent and side‑effect free.
Apply positional memoization safely and use Effect APIs when side effects are required.
Design reusable Slot APIs, choose between single content vs named slots, and employ subcomposition judiciously.
Write clear Kotlin using val/var appropriately, leverage type inference, and correctly apply Any/Unit/Nothing.

Practical emphasis

Insets: prefer WindowInsets and Scaffold’s contentWindowInsets over hardcoded padding.
Performance: hoist state, keep slot lambdas stable, and remember expensive objects.
Robust Kotlin: use Nothing for non‑returning code paths (e.g., error), Unit for functions with no meaningful value, and Any/Any? at API boundaries.

Interactive Quiz

Use the interactive quiz section below to answer each question and get instant feedback.

Interactive Quiz

Score: 0 / 20 | Answered: 0 / 20

Q1 In Kotlin, which statement about val and var is correct?

Fundamentals

A. var defines a read-only reference. B. val is an immutable reference; the referenced object may still be mutable. C. val can be reassigned after initialization. D. val guarantees deep immutability of the object graph.

Select one option.

Q2 What is the inferred type of the literal 42 in Kotlin (without suffixes)?

Fundamentals

A. Long B. Double C. Int D. Float

Select one option.

Q3 Given val name = "Ada", which template prints "Hello, Ada"?

Fundamentals

A. "Hello, ${name.toString}" B. "Hello, {name}" C. "Hello, $(name)" D. "Hello, $name"

Select one option.

Q4 What does the @Composable annotation signify in Jetpack Compose?

Fundamentals

A. Function can emit UI into the composition. B. Function recomposes every frame automatically. C. Function always runs on a background thread. D. Function replaces Android lifecycle components.

Select one option.

Q5 Which statements align with declarative UI in Compose?

Fundamentals

A. UI is derived from the current state. B. One‑way data flow is preferred; mutate state and let UI update. C. You primarily mutate view instances to update UI. D. Recomposition applies minimal updates when relevant state changes.

Select one or more options.

Q6 Which best describes the composition tree in Compose?

Intermediate

A. It exists only at compile time. B. It mirrors a RecyclerView’s adapter tree. C. It models composable function structure, decoupled from the Android view hierarchy. D. Each composable maps 1:1 to an Android View.

Select one option.

Q7 What can trigger recomposition of a composable?

Intermediate

A. A State<T> read by the composable changes. B. Its parent recomposes but passes identical stable parameters. C. A key used with remember(...) changes. D. A snapshot‑observed state mutates; Compose schedules recomposition.

Select one or more options.

Q8 Idempotency in composables means:

Intermediate

A. Same inputs/state yield the same UI with no observable side effects. B. They reuse the same slot nodes across all recompositions. C. They run only once during first composition. D. They allocate no objects during recomposition.

Select one option.

Q9 When a composable is disposed, what happens?

Intermediate

A. It goes to a background state but keeps effects running. B. Only effects are cancelled; remember values persist globally. C. Recomposition of that node finishes successfully. D. It is removed from composition; remember caches and effects are cleaned up.

Select one option.

Q10 Select all true statements about Any, Unit, and Nothing in Kotlin:

Intermediate

A. Any is the root supertype of all non‑nullable types. B. Unit has a single value and denotes no meaningful return value. C. Nothing represents the absence of null. D. Nothing has no instances and is a subtype of all types.

Select one or more options.

Q11 Which statement about remember(...) is accurate?

Intermediate

A. Its values survive process death. B. It’s keyed by call position and optional keys; moving it can invalidate the cache. C. It’s identical to rememberSaveable. D. It persists across configuration changes by default.

Select one option.

Q12 Which best characterizes a "pure" composable?

Intermediate

A. It may call suspend functions arbitrarily. B. It may write to files directly as needed. C. It derives output solely from parameters/observed state; side effects use Effect APIs. D. It always skips recomposition.

Select one option.

Q13 In Compose, a Slot API primarily refers to:

Advanced

A. Accepting composable lambdas so callers inject UI regions. B. Using reflection to bind XML view IDs to slots. C. Sealed classes that enumerate slot kinds. D. Persisting slots with rememberSaveable.

Select one option.

Q14 When are multiple named slots preferable to a single content slot?

Advanced

A. When the component is a trivial wrapper around one child. B. When customization should be restricted to maximize micro-optimizations. C. When the component exposes distinct regions (e.g., topBar, bottomBar) customized independently. D. When you want to prevent recomposition entirely.

Select one option.

Q15 About subcomposition in Compose, which statements are true?

Advanced

A. SubcomposeLayout can measure/compose some children using information from others. B. It should be your default layout primitive. C. It enables dependent layouts (e.g., using measured size to drive later composition). D. It can add overhead due to multiple composition passes if overused.

Select one or more options.

Q16 Insets handling with Scaffold and slots—what’s a recommended approach?

Advanced

A. Hardcode status bar height in dp. B. Use WindowInsets (e.g., safeDrawing) or Scaffold’s contentWindowInsets to apply padding. C. Always rely on absolute padding; devices are consistent. D. Wrap everything in a Scroll to ignore system bars.

Select one option.

Q17 Which Material 3 Scaffold slot is intended for the top app bar?

Advanced

A. topBar B. appBar C. header D. toolbarSlot

Select one option.

Q18 For performance with Slot APIs, which practice is recommended?

Advanced

A. Avoid remember around expensive lambdas/objects. B. Capture large mutable objects implicitly in lambdas. C. Inline every slot lambda unconditionally. D. Hoist state, pass stable params, and remember expensive objects to limit recomposition.

Select one option.

Q19 Common, correct uses of Kotlin’s Nothing include:

Advanced

A. Return type of a function that always throws. B. Return type of an infinite loop. C. A synonym for null. D. Elvis branches like error("...") that abort the code path.

Select one or more options.

Q20 Which Effect API launches a coroutine tied to the composition and cancels it on key change or disposal?

Advanced

A. SideEffect B. LaunchedEffect C. DisposableEffect D. produceState

Select one option.

References

Share

Share on X Share on LinkedIn

More to explore

Keep exploring

3/22/2026

Weekly Engineering Mastery Quiz (2026-03-16 to 2026-03-20)

A 20-question assessment covering fundamentals, implementation best practices, and advanced architecture insights from this week’s learning posts.

3/14/2026

Weekly Engineering Mastery Quiz (2026-03-09 to 2026-03-13)

A 20-question assessment covering fundamentals, implementation best practices, and advanced architecture insights from this week’s learning posts.

3/7/2026

Weekly Engineering Mastery Quiz (2026-03-02 to 2026-03-06)

A 20-question assessment covering fundamentals, implementation best practices, and advanced architecture insights from this week’s learning posts.

Previous

Flutter: Core Widget Concepts Deep Dive (Part 2/2)

Next

Weekly Engineering Mastery Quiz (2026-03-02 to 2026-03-06)