4. Built-in Images Quiz
4.1. Question 1
How many built-in images are roughly available within the microbit library according to the documentation?
Incorrect. There are far more than 10 built-in choices.
Incorrect. The library offers a much wider variety of pre-drawn selections.
Correct. The library contains over 60 built-in images that have specific names.
Incorrect. While extensive, it does not contain hundreds of images by default.
4.2. Question 2
Which of the following lines correctly displays a built-in heart image on the micro:bit?
Correct. This uses a capital ‘I’ for Image, all uppercase for HEART, and no quotes.
Incorrect. The Image object must be written with a capital ‘I’.
Incorrect. The built-in image name must be written in full capitals.
Incorrect. No quotation marks should be used around the image reference.
4.3. Question 3
According to standard code naming principles, what case style should be used for naming constants?
Incorrect. Lowercase is typically reserved for variables and functions.
Incorrect. CapWords (CamelCase) is standard formatting for class structures.
Correct. Naming principles specify that constants should be written in ALLCAPS, such as PIN or HEART.
Incorrect. Standard constants avoid mixed or lowercase configurations.
4.4. Question 4
In Python code architecture, how are the components Image and HEART classified?
Incorrect. Neither component represents an action function or plain value variable.
Correct. Image with a capital letter behaves as a class, and HEART is a constant within it.
Incorrect. They lack quotation marks and do not behave as keyword parameters.
Incorrect. Variables use lower case letters, unlike these components.
4.5. Question 5
What convenient feature triggers automatically inside the Python Editor when you type Image. (including the dot)?
Incorrect. Typing code does not trigger immediate script flashing.
Incorrect. This is proper syntax and does not prompt warnings.
Correct. As soon as the stop/dot is typed after Image, a drop list appears to let you pick an image.
Incorrect. It is unchanged by the editor.
4.6. Question 6
Which function is used to output a built-in image to the micro:bit LED grid?
Incorrect. Scrolling is for numbers and text strings, not image objects.
Correct. Images are shown, not scrolled.
Incorrect. There is no draw function.
Incorrect. There is no image function.
4.7. Question 7
Look at the following code snippet:
from microbit import *
shape_images = [
Image.TRIANGLE,
Image.DIAMOND,
Image.SQUARE,
]
while True:
display.show(shape_images, delay=250)
What is the outcome when this script runs on the micro:bit?
Incorrect. Lists are fully supported to create animations.
Incorrect. It displays the referenced image data types, not text strings.
Correct. Passing an array list of images to display.show() loops through them sequentially.
Incorrect. The 5x5 LED matrix can only show one Image at a time.
4.8. Question 8
When animating a list of images using display.show(object_images, delay=250), what does the delay parameter represent?
Incorrect. Delay sets a millisecond value, and loops continuously within while structures.
Correct. The delay controls the timing pause separating each listed image during playback.
Incorrect. LED activation depends on the brightness level set by each image.
Incorrect. It determines live runtime animation transition speeds instead.
4.9. Question 9
Which of the following Image objects is an example of a valid built-in object image name?
Incorrect. Built-in constants require fully capitalized text strings.
Incorrect. Small variations are noted for shapes like DIAMOND_SMALL, but not rollerskate.
Correct. Image.ROLLERSKATE is explicitly included under the valid object image listings within the documentation tasks.
Incorrect. The constant name is written together as CHESSBOARD without an underscore separator.
4.10. Question 10
Which of the following lists contains only valid geometric shape image names as structured in the documentation exercises?
Correct. These are all accurately classified as shape constants.
Incorrect. These item constants are categorized as object images rather than shapes.
Incorrect. These options fail because constant names used lowercase instead of the required uppercase format.
Incorrect. These represent object entities instead of shapes.