ARC-300 · Question #33
The development team is building a complex LINK cartridge for a hosted checkout solution. The provider s database is used as a single source of truth, but the information in the Basket on B2C…
The correct answer is D. Get logger for cartridge-specific category. Report Info level message for the back-end. See the full explanation below for the reasoning.
Question
The development team is building a complex LINK cartridge for a hosted checkout solution. The provider s database is used as a single source of truth, but the information in the Basket on B2C Commerce side needs to be synchronized. This is implemented asynchronously the back end when the customers interact will the hosted checkout page and change their shipping/biding details. As an Architect you have to advise the development team with how to implement the logging to ensure that there will be a mechanism available to allow troubleshooting in the case something goes wrong on production. Which solution should the Architect suggest?
Options
- AReport info level message for the back-end asynchronous communication between both systems
- BReport debug level message for the back-end asynchronous communication between both
- CGet logger for cartridge specific category. Report debug level message for the back end
- DGet logger for cartridge-specific category. Report Info level message for the back-end
How the community answered
(28 responses)- A4% (1)
- B14% (4)
- C11% (3)
- D71% (20)
Community Discussion
No community discussion yet for this question.