Exam MCD - Level 1 topic 1 question 99 discussion

C is correct

C is the correct answer since we are importing myModule using wildcard.

Correct answer is C. From mulesoft docs: Import the module, for example: import modules::MyModule. In this case, you must include the name of the module when you call the element (here, a function) in it, for example: MyModule::myFunc. Import all elements from the module, for example: import * from modules::MyModule. In this case, you do not need to include the name of the module when you call the element. For example: myFunc("dataweave") ++ "name" works. Import specific elements from a module, for example: import myFunc from modules::MyModule. In this case, you do not need to include the name of the module when you call the element. For example: myFunc("dataweave") ++ "name" works. You can import multiple elements from the module like this, for example: import myFunc someOtherFunction from modules::MyModule (assuming both myFunc and someOtherFunction are defined in the module).

C is correct. It's a catch all situation. Any other choice would be wrong based on process of elimination. A uses catch all so it shouldn't need to use MyModule::formatString. and C is the only one that imports correctly using ::

Anser is A

A is the correct answer, ignore my other comment.

ChatGPT: The correct answer is Option C: This option correctly imports all functions from MyModule and allows you to call formatString directly, without needing to prefix it with the module name.

"Import all elements from the module, for example: import * from modules::MyModule. In this case, you do not need to include the name of the module when you call the element. For example: myFunc("dataweave") ++ "name" works." - https://docs.mulesoft.com/dataweave/latest/dataweave-create-module

C is the correct Answer https://imgur.com/a/vK8L2CP Is the only flow that compiled without error and works.

A is correct. Look at this from official mulesoft docs: https://docs.mulesoft.com/dataweave/2.4/dw-functions "The way you import a module impacts the way you need to call its functions from a DataWeave script. If the directive does not list specific functions to import or use * from to import all functions from a function module, you need to specify the module when you call the function from your script. "

C is correct. https://apisero.com/import-a-function-module-in-dataweave/

A is correct , mule soft trainer is answer me.

A is correct

C is correct https://docs.mulesoft.com/dataweave/2.2/dataweave-create-module There are several ways to import a module or elements in it: Import the module, for example: import modules::MyModule. In this case, you must include the name of the module when you call the element (here, a function) in it, for example: MyModule::myFunc. Import all elements from the module, for example: import * from modules::MyModule. In this case, you do not need to include the name of the module when you call the element. For example: myFunc("dataweave") ++ "name" works. Import specific elements from a module, for example: import myFunc from modules::MyModule. In this case, you do not need to include the name of the module when you call the element. For example: myFunc("dataweave") ++ "name" works. You can import multiple elements from the module like this, for example: import myFunc someOtherFunction from modules::MyModule (assuming both myFunc and someOtherFunction are defined in the module).

A may be the right answer. ----- If the directive does not list specific functions to import or use * from to import all functions from a function module, you need to specify the module when you call the function from your script. ---- https://docs.mulesoft.com/mule-runtime/4.2/dw-functions