Archer-Expert Archer Certified Administrator-Expert Free Practice Exam Questions (2026 Updated)

In the Archer Questionnaire platform, "Target" records (the actual assessments sent to users) are dynamically linked to the Questionnaire Template . Unlike standard applications where record data is "frozen" in the database structure, Questionnaires are highly sensitive to template changes.

According to the Questionnaires and Assessment Maintenance curriculum, if you delete a question from a template, that question (and any responses previously provided) will disappear from all records currently using that template, including existing ones. Conversely, if you add a new question, it will immediately appear on all active assessments that have not yet been "submitted" or "locked." This is why Archer administrators are strictly cautioned to version their questionnaires or "retire" old templates rather than modifying an active one mid-campaign. Making direct changes to an active template causes immediate, global updates across the entire record set, potentially leading to data loss for the deleted items and unexpected work for users seeing the new items.

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.

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.

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

In Archer, Values List fields are strictly validated against the pre-defined options in the field configuration. During a manual Data Import , if the source file contains a value that does not exactly match an existing entry in the Values List, the import for that specific record (or the entire process, depending on settings) will fail.

According to the Archer Administration II guide, for the import to succeed with new data, the administrator must first enable the "Create new values for Values List fields" option in the Data Import settings. If this is not enabled, Archer treats the unknown value as an error. This is a critical data integrity feature that prevents "dirty data" from entering the system. Unlike a Data Feed, which has more advanced "lookup" and "creation" logic, the Data Import tool is less flexible by default to ensure administrators are consciously deciding whether to expand the application's metadata.

The Data Import Wizard offers three distinct processing modes: "Add New Records," "Update Existing Records," and "Add New and Update Existing Records." According to the Archer Administration II curriculum, the "Update Existing Records" mode is highly restrictive. It is used when an administrator only wants to modify records that already reside in the system.

During the import, Archer uses the specified Key Field(s) to find matches between the source file and the target application. If a match is found, the existing record is updated with the new data from the source file. However, if a row in the source file does not have a corresponding match in Archer, that row is simply ignored and discarded . No new records are created. This is a safety measure to prevent the accidental creation of "orphan" or duplicate data when the intent is strictly maintenance of existing content. If an administrator wishes to both update matches and create new records for non-matches, they must specifically choose the "Add New and Update Existing Records" (Upsert) option.

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.

While the Data Feed Manager (Option C) is primarily used to bring data into Archer, the Data Publication Service (DPS) is the specific tool designed to push data out of Archer into an external SQL Server database. As taught in the Data Integration module of Administration II, Data Publication allows an administrator to define a "Publication Task" that maps Archer applications and levels to external database tables.

This is the ideal solution for Sarah's HR request because the HR department can then point their own reporting tools or databases to that external "target" database without ever needing an Archer login. Data Gateway (Option B) is a legacy term or refers to specific API connectors, and Data Import (Option D) is strictly for ingestion. Data Publication ensures that the most recent "Golden Record" of the business hierarchy in Archer is synchronized to the external environment on a scheduled basis, maintaining data consistency across the enterprise.

The Archer Job Monitor is a dedicated administrative interface found within the "Administration" workspace. It is the primary dashboard for monitoring the health of the Archer Job Engine . According to the curriculum, the Job Monitor provides visibility into both scheduled and ad-hoc background tasks, including Data Feeds, Data Publication, Notifications, and Recalculations.

The report displays a chronological list of jobs, their current status (Queued, In Progress, Completed, or Failed), and their start/end times. This is the first place an administrator looks if a notification wasn't sent or a data feed didn't update. Unlike "User access logs" (which track logins) or "System performance metrics" (which are found in the ACP or IIS), the Job Monitor is focused strictly on the execution history of background system tasks, allowing administrators to identify bottlenecks or specific job failures without needing access to the server's event logs.

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

In the Archer platform, a "Calculated Field" is not a separate field type you select from the initial list (like Text or Date). Instead, almost any standard field type can be transformed into a calculated one. According to the Archer Administration II curriculum, the foundational step is to create the field first and then go into the field’s General Tab properties to check the box labeled "Calculate its value."

