I feel like allowing attachments to incident reports is really useful, but I can't recall if it was mentioned as a main advantage in our study materials.
I feel confident about this one. The "Quick to set up and cheap" and "Allows attachments (e.g. screen prints) to be linked to the incident reports" options are the clear winners in my opinion.
The "Electronic rather than manual" option seems like a pretty big advantage, but I'm not sure if that's the best one. I'll need to weigh the pros and cons of each choice.
Okay, let's see. I think "Quick to set up and cheap" and "Allows attachments (e.g. screen prints) to be linked to the incident reports" are the two main advantages here.
Okay, let's think this through. Solidity is definitely a must-choose, since it's the most widely used language for Ethereum smart contracts. As for the second one, I'm torn between Truffle and Serpent. I'll have to weigh the pros and cons of each.
Okay, the key here is that the attacker was able to access the system as root using a simple SQL injection attack. That means the application failed to properly validate the input, so I'm going with A.
As a veteran of the incident management wars, I can tell you that C and D are the way to go. Attachments and open source FTW! Although, 'quick to set up and cheap' - someone's been drinking the Kool-Aid, if you ask me.
Glory
3 months agoNohemi
3 months agoAshton
3 months agoSherita
4 months agoKeneth
4 months agoJesusa
4 months agoChantay
4 months agoTwana
4 months agoStevie
5 months agoMica
5 months agoPatrick
5 months agoPamella
5 months agoStephane
5 months agoGussie
5 months agoFrancesco
5 months agoKenneth
5 months agoRosamond
5 months agoThurman
10 months agoZana
8 months agoNadine
9 months agoLanie
9 months agoCelia
9 months agoJohanna
9 months agoMaryln
9 months agoElvera
10 months agoCeola
9 months agoCeola
9 months agoTrina
11 months agoGilma
11 months agoRessie
11 months ago