Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Adobe Exam AD0-E720 Topic 8 Question 39 Discussion

Actual exam question for Adobe's AD0-E720 exam
Question #: 39
Topic #: 8
[All AD0-E720 Questions]

An Adobe Commerce developer needs to alias URLs and third party libraries inside a require js-config.js file. Which configuration would the developer use?

A)

B)

C)

Show Suggested Answer Hide Answer
Suggested Answer: B

To alias URLs and third party libraries inside a requirejs-config.js file, the developer should use the paths configuration option. This option allows the developer to map module names to URLs or paths relative to the baseUrl. For example:

var config = { paths: { 'jquery': 'https://code.jquery.com/jquery-3.6.0.min', 'custom': 'Vendor_Module/js/custom' } };

This will map the module name 'jquery' to the URL of the jQuery library and the module name 'custom' to the path of the custom module. The developer can then use these module names in other modules or files without specifying the full URL or path.

Option A is not correct because it uses the shim configuration option, which is used to define dependencies and exports for non-AMD modules, not to alias URLs or paths. Option C is not correct because it uses the map configuration option, which is used to map module names to other module names for specific contexts, not to alias URLs or paths. Reference: [RequireJS configuration], [RequireJS paths]


Contribute your Thoughts:

Matt
28 days ago
That makes sense, thanks for sharing your rationale.
upvoted 0 times
...
Colene
30 days ago
Ah, the joys of RequireJS configuration. Option B is the one that'll make your Adobe Commerce developer life a little easier. At least it's not XML, right?
upvoted 0 times
Elmer
5 days ago
I agree, Option B is definitely the way to go for aliasing URLs and third party libraries.
upvoted 0 times
...
...
Xuan
1 months ago
I agree, Option B is the way to go. It's a clean and straightforward configuration that gets the job done.
upvoted 0 times
Linsey
16 days ago
Option B in the require js-config.js file is the way to go. It's a solid configuration.
upvoted 0 times
...
Lauryn
20 days ago
I agree, Option B is clean and straightforward. It's the way to go for sure.
upvoted 0 times
...
Luisa
23 days ago
Option B is definitely the best choice for aliasing URLs and third party libraries.
upvoted 0 times
...
...
Shayne
1 months ago
I read that Option B provides better support for aliasing URLs and third party libraries.
upvoted 0 times
...
Lelia
1 months ago
Option B looks like the correct configuration to alias URLs and third-party libraries in a require js-config.js file. The 'paths' section is where you define the aliases.
upvoted 0 times
Tayna
18 days ago
I have used Option B before, and it worked perfectly for aliasing in require js-config.js file.
upvoted 0 times
...
Kenneth
18 days ago
Yes, I agree. The 'paths' section in Option B allows you to define the aliases easily.
upvoted 0 times
...
Starr
20 days ago
Let's go with Option B for aliasing URLs and third-party libraries.
upvoted 0 times
...
Armanda
23 days ago
I think Option B is the right choice for aliasing URLs and third-party libraries.
upvoted 0 times
...
Raina
24 days ago
Yes, the 'paths' section in Option B is where you define the aliases.
upvoted 0 times
...
Peggie
24 days ago
I agree, Option B seems to be the correct configuration.
upvoted 0 times
...
Audry
1 months ago
I think Option B is the right choice.
upvoted 0 times
...
...
Matt
2 months ago
Why do you think Option B is better?
upvoted 0 times
...
Shayne
2 months ago
I disagree, I believe Option B is the correct configuration.
upvoted 0 times
...
Matt
2 months ago
I think the developer should use Option A.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77