Archer Archer-Expert Archer Certified Administrator-Expert Exam Practice Test

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.

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.

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.

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.

In the Advanced Workflow Beyond the Basics curriculum, the Wait for Content Update node is identified as the primary tool for time-based automation. While its name suggests it is waiting for a user to change a field, its secondary function is to act as a SLA (Service Level Agreement) timer .

Within the node configuration, an administrator can define an "Escalation" or "Timeout" path. You can set a specific duration (e.g., 5 days). If the expected content update does not occur within that timeframe, the node "times out" and automatically reroutes the record down a secondary transition path—typically to a manager's review or an automated notification. While a User Action node (Option B) can have a "due date," it does not automatically move the record to a different path solely based on time without the Wait for Content Update node logic. Update Content (Option D) and Send Notification (Option A) nodes are instantaneous actions and do not possess the ability to "pause" and monitor for duration.

Archer's Advanced Search provides sophisticated control over how data is returned to the user. Within the search configuration tabs, there is a section dedicated to Result Limits . As detailed in the Archer Administration II search module, this feature is essential for optimizing performance and creating specific types of reports (like "Top 10" or "Bottom 5%").

The administrator has the flexibility to limit the results in two ways:

Fixed Number: For example, "Show only the first 50 records."

Percentage: For example, "Show only the top 10% of records."

This is often combined with sorting; if you sort by "Risk Score" descending and limit the results to the top 10 records, you have successfully created a "Top 10 Risks" report. These limits are applied after the filters have narrowed down the dataset but before the data is rendered in the UI or exported. This dual-capability ensures that administrators can build reports that meet precise business requirements, whether they are based on a specific count or a statistical distribution.

In a standard corporate environment where users are already logged into a Windows Domain, Windows Integrated SSO (WIA) is considered the "easiest" and most seamless method. According to the Archer installation guides, WIA utilizes the NTLM or Kerberos protocols already built into the Windows OS and Internet Information Services (IIS).

Because the web server and the user's workstation share a common trust via Active Directory, the user is authenticated automatically without needing to provide credentials or interact with a third-party identity provider (IdP). While Federated SSO (Option C), like SAML, is more robust for cloud or multi-platform environments, it requires significantly more configuration, including certificate exchanges and metadata mapping. Token Based SSO (Option B) often requires custom coding or specialized header injection. For a pure Windows-based internal environment, Windows Integrated SSO provides the most "out-of-the-box" experience for both the administrator and the end-user.

In Archer Advanced Workflow, "Versioning" is a core concept designed to ensure data integrity. When a record enters a workflow, it is "enrolled" in the specific version of the workflow that is active at that moment. According to the Advanced Workflow Beyond the Basics curriculum, if an administrator modifies the workflow (e.g., adding a new node or changing a path) and saves it as a new version, the existing records do not automatically move to that new version.

Instead, they remain in the original version they were enrolled in. This prevents active records from "breaking" if a node they were currently sitting on was deleted in the newer version. To move existing records to the latest logic, the administrator must manually use the Bulk Update Jobs tool found in the Advanced Workflow tab of the application. This tool validates whether the records can safely transition from the old version's current state to a corresponding state in the new version. Without this manual action, the records will continue to follow the "legacy" path until they complete the workflow.

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 you initiate a manual import from the Data Imports menu (Option C), the actual execution and processing details of that task are monitored through the Job Queue . According to the Archer Administration II curriculum, once a user clicks "Import," the task is handed off to the Job Engine.

To see if the import was successful, how many rows were processed, or if any errors occurred, the administrator must navigate to Integration > Review Job Queues . This interface provides the granular details of the "Job Status," including start/end times and the specific results of the processing. This is consistent with how Archer handles all background tasks (Feeds, Recalculations, etc.). The "Data Imports" screen itself primarily serves as the portal for uploading the file and mapping fields, whereas "Review Job Queues" is the operational dashboard for tracking the actual work performed by the Archer services.

