MENU
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?
Suggested Answer: A
Get Premium CCSP Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
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.
36 comments · newest first
FE
Felicidad
10 months ago
But what about portability? Isn't that a concern too?
CA
Catrice
11 months ago
Yup, multitenancy is a dealbreaker for strict legal compliance.
CA
Catalina
11 months ago
Wait, are we sure it's just multitenancy? Seems too simple.
LA
Lavonda
11 months ago
I agree, multitenancy is a big issue here.
ED
Eden
11 months ago
Definitely multitenancy! Can't mix sensitive data with other apps.
OZ
Ozell
12 months ago
I definitely recall discussing multitenancy in class, and it seems like the most relevant option here given the strict legal requirements.
MA
Margart
12 months ago
I feel like broad network access could also be a concern, but it seems more related to accessibility than legal requirements.
SH
Shawna
12 months ago
I'm not entirely sure, but I remember a practice question that mentioned how multitenancy can pose risks for sensitive data.
KA
Kayleigh
1 year 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.
CH
Chuck
1 year 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.
TA
Tammara
1 year 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.
AS
Ashanti
1 year 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.
JU
Junita
1 year 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.
PA
Paris
1 year 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.
ME
Meaghan
1 year 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.
GR
Gracia
1 year 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.
SV
Svetlana
1 year 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.
MA
Martina
1 year 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!
CO
Coral
1 year ago
Elasticity might not provide the necessary data isolation needed in this case.
DE
Detra
1 year ago
D) Elasticity
AN
Antonio
1 year ago
I agree, portability would be a better option to ensure data isolation.
AL
Aliza
1 year ago
C) Portability
AR
Arlette
1 year ago
That's right, multitenancy would not be suitable for this scenario.
ER
Ernest
1 year ago
A) Multitenancy
CA
Catarina
1 year ago
D) Elasticity
XO
Xochitl
1 year ago
C) Portability
BU
Buck
1 year ago
A) Multitenancy
RO
Robt
1 year ago
I agree, Multitenancy is the correct answer. Mixing data across different systems and applications is a big no-no in this scenario.
OW
Owen
1 year ago
Multitenancy definitely seems like the main issue here. Keeping sensitive data separate from other applications is crucial in cases with strict legal requirements.
RO
Rozella
1 year ago
Portability could also be an issue if the data cannot be moved between systems easily.
BE
Bette
1 year ago
C) Portability
EL
Elizabeth
1 year ago
Yes, multitenancy would definitely be a concern in this case.
RI
Richelle
1 year ago
A) Multitenancy
CL
Clement
2 years ago
But what about D) Elasticity? Wouldn't that also involve sharing resources?
JO
Josefa
2 years ago
I agree with Chauncey, because multitenancy involves sharing resources with other applications.
CH
Chauncey
2 years ago
I think the answer is A) Multitenancy.