Class variables (static) are used for data that is shared by all instances of a class. manufacturer and screenResolution fit this description. Instance variables are used for data that is unique to each instance. serialNumber and batteryPercentage are specific to each individual laptop object, making them ideal instance variables.

Method decomposition is the process of breaking a large, complex method into several smaller, simpler helper methods. This improves code readability, makes it easier to test individual pieces of logic, and promotes code reuse. The scenario described is a classic example of this design principle.

Generalization is achieved by replacing specific, hard-coded values with parameters. By adding width and height as parameters, the method is no longer tied to a single case and becomes a reusable tool for calculating the area of any rectangle, which is a much more abstract and useful design.

Procedural abstraction means that the caller of a method only needs to know what the method does (as defined by its signature and documentation), not how it does it. As long as the signature (public static int[] sort(int[] data)) and the overall behavior (sorting an array) remain the same, the internal implementation can be changed without affecting the code that uses it.

This question tests AP Computer Science A skills, specifically abstraction and program design through selecting appropriate method signatures. The applyDiscount method should calculate a percentage discount on a product price, requiring it to accept a percentage parameter and return the discounted price as a double. Choice A is correct because it has public visibility (allowing external access), accepts a double percent parameter (supporting decimal percentages like 15.5%), and returns a double (the calculated discounted price). Choice B is incorrect because it returns void, preventing the method from returning the calculated discount amount, and uses int for percent which limits precision. To help students: Emphasize matching return types to the method's purpose - calculations typically return values. Practice identifying when methods should return values versus void. Watch for: confusion between void and value-returning methods, and inappropriate parameter types.

This question tests AP Computer Science A skills, specifically abstraction and program design through selecting appropriate method signatures for calculations. The calculateGpa method computes GPA from grades and returns it as a double, which is the standard data type for GPA values that include decimals (like 3.75). Choice B is correct because it has public visibility (allowing external access to this important calculation) and returns double, which properly represents GPA values with decimal precision. Choice A is incorrect because it returns int, which would truncate GPA values like 3.75 to 3, losing important precision in academic calculations. To help students: Emphasize choosing appropriate return types based on the nature of the data - GPAs need decimal precision. Practice identifying when to use int versus double for different types of calculations. Watch for: using integer types for values that require decimal precision.

This question tests AP Computer Science A skills, specifically abstraction and program design through implementing setter methods. The updateReadings method should accept three double parameters (temperature, humidity, windSpeed) and update the corresponding fields without returning a value. Choice A is correct because it has public visibility (allowing external sensor updates), accepts three double parameters matching the weather data types, and returns void since it's a setter method that updates state. Choice C is incorrect because it uses int parameters instead of double, which would lose precision for weather measurements like 72.5°F or 65.3% humidity. To help students: Emphasize that setter methods typically return void and use parameter types that match the field types. Practice writing setter methods with appropriate parameter types and visibility. Watch for: using incorrect parameter types that lose precision or returning values from setter methods.

This question tests AP Computer Science A skills, specifically abstraction and program design through understanding encapsulation benefits. Encapsulation involves making fields private and providing public methods to control access, ensuring data integrity and hiding implementation details. Choice C is correct because encapsulation allows the WeatherData class to provide public methods (like updateReadings) that validate and control how temperature, humidity, and windSpeed are modified, preventing invalid data. Choice A is incorrect because encapsulation actually requires fields to be private, not public, which is the opposite of what this choice states. To help students: Emphasize that encapsulation protects data by hiding it (private fields) while providing controlled access (public methods). Practice identifying the benefits of data hiding and controlled access. Watch for: confusion between making fields public (breaks encapsulation) versus providing public methods (proper encapsulation).

An instance variable is appropriate for the ID number because each Student object needs its own unique value. A class variable (static) is appropriate for the total count because this value is shared across all Student objects and belongs to the class as a whole, not to any single instance.

An attribute is a general term for a property or characteristic of a class in the design phase. An instance variable is the concrete implementation of an attribute whose value is distinct for each instance (object) of the class. Therefore, an instance variable is a specific kind of attribute.