The Security Events Report is the primary auditing tool for tracking administrative and sensitive user actions within the Archer platform. According to the Archer Administration II curriculum, this report captures a broad spectrum of "event-based" security data that standard access reports do not cover.

Specifically, it logs every failed login attempt , which is critical for identifying potential brute-force attacks. It also tracks metadata changes to the security infrastructure, such as when an Access Role is created or deleted , providing an audit trail of who modified the system's permissions. Furthermore, it records password changes initiated by users. While the "Locked Accounts Report" (Option B) only shows users currently barred from the system, the Security Events Report provides the historical context of why those events occurred. It is an essential resource for compliance officers and system auditors to ensure that the integrity of the Archer environment's security configuration remains intact.

This statement is FALSE . The default authentication mechanism for a fresh installation of Archer is Archer Native Authentication . As detailed in the Archer Installation and Troubleshooting guide, when an instance is first created, it relies on the internal Archer database to store usernames and encrypted passwords.

Single Sign-On (SSO), whether it be Windows Integrated, SAML, or LDAP-based, is an opt-in configuration that must be manually enabled and configured by a System Administrator within the Archer Control Panel (ACP) . Native authentication remains the fallback method and is used for the initial "System Administrator" account setup. While most enterprise organizations quickly transition to SSO for security and convenience, the platform itself defaults to its own internal authentication engine to ensure the system is accessible immediately after installation without requiring a pre-existing connection to an Identity Provider (IdP).

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.

This statement is TRUE and represents the standard architecture for Federated Single Sign-On. In the context of SAML (Security Assertion Markup Language), Archer acts as the Service Provider (SP) , which is the application the user wants to access. The Identity Provider (IdP) , such as Okta, PingFederate, or Azure AD, is the system that holds the user's credentials and performs the actual authentication.

As detailed in the Archer installation and security guides, when a user attempts to log into Archer via SAML, Archer sends an authentication request to the IdP. The IdP authenticates the user and sends a "SAML Assertion" (a signed digital token) back to Archer. Archer then validates this token and allows the user access without them ever having to type their password directly into the Archer interface. This workflow is a cornerstone of modern enterprise security, allowing for centralized identity management and the enforcement of Multi-Factor Authentication (MFA) at the IdP level.

The Archer Web Services Transporter is used for "Archer-to-Archer" data feeds. For the "Load Fields" button to work, Archer must be able to successfully authenticate and connect to the source instance's API to retrieve the report metadata.

As detailed in the Archer Administration II Data Feed module, if no fields appear, it almost always indicates a communication failure between the Feed Manager and the Web Service. The Transport Configuration section (found on the Source Connection tab) contains the critical connection details: the Base URL, the Instance Name, and the User Credentials. If the credentials are incorrect, the URL is mistyped, or the "Session Token" cannot be generated, Archer cannot "see" the source report's structure, and thus the field list will remain empty. Checking the connection settings is the primary troubleshooting step before looking at filters or target mappings.

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 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 the Advanced Workflow Beyond the Basics curriculum, administrators are taught how to manage "faulted" or "stuck" workflow jobs using the Advanced Workflow Job Troubleshooting Tool . When a record hits a snag—for example, if a Notification Node fails because of a mail server timeout or a Evaluate Content Node fails due to a missing field value—the job may stop at that specific node.

The Reset option is the specific administrative action used to re-trigger a node. Selecting "Reset" clears the error state of the current node and attempts to execute it again. This is distinct from Restart (Option C), which would typically send the record back to the very beginning of the entire workflow process, potentially duplicating previous steps. Update Job (Option A) is generally used to apply workflow version changes to an active record, and Cancel (Option D) terminates the workflow entirely. For a pinpointed "retry" of a specific failure point, "Reset" is the verified functional command within the troubleshooting utility.

Here are the verified answers and detailed explanations for Questions 8 through 11, strictly aligned with the Archer Administration II and Advanced Workflow Beyond the Basics curriculum standards.

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

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.