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

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

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.

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.

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 environment, LDAP synchronization is an asynchronous process managed by the Archer Support Tools and specific Windows services. When an administrator triggers a manual LDAP sync or a scheduled sync begins, the job is placed into a processing queue within the Archer database. If the status remains "QUEUED" and never progresses to "IN PROGRESS" or "COMPLETED," the primary culprit is almost always the underlying service responsible for picking up that task.

As detailed in the Archer Administration II technical troubleshooting modules, the Archer LDAP Synchronization Service (or in newer versions, the Archer Queuing/Job Engine service) must be in a "Started" state on the web or application server to process these requests. If the service is stopped, hung, or crashed, the job will sit in the queue indefinitely. While network connections (Option C) and configuration settings (Option A) are important, they typically result in an "FAILED" status with an error log rather than a "QUEUED" status. Restarting the entire server (Option B) is an inefficient "last resort" that doesn't address the specific root cause as directly as verifying the service status in the Services console.

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.

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