Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Google Exam Cloud-Digital-Leader Topic 8 Question 42 Discussion

Actual exam question for Google's Cloud Digital Leader exam
Question #: 42
Topic #: 8
[All Cloud Digital Leader Questions]

An organization is struggling to keep up with the growth of their application which is running on legacy infrastructure.

What might be holding them back?

Show Suggested Answer Hide Answer
Suggested Answer: D

Legacy infrastructure is typically based on on-premises hardware that is managed and maintained by the organization. As the application grows and the user base expands, the hardware required to support it must also grow. This can lead to significant costs associated with provisioning and maintaining hardware, particularly if the organization needs to provision for peak usage.


Contribute your Thoughts:

Wade
10 days ago
Haha, the 'overreliance on platform as a service' option is pretty funny. I don't think that's a real problem these days. Most organizations are trying to leverage PaaS to *solve* their scalability issues, not the other way around. I'm sticking with D as well.
upvoted 0 times
...
Jamal
11 days ago
Hmm, I'm not so sure. What if the data is actually inaccessible due to the perimeter security? That could also be a major bottleneck, especially if they're trying to scale the application. I might go with A on this one.
upvoted 0 times
...
Sanjuana
12 days ago
I agree, D seems like the most likely answer here. Legacy infrastructure is often not optimized for handling spikes in demand, so the cost of scaling up can be a major problem. The other options don't seem as relevant to the context provided.
upvoted 0 times
...
Mirta
13 days ago
This question is tricky. It seems like the organization is struggling with infrastructure and scalability issues, but the options don't seem to directly address that. I'm leaning towards D, the cost of provisioning hardware for peak usage, since that's a common challenge with legacy infrastructure.
upvoted 0 times
...

Save Cancel