Nested navigation graphs in Android Kotlin - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ navigation

intermediate

Identify the start destination in nested navigation graphs

Given the nested navigation graph below, which fragment will be shown first when the app starts?

Android Kotlin

val navGraph = navController.navInflater.inflate(R.navigation.main_nav_graph).apply {
  startDestination = R.id.home_nav_graph
}

val homeNavGraph = navController.navInflater.inflate(R.navigation.home_nav_graph).apply {
  startDestination = R.id.dashboardFragment
}

val settingsNavGraph = navController.navInflater.inflate(R.navigation.settings_nav_graph).apply {
  startDestination = R.id.settingsFragment
}

A main_nav_graph

B settingsFragment

C home_nav_graph

D dashboardFragment

💡 Hint

The start destination of the main graph points to a nested graph, which itself has a start destination fragment.

The main navigation graph's start destination is the home_nav_graph nested graph. Inside home_nav_graph, the start destination is dashboardFragment, so that fragment is shown first.

❓ ui_behavior

intermediate

Effect of nested graph on back button behavior

In an app with nested navigation graphs, what happens when the user presses the back button on a fragment inside a nested graph?

A The app navigates back within the nested graph until its start destination, then back to the parent graph.

B The back button is disabled inside nested graphs.

C The app skips the nested graph and goes directly to the main graph's start destination.

D The app immediately exits regardless of navigation stack.

💡 Hint

Think about how navigation stacks work with nested graphs.

The back button navigates back through the nested graph's stack first. Once at the nested graph's start destination, pressing back moves to the parent graph's previous destination or exits if none.

❓ lifecycle

advanced

Lifecycle impact of nested navigation graphs on fragments

When navigating from a fragment in one nested graph to a fragment in another nested graph, what happens to the lifecycle of the first fragment?

A The first fragment's onPause and onStop are called, but it remains in memory until popped from back stack.

B The first fragment is immediately destroyed and removed from memory.

C The first fragment remains fully active and visible behind the new fragment.

D The first fragment's lifecycle methods are not called until the app is closed.

💡 Hint

Consider how fragment lifecycle works with navigation and back stack.

Navigating away triggers onPause and onStop for the first fragment, but it stays in memory on the back stack until popped or replaced.

📝 Syntax

advanced

Correct Kotlin code to navigate between nested graphs

Which Kotlin code snippet correctly navigates from a fragment in one nested graph to a fragment in another nested graph using Navigation Component?

Android Kotlin

navController.navigate(R.id.action_currentGraphFragment_to_targetGraphFragment)

A navController.navigate("targetGraphFragment")

B navController.navigate(R.id.action_currentGraphFragment_to_targetGraphFragment)

C navController.navigate(R.id.targetGraphFragment)

D navController.navigate(R.navigation.targetGraphFragment)

💡 Hint

Use the generated action ID for navigation between fragments.

Navigation between fragments in nested graphs requires using the action ID defined in the navigation XML, not just the destination ID or string.

🔧 Debug

expert

Diagnose navigation crash due to nested graph misconfiguration

An app crashes with IllegalArgumentException: Navigation destination R.id.profileFragment is unknown to this NavController. The profileFragment is inside a nested graph. What is the most likely cause?

A The profileFragment ID is duplicated in multiple graphs causing conflict.

B The NavController was not initialized before navigation call.

C The nested graph containing profileFragment is not included or linked in the main navigation graph.

D The profileFragment class is missing from the project source code.

💡 Hint

Check if all nested graphs are properly referenced in the main graph.

If a nested graph is not included in the main graph, its destinations are unknown to the NavController, causing this crash.