Practice Free Archer-Expert Archer Certified Administrator-Expert Exam Questions Answers With 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.

In modern Archer environments (post-version 6.x), the Archer Job Engine Service is the primary service responsible for executing asynchronous tasks, including Data Feeds. When a Data Feed is initiated, it is placed in the queue. If the status remains "Pending," it indicates that the task has been recognized by the database, but no service has "picked it up" to begin processing.

As detailed in the Archer Administration II troubleshooting modules, the Job Engine is the "worker" that handles these requests. If this service is stopped, paused, or stuck on the application server, all scheduled and manual feeds will remain in a "Pending" state indefinitely. While the Queuing Service (Option D) is involved in the initial placement of the task, the actual execution and the transition out of "Pending" into "In Progress" is the responsibility of the Job Engine. The Indexing Service (Option C) handles search keyword indexing and is unrelated to data feed execution.

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.

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.

While the standard Archer Application Builder supports a wide array of field types, the Questionnaire module uses a more specialized subset of fields within the Question Library . According to the Questionnaires and Assessment Maintenance curriculum, questions are designed to gather specific response data that can be scored.

Valid question types include Values List (for multiple choice), Date (for timestamped responses), Numeric (for quantitative data), and Text (for qualitative comments). The User/Groups List is also a valid question type, often used to identify stakeholders or owners during an assessment. However, an Attachment is not a standalone question type in the library. In Archer Questionnaires, attachments are typically handled as "supporting evidence" linked to a specific question or the record as a whole, but you cannot define a question as an "Attachment type" in the same way you define a "Values List" question.

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.

In the Archer Questionnaire module, Display Rules function similarly to Conditional Layouts in standard applications, but they operate within the specific context of the Assessment/Questionnaire record. These rules are "active" logic. According to the Questionnaires and Assessment Maintenance curriculum, these rules are evaluated every time the questionnaire record is updated .

This means as a user is actively answering questions, the system evaluates the responses in real-time. If a user selects "Yes" to a specific question, the display rule immediately triggers to show the follow-up questions. If they change it to "No," the follow-up questions are hidden. This real-time evaluation ensures a streamlined user experience, preventing the user from seeing irrelevant questions. This is distinct from a "Save" event (Option D); if the rules only evaluated on save, the user would have to constantly save the record to see the next set of questions, which would be highly inefficient.

The Advanced Workflow Job Troubleshooting tool is a runtime utility designed to manage individual "instances" of records currently enrolled in a workflow. It is used to fix records that are stuck due to errors. According to the Advanced Workflow Beyond the Basics guide, this tool is purely for operational maintenance (Cancel, Reset, Restart, or "Force" movement).

Editing the Advanced Workflow structure (changing the flowchart, adding nodes, or modifying logic) cannot be done within the Troubleshooting tool. Workflow design changes must be made in the Application Builder under the Workflow tab. Attempting to "fix" a logic error by changing the design is a development task, whereas the Troubleshooting tool is an administrative task for existing data. Furthermore, editing a workflow requires saving a new version and potentially migrating active jobs, a process entirely separate from the record-level "Reset/Cancel" functions found in the Job Troubleshooting interface.

As detailed in the Archer Installation and Troubleshooting guide, the Archer Configuration Service is the foundational "heartbeat" of the platform. While the Job Engine (Option D) and Queuing Service (Option B) are essential for processing background tasks, the system cannot initialize or connect to the instance database without the Configuration Service.

The Configuration Service is responsible for retrieving settings from the Archer Control Panel (ACP) and providing them to the web server and other services. If this service is stopped, the Archer web interface will fail to load, and administrators will be unable to make any changes to the instance through the ACP. LDAP Synchronization (Option C) is a scheduled task and does not need to be running constantly for the platform to remain operational. Therefore, from an architectural standpoint, the Configuration Service is the mandatory prerequisite for all other platform functions.

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.

In a Multi-Host (Distributed) Environment , Archer components (Web, Application, and Database tiers) are spread across multiple physical or virtual machines to ensure high availability and scalability. According to the Archer Installation and Troubleshooting guides within the Administration II curriculum, it is a technical requirement that all servers within the Archer instance be on the same network or have high-speed, low-latency connectivity between them. This is because the Archer Control Panel (ACP) and the various services (Async, Indexing, Queuing) must communicate constantly to synchronize metadata and process jobs.

Option A is incorrect because the File Store must be accessible by both the Web and Services servers to handle attachments. Option B describes a "Single-Host" setup, not a multi-host one. Option C is false because if you have multiple Web Servers, a Load Balancer is mandatory to distribute user traffic and provide failover. Without being on the same network/segment, the latency would cause the Archer Services to "time out," leading to job engine failures and significant performance degradation across the platform.

The Archer LDAP Synchronization service is a "one-way" synchronization tool from the Directory Server (e.g., Active Directory) to Archer.

A and D are correct: The service allows for the synchronization of users and groups (D), ensuring that any updates—such as name changes, department updates, or account deactivations (A)—made in the directory server are mirrored in Archer.

B is incorrect: LDAP Synchronization does not facilitate "automatic" login (SSO). While LDAP Authentication can be used to verify a password, the seamless "no username/password" experience is provided by Windows Integrated SSO or SAML , which are distinct from the synchronization service.

C is incorrect: Archer cannot write back to the organization's directory server. It is a consumer of LDAP data, not a manager of it. Changes made in Archer (like updating a phone number in the User Profile) will not be pushed back to Active Directory; in fact, they will likely be overwritten by the next LDAP sync.

The Data Import tool is designed for strict adherence to application business rules. According to the Archer Administration II curriculum, required fields are mandatory for the creation of any record. If a source file contains even a single row that is missing data for a "Required" field, the validation engine will trigger an error.

Unlike the Data Feed Manager , which can be configured to "Skip" errors and continue, a standard Data Import is an "all or nothing" operation by default when it encounters critical structural failures like missing required data. The import process will stop, and no records from that file will be committed to the database. This ensures that the application does not end up with "broken" records that bypass the logic intended by the administrator. To fix this, the administrator must either populate the missing data in the source file or temporarily make the field "Not Required" in the application builder before re-attempting the import.

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

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.