Once this option is enabled, the "Formula" and "Calculation Properties" tabs appear, allowing the administrator to define the logic. You cannot write a formula (Option A) or validate it (Option D) until the field has been designated as a calculated field. Option C is irrelevant as a "first step," as calculations can be applied to many field types, not just User/Groups lists. By enabling the calculation property first, you signal to the Archer Calculation Engine that this field's value will be managed by the system rather than by manual user input.

The RESTful API in Archer utilizes the OData (Open Data Protocol) standard to provide powerful querying capabilities. According to the Archer Administration II integration documentation, OData allows developers to use specific URL parameters—such as $filter, $select, $top, and $orderby—to refine the data returned by the API.

Without OData, a REST call might return every field for every record in an application, leading to significant overhead and slow response times. By using OData, the client can "narrow down the responses" by requesting only specific fields (using $select) or only records that meet certain criteria (using $filter). This is fundamentally different from the SOAP API (Options B and D), which relies on structured XML search requests. OData is what makes the RESTful API efficient for mobile applications and external integrations that require specific, lightweight data payloads.

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.

When troubleshooting a failure in Advanced Workflow (AWF) notifications, the administrator should start at the most granular level of the recent change. Since the scenario mentions updates were made to the On Demand Notification Templates (ODNT) , that is the most likely point of failure.

According to the Advanced Workflow Beyond the Basics curriculum, for an AWF notification to fire, the node in the workflow must be correctly mapped to an ODNT, and that template must have a valid Recipient (e.g., a field mapping or a specific user) and a "Status" of Active . If the template was accidentally set to Inactive or if the Recipient field mapping was broken during the update, the email will never trigger. While Options A, B, and D are valid system-wide checks, they are less likely to be the cause if other notifications in the system are still working correctly; therefore, validating the specific template is the standard first step.

Archer is a Windows-based enterprise application that relies on the Microsoft technology stack. As detailed in the Archer Installation and Troubleshooting guide, there are three primary prerequisites for a successful deployment:

IIS (Internet Information Services): This is the web server that hosts the Archer web interface and APIs.

SQL Server: Archer requires a Microsoft SQL Server database to store all application data, metadata, and the instance configurations.

Microsoft .NET Framework: Archer is built on .NET; specific versions (such as 4.7.2 or higher, depending on the Archer version) must be installed for the web and service components to function.

Apache (Option A) is an alternative web server used primarily for Linux-based environments and is not a prerequisite or a supported web server for the Archer platform.

The Archer Question Library is a centralized repository of questions used to build questionnaires. According to the Questionnaires and Assessment Maintenance curriculum, the "Out of the Box" (OOTB) content provided by Archer is modular. When an organization licenses a specific Use Case (e.g., IT Security Risk Management, Third Party Governance, or Business Continuity), the relevant question sets for those domains are imported into the library.

For example, an organization that only licenses Third Party Governance will have a Question Library populated with vendor-related assessments (like SIG or ISO-based questions), but they will not see Business Continuity-specific questions unless that use case is also licensed. This ensures that the platform remains uncluttered and relevant to the specific business needs of the organization. The deployment option (On-Premise vs. SaaS) and the support model have no impact on the actual metadata content of the library; it is strictly driven by the licensed functional modules.

The manual Data Import tool has specific structural limitations compared to the more robust Data Feed Manager. As taught in Archer Administration II , Data Imports are designed to handle standard Applications and their associated Sub-Forms .

When importing into an application that contains a sub-form, the administrator can map source columns to the sub-form fields to create multiple sub-form line items for a single parent record. However, Questionnaires (Option A, B, and D) cannot be populated via the standard Data Import tool. Questionnaires utilize a unique "Target/Assessment" architecture that requires either manual launching via a Campaign or the use of the Data Feed Manager with a specialized "Questionnaire" transporter. Because the Data Import tool lacks the ability to handle the complex relationship between the Question Library, the Questionnaire Template, and the Target record, it is restricted to standard application and sub-form data ingestion.