Actually, none of the answers are correct. Even if you take the correct action according to the answers provided, it is possible that the proc won't auto run on startup because the "scan for startup procs" server setting must also be enabled. In SQL Server 2000, the default value for scan for startup procs is 0 (do not scan).
Additionally, the startup procedures must be owned by the database owner, as well.
That, notwithstanding, the answer considered to be correct is the most correct answer of those given. I just want to make sure that no one still forced to use 2000 thinks that's all there is.