Archer-Expert Dumps Updated Aug 04, 2026 Practice Test and 72 unique questions
2026 Latest 100% Exam Passing Ratio - Archer-Expert Dumps PDF
NEW QUESTION # 20
Details such as installation history, applications, solutions, jobs, Top 10 field histories are viewed in:
- A. Application builder Report
- B. Access Control Report
- C. Installation Report
- D. Instance Report
Answer: D
Explanation:
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.
NEW QUESTION # 21
When selecting "Load Fields" in the Source Definition tab > Source Data sub-tab of an Archer Web Services Transporter Data Feed, no fields appear. What should you check to fix this?
- A. Confirm the Data Feed is set to Active.
- B. Confirm the settings on the Transport Configuration section within the Source Connection tab are correct.
- C. Confirm the Data Feed target application or questionnaire is set correctly.
- D. Confirm the settings on the Source Definition tab > Data Filter sub-tab are correct.
Answer: B
Explanation:
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.
NEW QUESTION # 22
Which statement is NOT true regarding Bulk Update of Advanced Workflow jobs?
- A. Making changes to a workflow can make existing jobs fail.
- B. If there are workflow jobs in progress, you will receive a warning which tells you how many jobs may be affected by this update.
- C. Bulk update jobs will automatically skip records enrolled in a workflow but already in an error state.
- D. Only one update job can be run at the same time.
Answer: C
Explanation:
The Bulk Update Jobs feature is used to migrate active records from one version of an Advanced Workflow (AWF) to another. As taught in Advanced Workflow Beyond the Basics , Archer is designed to be cautious but thorough. Statement A is NOT true because the Bulk Update process actually attempts to evaluate all records targeted for migration. If a record is in an error state, the Bulk Update tool provides an opportunity to see if the new workflow version can resolve that state or if it remains "Incompatible." Statements B, C, and D are all accurate reflections of the platform's behavior. Archer will indeed warn you about the volume of affected records (B), and the system enforces a "one-at-a-time" rule for Bulk Updates (C) to prevent database deadlocks and performance spikes. Furthermore, it is a known risk (D) that structural changes (like deleting a node where records currently reside) can cause those specific jobs to fail during or after an update. Therefore, administrators must use the "Compatibility" check within the Bulk Update interface to identify and resolve these issues before finalizing the migration.
NEW QUESTION # 23
The Open Data Protocol (OData) allows ...
- A. The SOAP API to perform Advanced Search and subsequently run reports.
- B. The RESTful API to narrow down the responses sent back from the server.
- C. The SOAP API to narrow down the responses sent back from the server.
- D. The RESTful API to perform Advanced Search and subsequently run reports.
Answer: B
Explanation:
The RESTful API in Archer utilizes the OData (Open Data Protocol) standard to provide powerful querying capabilities. According to the Archer Administration II integration documentation, OData allows developers to use specific URL parameters-such as $filter, $select, $top, and $orderby-to refine the data returned by the API.
Without OData, a REST call might return every field for every record in an application, leading to significant overhead and slow response times. By using OData, the client can "narrow down the responses" by requesting only specific fields (using $select) or only records that meet certain criteria (using $filter). This is fundamentally different from the SOAP API (Options B and D), which relies on structured XML search requests. OData is what makes the RESTful API efficient for mobile applications and external integrations that require specific, lightweight data payloads.
NEW QUESTION # 24
SAML SSO facilitates the user login into a Service Provider (Archer) through the Identity Provider (eg: Okta).
- A. TRUE
- B. FALSE
Answer: A
Explanation:
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.
NEW QUESTION # 25
Which users are capable of performing data imports?
- A. Any user with proper access role permissions
- B. Members of the Data Import group
- C. Only Report Administrators
- D. Only System Administrators
Answer: A
Explanation:
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.
NEW QUESTION # 26
Assume you make changes to an existing workflow design but you don't run the Bulk Update Jobs. What will happen to any records which existed before making the changes to the AWF?
- A. The active jobs for these records will fail
- B. The jobs will be marked as cancelled
- C. The records will process in the original version they were enrolled in.
- D. The records will automatically enroll in the new version of AWF
Answer: C
Explanation:
In Archer Advanced Workflow, "Versioning" is a core concept designed to ensure data integrity. When a record enters a workflow, it is "enrolled" in the specific version of the workflow that is active at that moment.
According to the Advanced Workflow Beyond the Basics curriculum, if an administrator modifies the workflow (e.g., adding a new node or changing a path) and saves it as a new version, the existing records do not automatically move to that new version.
Instead, they remain in the original version they were enrolled in. This prevents active records from
"breaking" if a node they were currently sitting on was deleted in the newer version. To move existing records to the latest logic, the administrator must manually use the Bulk Update Jobs tool found in the Advanced Workflow tab of the application. This tool validates whether the records can safely transition from the old version's current state to a corresponding state in the new version. Without this manual action, the records will continue to follow the "legacy" path until they complete the workflow.
NEW QUESTION # 27
Which API(s) are capable of running Archer reports?
- A. RESTful API
- B. All of the Archer APIs
- C. Content API
- D. SOAP API
Answer: D
Explanation:
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.
NEW QUESTION # 28
Select the service which must always run for Archer to properly function.
- A. Queuing service
- B. Configuration service
- C. Job Engine service
- D. LDAP Synchronization service
Answer: B
Explanation:
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.
NEW QUESTION # 29
Where are LDAP-related errors logged?
- A. Configuration service log file
- B. Data Feed Service log file
- C. Job framework log file
- D. Queuing service log file
Answer: C
Explanation:
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.
NEW QUESTION # 30
Which of the following is true about the report content in a Scheduled Report Distribution?
- A. Content in the attached report depends on the access rights of the user who created the report.
- B. Content in the attached report depends on the access rights of the administrator who built the Scheduled Report Distribution.
- C. Content in the attached report varies based on access rights granted to the recipient.
- D. Content in the attached report will be updated in the recipient's inbox with real-time data.
Answer: B
Explanation:
Scheduled Report Distributions behave differently than standard "On-Demand" reports. According to the Archer Administration II curriculum, when a report is scheduled for distribution (e.g., emailed as a PDF or Excel file), the Archer platform must "impersonate" a user to run the query and generate the file.
The platform uses the security context of the user who configured the Scheduled Report Distribution (typically an administrator). This means that all recipients of the email will see the exact same data-the data that the administrator is authorized to see. This is a critical security consideration: if an administrator has
"System Administrator" rights and schedules a report for a group of low-privilege users, those users may see sensitive data in the attachment that they would not be able to see if they logged into Archer directly. Option B is incorrect because the system does not run a separate query for every individual recipient's unique permissions at the time of the email burst.
NEW QUESTION # 31
If a valid global search returns no results, where is that logged?
- A. Configuration service log file
- B. Data feed service log file
- C. Job framework log file
- D. Queuing service log file
Answer: C
Explanation:
In the Archer architecture, search operations-particularly Global Search and Indexing -are handled by the Search service, which operates under the broader Job Framework . According to the Archer Installation and Troubleshooting guide, when a user executes a search that is technically "valid" (meaning the syntax is correct) but fails to return expected results or fails during execution, the details are captured in the Job Framework log files .
These logs provide insight into how the Search service is interacting with the Lucene indexes. If the index is corrupt or if the search query is timing out, the Job Framework logs (usually found in the \Logs directory on the Services server) will contain the specific stack traces or warnings. The Configuration Service (Option A) only logs system-level startup and ACP connectivity, and the Data Feed Service (Option D) is irrelevant to UI search queries. Reviewing the Job Framework logs is the standard first step for administrators when users report that "search isn't working" despite records clearly existing in the system.
NEW QUESTION # 32
Which would be an accurate function(s) description for Archer LDAP Synchronization?
- A. Only associates Archer users/groups with domain users/groups
- B. None of these answers are correct
- C. Updates user profile data and deactivates accounts based on LDAP changes
- D. Only creates accounts for new users found on the LDAP server
Answer: C
Explanation:
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.
NEW QUESTION # 33
Which Archer feature allows you to connect to and interact with an external data source without duplicating data into Archer?
- A. Data Gateway
- B. Data Import
- C. Data Feed
- D. APIs
Answer: A
Explanation:
This is a core concept of the Archer Data Gateway (ADG) feature. While traditional Data Feeds (Option A) and Data Imports (Option C) work by pulling a copy of external data and saving it into the Archer SQL database, Data Gateway functions differently. It provides a "window" into an external data source.
As taught in the Archer Administration II integration module, ADG allows users to view and interact with data stored in external SQL databases or other systems as if the data were inside Archer, but the information remains in the source system. This is crucial for high-volume data or sensitive information where
"duplication" is prohibited by policy or storage constraints. APIs (Option D) are used to programmatically move data but still generally involve moving a copy of that data. Data Gateway is the only listed feature specifically designed for "non-duplicating" interaction.
NEW QUESTION # 34
In preparation for this quarter's scheduled questionnaire campaign, you are asked to delete a question and add another to the questionnaire. How do these changes impact new and existing questionnaire records?
- A. Both changes will impact new and existing questionnaire records.
- B. Deleting a question will impact new and existing questionnaire records. Adding a question will impact only new questionnaire records.
- C. Deleting a question will impact only new questionnaire records. Adding a question will impact new and existing questionnaire records.
- D. Both changes will impact only new questionnaire records, but existing ones will remain the same.
Answer: A
Explanation:
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.
NEW QUESTION # 35
What is the main difference between an environment and an instance in Archer?
- A. An environment is a single system, and an instance is a collection of systems.
- B. An environment can host multiple instances, and each instance has its own database and file repository.
- C. An instance can host multiple environments.
- D. An environment and an instance are the same.
Answer: B
Explanation:
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.
NEW QUESTION # 36
......
Verified Archer-Expert dumps Q&As - 100% Pass from PracticeVCE: https://vceplus.practicevce.com/Archer/Archer-Expert-practice-exam-dumps.html