Free Archer Archer-Expert Practice Exam with Questions & Answers

The Instance Report is a comprehensive diagnostic document that provides a "snapshot" of an entire Archer instance. According to the Archer Administration II curriculum, this report is found within the Archer Control Panel (ACP) or can be generated from the Administration workspace.

It is specifically designed to aid in troubleshooting and system auditing. It contains metadata about the installation history , a list of all applications and solutions , and the status of background jobs . Most importantly, it includes performance-related data such as the Top 10 field histories (identifying which fields are growing the fastest in the database) and record counts. This report is often requested by Archer Support when investigating system-wide performance issues, as it aggregates critical architectural data into a single, readable view that is more holistic than an Access Control or Application Builder report.

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.

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.

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.

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.

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

In a Single-Server Installation (typically used for Sandbox, Development, or small-scale environments), the goal is to consolidate the entire Archer architecture onto one machine. According to the Archer Administration II setup guides, this means the Web Server (IIS), the Archer Services (Job Engine, Indexing), the Advanced Workflow (AWF) service, and the SQL Server Instance Database must all reside on that single host.

While production environments favor a distributed model (Option B) for performance and redundancy, a single-server setup requires that all roles are configured to point to "localhost" or the local server's IP. The administrator must ensure the server has sufficient CPU and RAM to handle the overlapping resource demands of the SQL database engine and the Archer web services simultaneously. Options C and D describe "Distributed" or "Hybrid" models, which contradict the definition of a single-server installation.

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.