Instance Configuration
Instance configuration covers the metadata that shapes behavior without writing code: system properties (glide.*), dictionary entries, choice lists, UI policies, business rules, and scheduled jobs, plus the update set machinery that ships them. Candidates must understand the sys_properties table, how to create a custom property, and that properties are cached - changes may need a cache flush to take effect.
The dictionary is the backbone: every field has a dictionary entry defining its type, max length, default value, and reference target. Overriding a dictionary entry on an extended table is a classic exam trap - child tables inherit the parent's dictionary, and you override, not duplicate. Also know application scopes, plugins (which activate features like Flow Designer or CSM), and system clones (which refresh a sub-production instance from production and require post-clone steps such as disabling notifications).
Traps: assuming a property change is instant (caching); confusing plugins with applications; and forgetting that update sets must be retrieved, previewed, and committed in order. Another trap is thinking a UI policy can enforce data integrity server-side - it cannot; use a business rule or data policy for that.
Worked example: To add a custom property controlling a feature flag, create a record in sys_properties with a unique name (e.g., x_acme.feature.enabled), set the type to true/false, then read it in script with gs.getProperty('x_acme.feature.enabled'). Add it to your update set so it travels with the app.