Archer Archer-Expert - Archer Certified Administrator-Expert

The primary driver for Single Sign-On (SSO) in an Archer environment is user convenience and centralized identity management. As taught in Archer Administration II , the "goal" of SSO is to reduce the friction of accessing the platform. By allowing users to leverage their existing corporate credentials (via SAML, Windows Integrated, or LDAP), they can access Archer without needing to maintain a separate, "native" Archer password.

This strategy improves security by centralizing credential management in a single Identity Provider (IdP), where Multi-Factor Authentication (MFA) and account revocation policies can be strictly enforced. Option A is incorrect because SSO actually helps enforce enterprise security parameters rather than bypassing them. Option B is false because SSO is intended for all users, not just admins. Option C describes the opposite of SSO. Ultimately, the successful implementation of SSO ensures that users have a seamless transition into Archer while the organization maintains a high standard of access control.

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.

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.

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

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 Archer Formula Builder is equipped with a built-in documentation tool specifically designed to assist administrators with syntax and logic. As taught in the Archer Administration II course, clicking the "Help" or "Info" icon within the Formula Builder interface provides a searchable library of all available functions.

For the COUNT vs. COUNTA dilemma, the Help section clarifies that COUNT is typically used for numeric values, whereas COUNTA (Count All) counts any cell that is not empty, including text and dates. This built-in resource provides the exact syntax and common use-case examples, making it the most efficient and standard "best practice" for self-service troubleshooting. Options C and D are inefficient for such a common task, and Option A is a "trial and error" approach that can lead to database clutter and performance issues if calculations are built incorrectly during the testing phase.

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.

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 the Archer Security Parameters configuration (found in the Archer Control Panel or the Administration workspace), administrators define the "Maximum login attempts." According to the Archer Administration II curriculum, when a user exceeds this threshold (e.g., five failed attempts), the system automatically updates their account status to Locked .

It is important to distinguish "Locked" from "Inactive" or "Disabled." An Inactive or Disabled account usually implies an administrative action or a termination of the user's employment. A Locked status is a temporary security measure triggered by the system to prevent "brute force" attacks. Depending on the Security Parameter settings, a locked account may automatically unlock after a specified duration (e.g., 30 minutes), or it may require an administrator to manually click the "Unlock" button within the user's profile. This distinction allows administrators to run reports specifically on "Locked" users to identify potential security threats or users who simply need assistance with their credentials.