Right.
For (and from) all the newbies out there who want help for studying, there have been numerous questions about, well, questions. As in, "what's the best set of practice questions to use while studying for the exam?"
The answer is, none of them.
I have looked at an awful lot of practice question sets, and they are uniformly awful. Most try to be "hard" by bringing in trivia: that is not representative of the exam. Most concentrate on a bunch of facts: that is not representative of the exam.
So, from my own stash, collected and developed over the decades, I'm going to give you some samples that do represent the types of questions that you will probably see on the exam. Note that none of these questions will appear on the exam. You can't pass the CISSP exam by memorizing a brain dump. These will just give you a feel.
For each question I'll give the answer, what type of question this represents, and possibly ways to approach this type of question.
I'll be doing this over time, "replying" to this post to add questions. Others are free to add sample questions if they wish, but be ready to be (possibly severely) critiqued.
I would think the answer is Control because Asset and Exposure should be obvious but we would like to know through this implementation what control objective are we trying to achieve.
I may be completely off here though.
@rajus wrote:I would think the answer is Control because Asset and Exposure should be obvious but we would like to know through this implementation what control objective are we trying to achieve.
I may be completely off here though.
The answer provided by @rslade on page 2 of this thread was b (Asset). However, I personally think the question is incomplete because it doesn't say what it is that we are implementing.
@rslade wrote:
In an on-line computer application system, erroneous or invalid transactions that
are detected by the computer program should be
a. dropped from processing.
b. written to a report and reviewed.
c. terminated and the process aborted.
d. written to a computer log.
Answer: b.
Dropping a transaction from processing, and not doing anything with it, *can*
create all kinds of problems for the business. terminating and aborting the process
is a good way to open yourself to some kind of denial of service attack. Writing
to a report is good, but writing to a report and then reviewing it is better.
====================== (quote inserted randomly by Pegasus Mailer)
rslade@gmail.com rmslade@outlook.com rslade@computercrime.org
The vast accumulations of knowledge--or at least of information--
deposited by the nineteenth century have been responsible for an
equally vast iqnorance. When there is so much to be known, when
there are so many fields of knowledge in which the same words are
used with different meanings, when every one knows a little about
a great many things, it becomes increasingly difficult for anyone
to know whether he knows what he is talking about or not. And
when we do not know, or when we do not know enough, we tend
always to substitute emotions for thoughts. - T. S. Eliot
victoria.tc.ca/techrev/rms.htm http://twitter.com/rslade
http://blogs.securiteam.com/index.php/archives/author/p1/
https://community.isc2.org/t5/forums/recentpostspage/user-id/1324864413
@rsladecould you please share a book reference that would sustain this answer?
Does this mean that transactions that are detected as invalid (e.g. a banking operation attempting to transfer more funds than are available in an account) should still be executed and in parallel written to a report and reviewed?