New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISC2 CCSP Exam - Topic 3 Question 82 Discussion

Actual exam question for ISC2's CCSP exam
Question #: 82
Topic #: 3
[All CCSP Questions]

If you are running an application that has strict legal requirements that the data cannot reside on systems that contain other applications or systems, which aspect of cloud computing would be prohibitive in this case?

Show Suggested Answer Hide Answer
Suggested Answer: A

The hypervisor level, as a backend cloud infrastructure component, is not a unit where limits may be applied to control resource utilization. Limits can be placed at the service, virtual machine, and cloud customer levels within a cloud environment.


Contribute your Thoughts:

0/2000 characters
Felicidad
3 months ago
But what about portability? Isn't that a concern too?
upvoted 0 times
...
Catrice
3 months ago
Yup, multitenancy is a dealbreaker for strict legal compliance.
upvoted 0 times
...
Catalina
3 months ago
Wait, are we sure it's just multitenancy? Seems too simple.
upvoted 0 times
...
Lavonda
4 months ago
I agree, multitenancy is a big issue here.
upvoted 0 times
...
Eden
4 months ago
Definitely multitenancy! Can't mix sensitive data with other apps.
upvoted 0 times
...
Ozell
4 months ago
I definitely recall discussing multitenancy in class, and it seems like the most relevant option here given the strict legal requirements.
upvoted 0 times
...
Margart
4 months ago
I feel like broad network access could also be a concern, but it seems more related to accessibility than legal requirements.
upvoted 0 times
...
Shawna
4 months ago
I'm not entirely sure, but I remember a practice question that mentioned how multitenancy can pose risks for sensitive data.
upvoted 0 times
...
Kayleigh
5 months ago
I think this might be about multitenancy since it involves sharing resources, which could lead to legal issues if data is mixed with other applications.
upvoted 0 times
...
Chuck
5 months ago
Multitenancy seems like the obvious choice here. The question is specifically about legal requirements around data isolation, which goes against the shared infrastructure model of Multitenancy in cloud computing.
upvoted 0 times
...
Tammara
5 months ago
Okay, let me think this through. The legal requirement is about data isolation, so I'm guessing Multitenancy would be the aspect that's prohibitive here. Cloud providers typically share infrastructure across multiple tenants, which wouldn't meet the strict data separation requirement.
upvoted 0 times
...
Ashanti
5 months ago
Hmm, this is a tricky one. I'm not entirely sure, but I'm leaning towards Multitenancy as the prohibitive aspect since the question specifically mentions the data can't be on systems with other applications or systems.
upvoted 0 times
...
Junita
5 months ago
I think the key here is the strict legal requirement that the data cannot reside on systems with other applications or systems. That rules out the multitenancy aspect of cloud computing, where multiple customers share the same infrastructure.
upvoted 0 times
...
Paris
5 months ago
I'm pretty confident the answer is Multitenancy. The question is clear that the data can't be on systems with other applications or systems, and that's exactly what Multitenancy in cloud computing refers to.
upvoted 0 times
...
Meaghan
5 months ago
This is a tricky situation. I think the best approach is to request the customer send their complaints by email, so we have a clear record of the communication. That way, we can address the issues properly in the meeting.
upvoted 0 times
...
Gracia
5 months ago
The daily scrum is all about what was done yesterday and what will be done today, so that's not the right answer. I think it has to be either the sprint review or sprint planning, but I'm leaning more towards sprint planning.
upvoted 0 times
...
Svetlana
10 months ago
Multitenancy is the clear choice. I wouldn't want my boss's vacation photos in the same cloud as our top-secret project files, that's for sure.
upvoted 0 times
...
Martina
10 months ago
Hmm, Multitenancy is the way to go. Can't have my grandma's famous pie recipe getting mixed up with the company's financial records!
upvoted 0 times
Coral
8 months ago
Elasticity might not provide the necessary data isolation needed in this case.
upvoted 0 times
...
Detra
8 months ago
D) Elasticity
upvoted 0 times
...
Antonio
8 months ago
I agree, portability would be a better option to ensure data isolation.
upvoted 0 times
...
Aliza
8 months ago
C) Portability
upvoted 0 times
...
Arlette
8 months ago
That's right, multitenancy would not be suitable for this scenario.
upvoted 0 times
...
Ernest
9 months ago
A) Multitenancy
upvoted 0 times
...
Catarina
9 months ago
D) Elasticity
upvoted 0 times
...
Xochitl
9 months ago
C) Portability
upvoted 0 times
...
Buck
10 months ago
A) Multitenancy
upvoted 0 times
...
...
Robt
10 months ago
I agree, Multitenancy is the correct answer. Mixing data across different systems and applications is a big no-no in this scenario.
upvoted 0 times
...
Owen
10 months ago
Multitenancy definitely seems like the main issue here. Keeping sensitive data separate from other applications is crucial in cases with strict legal requirements.
upvoted 0 times
Rozella
8 months ago
Portability could also be an issue if the data cannot be moved between systems easily.
upvoted 0 times
...
Bette
9 months ago
C) Portability
upvoted 0 times
...
Elizabeth
9 months ago
Yes, multitenancy would definitely be a concern in this case.
upvoted 0 times
...
Richelle
9 months ago
A) Multitenancy
upvoted 0 times
...
...
Clement
10 months ago
But what about D) Elasticity? Wouldn't that also involve sharing resources?
upvoted 0 times
...
Josefa
11 months ago
I agree with Chauncey, because multitenancy involves sharing resources with other applications.
upvoted 0 times
...
Chauncey
11 months ago
I think the answer is A) Multitenancy.
upvoted 0 times
...

Save Cancel