Archer Expert Exam Preparation Material | Archer Certified Administrator-Expert

Explanation:
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.

Explanation:
In the Advanced Workflow Beyond the Basics curriculum, administrators are taught how to manage "faulted" or "stuck" workflow jobs using the Advanced Workflow Job Troubleshooting Tool. When a record hits a snag―for example, if a Notification Node fails because of a mail server timeout or a Evaluate Content Node fails due to a missing field value―the job may stop at that specific node.
The Reset option is the specific administrative action used to re-trigger a node. Selecting "Reset" clears the error state of the current node and attempts to execute it again. This is distinct from Restart (Option C), which would typically send the record back to the very beginning of the entire workflow process, potentially duplicating previous steps. Update Job (Option A) is generally used to apply workflow version changes to an active record, and Cancel (Option D) terminates the workflow entirely. For a pinpointed "retry" of a specific failure point, "Reset" is the verified functional command within the troubleshooting utility.
Here are the verified answers and detailed explanations for Questions 8 through 11, strictly aligned with the Archer Administration II and Advanced Workflow Beyond the Basics curriculum standards.

Explanation:
Scheduled Report Distributions behave differently than standard "On-Demand" reports. According to the Archer Administration II curriculum, when a report is scheduled for distribution (e.g., emailed as a PDF or Excel file), the Archer platform must "impersonate" a user to run the query and generate the file.
The platform uses the security context of the user who configured the Scheduled Report Distribution (typically an administrator). This means that all recipients of the email will see the exact same data―the data that the administrator is authorized to see. This is a critical security consideration: if an administrator has "System Administrator" rights and schedules a report for a group of low-privilege users, those users may see sensitive data in the attachment that they would not be able to see if they logged into Archer directly.
Option B is incorrect because the system does not run a separate query for every individual recipient's unique permissions at the time of the email burst.

Explanation:
In the Manage Users section of Archer, the platform uses global defaults to ensure that new accounts are created with a baseline security posture. According to the Archer Administration II security module, every new user record is automatically assigned the Default Security Parameter and the Default Access Role defined in the instance settings.
The Security Parameter (Option D) governs password complexity, expiration, and session timeouts. The Default Access Role typically provides very limited "Read" access to ensure the user can at least log in to the workspace, but usually requires further administrative adjustment to grant functional permissions. A Username (Option A) must be manually entered or mapped from LDAP; Archer cannot guess a unique username. Similarly, email addresses and passwords require specific input or integration triggers. By automatically assigning the default Security Parameter and Access Role, Archer ensures that no user is created without essential security governance already in place.

Explanation:
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.