In systems deployment, which method is a practical way to transfer a program so it can run on a central system without re-keying code on the target machine?

Introduction / Context:
When moving software to a central system, teams need reliable transfer methods that preserve code integrity and avoid manual re-entry. Historically and in embedded contexts, one approach is to burn code into programmable read-only memories (PROMs) and physically install them. While modern environments use networks, removable media, or images, the question focuses on conceptually valid transfer approaches beyond typing in code at the destination.

Given Data / Assumptions:

• The scenario asks for a way to transfer programs to a central system.
• Options include low-level hardware entry (bit switches), PROM installation, and developing only on the target.
• We seek a method that actually performs a transfer.

Concept / Approach:
Manually setting CPU bit switches is a legacy bootstrap technique, not a practical way to transfer a full program. Developing only on the central system is a process choice that eliminates transfer but is often impractical (shared access, risk, downtime). Programming PROMs off-target and installing them provides a tangible transfer mechanism—especially for firmware or fixed-function code—ensuring the central system runs the intended program image without manual re-keying.

Step-by-Step Solution:

Verification / Alternative check:
Classic firmware workflows burn code into ROM/PROM/EPROM and then install it, which is a recognized deployment and transfer method, especially before ubiquitous networking.

Why Other Options Are Wrong:

Common Pitfalls:
Confusing bootstrapping with full program deployment; ignoring that many environments require moving images between build hosts and central systems.

Final Answer:
Copying the program into PROMs and installing those PROMs in the system.