Question 1 of 10
Naming a list inventory instead of describing each product record in every line of code is primarily an example of:
- A. Losing all product data
- B. Forcing every value to be Boolean
- C. Data abstraction
- D. A syntax error
Naming a list inventory instead of describing each product record in every line of code is primarily an example of:
A team documents PROCEDURE median(values) but keeps the body private from other teams. Other teams still call it successfully. What does this show?
Which situation least demonstrates data abstraction?
A graphics library lets artists call drawSprite(icon) while the library stores pixels internally. Artists never edit pixel arrays. Which statement is best?
Why might a programmer prefer one list named quizScores over five variables q1 through q5 for the same five numbers?
Module Alpha builds a list named route. Module Beta only calls LENGTH(route) and route[i]. Module Beta never sees how Alpha collected GPS points. This separation is valuable because:
Which rename most improves clarity of a data abstraction?
A procedure compress(data) returns a shorter representation. Callers treat data as a list of bytes. Which claim matches AP CSP data abstraction ideas?
Data abstraction is most nearly:
A program stores map locations in a list named stops. A future update changes internal geotag precision but keeps the same list name and element order for callers. Existing code that only reads stops[i] keeps working. What does this illustrate?