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.

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.

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.

The scenario described is a classic implementation of Windows Integrated Authentication (WIA) , a form of Single Sign-On (SSO). As detailed in the Archer Installation and Troubleshooting guides, when Archer is configured for Windows Integrated SSO, it leverages the Kerberos or NTLM protocol. Since Sarah has already authenticated to the Windows Domain at the start of her shift, her browser passes her "security token" directly to the Archer web server (IIS).

The Archer Control Panel (ACP) must be configured to recognize the domain, and the user's Archer account must have their Windows account name (e.g., DOMAIN\Username) populated in the "Domain Account" field. This creates a seamless "handshake" that bypasses the Archer login screen entirely. Unlike a password manager (Option C), which still technically "types" the details, or biometrics (Option B), which requires a new physical scan, Windows Integrated SSO provides a passive experience where the existing OS-level authentication is trusted by the application, drastically improving user workflow and productivity.

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.

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.

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.