Bird
Raised Fist0
Kotlinprogramming~10 mins

Map-backed delegated properties in Kotlin - Interactive Code Practice

Choose your learning style10 modes available
Practice - 5 Tasks
Answer the questions below
1fill in blank
easy

Complete the code to declare a map-backed delegated property for 'name'.

Kotlin
val user = mapOf("name" to "Alice", "age" to 30)
val name: String by [1]
Drag options to blanks, or click blank then click option'
Amap
Buser
CmutableMapOf()
DHashMap()
Attempts:
3 left
💡 Hint
Common Mistakes
Using a new empty map instead of the existing 'user' map.
2fill in blank
medium

Complete the code to access the 'age' property delegated to the map.

Kotlin
val user = mapOf("name" to "Bob", "age" to 25)
val age: Int by [1]
println(age)
Drag options to blanks, or click blank then click option'
Amap
BmutableMapOf()
CHashMap()
Duser
Attempts:
3 left
💡 Hint
Common Mistakes
Delegating to a new empty map which has no data.
3fill in blank
hard

Fix the error in the code to correctly delegate 'email' property to the map.

Kotlin
val user = mapOf("email" to "test@example.com")
val email: String by [1]
println(email)
Drag options to blanks, or click blank then click option'
Amap
BmutableMapOf()
Cuser
DHashMap()
Attempts:
3 left
💡 Hint
Common Mistakes
Delegating to a new empty map instead of the existing one.
4fill in blank
hard

Fill both blanks to create a map-backed delegated property 'city' and print its value.

Kotlin
val data = mapOf("city" to "Paris", "country" to "France")
val city: String by [1]
println([2])
Drag options to blanks, or click blank then click option'
Adata
Bcity
Ccountry
DdataMap
Attempts:
3 left
💡 Hint
Common Mistakes
Using wrong variable names for delegation or printing.
5fill in blank
hard

Fill all three blanks to create map-backed delegated properties 'firstName' and 'lastName', then print full name.

Kotlin
val personData = mapOf("firstName" to "John", "lastName" to "Doe")
val firstName: String by [1]
val lastName: String by [2]
println("Full name: $[3] $lastName")
Drag options to blanks, or click blank then click option'
ApersonData
CfirstName
DlastName
Attempts:
3 left
💡 Hint
Common Mistakes
Using different map variables for delegation or printing the map variable instead of the property.

Practice

(1/5)
1. What is the main purpose of using Map-backed delegated properties in Kotlin?
easy
A. To convert maps into JSON strings automatically
B. To link class properties directly to entries in a map
C. To perform arithmetic operations on map values
D. To create immutable lists easily

Solution

  1. Step 1: Understand the concept of map-backed delegation

    Map-backed delegated properties allow class properties to get and set values directly from a map using the property name as the key.
  2. Step 2: Identify the main purpose

    This reduces boilerplate code when working with dynamic data by linking properties to map entries.
  3. Final Answer:

    To link class properties directly to entries in a map -> Option B
  4. Quick Check:

    Map-backed delegation links properties to map keys [OK]
Hint: Remember: properties match map keys exactly [OK]
Common Mistakes:
  • Thinking it creates immutable lists
  • Assuming it converts maps to JSON
  • Confusing it with arithmetic operations on maps
2. Which of the following is the correct syntax to declare a property name delegated to a map map in Kotlin?
easy
A. val name by map["name"]
B. val name = map["name"]
C. val name by map.get("name")
D. val name by map

Solution

  1. Step 1: Recall the syntax for map-backed delegated properties

    In Kotlin, you delegate a property to a map using val property by map, where the property name matches the map key.
  2. Step 2: Analyze each option

    val name by map uses the correct syntax. val name by map["name"] tries to delegate to a map entry, which is invalid. val name by map.get("name") calls a function, not delegation. val name = map["name"] just assigns the value, not delegation.
  3. Final Answer:

    val name by map -> Option D
  4. Quick Check:

    Property delegation uses 'by map' syntax [OK]
Hint: Use 'by map' with property name matching key [OK]
Common Mistakes:
  • Trying to delegate to map entry like map["key"]
  • Using map.get() instead of delegation
  • Assigning value directly without delegation
3. What will be the output of the following Kotlin code?
class User(val map: Map<String, Any?>) {
    val name: String by map
    val age: Int by map
}

fun main() {
    val user = User(mapOf("name" to "Alice", "age" to 30))
    println("Name: ${user.name}, Age: ${user.age}")
}
medium
A. Name: Alice, Age: 30
B. Name: null, Age: 0
C. Compilation error due to type mismatch
D. Runtime exception due to missing keys

Solution

  1. Step 1: Understand map-backed delegation behavior

    The properties name and age delegate to the map keys "name" and "age" respectively, retrieving their values.
  2. Step 2: Check the map contents and output

    The map contains "name" as "Alice" and "age" as 30, so printing these properties outputs "Name: Alice, Age: 30".
  3. Final Answer:

    Name: Alice, Age: 30 -> Option A
  4. Quick Check:

    Map keys match properties, so values print correctly [OK]
Hint: Property names must match map keys exactly [OK]
Common Mistakes:
  • Expecting null or default values
  • Confusing delegation with direct assignment
  • Assuming runtime error without missing keys
4. Identify the error in this Kotlin code using map-backed delegated properties:
class Person(val map: Map<String, Any>) {
    val firstName: String by map
    val lastName: String by map
}

fun main() {
    val data = mapOf("firstName" to "John")
    val person = Person(data)
    println(person.lastName)
}
medium
A. No error; prints null for missing key
B. Compilation error because map type is incorrect
C. Runtime exception due to missing key "lastName" in map
D. Syntax error in property delegation

Solution

  1. Step 1: Check map keys vs delegated properties

    The map contains only "firstName", but the class expects both "firstName" and "lastName" keys for delegation.
  2. Step 2: Understand behavior on missing keys

    Accessing person.lastName tries to get a missing key, causing a runtime exception (NoSuchElementException).
  3. Final Answer:

    Runtime exception due to missing key "lastName" in map -> Option C
  4. Quick Check:

    Missing map keys cause runtime errors [OK]
Hint: All delegated keys must exist in the map [OK]
Common Mistakes:
  • Assuming missing keys return null
  • Thinking it's a compile-time error
  • Ignoring runtime exceptions on missing keys
5. Given a map data = mapOf("x" to 10, "y" to 20, "z" to 0), how can you create a Kotlin class Point with map-backed delegated properties x, y, and z but only expose x and y publicly, hiding z internally?
hard
A. Declare val x: Int by map, val y: Int by map as public and private val z: Int by map
B. Declare all properties as val without visibility modifiers
C. Use var for z and val for others
D. Exclude z from the map passed to the class

Solution

  1. Step 1: Understand visibility modifiers in Kotlin

    Properties can be declared with private to hide them from outside the class.
  2. Step 2: Apply visibility to map-backed properties

    Declare x and y as public (default) and z as private val z: Int by map to hide it internally.
  3. Final Answer:

    Declare val x: Int by map, val y: Int by map as public and private val z: Int by map -> Option A
  4. Quick Check:

    Use 'private' modifier to hide delegated properties [OK]
Hint: Use 'private' keyword to hide properties [OK]
Common Mistakes:
  • Assuming all properties are public by default
  • Trying to exclude keys from the map instead of hiding
  • Confusing var and val for visibility
Recommended

Ready to prove it?

Pass the test and this pattern moves unknown strong while earning +1 Grip toward your certificate.

10 questions~5 mineasy hard