156-315.77 · Question #701
Which file defines the fields for each object used in the file objects.C (color, num/string, default value...)?
The correct answer is A. $FWDIR/conf/classes.C. See the full explanation below for the reasoning.
Question
Which file defines the fields for each object used in the file objects.C (color, num/string, default value...)?
Options
- A$FWDIR/conf/classes.C
- B$FWDIR/conf/scheam.C
- C$FWDIR/conf/table.C
- D$FWDIR/conf/fields.C
How the community answered
(42 responses)- A71% (30)
- B17% (7)
- C5% (2)
- D7% (3)
Community Discussion
5
Bahar F.Mar 1, 2026A is correct. The file $FWDIR/conf/classes.C is the schema definition file that declares each object class along with its fields, field types (color, string, number), and default values, which is exactly what objects.C references when the policy database is loaded.
Samuel O.Mar 1, 2026Bahar's got the right idea but worth noting that classes.C defines the class structure while objects.C holds the actual instantiated objects, so they work together at load time rather than objects.C simply referencing classes.C as a lookup.
Fatima Z.Feb 17, 2026D is the trap that catches everyone because "fields.C" literally has the word fields in it, but think of it this way, you build the CLASS before you fill in the fields, just like every OOP course you ever took, so burn this into your brain: CLASSES COME FIRST, and that locks in $FWDIR/conf/classes.C as the file that defines every object's field properties for objects.C.
Samuel O.Feb 18, 2026The OOP analogy is exactly right and I would add that in production, when objects.C gets corrupt or out of sync, the first thing a seasoned Check Point engineer verifies is whether the class definitions in classes.C still align, so understanding that dependency order saves you in a real outage, not just on the exam.
Samuel O.Feb 22, 2026classes.C is what you want, even though "fields" sounds more tempting for that job.