050-SEPROGRC-01 · Question #57
Within RSA Archer, data is stored in the following nested sequence of items:
The correct answer is A. Solution > Application > Record > Field. RSA Archer organizes data in a hierarchical structure where Solutions contain Applications, Applications contain Records, and Records contain Fields.
Question
Within RSA Archer, data is stored in the following nested sequence of items:
Options
- ASolution > Application > Record > Field
- BWorkspace > Dashboard > iView > Report
- CAccess role > Group > User Account > User
- DUser Account > Workspace > Solution > Application
How the community answered
(46 responses)- A78% (36)
- B4% (2)
- C2% (1)
- D15% (7)
Why each option
RSA Archer organizes data in a hierarchical structure where Solutions contain Applications, Applications contain Records, and Records contain Fields.
In RSA Archer, a Solution is a packaged grouping of Applications for a business domain (e.g., Risk Management); each Application is a structured container like a database table; Records are individual entries within an Application; and Fields are the discrete data elements within each Record - forming the complete nested storage hierarchy.
Workspace, Dashboard, iView, and Report describe the user interface and navigation hierarchy, not the underlying data storage structure.
Access Role, Group, User Account, and User describe the identity and access management hierarchy, which is separate from how data itself is stored.
This option incorrectly mixes administrative account objects with data containers and presents them in a sequence that does not reflect Archer's actual data model.
Concept tested: RSA Archer data hierarchy - Solution Application Record Field
Source: https://community.rsa.com/t5/archer-documentation/tkb-p/archer-documentation
Topics
Community Discussion
7
Carlos M.Jun 15, 2026A is the right answer. In Archer, Solutions are the top-level containers that group related Applications together, and Applications are where you define the structure of your data using Fields. When someone actually enters data, that creates a Record inside the Application, so the nesting goes Solution, then Application, then Record, then Field. The other options describe real Archer concepts but they are either UI navigation paths (B), access control hierarchies (C), or just a jumbled order that does not reflect how data is actually stored (D).
Wesley A.Jun 26, 2026Solution wraps Application wraps Record wraps Field, locked in. Do you remember which level you actually *create* records at?
Lena V.Jun 26, 2026Solution holds Applications, which hold Records, which hold Fields. Does your study guide explain what types of data live at the Field level versus the Record level?
Carlos M.Jun 27, 2026Fields are the schema definition, things like data type, required or optional, max length, so they describe the shape of data, while Records are the actual instances that hold the real values people enter at runtime.
Viktor S.Jun 26, 2026Has to be C, and here is why I landed there. Archer is fundamentally an identity and access management platform at its core, so the logical nesting starts at the permission layer and works inward toward the individual. You assign an access role first, that role is applied to a group, users inside that group inherit the access, and the individual user account is the terminal object that all of that flows down to. The other options read like they describe navigation menus or GUI layouts, not actual data storage hierarchy, and the question specifically says data is stored in this nested sequence, which points straight at the security model. C maps cleanly to how Archer actually governs what gets stored and who can touch it, which is the architecture that matters operationally.
Ola B.Jun 29, 2026Viktor, your security model reasoning is solid but it answers a different question, because Archer stores data in the hierarchy of application, level, record, and field, which is option A, and that nested sequence is what the question is testing you on. Spin up a trial instance and poke around the data architecture layer, it makes A click immediately.
Ola B.Jun 26, 2026Saw this exact question on my sitting last spring and almost overthought it, but once you spin up Archer in a sandbox and actually click through creating a field inside a record inside an app inside a solution, the hierarchy just burns itself into your brain. The answer is A, Solution > Application > Record > Field, and no amount of flashcards will cement it faster than five minutes of hands-on navigation in the tool.