In order to begin installing the RSA Archer Platform, you should first copy the installation package to:

Hiroshi T.Jan 29, 2026

The correct answer is D. Before you can install the RSA Archer Platform, the installation package must be placed on the web server that will host the web and application files, because the installer needs to run locally on that server to properly configure IIS, write application files to the correct directories, and set up the necessary service accounts and permissions in the right context. Copying it to your desktop (A) or a shared network drive (B) would require you to move it anyway before the installer can do its job, and placing it in a subfolder within an existing Archer directory (C) is not the documented pre-installation step. The official RSA Archer installation guide is explicit on this point, so go with D and you will not be second-guessing yourself on exam day.

Fatima Z.Feb 21, 2026

D is it, though "webserver" almost makes you second-guess, since Archer splits web from app roles, copy the package straight to that host.

Bedros C.Feb 13, 2026

D is the right call and it makes sense when you think about how Archer actually runs. The platform's web and application services need to resolve paths relative to the server they live on, and if you drop the installer somewhere else, like a shared drive or your desktop, you risk permission issues during the extraction and service registration steps that are a nightmare to untangle mid-install. The installer also writes temp files and logs to local paths on that same machine, so having everything co-located on the webserver keeps the process clean from the start. I have seen installs go sideways because someone staged the package on a mapped network drive and hit a UNC path error right when the IIS app pool was being configured. Saw this exact question on my exam, and I almost second-guessed myself toward C because I was thinking about where Archer content and config files live after the fact. But then I remembered that the install guide specifically says to copy the package to the webserver before you even touch the setup wizard, which snapped me back to D. Trust the sequence the install guide lays out and you will not lose points on setup-related questions.

Samuel O.Feb 16, 2026

D is the right call here. The installer needs to run in the context of the machine that will actually serve the application, so dropping the package on your desktop or a network share just introduces unnecessary transfer steps and permission headaches you do not need before you even get started. When I did a similar enterprise platform rollout a few years back, putting the installer somewhere outside the target server meant dealing with UNC path issues and mapped drive drop-outs mid-install, which killed the process twice before we wised up. Get it on the webserver first, then kick off the install from a local path on that box and save yourself the grief.