[2026年03月30日]Archer-Expertサンプルには正確で更新された問題
Archer-Expert試験情報と無料練習テスト
質問 # 33
What happens when an administrator selects to cascade private field permissions for a group?
- A. Only members of the selected group would have access to the field; members of any child groups would NOT have access to the field.
- B. Members of the selected group and members of its child groups would have access to the field.
- C. Only members of the selected group and its child groups would have access to the field.
- D. Members of the selected group would NOT have access to the field; members of child groups would have access to the field.
正解：B
解説：
In Archer, Private Fields are a high-security feature where access is restricted to specific Users or Groups, regardless of their Access Role permissions. When an administrator manages these permissions, the concept of Cascading is vital for hierarchy management.
As taught in Archer Administration II , if you grant a parent group access to a private field and select the
"Cascade" option, Archer automatically extends those permissions to every child group within that hierarchy.
This follows the standard inheritance model used throughout the platform's security architecture. Without cascading (Option C), only the direct members of the parent group would see the field data, and administrators would have to manually add every subgroup individually. Selecting cascade ensures that as the organization grows and new subgroups are added under the parent, those new members will automatically inherit the necessary access to view or edit the protected field.
質問 # 34
Which action is recommended before updating an Archer Advanced Workflow?
- A. Add an error handling node at the end for the workflow to catch records which generate errors as a result of the update.
- B. Complete all active jobs before updating the Advanced Workflow.
- C. No special action is needed since Advanced Workflow automatically returns all actively enrolled records to the Start node.
- D. Open the application and deactivate Advanced Workflow before making changes to the workflow process, then reactivate the workflow so all records update.
正解：D
解説：
According to the Advanced Workflow Beyond the Basics curriculum, the safest administrative practice when modifying an active workflow is to briefly deactivate it. When you deactivate the workflow, you prevent new records from entering a potentially "in-flux" process while you are saving new versions.
Once the changes are finalized and the new version is saved, reactivating the workflow allows the system to initialize the new logic. It is important to note that reactivating the workflow does not automatically update existing records (as discussed in previous questions regarding Bulk Update Jobs), but it ensures that the transition between versions is "clean." Option D is often impossible in a production environment with thousands of active records. Option B is factually incorrect as records do not return to the Start node; they stay exactly where they were in their specific version. Deactivating ensures that the Advanced Workflow Service doesn't attempt to process a record against a design that is currently being overwritten or modified by the administrator.
質問 # 35
Where are LDAP-related errors logged?
- A. Queuing service log file
- B. Configuration service log file
- C. Job framework log file
- D. Data Feed Service log file
正解：C
解説：
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.
質問 # 36
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.
正解：B
解説：
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.
質問 # 37
Using LDAP an Administrator can do which of the following? Select all that apply:
- A. Reflect user changes from Archer to organization's directory server
- B. Make users login to Archer automatically without username and password
- C. Allow updates and changes made in the organization's directory server to automatically reflect in Archer
- D. Synchronize an organizations Directory users and groups with an Archer Instance
正解：C、D
解説：
The Archer LDAP Synchronization service is a "one-way" synchronization tool from the Directory Server (e.g., Active Directory) to Archer.
* A and D are correct: The service allows for the synchronization of users and groups (D), ensuring that any updates-such as name changes, department updates, or account deactivations (A)-made in the directory server are mirrored in Archer.
* B is incorrect: LDAP Synchronization does not facilitate "automatic" login (SSO). While LDAP Authentication can be used to verify a password, the seamless "no username/password" experience is provided by Windows Integrated SSO or SAML , which are distinct from the synchronization service.
* C is incorrect: Archer cannot write back to the organization's directory server. It is a consumer of LDAP data, not a manager of it. Changes made in Archer (like updating a phone number in the User Profile) will not be pushed back to Active Directory; in fact, they will likely be overwritten by the next LDAP sync.
質問 # 38
What will happen if the source file for a Data Import contains a row missing required field content for the target application?
- A. The Data Import fails unless the row with the missing required field content is the last row in the file.
- B. The Data Import logs a warning message asking the user to check the source file and processes successfully for the rest of the complete rows.
- C. An administrator must process the file using administrator override.
- D. The Data Import fails without creating or updating any content records.
正解：D
解説：
The Data Import tool is designed for strict adherence to application business rules. According to the Archer Administration II curriculum, required fields are mandatory for the creation of any record. If a source file contains even a single row that is missing data for a "Required" field, the validation engine will trigger an error.
Unlike the Data Feed Manager , which can be configured to "Skip" errors and continue, a standard Data Import is an "all or nothing" operation by default when it encounters critical structural failures like missing required data. The import process will stop, and no records from that file will be committed to the database.
This ensures that the application does not end up with "broken" records that bypass the logic intended by the administrator. To fix this, the administrator must either populate the missing data in the source file or temporarily make the field "Not Required" in the application builder before re-attempting the import.
質問 # 39
Which is NOT a valid question type in the Question Library?
- A. Values List
- B. User/Groups List
- C. Attachment
- D. Date
正解：C
解説：
While the standard Archer Application Builder supports a wide array of field types, the Questionnaire module uses a more specialized subset of fields within the Question Library . According to the Questionnaires and Assessment Maintenance curriculum, questions are designed to gather specific response data that can be scored.
Valid question types include Values List (for multiple choice), Date (for timestamped responses), Numeric (for quantitative data), and Text (for qualitative comments). The User/Groups List is also a valid question type, often used to identify stakeholders or owners during an assessment. However, an Attachment is not a standalone question type in the library. In Archer Questionnaires, attachments are typically handled as
"supporting evidence" linked to a specific question or the record as a whole, but you cannot define a question as an "Attachment type" in the same way you define a "Values List" question.
質問 # 40
What feature in the Administration Menu allows you to troubleshoot users' record permissions?
- A. Admin Notifications
- B. Investigate Access
- C. Manage Users
- D. Access Control Reports
正解：B
解説：
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.
質問 # 41
Administrators can grant users Application access through:
- A. A DDE
- B. Groups
- C. Record Permission Field
- D. Access Roles
正解：D
解説：
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.
質問 # 42
How does the pre-built content of the Question Library vary from one organization to another?
- A. The pre-built Question Library content depends on the use cases licensed.
- B. The pre-built Question Library content depends on the deployment option used.
- C. The pre-built Question Library content varies based on the support model selected.
- D. The pre-built Question Library content is the same for any number of use cases licensed.
正解：A
解説：
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.
質問 # 43
Which API(s) enable the automated creation of packages?
- A. SOAP API
- B. Content API
- C. RESTful API
- D. All of the Archer APIs do this
正解：C
解説：
The Archer Packaging API is a component of the modern RESTful API suite. As organizations move toward DevOps and automated deployment models, the ability to programmatically create and export Archer packages (the containers used to move applications between Dev, Test, and Production) has become essential.
According to the Archer Administration II curriculum, the RESTful API provides endpoints specifically for the Packaging Service . This allows administrators to write scripts that automatically bundle application changes into a .zip package without manually navigating the "Packaging" menu in the Archer UI. The SOAP API (Option B) is primarily focused on record data and search services and does not have comprehensive packaging capabilities. The Content API (Option C) is strictly for record-level content (CRUD operations) and does not interact with the system's metadata packaging engine. Therefore, the RESTful API is the correct tool for automating the "Package Creation" workflow.
質問 # 44
When viewing the Advanced Workflow Job Troubleshooting tool for a record currently enrolled in Advanced Workflow, what option allows you to retry a specific node?
- A. Reset
- B. Restart
- C. Cancel
- D. Update Job
正解：A
解説：
In the Advanced Workflow Beyond the Basics curriculum, administrators are taught how to manage
"faulted" or "stuck" workflow jobs using the Advanced Workflow Job Troubleshooting Tool . When a record hits a snag-for example, if a Notification Node fails because of a mail server timeout or a Evaluate Content Node fails due to a missing field value-the job may stop at that specific node.
The Reset option is the specific administrative action used to re-trigger a node. Selecting "Reset" clears the error state of the current node and attempts to execute it again. This is distinct from Restart (Option C), which would typically send the record back to the very beginning of the entire workflow process, potentially duplicating previous steps. Update Job (Option A) is generally used to apply workflow version changes to an active record, and Cancel (Option D) terminates the workflow entirely. For a pinpointed "retry" of a specific failure point, "Reset" is the verified functional command within the troubleshooting utility.
Here are the verified answers and detailed explanations for Questions 8 through 11, strictly aligned with the Archer Administration II and Advanced Workflow Beyond the Basics curriculum standards.
質問 # 45
Select the service which must always run for Archer to properly function.
- A. LDAP Synchronization service
- B. Configuration service
- C. Job Engine service
- D. Queuing service
正解：B
解説：
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.
質問 # 46
Which of the following Advanced Workflow nodes allows you to set a timer after which the record is automatically rerouted?
- A. Wait for Content Update node
- B. Send Notification node
- C. User Action node
- D. Update Content node
正解：A
解説：
In the Advanced Workflow Beyond the Basics curriculum, the Wait for Content Update node is identified as the primary tool for time-based automation. While its name suggests it is waiting for a user to change a field, its secondary function is to act as a SLA (Service Level Agreement) timer .
Within the node configuration, an administrator can define an "Escalation" or "Timeout" path. You can set a specific duration (e.g., 5 days). If the expected content update does not occur within that timeframe, the node
"times out" and automatically reroutes the record down a secondary transition path-typically to a manager's review or an automated notification. While a User Action node (Option B) can have a "due date," it does not automatically move the record to a different path solely based on time without the Wait for Content Update node logic. Update Content (Option D) and Send Notification (Option A) nodes are instantaneous actions and do not possess the ability to "pause" and monitor for duration.
質問 # 47
Failed user login, Access Role Created and Deleted, and password change by user events are viewed in:
- A. Access Control Rights by Role Report
- B. Security Events Report
- C. Locked Accounts Report
正解：B
解説：
The Security Events Report is the primary auditing tool for tracking administrative and sensitive user actions within the Archer platform. According to the Archer Administration II curriculum, this report captures a broad spectrum of "event-based" security data that standard access reports do not cover.
Specifically, it logs every failed login attempt , which is critical for identifying potential brute-force attacks.
It also tracks metadata changes to the security infrastructure, such as when an Access Role is created or deleted , providing an audit trail of who modified the system's permissions. Furthermore, it records password changes initiated by users. While the "Locked Accounts Report" (Option B) only shows users currently barred from the system, the Security Events Report provides the historical context of why those events occurred. It is an essential resource for compliance officers and system auditors to ensure that the integrity of the Archer environment's security configuration remains intact.
質問 # 48
If a Data Feed is stuck in the status of "Pending", which service should you check first to troubleshoot the issue?
- A. Job Engine service
- B. Configuration service
- C. Indexing service
- D. Queuing service
正解：A
解説：
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.
質問 # 49
Where can you view import file processing details?
- A. Integration > Data Imports
- B. Integration > Data Feeds
- C. Integration > Data Publications
- D. Integration > Review Job Queues
正解：D
解説：
While you initiate a manual import from the Data Imports menu (Option C), the actual execution and processing details of that task are monitored through the Job Queue . According to the Archer Administration II curriculum, once a user clicks "Import," the task is handed off to the Job Engine.
To see if the import was successful, how many rows were processed, or if any errors occurred, the administrator must navigate to Integration > Review Job Queues . This interface provides the granular details of the "Job Status," including start/end times and the specific results of the processing. This is consistent with how Archer handles all background tasks (Feeds, Recalculations, etc.). The "Data Imports" screen itself primarily serves as the portal for uploading the file and mapping fields, whereas "Review Job Queues" is the operational dashboard for tracking the actual work performed by the Archer services.
質問 # 50
Which statement is NOT true for the Archer APIs?
- A. The SOAP API can use JSON for the API request and response.
- B. The Content API can use XML for the API request and response.
+1 - C. The RESTful API can use XML for the API request and response.
- D. The RESTful API can use JSON for the API request and response.
正解：A
解説：
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.
質問 # 51
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 Data Feed target application or questionnaire is set correctly.
- C. Confirm the settings on the Transport Configuration section within the Source Connection tab are correct.
- D. Confirm the settings on the Source Definition tab > Data Filter sub-tab are correct.
正解：C
解説：
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.
質問 # 52
Details such as installation history, applications, solutions, jobs, Top 10 field histories are viewed in:
- A. Installation Report
- B. Application builder Report
- C. Instance Report
- D. Access Control Report
正解：C
解説：
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.
質問 # 53
......
合格させるArcher Archer-Expertプレミアムお試しセットテストエンジンPDFで無料問題集セット：https://www.jpntest.com/shiken/Archer-Expert-mondaishu
2026年最新の実際に出るArcher-Expert問題集テストエンジン試験問題はここにある：https://drive.google.com/open?id=1Ah2MKkDu8m_T8nGP6yVVGbgnL0lcUbPs