Which of the below matches the most to Core Module Pattern - ECS with Direct Integration Pattern

1. A. ... Entity is not in Outsystems but in an external ERP syste
2. B. IS just makes remote call top external system/databas
3. C. No data is being kept inside O
4. D. Data retrieval may not be optimized as it needs to traverse two different systems to get the information bac
5. E. Con: Integration API must support all use cases
6. F. ... caches only summary data that is frequently lister, joined or searche
7. G. Full detail for a single entry is fetched directly from external syste
8. H. Use when whole database too big or costly to synchroniz
9. I. Details are only required for single entities (not lists)
10. J. ... a wrapper used to contain the logic, actions and data that will expose code that is inside of external library or to inspect external database and import the data structures so they can be used as entities inside of OS
11. K. Same as Base ECS pattern, but have a local replic
12. L. Store data to serve as a local cach
13. M. Pro: Leverage Entity Use, Simpler Integration AP
14. N. Con: Less impact on source system
15. O. ... is a pattern with two modules, a connector module that can be used to encapsulate an external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.
16. P. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
17. Q. . Same as ECS with local replica but synchronization logic is separate
18. R. Pro: Code independenc
19. S. Consumers of CS is not affected by Syn
20. T. Sync can orchestrate several CS
21. . Same as ECS with local replica but API module is provide
22. . So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)
23. . ... is needed if data is coming from MULTIPLE external system
24. . IS will decide which driver to use depending on the data.
25. . ... tries to fetch data from local cache entity, if not there, get single entry from the external syste
26. . Cache only that record (read-through caching) Use when whole database too big or costly to synchroniz
27. . Integration only touches a small portion of the databas
28. . Avoid if access to lists of data is needed up front

Correct Answer: H

Which of the below is NOT a suitable advice for designing a LIGHTWEIGHT mobile local storage?

1. A. Denormalize the local storage
2. B. Define only used attributes
3. C. Group relevant information
4. D. Store all records no matter if relevant or irrelevant

Correct Answer: D

_BL module is for

1. A. A BL becomes a Calculation Engine if it performs complex calculations, (e.
2. B. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.
3. C. Logic to Synchronize data in CS's with an external syste
4. D. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.
5. E. Isolated Business Logic (Actions), to manage complexity, composition or to have its own 'ifecycle.
6. F. Reusable Core Services with public entities, actions, and blocks.
7. G. Technical wrapper to expose an API to External consumers, keeping core services system agnostic and supporting multiple versions of the API.

Correct Answer: C

Which of the below matches the most to Core Module Pattern - ECS with Publish/Subscribe through ESB...

1. A. ... Entity is exposed as read-only and API is available to centralize business logic for entity creation/update
2. B. Same as Base ECS pattern, but have a local replic
3. C. Store data to serve as a local cach
4. D. Pro: Leverage Entity Use, Simpler Integration AP
5. E. Con: Less impact on source system
6. F. Same as ECS with direct integration, but through an Enterprise Service Bus
7. G. ... is a pattern with two modules, a connector module that can be used to encapsulate an O external API with the input/output structures and a wrapper module to expose the normalized API to the consumers.
8. H. ... tries to fetch data from local cache entity, if not there, get single entry from the external p syste
9. I. Cache only that record (read-through caching) Use when whole database too big or costly to synchroniz
10. J. Integration only touches a small portion of the databas
11. K. Avoid if access to lists of data is needed up front
12. L. Same as ECS with local replica but API module is provide
13. M. So any changes to the external system can notify OS, which OS then gets update from the ERP system (subscription system)
14. N. Same as ECS with local replica but synchronization logic is separate
15. O. Pro: Code independenc
16. P. Consumers of CS is not affected by Syn
17. Q. Sync can orchestrate several CS
18. R. ... a wrapper used to contain the logic, actions and data that will expose code that is inside of O external library or to inspect external database and import the data structures so they can be used as entities inside of OS
19. S. ... Entity is not in Outsystems but in an external ERP syste
20. T. IS just makes remote call to
21. . external system/databas
22. . No data is being kept inside O
23. . Data retrieval may not be optimized as it needs to traverse two different systems to get the information bac
24. . Con: Integration API must support all use cases
25. . ... is needed if data is coming from MULTIPLE external system
26. . IS will decide which driver to use depending on the data.

Correct Answer: C

"Spaghetti Architecture" is also known as 'tightly coupled architecture' or 'brittle architecture'. Which is NOT a reason why is "Spaghetti Architecture" bad?

1. A. One small change in a component cause a series of cascading effects on other components
2. B. Hinder future changes as they become less flexible and difficult to manage
3. C. Any changes is maintainable and easy to deploy

Correct Answer: C