Fill This Form To Receive Instant Help
Homework answers / question archive / Harvard University AUDIT 111 Chapter 2-Auditing IT Governance Controls TRUE/FALSE 1)To fulfill the segregation of duties control objective, computer processing functions (like authorization of credit and billing) are separated
Harvard University
AUDIT 111
Chapter 2-Auditing IT Governance Controls
disaster.
a. |
releasing incorrect data to authorized individuals |
b. |
permitting computer operators unlimited access to the computer room |
c. |
permitting access to data by unauthorized individuals |
d. |
providing correct data to unauthorized individuals |
a. |
separating the programmer from the computer operator |
b. |
preventing management override |
c. |
separating the inventory process from the billing process |
d. |
performing independent verifications by the computer operator |
a. |
program coding from program operations |
b. |
program operations from program maintenance |
c. |
program maintenance from program coding |
d. |
all of the above duties should be separated |
a. |
rapid turnover of systems professionals complicates management's task of assessing the competence and honesty of prospective employees |
b. |
many systems professionals have direct and unrestricted access to the organization's programs and data |
c. |
rapid changes in technology make staffing the systems environment challenging |
d. |
systems professionals and their supervisors work at the same physical location |
a. |
natural disasters such as fires |
b. |
unauthorized access |
c. |
data corruption caused by program errors |
d. |
system crashes |
a. |
systems development from data processing |
b. |
data operations from data librarian |
c. |
data preparation from data control |
d. |
data control from data librarian |
so
a. |
weakens database access security |
b. |
allows programmers access to make unauthorized changes to applications during execution |
c. |
results in inadequate documentation |
d. |
results in master files being inadvertently erased |
a. |
separate systems development from systems maintenance |
b. |
separate systems analysis from application programming |
c. |
separate systems development from data processing |
d. |
separate database administrator from data processing |
a. |
lack of separation of duties |
b. |
system incompatibilities |
c. |
system interdependency |
d. |
lack of documentation standards |
a. |
off-site storage of backups |
b. |
computer services function |
c. |
second site backup |
d. |
critical applications identified |
a. |
internally provided backup |
b. |
recovery operations center |
c. |
empty shell |
d. |
mutual aid pact |
a. |
the host site may be unwilling to disrupt its processing needs to process the critical applications of the disaster stricken company |
b. |
intense competition for shell resources during a widespread disaster |
c. |
maintenance of excess hardware capacity |
d. |
the control of the shell site is an administrative drain on the company |
a. |
this is an inexpensive solution |
b. |
the initial recovery period is very quick |
c. |
the company has sole control over the administration of the center |
d. |
none of the above are advantages of the recovery operations center |
a. |
month-end adjustments |
b. |
accounts receivable |
c. |
accounts payable |
d. |
order entry/billing |
a. |
backups of systems software |
b. |
backups of application software |
c. |
documentation and blank forms |
d. |
results of the latest test of the disaster recovery program |
a. |
systems documentation is inadequate because of pressures to begin coding a new program before documenting the current program |
b. |
illegal lines of code are hidden among legitimate code and a fraud is covered up for a long period of time |
c. |
a new systems analyst has difficulty in understanding the logic of the program |
d. |
inadequate systems documentation is prepared because this provides a sense of job security to the programmer |
a. |
clearly marked exits |
b. |
an elaborate water sprinkler system |
c. |
manual fire extinguishers in strategic locations |
d. |
automatic and manual alarms in strategic locations |
a. |
review of fire marshal records |
b. |
review of the test of the backup power supply |
c. |
verification of the second site backup location |
d. |
observation of procedures surrounding visitor access to the computer center |
a. |
inspection of the second site backup |
b. |
analysis of the fire detection system at the primary site |
c. |
review of the critical applications list |
d. |
composition of the disaster recovery team |
a. |
network management |
b. |
systems operations |
c. |
systems development |
d. |
server maintenance |
a. |
separating the programmer from the computer operator |
b. |
preventing management override |
c. |
separating the inventory process from the billing process |
d. |
performing independent verifications by the computer operator |
5.. Why is poor-quality systems documentation a prevalent problem?
Functions to Separate |
Risk Exposure |
|
|
|
|
|
|
|
|
|
|
|
|
.
Already member? Sign In