Debugging and Logging B2C-COMMERCE-DEVELOPER Practice Questions (Page 3)

Questions 11–15

1. 11application · medium

   A team is developing a new B2C Commerce cartridge. They want to log detailed diagnostic information during development, but only log errors and warnings in production. They also want to log non-sensitive operational data such as order IDs and status changes. Which logging strategy should they implement?

   • AUse `log.debug` for detailed diagnostics and `log.warn` and `log.error` for production issues, and configure log levels per environment.
   • BWrite all messages to a custom log file and set the log level to `debug` in production.
   • CUse `log.error` for all messages to ensure they are always captured.
   • DUse `log.info` for all messages, including detailed diagnostics, and rely on log rotation to manage volume.
   Reveal Solution Discussion Select an answer first
2. 12expert · hard

   A developer is debugging a pipeline that calls a custom script. The script is not receiving the expected input from the pipeline. The developer wants to inspect the input parameters of the script as they are passed from the pipeline. The developer has attached the debugger to the server. What is the best way to inspect the input parameters?

   • AUse the pipeline inspector to view the parameters at runtime.
   • BSet a breakpoint in the pipeline function that calls the script and inspect the parameters before the call.
   • CSet a breakpoint at the beginning of the script and use the debugger to inspect the input parameters.
   • DAdd a `log` statement in the pipeline to print the parameters before calling the script.
   Reveal Solution Discussion Select an answer first
4. 13foundation · easy

   In the B2C Commerce debugger, which view is used to examine the current values of variables while debugging a script function?

   • AOutline view
   • BConsole view
   • CVariables view
   • DProblems view
   Reveal Solution Discussion Select an answer first
5. 14application · medium

   A developer is debugging a script that is called from a pipeline. The script receives a parameter that is not the expected value. The developer wants to inspect the value of the parameter when the script is called. What is the best way to do this?

   • ASet a breakpoint at the beginning of the script and use the debugger to inspect the parameter value.
   • BModify the script to write the parameter to a custom log file.
   • CAdd a `log` statement in the pipeline to print the parameter value before calling the script.
   • DUse the pipeline inspector to view the parameter value at runtime.
   Reveal Solution Discussion Select an answer first
6. 15expert · hard

   A developer is debugging a complex pipeline that involves multiple pipeline functions and a custom script. The pipeline is failing intermittently, and the developer needs to identify which function is causing the failure. The developer has attached the debugger to the server. What is the most effective approach?

   • ASet a breakpoint in the custom script and step through it, ignoring the pipeline functions.
   • BAdd `log` statements in each pipeline function to log the input and output parameters, and deploy to production.
   • CSet breakpoints in each pipeline function and step through the pipeline, examining the input and output parameters at each step.
   • DUse the pipeline inspector to view the execution flow and identify the failing function.
   Reveal Solution Discussion Select an answer first