Pass the Archer Certified Administrator Archer-Expert Questions and answers with ExamsMirror

In the Archer platform, the Recalculation Schedule (found within the application's General Tab) is a powerful tool, but it can become a performance bottleneck if not configured efficiently. When a recalculation job is triggered, the Archer services must evaluate every record in the application to determine if calculations need to be updated. According to the Archer Administration II curriculum, the most effective way to optimize this process is by using Calculation Filters .

By selecting option A, you are instructing the system to ignore records that are irrelevant to the specific business logic (e.g., records that are already "Expired," "Rejected," or "Draft"). By filtering the schedule to run only for "Approved" requests, the job engine processes a significantly smaller subset of data, which reduces the load on the Async Service and speeds up the completion time. Option B would likely slow the system down further by adding logical complexity to the calculation itself. Option C (Data-Driven Events) is not suitable for date-based triggers because DDEs only fire upon a record "Save" event; they cannot proactively "watch" a date to trigger a change without user intervention or a scheduled recalculation.

In Archer, the ability to perform a data import is governed by Access Roles , not strictly by high-level system administrative accounts. Under the "Rights" tab of an Access Role configuration, there is a specific permission labeled "Data Import." According to the Archer Administration II curriculum, any user assigned to a role with this right enabled—and who also possesses "Create" or "Update" permissions for the target application—can utilize the Data Import tool.

While a System Administrator (Option A) inherently has these rights, the platform is designed for delegated administration. Therefore, a business user or a "Power User" can be granted the specific ability to import data without having full system-wide control. Options B and C are incorrect because "Report Administrators" focus on dashboard and report metadata, and while an administrator might create a custom group named "Data Import," no such hard-coded group exists by default in the Archer out-of-the-box security model. The granularity of Archer's security ensures that data integrity is maintained by linking the import capability directly to the user's functional role and application-level permissions.

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.

Understanding the Archer hierarchy is fundamental to system administration. As detailed in the Archer Administration II curriculum and the Archer Control Panel (ACP) guides, an Environment refers to the overall installation of the Archer software on a set of servers (Web, Services, and Database).

Within a single environment, an administrator can host multiple Instances . Each instance represents a logically isolated "tenant" with its own unique Instance Database , File Repository (for attachments), and set of users. For example, an organization might have one environment that hosts a "Production" instance, a "UAT" instance, and a "Training" instance. This architecture allows organizations to share the same server hardware and software binaries while keeping the data and configurations of different business units or development stages completely separate and secure from one another.

The Data-Driven Event (DDE) Analyzer is a diagnostic tool used to see why certain UI changes (like hiding a field or making it required) occurred. As taught in the Archer Administration II troubleshooting module, the Analyzer provides a high-level summary of the DDE execution path. It will show the name of the rule (Option A), the fields involved (Option B), and the actions triggered (Option C).

However, it does not provide a granular, "Boolean-level" breakdown of every individual filter condition within a complex rule. If a rule has five different conditions joined by AND/OR logic, the Analyzer will tell you if the entire rule evaluated to True or False, but it will not specify the result of each individual condition (Option D). To see that level of detail, administrators often have to simplify the rule or use "Dummy Fields" for testing. Understanding this limitation is key to effectively using the Analyzer for debugging complex conditional layouts.

In a distributed (multi-host) Archer environment, the Archer Configuration Service is the most critical underlying component that must exist on every server in the web and services tiers. As taught in Archer Administration II , this service is responsible for "registering" the server with the Archer Control Panel (ACP) .

The Configuration Service allows the central ACP to communicate with each node in the cluster to manage settings, update the nlog.config files, and ensure that all servers are using the correct database connection strings. While the Queuing Service (Option C) might only reside on the Services server, and the Workflow Service (Option B) is specific to AWF tasks, the Configuration Service is the "heartbeat" that connects any given Archer server to the instance's central management framework. If this service is stopped on a web server, that server will effectively become "orphaned" and will not be able to process user requests correctly or receive updates from the ACP.

According to the Advanced Workflow Beyond the Basics curriculum, the safest administrative practice when modifying an active workflow is to briefly deactivate it. When you deactivate the workflow, you prevent new records from entering a potentially "in-flux" process while you are saving new versions.

Once the changes are finalized and the new version is saved, reactivating the workflow allows the system to initialize the new logic. It is important to note that reactivating the workflow does not automatically update existing records (as discussed in previous questions regarding Bulk Update Jobs), but it ensures that the transition between versions is "clean." Option D is often impossible in a production environment with thousands of active records. Option B is factually incorrect as records do not return to the Start node; they stay exactly where they were in their specific version. Deactivating ensures that the Advanced Workflow Service doesn't attempt to process a record against a design that is currently being overwritten or modified by the administrator.

While you initiate a manual import from the Data Imports menu (Option C), the actual execution and processing details of that task are monitored through the Job Queue . According to the Archer Administration II curriculum, once a user clicks "Import," the task is handed off to the Job Engine.

To see if the import was successful, how many rows were processed, or if any errors occurred, the administrator must navigate to Integration > Review Job Queues . This interface provides the granular details of the "Job Status," including start/end times and the specific results of the processing. This is consistent with how Archer handles all background tasks (Feeds, Recalculations, etc.). The "Data Imports" screen itself primarily serves as the portal for uploading the file and mapping fields, whereas "Review Job Queues" is the operational dashboard for tracking the actual work performed by the Archer services.

In Archer, the LDAP Synchronization process is a comprehensive identity management tool. According to the Archer Administration II curriculum, its primary purpose is to ensure that the Archer user database mirrors the corporate directory (Active Directory/LDAP). It is not limited to just creating accounts or linking groups; its most critical function is the automation of the user lifecycle .

When the sync runs, it checks for changes in the LDAP source. If a user’s department or email changes in Active Directory, Archer updates the user profile data accordingly. Most importantly for security, if a user is disabled or removed from the LDAP group/OU being synced, Archer can automatically deactivate the account (or move it to a "terminated" status) based on the "Missing Person" configuration in the LDAP setup. This prevents unauthorized access by former employees. Options C and D are "Only" statements that describe small portions of the tool's capability, whereas Option B captures the ongoing maintenance and security synchronization that is the hallmark of the Archer LDAP service.

Dynamic Filtering is a sophisticated feature that allows Archer to filter data based on the context of the current record or the current user. In Archer Administration II , this is highlighted as a tool for improving the user experience by reducing "data noise."

Record Lookup (A): Allows you to filter the available records in a lookup based on a value in the current record (e.g., only show "Users" that belong to the "Department" selected on the form).

Calculated Cross Reference (B): Uses dynamic logic to automatically link records based on matching field values.

Report Object (C): When a report is placed on a record as a "Record-Level Report," Dynamic Filtering ensures the report only shows data related to that specific record (e.g., showing only "Findings" related to "Asset A" when viewing Asset A).

Advanced Search (D) does NOT support Dynamic Filtering in the same "contextual" sense; Advanced Searches use static filters or "Current User" filters, but they do not dynamically react to field values in a specific source record during the search build process like the other three objects.