Archer is a Windows-based enterprise application that relies on the Microsoft technology stack. As detailed in the Archer Installation and Troubleshooting guide, there are three primary prerequisites for a successful deployment:
* IIS (Internet Information Services): This is the web server that hosts the Archer web interface and APIs.
* SQL Server: Archer requires a Microsoft SQL Server database to store all application data, metadata, and the instance configurations.
* Microsoft .NET Framework: Archer is built on .NET; specific versions (such as 4.7.2 or higher, depending on the Archer version) must be installed for the web and service components to function.
Apache (Option A) is an alternative web server used primarily for Linux-based environments and is not a prerequisite or a supported web server for the Archer platform.

Archer's functionality is governed by a License Key . As taught in Archer Administration II , all the code for all use cases usually exists within the installer, but they are "locked" based on your organization's specific entitlements.
When a new use case is purchased, Archer provides a new alphanumeric license key. The System Administrator must log into the Archer Control Panel (ACP) , navigate to the "Instance" settings, and update the license key field. Once saved, the new use case-including its applications, workflows, and reports-becomes available for installation or activation. You do not need to perform a full system upgrade (Option C) or wait for a "push" from Archer (Option B). While you may need to download the specific Package File (.zip) for the use case from the Archer Community, the "step to gain access" and unlock the rights within your specific instance is the application of the license key in the ACP.

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.

This statement is FALSE . The default authentication mechanism for a fresh installation of Archer is Archer Native Authentication . As detailed in the Archer Installation and Troubleshooting guide, when an instance is first created, it relies on the internal Archer database to store usernames and encrypted passwords.
Single Sign-On (SSO), whether it be Windows Integrated, SAML, or LDAP-based, is an opt-in configuration that must be manually enabled and configured by a System Administrator within the Archer Control Panel (ACP) . Native authentication remains the fallback method and is used for the initial "System Administrator" account setup. While most enterprise organizations quickly transition to SSO for security and convenience, the platform itself defaults to its own internal authentication engine to ensure the system is accessible immediately after installation without requiring a pre-existing connection to an Identity Provider (IdP).

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.