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 the Archer platform, the Recalculation Schedule (found within the application's General Tab) is a powerful tool, but it can become a performance bottleneck if not configured efficiently. When a recalculation job is triggered, the Archer services must evaluate every record in the application to determine if calculations need to be updated. According to the Archer Administration II curriculum, the most effective way to optimize this process is by using Calculation Filters .

By selecting option A, you are instructing the system to ignore records that are irrelevant to the specific business logic (e.g., records that are already "Expired," "Rejected," or "Draft"). By filtering the schedule to run only for "Approved" requests, the job engine processes a significantly smaller subset of data, which reduces the load on the Async Service and speeds up the completion time. Option B would likely slow the system down further by adding logical complexity to the calculation itself. Option C (Data-Driven Events) is not suitable for date-based triggers because DDEs only fire upon a record "Save" event; they cannot proactively "watch" a date to trigger a change without user intervention or a scheduled recalculation.

LDAP Synchronization is an asynchronous task managed by the Archer Job Engine . According to the Archer Installation and Troubleshooting guide, all tasks that are processed by the background Job Engine—including Recalculations, Notifications, and LDAP Syncs—capture their detailed execution data and error stack traces in the Job Framework log files .

These logs are typically found on the Services server in the \Logs directory (e.g., Archer.JobFramework.log). When an LDAP sync fails (perhaps due to a service account lockout or a network timeout reaching the Domain Controller), the error will not appear in the Configuration Service (Option D), which only handles ACP settings, nor the Queuing Service (Option C), which only manages the "hand-off" of tasks. The Job Framework log is the granular technical record that administrators must consult to identify the specific LDAP error codes (like "52e" for invalid credentials) returned by the directory server.

In the Archer security model, record-level access is determined by the complex intersection of Access Roles , Groups , and Record Permission Fields . According to the Archer Administration II curriculum, the Investigate Access tool is the primary diagnostic utility for troubleshooting "Why can't User X see Record Y?"

Unlike standard reports, Investigate Access allows an administrator to select a specific user and a specific record (or application) and run a simulation. The tool then provides a detailed breakdown of the "Final Access" (Read, Update, Delete) and, crucially, explains how that access was derived. It will highlight if the user is being granted access via a specific Group, if a Record Permission field is restricting them, or if their Access Role lacks the necessary rights. This is more efficient than the Access Control Reports (Option C), which provide a broad overview of permissions but do not provide the record-specific context that "Investigate Access" offers for pinpoint troubleshooting.

In the Manage Users section of Archer, the platform uses global defaults to ensure that new accounts are created with a baseline security posture. According to the Archer Administration II security module, every new user record is automatically assigned the Default Security Parameter and the Default Access Role defined in the instance settings.

The Security Parameter (Option D) governs password complexity, expiration, and session timeouts. The Default Access Role typically provides very limited "Read" access to ensure the user can at least log in to the workspace, but usually requires further administrative adjustment to grant functional permissions. A Username (Option A) must be manually entered or mapped from LDAP; Archer cannot guess a unique username. Similarly, email addresses and passwords require specific input or integration triggers. By automatically assigning the default Security Parameter and Access Role, Archer ensures that no user is created without essential security governance already in place.

According to the Archer API Guide and Administration II materials, the Archer APIs have specific formatting requirements based on their architecture. The SOAP API (Simple Object Access Protocol) is strictly bound to the XML-based SOAP protocol. It uses a Web Services Description Language (WSDL) to define the structure of its messages, and these messages must be formatted as XML . It cannot process or return JSON payloads.

In contrast, the RESTful API is more flexible; while it defaults to JSON for modern integrations, it is capable of supporting both XML and JSON depending on the "Content-Type" and "Accept" headers provided in the request. The Content API , which is a specific subset of the Archer RESTful infrastructure, also follows these multi-format capabilities. Therefore, the statement that the SOAP API can use JSON is the incorrect one. For administrators building integrations, understanding this distinction is vital, as modern web applications typically prefer JSON, but legacy Archer SOAP services will reject any request that is not valid XML.

Actions by E-mail (ABE) is a feature designed to allow executives and busy stakeholders to progress a workflow without logging into the Archer UI. According to the Advanced Workflow Beyond the Basics course, ABE notifications include specific "action buttons" (e.g., Approve, Reject, Needs More Info).

When a user clicks a button, a new email is generated with a unique encoded string. If the user types a message in that reply email, the Archer Mail Processing Service parses the response. It not only moves the record to the next node based on the button clicked but also captures any text the user typed and appends it to the Workflow Action History (or a designated "Comments") field. This ensures that the rationale for the decision is audited within the record. Option A is incomplete because it ignores the comment-capturing capability, and Option C is incorrect because ABE does not support complex UI elements like drop-down menus within the email client.

When moving data between two applications within the same Archer environment (often called an "Archer-to-Archer" feed), the Archer Web Services Transporter is the standard and recommended method. As detailed in the Archer Administration II Data Feed module, this transporter uses Archer’s own API (Web Services) to authenticate and "read" a report from the source application.

The transporter then passes that data to the Target section of the feed for mapping. Using a Database Query Transporter (Option C) directly against the Archer back-end SQL tables is strongly discouraged and often unsupported because it bypasses the application logic and security layers. The File Transporter (Option B) would require an intermediate step of exporting data to a CSV first. The Web Services Transporter allows for a direct, secure, and API-compliant way to keep data synchronized between inter nal applications, such as feeding "Findings" from various modules into a centralized "Master Findings" application.

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.

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.