매달, 우리는 1000명 이상의 사람들이 시험 준비를 잘하고 시험을 잘 통과할 수 있도록 도와줍니다.
Archer Certified Administrator-Expert 온라인 연습
최종 업데이트 시간: 2026년06월04일
당신은 온라인 연습 문제를 통해 Archer Archer Expert 시험지식에 대해 자신이 어떻게 알고 있는지 파악한 후 시험 참가 신청 여부를 결정할 수 있다.
시험을 100% 합격하고 시험 준비 시간을 35% 절약하기를 바라며 Archer Expert 덤프 (최신 실제 시험 문제)를 사용 선택하여 현재 최신 70개의 시험 문제와 답을 포함하십시오.
정답:
Explanation:
The Archer Formula Builder is equipped with a built-in documentation tool specifically designed to assist administrators with syntax and logic. As taught in the Archer Administration II course, clicking the "Help" or "Info" icon within the Formula Builder interface provides a searchable library of all available functions.
For the COUNT vs. COUNTA dilemma, the Help section clarifies that COUNT is typically used for numeric values, whereas COUNTA (Count All) counts any cell that is not empty, including text and dates. This built-in resource provides the exact syntax and common use-case examples, making it the most efficient and standard "best practice" for self-service troubleshooting.
Options C and D are inefficient for such a common task, and Option A is a "trial and error" approach that can lead to database clutter and performance issues if calculations are built incorrectly during the testing phase.
정답:
Explanation:
In the Archer Security Parameters configuration (found in the Archer Control Panel or the Administration workspace), administrators define the "Maximum login attempts." According to the Archer Administration II curriculum, when a user exceeds this threshold (e.g., five failed attempts), the system automatically updates their account status to Locked.
It is important to distinguish "Locked" from "Inactive" or "Disabled." An Inactive or Disabled account usually implies an administrative action or a termination of the user's employment. A Locked status is a temporary security measure triggered by the system to prevent "brute force" attacks. Depending on the Security Parameter settings, a locked account may automatically unlock after a specified duration (e.g., 30 minutes), or it may require an administrator to manually click the "Unlock" button within the user's profile. This distinction allows administrators to run reports specifically on "Locked" users to identify potential security threats or users who simply need assistance with their credentials.
정답:
Explanation:
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.
정답:
Explanation:
In modern Archer environments (post-version 6.x), the Archer Job Engine Service is the primary service responsible for executing asynchronous tasks, including Data Feeds. When a Data Feed is initiated, it is placed in the queue. If the status remains "Pending," it indicates that the task has been recognized by the database, but no service has "picked it up" to begin processing.
As detailed in the Archer Administration II troubleshooting modules, the Job Engine is the "worker" that handles these requests. If this service is stopped, paused, or stuck on the application server, all scheduled and manual feeds will remain in a "Pending" state indefinitely. While the Queuing Service (Option D) is involved in the initial placement of the task, the actual execution and the transition out of "Pending" into "In Progress" is the responsibility of the Job Engine. The Indexing Service (Option C) handles search keyword indexing and is unrelated to data feed execution.
정답:
Explanation:
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.
정답:
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 Search Svc (Search Service) within the SOAP API includes the Execute Search and Search Records By Report 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.
정답:
Explanation:
In a standard corporate environment where users are already logged into a Windows Domain, Windows Integrated SSO (WIA)is considered the "easiest" and most seamless method. According to the Archer installation guides, WIA utilizes the NTLM or Kerberos protocols already built into the Windows OS and Internet Information Services (IIS).
Because the web server and the user's workstation share a common trust via Active Directory, the user is authenticated automatically without needing to provide credentials or interact with a third-party identity provider (IdP). While Federated SSO (Option C), like SAML, is more robust for cloud or multi-platform environments, it requires significantly more configuration, including certificate exchanges and metadata mapping. Token Based SSO (Option B) often requires custom coding or specialized header injection. For a pure Windows-based internal environment, Windows Integrated SSO provides the most "out-of-the-box" experience for both the administrator and the end-user.
정답:
Explanation:
To build a hierarchical view within a single application (like a "Manager" field in the Contacts application that points back to another record in the Contacts application), Archer utilizes Internal References. As taught in the Archer Administration II Advanced Search module, when an application references itself, you can use Directional Search logic to traverse the hierarchy.
By configuring the search to look "Upstream" or "Downstream" through the internal reference, Archer can recursively find all subordinates under a manager or all managers above an employee. This allows the system to flatten a complex organizational tree into a readable report. External References (Option B) are used between different applications, and Statistical Search (Option D) is used for mathematical aggregations (Sum, Count, Average). Only the combination of Internal References and Directional Search provides the specialized recursive logic required to map out a multi-level organizational hierarchy.
정답:
Explanation:
In the Archer security hierarchy, Access Roles are the primary mechanism used to grant functional access to an application. According to the Archer Administration II curriculum, an Access Role defines "what" a user can do (Create, Read, Update, Delete) within a specific application. While Groups (Option B) are used to organize users, a group itself does not grant permissions until that group is linked to an Access Role.
Record Permission Fields (Option D) are used for "Record-Level Security"―narrowing down which specific records a user can see―but they cannot grant access to the application itself if the user doesn't first have an Access Role granting them entry DDEs. (Option C) are used for UI automation and cannot manage security permissions. Therefore, to provide a user with the ability to see an application icon in their workspace and interact with its data, an administrator must assign them to an Access Role that has the "Read" right (and potentially others) selected for that specific application module.
정답:
Explanation:
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 internal applications, such as feeding "Findings" from various modules into a centralized "Master Findings" application.
정답:
Explanation:
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.
정답:
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.
정답:
Explanation:
The Advanced Workflow Job Troubleshooting tool is a runtime utility designed to manage individual "instances" of records currently enrolled in a workflow. It is used to fix records that are stuck due to errors. According to the Advanced Workflow Beyond the Basics guide, this tool is purely for operational maintenance (Cancel, Reset, Restart, or "Force" movement).
Editing the Advanced Workflow structure (changing the flowchart, adding nodes, or modifying logic) cannot be done within the Troubleshooting tool. Workflow design changes must be made in the Application Builder under the Workflow tab. Attempting to "fix" a logic error by changing the design is a development task, whereas the Troubleshooting tool is an administrative task for existing data. Furthermore, editing a workflow requires saving a new version and potentially migrating active jobs, a process entirely separate from the record-level "Reset/Cancel" functions found in the Job Troubleshooting interface.
정답:
Explanation:
In Archer, the LDAP Synchronization process is a comprehensive identity management tool. According to the Archer Administration II curriculum, its primary purpose is to ensure that the Archer user database mirrors the corporate directory (Active Directory/LDAP). It is not limited to just creating accounts or linking groups; its most critical function is the automation of the user lifecycle.
When the sync runs, it checks for changes in the LDAP source. If a user’s department or email changes in Active Directory, Archer updates the user profile data accordingly. Most importantly for security, if a user is disabled or removed from the LDAP group/OU being synced, Archer can automatically deactivate the account (or move it to a "terminated" status) based on the "Missing Person" configuration in the LDAP setup. This prevents unauthorized access by former employees.
Options C and D are "Only" statements that describe small portions of the tool's capability, whereas Option B captures the ongoing maintenance and security synchronization that is the hallmark of the Archer LDAP service.
정답:
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.