Google Developers Certification - Associate Android Developer (Kotlin and Java Exam) - Associate-Android-Developer Free Exam Questions

A. advance to the first line inside a method call

B. evaluate an expression at the current execution point

C. continue running the app normally

D. advance to the next line in the code (without entering a method)

E. examine the object tree for a variable; expand it in the Variables view. If the Variables view is not visible

F. advance to the next line outside the current method

A. MODE_PRIVATE or MODE_PUBLIC

B. Value is either 0 or a combination of MODE_PRIVATE, MODE_WORLD_READABLE

C. MODE_WORLD_WRITEABLE, and MODE_MULTI_PROCESS

D. combination of MODE_WORLD_READABLE and MODE_WORLD_WRITEABLE

A. Always place this item in the app bar. Avoid using this unless it's critical that the item always appear in the action bar. Setting multiple items to always appear as action items can result in them overlapping with other UI in the app bar.

B. The action view associated with this action item (as declared by android:actionLayout or android:actionViewClass) is collapsible.

C. Also include the title text (defined by android:title) with the action item. You can include this value along with one of the others as a flag set, by separating them with a pipe.

D. Never place this item in the app bar. Instead, list the item in the app bar's overflow menu.

E. Only place this item in the app bar if there is room for it. If there is not room for all the items marked by this value, the items with the lowest orderInCategory values are displayed as actions, and the remaining items are displayed in the overflow menu.

A. override fun onKeyUp(keyCode: Int, event: KeyEvent): Boolean { return when(keyCode) { KeyEvent.KEYCODE_DPAD_LEFT -> { currentValue-- sendAccessibilityEvent(AccessibilityEvent.TYPE_VIEW_TEXT_CHANGED) true
}
...
}
}

B. override fun onKeyUp(keyCode: Int, event: KeyEvent): Boolean { return when(keyCode) { KeyEvent.KEYCODE_ENTER -> { currentValue-- sendAccessibilityEvent (AccessibilityEvent.TYPE_VIEW_CONTEXT_CLICKED) true
}
...
}
}

C. override fun dispatchPopulateAccessibilityEvent(event: AccessibilityEvent): Boolean { return super.dispatchPopulateAccessibilityEvent(event).let { completed -> if (text?.isNotEmpty() == true) { event.text.add(text) true
} else {
completed
}
}
}

A. InputStream input = context.getResources().openRawResource(R.raw.sample_teas);

B. InputStream input = context.getResources().getAssets().open ("sample_teas.json");

C. InputStream input = context.getAssets().open("sample_teas.json");

A. No, the debug variant should be visible in the build.gradle file anyway.

B. No, if you define new build types that should be debuggable, you must add 'debuggable false'

C. Yes.

A. InputStream input = context.getResources().openRawResource(R.raw.sample_teas);

B. InputStream input = context.getRawResource(R.raw.sample_teas);

C. InputStream input = context.openRawResource(R.raw.sample_teas);

A. android:contentDescription

B. android:labelFor

C. android:hint

A. validate either interactions between levels of the stack within a module, or interactions between related modules.

B. validate your app's behavior one class at a time.

C. validate user journeys spanning multiple modules of your app.

A. Log.v(String, String) (verbose)

B. Log.e(String, String) (error)

C. Log.a(String, String) (all outputs)

D. Log.q(String, String) (Question:s)

E. Log.d(String, String) (debug)

F. Log.i(String, String) (information)

G. Log.w(String, String) (warning)