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

Nokia BL0-220 Exam - Topic 4 Question 43 Discussion

Actual exam question for Nokia's BL0-220 exam
Question #: 43
Topic #: 4
[All BL0-220 Questions]

Which of the following are characteristics of traditional monolithic services. (Select 2)

Show Suggested Answer Hide Answer
Suggested Answer: A, C

The characteristics of traditional monolithic services are low scalability and fixed capacity. Monolithic services are applications that are built as a single unit, where all the components are tightly coupled and run in the same process. This makes them hard to scale, as they require more resources and coordination to handle increased demand. Monolithic services also have fixed capacity, as they are designed for a specific workload and cannot adapt to changing requirements or traffic patterns. Monolithic services are often slow to deploy, as they require updating the entire application for any change or improvement.Reference: [Cloud Native applications design], [Microservices and Containerization]


Contribute your Thoughts:

0/2000 characters
Keva
13 hours ago
C is definitely true, fixed capacity is a classic trait.
upvoted 0 times
...
Serita
6 days ago
Wait, are we sure about A? Some can scale up.
upvoted 0 times
...
Fletcher
11 days ago
A and C are spot on!
upvoted 0 times
...
Horace
16 days ago
D is a joke, right? Monolithic services take forever to deploy, that's like the opposite of "very fast".
upvoted 0 times
...
Adria
21 days ago
A and C make sense. Monolithic services are the dinosaurs of the software world - big, slow, and not very adaptable.
upvoted 0 times
...
Nakita
26 days ago
I agree with A and C. Monolithic services are like a big, heavy rock - not very scalable or flexible.
upvoted 0 times
...
Bulah
1 month ago
A and C are definitely the correct answers. Monolithic services are known for their low scalability and fixed capacity.
upvoted 0 times
...
Lynelle
1 month ago
I’m pretty confident that low scalability is one of the answers, but I’m torn between fixed capacity and very light weight application.
upvoted 0 times
...
Jimmie
1 month ago
I feel like I’ve seen questions about deployment speed in monolithic services before, but I can’t recall if it’s fast or slow.
upvoted 0 times
...
Rene
2 months ago
I remember discussing how monolithic applications are often heavy and not lightweight, so I’m leaning towards A and C.
upvoted 0 times
...
Kris
2 months ago
I think low scalability is definitely a characteristic of monolithic services, but I'm not sure about fixed capacity.
upvoted 0 times
...
Phung
2 months ago
Hmm, I'm a little unsure on this one. I know monolithic services can be a pain to scale, but I'm not totally confident about the other answer. Guess I'll have to make an educated guess.
upvoted 0 times
...
Ernest
2 months ago
I think A and C are correct. Monolithic services struggle with scalability.
upvoted 0 times
...
Zana
2 months ago
I've got a good feeling about this one. A) and C) definitely sound like they'd be characteristics of traditional monolithic services. The other two just don't seem to fit.
upvoted 0 times
...
Fausto
2 months ago
Alright, let's see. I'm pretty sure monolithic services are known for being heavyweight and slow to deploy, so B) and D) are probably not the right answers here.
upvoted 0 times
...
Aleisha
3 months ago
Totally agree, low scalability is a big issue.
upvoted 0 times
...
Gracia
3 months ago
Haha, monolithic services are like trying to move a mountain with a toothpick. No wonder they have fixed capacity and low scalability!
upvoted 0 times
...
Paris
3 months ago
Okay, let me think this through. I know monolithic services tend to be less scalable, so A) and C) seem like good options. But I'm not sure about the other two...
upvoted 0 times
...
Lachelle
3 months ago
Hmm, this one's tricky. I think the key is to focus on the "traditional monolithic services" part - that's the key to narrowing it down.
upvoted 0 times
...

Save Cancel