Pass the Archer Archer Certified Administrator Archer-Expert Questions and answers with CertsForce

Mail Merge Templates are the specific feature in Archer designed to bridge the gap between Archer record data and Microsoft Office documents. According to the Archer Administration II curriculum, these templates allow administrators to upload a Word .docx file containing "mail merge tags" that correspond to Archer field aliases.

When a user triggers the mail merge (via the Export button on a record), Archer dynamically replaces those tags with the actual data from the record and generates a finished document. This is the standard method for producing formal reports, certificates, or letters that require specific corporate branding and formatting that cannot be achieved with a standard CSV or PDF export. On Demand Notification Templates (Option C) are for emails, and Scheduled Report Distributions (Option B) are for sending saved Archer reports on a timer, not for creating formatted Word documents based on a single record's context.

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

In the Archer Questionnaire platform, "Target" records (the actual assessments sent to users) are dynamically linked to the Questionnaire Template . Unlike standard applications where record data is "frozen" in the database structure, Questionnaires are highly sensitive to template changes.

According to the Questionnaires and Assessment Maintenance curriculum, if you delete a question from a template, that question (and any responses previously provided) will disappear from all records currently using that template, including existing ones. Conversely, if you add a new question, it will immediately appear on all active assessments that have not yet been "submitted" or "locked." This is why Archer administrators are strictly cautioned to version their questionnaires or "retire" old templates rather than modifying an active one mid-campaign. Making direct changes to an active template causes immediate, global updates across the entire record set, potentially leading to data loss for the deleted items and unexpected work for users seeing the new items.

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.

As detailed in the Archer Installation and Troubleshooting guide, the Archer Configuration Service is the foundational "heartbeat" of the platform. While the Job Engine (Option D) and Queuing Service (Option B) are essential for processing background tasks, the system cannot initialize or connect to the instance database without the Configuration Service.

The Configuration Service is responsible for retrieving settings from the Archer Control Panel (ACP) and providing them to the web server and other services. If this service is stopped, the Archer web interface will fail to load, and administrators will be unable to make any changes to the instance through the ACP. LDAP Synchronization (Option C) is a scheduled task and does not need to be running constantly for the platform to remain operational. Therefore, from an architectural standpoint, the Configuration Service is the mandatory prerequisite for all other platform functions.

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.

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.

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.

In the Questionnaires and Assessment Maintenance curriculum, the Question Library acts as a "blueprint" for the final assessment. When you add a record to the Library, you aren't just adding text; you are defining the metadata for a future field.

The Question Type (e.g., Numeric, Values List, Text) and Display Format (e.g., Radio Buttons vs. Dropdown) are mandatory because they tell the Archer platform how to dynamically generate the user interface when a Questionnaire is launched. When a target record is created from a template, Archer looks at these library fields to determine which database column types to use and how the web browser should render the interaction. Without this information, the system would not know whether to provide a text box for a comment or a list of "Yes/No" options for the respondent.