Free Archer Archer-Expert Practice Exam with Questions & Answers | Set: 2

In a distributed Archer environment, the Archer Configuration Certificate is used to encrypt and secure communication between the Archer Control Panel (ACP) and the various server nodes. As taught in Archer Administration II , this certificate ensures that only authorized servers can join the instance and access the encrypted configuration files (like settings.config).

The certificate must be installed on all Web and Services servers. The Web server requires it to process user requests and communicate with the ACP, while the Services server (which handles the Job Engine, Indexing, and Workflow) requires it to decrypt the task instructions it receives. The SQL Server (Option B and C) does not require the Archer Configuration Certificate because it interacts with Archer via standard SQL authentication or Windows Authentication protocols at the database layer; it does not run the Archer Configuration Service. "DC servers" (Domain Controllers) are also outside the scope of this certificate requirement.

This question reinforces a critical security concept in Archer Administration II . LDAP Synchronization is not just a "one-time" user creation tool; it is a lifecycle management service. While it does create accounts and associate groups, its most vital ongoing function is the synchronization of state .

If a user's title changes in Active Directory, the next LDAP sync will update that title in Archer, ensuring that reports and workflows based on user attributes remain accurate. Furthermore, if a user is removed from the corporate directory, the LDAP sync identifies them as a "Missing Person" based on the administrator's configuration and can automatically deactivate the Archer account. This automated deactivation is a core compliance requirement for most organizations to ensure that terminated employees lose access to sensitive GRC data immediately. Options A and C are incorrect because they use the word "Only," which ignores the broader, dynamic maintenance capabilities of the service.

In the Data Feed Manager , the "Target Record Processing" setting on the Run Configuration tab determines how Archer handles records that are not present in the current source file. As taught in Archer Administration II , selecting the Delete radio button (often referred to as a "destructive feed" or "mirroring") instructs Archer to compare the source file to the target application.

If the feed finds records in the target application that do not match the keys provided in the source file, it will delete them. In this scenario, since there are only 20 entries in the source file, Archer will keep (or create) those 20 records and delete the remaining 80 records that were already in the system but were missing from the source. Consequently, the final count in the target application will be 20. This setting is typically used for synchronization tasks where Archer must exactly match an external "system of record." Administrators are cautioned when using this setting, as it can lead to massive data loss if the source file is accidentally truncated or filtered incorrectly.

According to the Archer Administration and Security documentation, Single Sign-On (SSO) integration provides a multi-faceted advantage for both the end-user and the system administrator. Reduced Password Fatigue occurs because users no longer need to remember unique credentials for Archer, which directly leads to a decrease in Help Desk Costs associated with password reset requests. Increased Productivity is achieved through seamless access; users can move from their workstation or corporate portal directly into Archer without the interruption of a manual login prompt.

+1

Furthermore, Improved Security is a primary driver for SSO. By leveraging centralized authentication providers (like Active Directory via SAML 2.0 or Windows Integrated Authentication), Archer administrators ensure that corporate password policies (complexity, rotation, and MFA) are strictly enforced. When an employee leaves the organization and their account is disabled in the central directory, their access to Archer is revoked instantaneously. This eliminates the risk of "orphan accounts" existing within the Archer user database. Therefore, because SSO addresses administrative overhead, user experience, and enterprise-grade security protocols simultaneously, "All these answers are correct" is the verified professional standard.

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.

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.

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.

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.

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.

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.