I've got a strategy for this - I'll start by eliminating the options I know are incorrect, then focus on the remaining choices to determine the best answer.
I'm not totally confident on this one. I'll need to review my notes to make sure I understand the differences between the various cloud service models.
Okay, I remember learning about this in class. I believe the key is understanding the shared responsibility model between the cloud provider and the customer.
This seems like a straightforward question about cloud security responsibilities. I think I've got a good handle on this topic, so I'll give it a shot.
I think I've got a good handle on this. The key is to identify the different network layers and consider how any operations at those layers could impact live services.
Packet filtering firewall is the way to go here. It's the device specifically designed to control access to the network and protect against unauthorized access.
Composition settings, for sure. That's the main tool we use in this software to combine and blend different visual elements. I feel confident about this one.
Let me see... Objectivity, Professional Competence and Due Care, and Integrity - those sound like the key principles, but I want to double-check the CIMA Ethical Code to make sure I'm not missing anything.
Okay, let's think this through. The key requirements are redundant WAN links, ability to easily increase link speed, and limited budget. I'll need to weigh the tradeoffs between the options.
Hmm, good point. Wouldn't be much of a 'service' if the customers had to worry about the underlying OS and network, am I right? *chuckles* Anyway, I think D makes the most sense here. Gotta keep those user accounts locked down, you know?
Yeah, I agree. The operating system and network are probably on the provider side. So it's gotta be either A or D. I'm leaning towards D since user identity and access management is a huge part of cloud security that customers have to manage.
Okay, let's break this down. In a SaaS model, the provider usually handles the infrastructure and platform, so I'm guessing the customers are mainly responsible for the application layer and user access. That would rule out B and C, right?
I'm not too sure about this one. The way it's phrased, it seems like we're supposed to focus on what customers are responsible for, not the whole security picture. Hmm, let me think this through...
upvoted 0 times
...
Log in to Pass4Success
Sign in:
Report Comment
Is the comment made by USERNAME spam or abusive?
Commenting
In order to participate in the comments you need to be logged-in.
You can sign-up or
login
Janet
3 months agoRueben
3 months agoDomonique
3 months agoTijuana
4 months agoAntonio
4 months agoGearldine
4 months agoOlen
4 months agoDestiny
4 months agoJutta
5 months agoBuddy
5 months agoAnnamae
5 months agoHerman
5 months agoDaren
5 months agoYolando
5 months agoVicky
5 months agoEssie
5 months agoMabel
5 months agoChrista
5 months agoGabriele
5 months agoDorothy
5 months agoMargarett
2 years agoLoren
2 years agoKanisha
2 years agoKenia
2 years agoInocencia
2 years agoSabra
2 years agoDesiree
2 years agoAnnalee
2 years agoKristine
2 years agoJeniffer
2 years ago