Final answer:
In object-oriented programming, it's standard to make class fields private and to provide public methods to access and modify those fields, following the principle of encapsulation.
Step-by-step explanation:
When designing an object-oriented program and writing classes, it is common practice to:
- make all of a class's fields private (b)
- provide public methods to access and change the private fields (d)
Making class fields private is a key aspect of encapsulation, a core principle of object-oriented design. This helps to protect the integrity of the data by preventing outside code from directly altering the internal state of the object. Instead, classes should provide public methods, often referred to as setters and getters, which allow controlled access to the class's fields. These methods can include validation logic to ensure that only valid data is assigned to the fields. Therefore, options b and d are the correct practices in most object-oriented programming scenarios.