What type of fields must not be included in the application?

The correct answer identifies that system fields must not be included in the application. System fields are predefined fields that are integral to the core functionality and structure of the application. These fields are typically used for system-level operations, security, and data integrity, and are managed by the platform itself.

Including system fields in the application can lead to complications, such as unintended changes to critical system behavior, performance issues, or conflicts with the platform’s internal mechanisms. Therefore, understanding that system fields are reserved for system use is essential for maintaining a stable and secure application.

In contrast, object fields, relational fields, and non-system fields can be customized and utilized freely within the application as they are designed for user-defined data structures and interactions. These fields do not have the same constraints and can be manipulated as needed, making them more appropriate for inclusion depending on the specific requirements of the application.