050-SEPROGRC-01 · Question #39
What two steps are necessary in order to import data into sub-forms?
The correct answer is A. Import data into the parent records (or verify parent records exist), and then import the data into. Importing sub-form data in RSA Archer requires parent records to exist first, after which the sub-form data is imported and linked to those established parent records.
Question
What two steps are necessary in order to import data into sub-forms?
Options
- AImport data into the parent records (or verify parent records exist), and then import the data into
- BImport the sub-form data first, and then link the sub-form records to the parent records using a
- CSet the application to Retired status prior to performing the import, and then return the application
- DUse a second tab in your spreadsheet to load the sub-form data, and then configure the data
How the community answered
(37 responses)- A78% (29)
- B14% (5)
- C3% (1)
- D5% (2)
Why each option
Importing sub-form data in RSA Archer requires parent records to exist first, after which the sub-form data is imported and linked to those established parent records.
Sub-form records in RSA Archer are child entities that are structurally dependent on a parent record, so the parent must be created or verified to exist before sub-form data can be imported and associated. The recommended two-step process is to first import or confirm parent records, then perform a second import that maps each sub-form row to its parent using a matching key field. Reversing this order or skipping the parent step causes the sub-form import to fail because there is no record to attach the child data to.
Importing sub-form data before parent records exist is not supported, because sub-form records require an existing parent to link to and will not import successfully without one.
Setting an application to Retired status before importing is not a required step and would disrupt normal application availability and data import operations.
Using a second tab in a spreadsheet to load sub-form data is not a supported import method in RSA Archer's data feed and import tooling.
Concept tested: RSA Archer sub-form data import sequencing requirements
Topics
Community Discussion
6
Nina C.Jun 26, 2026The answer is A, and once I thought it through it actually clicked for me pretty well. Sub-forms are dependent records, meaning they have to be linked to a parent, so if the parent does not exist yet, there is nothing for the sub-form data to attach to. You have to either import your parent records first or confirm they are already in the system, and only then can you bring in the sub-form data and have it connect properly. Think of it like a filing cabinet, you need the folder before you can drop papers into it. Option B has the order backwards, C is about application status which has nothing to do with the import sequence, and D is about spreadsheet tabs which is not a real system requirement for this process.
Mateus R.Jun 21, 2026Honestly I almost picked D because the spreadsheet tab thing sounded familiar from something I set up at work, but then I thought about it like moving into an apartment building, you cannot assign tenants to units that do not exist yet, so you have to make sure the building (parent record) is there first before you start filling rooms (sub-form records), which is exactly what A describes.
Nina C.Jun 22, 2026The apartment analogy really clicked for me too, and I'd just add that on the exam they might phrase it as referential integrity, so if you see that term in a question it is the same rule you just described.
Wesley A.Jun 26, 2026A is exactly right. Sub-forms depend on parent records existing first because the import engine needs a valid parent key to attach child rows to, so if you try to load sub-form data against a parent that does not exist yet, the import will either error out or silently drop those records.
Brenda K.Jun 26, 2026C is the move, retire the app first, then reimport clean.
Wesley A.Jun 28, 2026Hey Brenda, totally see the logic there, but A is actually correct because you need to complete the migration and verify data integrity before retiring the source app, otherwise you risk permanent data loss if something goes wrong during reimport.