Archer Archer-Expert Practice Test Questions Answers

In Archer, not every field created in an application is automatically indexed for searching. Within the Field Properties (General Tab), there is a checkbox titled "Searchable." As taught in Archer Administration II , if this option is unchecked, the field will be invisible to the Advanced Search tool.

This is often done by administrators to improve system performance or to hide technical "helper" fields (like those used in calculations or DDEs) that have no business value for end-user reporting. If a field is missing from the "Available" list in the search builder, the administrator must go back to the Application Builder, edit the field's properties, and ensure the "Searchable" checkbox is enabled. Option B (Key Field) would actually make the field more prominent, and Options C and D do not control the visibility of fields within the Advanced Search interface.

In the Archer Questionnaire platform, "Target" records (the actual assessments sent to users) are dynamically linked to the Questionnaire Template . Unlike standard applications where record data is "frozen" in the database structure, Questionnaires are highly sensitive to template changes.

According to the Questionnaires and Assessment Maintenance curriculum, if you delete a question from a template, that question (and any responses previously provided) will disappear from all records currently using that template, including existing ones. Conversely, if you add a new question, it will immediately appear on all active assessments that have not yet been "submitted" or "locked." This is why Archer administrators are strictly cautioned to version their questionnaires or "retire" old templates rather than modifying an active one mid-campaign. Making direct changes to an active template causes immediate, global updates across the entire record set, potentially leading to data loss for the deleted items and unexpected work for users seeing the new items.

The Bulk Update Jobs feature is used to migrate active records from one version of an Advanced Workflow (AWF) to another. As taught in Advanced Workflow Beyond the Basics , Archer is designed to be cautious but thorough. Statement A is NOT true because the Bulk Update process actually attempts to evaluate all records targeted for migration. If a record is in an error state, the Bulk Update tool provides an opportunity to see if the new workflow version can resolve that state or if it remains "Incompatible."

Statements B, C, and D are all accurate reflections of the platform's behavior. Archer will indeed warn you about the volume of affected records (B), and the system enforces a "one-at-a-time" rule for Bulk Updates (C) to prevent database deadlocks and performance spikes. Furthermore, it is a known risk (D) that structural changes (like deleting a node where records currently reside) can cause those specific jobs to fail during or after an update. Therefore, administrators must use the "Compatibility" check within the Bulk Update interface to identify and resolve these issues before finalizing the migration.

The Mail Merge functionality in Archer allows administrators to take record data and push it into a pre-formatted Word or PDF template. This is a common requirement for generating formal "Exception Letters" or "Audit Reports."

As taught in the Archer Administration II curriculum, when a user is viewing a record and wishes to generate one of these documents, they must click the Export button. Upon clicking Export, the user is presented with several options: standard exports (like CSV or Rich Text) and any Mail Merge Templates that have been associated with that specific application and made available to the user's role. Option B (Email) is used for sending on-demand notifications, not for generating formatted document templates based on Word/PDF layouts.

This is a critical performance and behavior concept taught in Archer Administration II . Conditional Layout (CL) rules are intended to be "dynamic," meaning they should fire as the user interacts with the record (on-the-fly). However, Archer's Calculation Engine primarily runs on the server side during a "Save" event. If a CL rule depends on the value of a Calculated Field , the UI cannot determine the rule's outcome until the calculation has been processed by the database.

Consequently, the section remains hidden while the user is editing because the calculated value hasn't been updated in the current session yet. To make CL rules fire "instantly" before a save, administrators should use non-calculated fields (like Values Lists or Text fields) as the trigger. If a calculated field must be used, the behavior described—where the layout only updates after the record is committed to the database—is the expected platform limitation. Options C and D would not specifically cause a "save-only" refresh; a Date field (unless it is a calculated date) would trigger the CL rule immediately upon selection.