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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

OutSystems Architecture-Specialist-11 Exam - Topic 1 Question 11 Discussion

Actual exam question for OutSystems's Architecture-Specialist-11 exam
Question #: 11
Topic #: 1
[All Architecture-Specialist-11 Questions]

Which of the following recommendations should be applied to the Core layer?

Show Suggested Answer Hide Answer
Suggested Answer: B

by Gail at Mar 08, 2024, 04:39 PM

Limited Time Offer

25%

Off

Get Premium Architecture-Specialist-11 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Jill
3 months ago
Agreed, no business logic in Core modules makes sense!
upvoted 0 times
...
Cheryl
4 months ago
Core modules should not have Core Entities, that's a solid point.
upvoted 0 times
...
Micah
4 months ago
Surprised to see the suggestion about Front-end Screens for testing!
upvoted 0 times
...
Martina
4 months ago
I disagree, they should have business logic for better functionality.
upvoted 0 times
...
Joseph
4 months ago
Core modules should definitely have public Read-only Entities.
upvoted 0 times
...
Cherri
4 months ago
I practiced a question similar to this, and I think the recommendation was about avoiding Front-end Screens in the Core layer, which might relate to option A.
upvoted 0 times
...
Lorean
5 months ago
I feel like there was something about Core modules not having Core Entities, but I can't recall the exact reasoning behind it.
upvoted 0 times
...
Lucia
5 months ago
I remember discussing that Core modules should have public Read-only Entities, which sounds like option C.
upvoted 0 times
...
Laticia
5 months ago
I think Core modules should definitely not have business logic, but I'm not entirely sure if that's option D or something else.
upvoted 0 times
...
Germaine
5 months ago
I feel pretty confident about this. The core layer should be focused on the domain model and business logic, not the UI. I think option C is the best choice here.
upvoted 0 times
...
Janey
5 months ago
I'm a bit confused on this one. The core layer is supposed to be the most fundamental part, so I'm not sure if it should have any entities at all. Maybe option D is the way to go?
upvoted 0 times
...
Annmarie
5 months ago
Okay, let's see. The core layer is the foundation, so it shouldn't have front-end screens or business logic. I'm leaning towards option C - public read-only entities.
upvoted 0 times
...
Aleta
5 months ago
Hmm, this is a tricky one. I'll need to think carefully about the core layer and what it should and shouldn't contain.
upvoted 0 times
...
Joaquin
5 months ago
Hmm, I'm not sure about the "out of the box" part. I'll need to think this through carefully.
upvoted 0 times
...
Asuncion
5 months ago
Hmm, I'm not sure about this one. I know Azure SQL Database has some differences from on-premises SQL Server, but I'm not familiar with the specific feature differences. I'll need to review the documentation to be sure.
upvoted 0 times
...
Onita
10 months ago
B is just plain wrong. Core modules should definitely have core entities, that's kind of the whole point of the core layer!
upvoted 0 times
Myra
9 months ago
Business logic should definitely be included in the core modules.
upvoted 0 times
...
Gennie
9 months ago
Having public read-only entities in the core layer is also important.
upvoted 0 times
...
Cordelia
9 months ago
I agree, core entities are essential for the core layer.
upvoted 0 times
...
...
Billy
10 months ago
I'm leaning towards C as well. Keeping the core pure and exposing read-only entities sounds like a solid architectural pattern.
upvoted 0 times
Isaac
9 months ago
C seems like the best option for maintaining a solid architectural pattern in the Core layer.
upvoted 0 times
...
Carline
9 months ago
It's important to keep the Core layer clean and focused on providing data without any business logic.
upvoted 0 times
...
Cecilia
9 months ago
I agree, having public read-only entities in the Core layer can help maintain separation of concerns.
upvoted 0 times
...
...
Yolando
10 months ago
Haha, A is a funny one. Core modules with front-end screens? That's like putting wheels on a toaster!
upvoted 0 times
Amalia
9 months ago
D) Core modules should not have business logic.
upvoted 0 times
...
Kristian
10 months ago
C) Core modules should have public Read-only Entities.
upvoted 0 times
...
Sherly
10 months ago
A) Core modules should have public Read-only Entities.
upvoted 0 times
...
...
Mattie
11 months ago
D seems like the obvious choice. Core modules shouldn't have any business logic, that should be in the application layer.
upvoted 0 times
Cherrie
9 months ago
By following best practices, we can ensure a more scalable and maintainable system.
upvoted 0 times
...
Tiffiny
9 months ago
It's important to keep the Core layer focused on essential functions and keep business logic in the appropriate layer.
upvoted 0 times
...
Stefan
10 months ago
Having business logic in the Core layer can lead to dependencies and make the system harder to maintain.
upvoted 0 times
...
Joseph
10 months ago
Yes, keeping business logic out of the Core layer helps maintain separation of concerns.
upvoted 0 times
...
Stephen
10 months ago
I agree, D is the correct choice. Core modules should not have business logic.
upvoted 0 times
...
Truman
10 months ago
I agree, D is the best choice. Core modules should focus on data and not business logic.
upvoted 0 times
...
...
Glenn
11 months ago
But having public Read-only Entities in the Core modules can help with data consistency and reusability.
upvoted 0 times
...
Crissy
11 months ago
I disagree, I believe recommendation D is more suitable for the Core layer.
upvoted 0 times
...
Jill
11 months ago
I'm not sure, but I think C might be the right answer. Core modules should have public read-only entities to expose data without exposing business logic.
upvoted 0 times
Magnolia
9 months ago
Definitely, it's a good practice to keep business logic separate from data access in the Core layer.
upvoted 0 times
...
Santos
10 months ago
I agree, having read-only entities in the Core layer can help maintain separation of concerns.
upvoted 0 times
...
Peter
10 months ago
That makes sense, it's important to expose data without exposing business logic.
upvoted 0 times
...
Kina
10 months ago
I think C is the right answer. Core modules should have public read-only entities.
upvoted 0 times
...
...
Glenn
11 months ago
I think we should apply recommendation C to the Core layer.
upvoted 0 times
...

Save Cancel