ASSOCIATE-REACTIVE-DEVELOPER practice question 27 of 35

Which of the following is a characteristic of a Static Entity?

Full set: 262 questions
Answer options
A: It can't be extended with any new attributes.
B: It has two Entity Actions.
C: It can't be changed after the first publish.
D: It contains a set of Records. Correct answer
Correct Answer:
D. It contains a set of Records.
Explanation

A Static Entity is a core concept in OutSystems used to define a fixed set of data, similar to an enumeration or a lookup table. Its primary characteristic is that its records are created and managed at design time within Service Studio. These records are then deployed with the application and are read-only at runtime, providing a consistent and static data source for logic, dropdowns, and other UI elements. This predefined set of records is the fundamental feature that distinguishes it from a standard database entity.

Why Incorrect

A. It can't be extended with any new attributes. This is incorrect. You can add, modify, or remove attributes from a Static Entity in Service Studio at any time, just like a regular Entity.
B. It has two Entity Actions. This is misleading. While OutSystems automatically creates Get and GetForUpdate actions, this is a secondary implementation detail, not its defining characteristic. The fundamental nature is its static data.
C. It can't be changed after the first publish. This is incorrect. Developers can modify a Static Entity's attributes and its records in Service Studio and then republish the module to apply the changes.

References

1. OutSystems Official Documentation - "Create a Static Entity": This document explicitly states, "Static Entities are the OutSystems equivalent to an enumeration or a lookup table. They allow you to have a set of predefined values (records) that can be used in your application..." It also confirms that you can add new attributes and edit records at design time. (See section: "Create a Static Entity" and "Static Entity Records").

2. OutSystems Official Documentation - "Entities": In the section comparing Entity types, it clarifies that Static Entities have their data "defined at development time in Service Studio." This directly supports the concept that their defining feature is the set of predefined records. (See section: "Static Entities").

3. OutSystems Training Material - "Modeling Data": In the guided path "Developing Reactive Web Apps," the section on data modeling explains that Static Entities are used for "data that does not change often, like status lists or categories." This reinforces that their purpose is to hold a specific set of records. (See lesson: "Data Model" -> "Entities").

Scroll to Top