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

OutSystems Exam Architecture-Specialist-11 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:

Submit Cancel
Onita
21 days 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
Cordelia
1 days ago
I agree, core entities are essential for the core layer.
upvoted 0 times
...
...
Billy
25 days 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
...
Yolando
1 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
Kristian
21 days ago
C) Core modules should have public Read-only Entities.
upvoted 0 times
...
Sherly
26 days ago
A) Core modules should have public Read-only Entities.
upvoted 0 times
...
...
Mattie
2 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
Tiffiny
3 days 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
18 days ago
Having business logic in the Core layer can lead to dependencies and make the system harder to maintain.
upvoted 0 times
...
Joseph
19 days ago
Yes, keeping business logic out of the Core layer helps maintain separation of concerns.
upvoted 0 times
...
Stephen
27 days ago
I agree, D is the correct choice. Core modules should not have business logic.
upvoted 0 times
...
Truman
1 months ago
I agree, D is the best choice. Core modules should focus on data and not business logic.
upvoted 0 times
...
...
Glenn
2 months ago
But having public Read-only Entities in the Core modules can help with data consistency and reusability.
upvoted 0 times
...
Crissy
2 months ago
I disagree, I believe recommendation D is more suitable for the Core layer.
upvoted 0 times
...
Jill
2 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
6 days ago
Definitely, it's a good practice to keep business logic separate from data access in the Core layer.
upvoted 0 times
...
Santos
13 days ago
I agree, having read-only entities in the Core layer can help maintain separation of concerns.
upvoted 0 times
...
Peter
23 days ago
That makes sense, it's important to expose data without exposing business logic.
upvoted 0 times
...
Kina
1 months ago
I think C is the right answer. Core modules should have public read-only entities.
upvoted 0 times
...
...
Glenn
2 months ago
I think we should apply recommendation C to the Core layer.
upvoted 0 times
...

Save Cancel