Archer Updated Archer-Expert Exam Questions and Answers by leonidas

LDAP Synchronization is an asynchronous task managed by the Archer Job Engine . According to the Archer Installation and Troubleshooting guide, all tasks that are processed by the background Job Engine—including Recalculations, Notifications, and LDAP Syncs—capture their detailed execution data and error stack traces in the Job Framework log files .

These logs are typically found on the Services server in the \Logs directory (e.g., Archer.JobFramework.log). When an LDAP sync fails (perhaps due to a service account lockout or a network timeout reaching the Domain Controller), the error will not appear in the Configuration Service (Option D), which only handles ACP settings, nor the Queuing Service (Option C), which only manages the "hand-off" of tasks. The Job Framework log is the granular technical record that administrators must consult to identify the specific LDAP error codes (like "52e" for invalid credentials) returned by the directory server.

To build a hierarchical view within a single application (like a "Manager" field in the Contacts application that points back to another record in the Contacts application), Archer utilizes Internal References . As taught in the Archer Administration II Advanced Search module, when an application references itself, you can use Directional Search logic to traverse the hierarchy.

By configuring the search to look "Upstream" or "Downstream" through the internal reference, Archer can recursively find all subordinates under a manager or all managers above an employee. This allows the system to flatten a complex organizational tree into a readable report. External References (Option B) are used between different applications, and Statistical Search (Option D) is used for mathematical aggregations (Sum, Count, Average). Only the combination of Internal References and Directional Search provides the specialized recursive logic required to map out a multi-level organizational hierarchy.

In Archer, Private Fields are a high-security feature where access is restricted to specific Users or Groups, regardless of their Access Role permissions. When an administrator manages these permissions, the concept of Cascading is vital for hierarchy management.

As taught in Archer Administration II , if you grant a parent group access to a private field and select the "Cascade" option, Archer automatically extends those permissions to every child group within that hierarchy. This follows the standard inheritance model used throughout the platform's security architecture. Without cascading (Option C), only the direct members of the parent group would see the field data, and administrators would have to manually add every subgroup individually. Selecting cascade ensures that as the organization grows and new subgroups are added under the parent, those new members will automatically inherit the necessary access to view or edit the protected field.

While Archer has been aggressively moving toward the RESTful API (Option C) for modern integrations, the ability to execute an existing Archer Report and retrieve the results has historically been a core function of the SOAP API (Web Services). Specifically, the SearchSvc (Search Service) within the SOAP API includes the ExecuteSearch and SearchRecordsByReport methods.

According to the Archer Administration II technical integration documents, the RESTful API is primarily designed for CRUD operations (Create, Read, Update, Delete) on individual records and metadata. While newer versions of the REST API are expanding, the legacy SOAP Web Services remain the primary, verified method for triggering a pre-defined "Saved Report" via an external call. The Content API (Option D) is a subset of the RESTful API focused on record data but lacks the high-level report execution engine found in the SOAP services.