MENU
Which of the following recommendations should be applied to the Core layer?
Suggested Answer: B
Get Premium Architecture-Specialist-11 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
42 comments · newest first
JI
Jill
11 months ago
Agreed, no business logic in Core modules makes sense!
CH
Cheryl
11 months ago
Core modules should not have Core Entities, that's a solid point.
MI
Micah
11 months ago
Surprised to see the suggestion about Front-end Screens for testing!
MA
Martina
12 months ago
I disagree, they should have business logic for better functionality.
JO
Joseph
12 months ago
Core modules should definitely have public Read-only Entities.
CH
Cherri
12 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.
LO
Lorean
1 year ago
I feel like there was something about Core modules not having Core Entities, but I can't recall the exact reasoning behind it.
LU
Lucia
1 year ago
I remember discussing that Core modules should have public Read-only Entities, which sounds like option C.
LA
Laticia
1 year 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.
GE
Germaine
1 year 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.
JA
Janey
1 year 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?
AN
Annmarie
1 year 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.
AL
Aleta
1 year 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.
JO
Joaquin
1 year ago
Hmm, I'm not sure about the "out of the box" part. I'll need to think this through carefully.
AS
Asuncion
1 year 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.
ON
Onita
1 year ago
B is just plain wrong. Core modules should definitely have core entities, that's kind of the whole point of the core layer!
MY
Myra
1 year ago
Business logic should definitely be included in the core modules.
GE
Gennie
1 year ago
Having public read-only entities in the core layer is also important.
CO
Cordelia
1 year ago
I agree, core entities are essential for the core layer.
BI
Billy
1 year ago
I'm leaning towards C as well. Keeping the core pure and exposing read-only entities sounds like a solid architectural pattern.
IS
Isaac
1 year ago
C seems like the best option for maintaining a solid architectural pattern in the Core layer.
CA
Carline
1 year ago
It's important to keep the Core layer clean and focused on providing data without any business logic.
CE
Cecilia
1 year ago
I agree, having public read-only entities in the Core layer can help maintain separation of concerns.
YO
Yolando
1 year ago
Haha, A is a funny one. Core modules with front-end screens? That's like putting wheels on a toaster!
AM
Amalia
1 year ago
D) Core modules should not have business logic.
KR
Kristian
1 year ago
C) Core modules should have public Read-only Entities.
SH
Sherly
1 year ago
A) Core modules should have public Read-only Entities.
MA
Mattie
2 years ago
D seems like the obvious choice. Core modules shouldn't have any business logic, that should be in the application layer.
CH
Cherrie
1 year ago
By following best practices, we can ensure a more scalable and maintainable system.
TI
Tiffiny
1 year ago
It's important to keep the Core layer focused on essential functions and keep business logic in the appropriate layer.
ST
Stefan
1 year ago
Having business logic in the Core layer can lead to dependencies and make the system harder to maintain.
JO
Joseph
1 year ago
Yes, keeping business logic out of the Core layer helps maintain separation of concerns.
ST
Stephen
1 year ago
I agree, D is the correct choice. Core modules should not have business logic.
TR
Truman
1 year ago
I agree, D is the best choice. Core modules should focus on data and not business logic.
GL
Glenn
2 years ago
But having public Read-only Entities in the Core modules can help with data consistency and reusability.
CR
Crissy
2 years ago
I disagree, I believe recommendation D is more suitable for the Core layer.
JI
Jill
2 years 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.
MA
Magnolia
1 year ago
Definitely, it's a good practice to keep business logic separate from data access in the Core layer.
SA
Santos
1 year ago
I agree, having read-only entities in the Core layer can help maintain separation of concerns.
PE
Peter
1 year ago
That makes sense, it's important to expose data without exposing business logic.
KI
Kina
1 year ago
I think C is the right answer. Core modules should have public read-only entities.
GL
Glenn
2 years ago
I think we should apply recommendation C to the Core layer.