Intermediate Dart & Flutter test (Intermediate)

Sample questions

5 sample questions from the Intermediate Dart & Flutter test, with the answers. Samples are taken out of the live test, so you will not meet these when you sit it.

1. Which of the following statements accurately describes the correct usage of the ProviderScope widget?

   1. ProviderScope is not needed when using the Riverpod package.
   2. ProviderScope is only used for local state management and not for global state.
   3. ProviderScope should be placed directly as a parent of every widget that needs access to providers.
   4. The ProviderScope widget must be placed at the root of the widget tree to ensure that all providers are accessible throughout the app.

   Answer: D. The ProviderScope widget must be placed at the root of the widget tree to ensure that all providers are accessible throughout the app.

   ProviderScope is a crucial widget in the Provider package as it provides access to providers for all descendants in the widget tree. Placing it at the root ensures that all widgets in the app can access the providers without needing to be explicitly wrapped in a Consumer or Provider widget. Other options are incorrect because ProviderScope can be placed higher up in the widget tree, not necessarily at the root, and it doesn't require being a direct parent of every widget.

2. Which of the following is used to reset all form fields to their initial values and clear any validation errors in Flutter?

   1. Future.error() handling
   2. Riverpod family parameter
   3. FormState.reset() method
   4. StreamTransformer usage

   Answer: C. FormState.reset() method

   The FormState.reset() method is used to reset all the form fields to their initial values and clear any validation errors. This is particularly useful when the user wants to reuse the form for new input after submission or when the form needs to be cleared for some other reason. The other options listed do not directly relate to the behavior of the reset() method.

3. In a realistic Flutter project using Riverpod, how should ProviderScope be applied to ensure efficient dependency management?

   1. Wrap the root of the app with ProviderScope and use Provider in descendant widgets
   2. ProviderScope should be used in conjunction with InheritedWidget
   3. Use ProviderScope only for stateful widgets
   4. Use ProviderScope in every widget that needs to access the provider

   Answer: A. Wrap the root of the app with ProviderScope and use Provider in descendant widgets

   ProviderScope is used to provide the dependencies to the entire app, and Provider is used to consume them in descendant widgets. This is the correct and recommended approach in a realistic project scenario with Riverpod.

4. Which of the following statements correctly describes the behavior of Navigator.push() and Navigator.pop() in Flutter?

   1. Navigator.push() runs on a separate thread, while Navigator.pop() runs on the main thread.
   2. Navigator.push() and Navigator.pop() both run on a separate thread to avoid blocking the main thread.
   3. Navigator.push() and Navigator.pop() are both synchronous operations and do not run on a separate thread.
   4. Navigator.pop() is asynchronous, while Navigator.push() is synchronous.

   Answer: C. Navigator.push() and Navigator.pop() are both synchronous operations and do not run on a separate thread.

   Navigator.push() and Navigator.pop() are synchronous operations in Flutter. They are used to navigate between routes and manage the navigation stack. These operations do not run on a separate thread and are handled on the main thread. This is important for performance considerations because it ensures that the UI remains responsive and avoids blocking the main thread.

5. What will happen when the following code is executed? Assume the HTTP request returns a 404 status code: final res = await http.get(Uri.parse('https://example.com/nonexistent')); if (res.statusCode != 200) { print('Error: ${res.statusCode} ${res.reasonPhrase}'); } else { print('Success: ${res.statusCode} ${res.reasonPhrase}'); }

   1. The code will not print anything because the HTTP request is asynchronous and not awaited.
   2. The code will print 'Success: 200 OK' because the HTTP request is always successful.
   3. The code will print 'Error: 404 Not Found' because the HTTP response status code is checked, and the error is handled explicitly.
   4. The code will throw an exception because the HTTP response is not handled properly.

   Answer: C. The code will print 'Error: 404 Not Found' because the HTTP response status code is checked, and the error is handled explicitly.

   In the provided code, the HTTP response is checked for a status code using res.statusCode. If the status code is not 200 (OK), the code explicitly handles the error by printing an error message. This is a best practice for handling HTTP responses, as it ensures that errors are caught and handled properly.