Archer Expert Certification Exam Guide + Practice Questions Updated 2026

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

Explanation:
In the Archer architecture, search operations―particularly Global Search and Indexing―are handled by the Search service, which operates under the broader Job Framework. According to the Archer Installation and Troubleshooting guide, when a user executes a search that is technically "valid" (meaning the syntax is correct) but fails to return expected results or fails during execution, the details are captured in the Job Framework log files.
These logs provide insight into how the Search service is interacting with the Lucene indexes. If the index is corrupt or if the search query is timing out, the Job Framework logs (usually found in the \Logs directory on the Services server) will contain the specific stack traces or warnings. The Configuration Service (Option A) only logs system-level startup and ACP connectivity, and the Data Feed Service (Option D) is irrelevant to UI search queries. Reviewing the Job Framework logs is the standard first step for administrators when users report that "search isn't working" despite records clearly existing in the system.

Explanation:
In Advanced Workflow (AWF), logic-based branching is handled by the Evaluate Content node. As taught in the Advanced Workflow Beyond the Basics course, this node acts as a "decision engine" within the workflow. An administrator configures one or more rules within the node that evaluate the fields of the record currently in the workflow.
Based on whether these rules evaluate to true or false, the record is routed down different paths (outbound transitions). For example, an Evaluate Content node might check the "Risk Rating" of a record; if the rating is "High," it transitions to an Executive Approval node; if it is "Low," it transitions directly to the Archive node. This is distinct from a User Action node (Option D), where the path is chosen manually by a person, or an Update Content node (Option B), which simply changes a field value without necessarily redirecting the workflow path.

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

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