Free Associate Android Developer Exam Associate-Android-Developer Exam Practice Test

What happens when you create a DAO method and annotate it with @Insert?Example:@Daointerface MyDao {@Insert(onConflict = OnConflictStrategy.REPLACE)fun insertUsers(vararg users: User)}

• Room generates an implementation that inserts all parameters into the database in a single transaction.
  
• Room modifies a set of entities, given as parameters, in the database. It uses a query that matches against the primary key of each entity.
  
• Room removes a set of entities, given as parameters, from the database. It uses the primary keys to find the entities to delete.
  

RecyclerView is a subclass of ViewGroup and is a more resource-efficient way to display scrollable lists. Instead of creating a View for each item that may or may not be visible on the screen, RecyclerView:

• creates a single list item and reuses it for visible content.
  
• creates an unlimited number of list items and never reuses them
  
• creates a limited number of list items and reuses them for visible content.
  
• creates a single list item and never reuses it
  

What is illustrated in the picture?

• Logcat window with filter settings
  
• Debugging native code using LLDB
  
• The Variables and Watches panes in the Debugger window
  
• The Breakpoints window lists all the current breakpoints and includes behavior settings for each
  
• Adding a watchpoint to a variable in memory
  

Filter logcat messages. If in the filter menu, a filter option ''Show only selected application''? means:

• Display the messages produced by the app code only (the default). Logcat filters the log messages using the PID of the active app.
  
• Apply no filters. Logcat displays all log messages from the device, regardless of which process you selected.
  
• Create or modify a custom filter. For example, you could create a filter to view log messages from two apps at the same time.
  

In application theme style, flag windowNoTitle (<item name='windowNoTitle'>) indicates:

• whether this window should have an Action Bar in place of the usual title bar.
  
• whether there should be no title on this window.
  
• that this window should not be displayed at all.
  
• whether this is a floating window.
  
• whether this Window is responsible for drawing the background for the system bars.
  

An example. In our ViewModelFactory (that implements ViewModelProvider.Factory) we have an instance of our Repository, named mRepository. Our ViewModel has such constructor:public MyViewModel(MyRepository myRepository)...Next, in our ViewModelFactory create ViewModel method (overriden) looks like this:@NonNull@Overridepublic <T extends ViewModel> T create(@NonNull Class<T> modelClass) { try {//MISSED RETURN VALUE HERE} catch (InstantiationException | IllegalAccessException | NoSuchMethodException | InvocationTargetException e) {throw new RuntimeException('Cannot create an instance of ' + modelClass, e);}}What should we write instead of ''//MISSED RETURN VALUE HERE''?

• return modelClass.getConstructor()
  .newInstance(mRepository);
  
• return modelClass.getConstructor(MyRepository.class)
  .newInstance();
  
• return modelClass.getConstructor(MyRepository.class)
  .newInstance(mRepository);
  

If you want the Database Inspector to automatically update the data it presents as you interact with your running app, check the Live updates checkbox at the top of the inspector window. While live updates are enabled, what happens with the table in the inspector window?

• It is still editable. You can modify data in a table by double-clicking a cell, typing a new value, and pressing Enter.
  
• It becomes read-only and you cannot modify its values.
  
• It becomes read-only, but you cannot see its updated values before updating the data by clicking the Refresh table button at the top of the inspector window.
  

With a room database. When performing queries, you'll often want your app's UI to update automatically when the data changes. Can you use a return value of type LiveData in your query method description to achieve this?

• Yes
  
• No
  

To run your local unit tests, follow these steps:1. Be sure your project is synchronized with Gradle by clicking Sync Project in the toolbar.2. Run your test in one of the following ways (select possible): (Choose three.)

• To run a single test, open the Project window, and then right-click a test and click Run .
  
• To test all methods in a class, right-click a class or method in the test file and click Run .
  
• To run all tests in a directory, right-click on the directory and select Run tests .
  
• To run all tests in Project, open the Project window, and then right-click a test and click Run .
  

''workManager'' is an instance of WorkManager. Select correct demonstration of WorkRequest cancellation:

• workManager.enqueue(new OneTimeWorkRequest.Builder(FooWorker.class).build());
  
• WorkRequest request = new OneTimeWorkRequest.Builder(FooWorker.class).build(); workManager.enqueue(request);
  LiveData<WorkInfo> status = workManager.getWorkInfoByIdLiveData(request.getId ());
  status.observe(...);
  
• WorkRequest request = new OneTimeWorkRequest.Builder(FooWorker.class).build(); workManager.enqueue(request);
  workManager.cancelWorkById(request.getId());
  
• WorkRequest request1 = new OneTimeWorkRequest.Builder(FooWorker.class).build();
  WorkRequest request2 = new OneTimeWorkRequest.Builder(BarWorker.class).build
  ();
  WorkRequest request3 = new OneTimeWorkRequest.Builder(BazWorker.class).build
  ();
  workManager.beginWith(request1, request2).then(request3).enqueue();
  
• WorkRequest request = new OneTimeWorkRequest.Builder(FooWorker.class).build(); workManager.enqueue(request);
  workManager.cancelWork(request);