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
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Adobe Exam AD0-E706 Topic 5 Question 39 Discussion

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

You added a grunt autoprefixer command, which adds CSS vendor prefix like --webkit- and --moz- to CSS files generated by the setup:static-connect: deploy command.

After deployment you still see CSS files without prefixes. The hooks section in the .magento. app. Yaml file is:

Considering static assets are being generated on the build phase why are CSS prefixes missing?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Benton at Aug 07, 2024, 01:45 PM

Limited Time Offer

25%

Off

Get Premium AD0-E706 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

Submit Cancel
Louisa
10 months ago
Haha, this question is a real head-scratcher! I'd say the answer is C, just because it sounds the most like something a clueless developer would do. 'The static assets were not generated yet when the grunt command ran' - classic rookie mistake!
upvoted 0 times
...
Madalyn
10 months ago
Woah, hold up! I thought this was a certification exam, not a guessing game. Let's go with the official answer, which is D. The custom command was run before the static assets were transferred. Boom, problem solved!
upvoted 0 times
...
Brock
10 months ago
That's a good point, Lenna. It could be a timing issue with when the custom command is executed.
upvoted 0 times
...
Lenny
10 months ago
C'mon, it's clearly B. The CSS vendor prefixes need to be added locally and committed as part of the theme. Otherwise, how else are they going to magically appear in the deployed files?
upvoted 0 times
Micaela
9 months ago
A) Custom commands can be run only on the deploy phase
upvoted 0 times
...
Leonor
9 months ago
C) The static assets were not generated yet when the grunt command ran
upvoted 0 times
...
Gwenn
9 months ago
C) The static assets were not generated yet when the grunt command ran
upvoted 0 times
...
Nichelle
9 months ago
B) CSS vendor prefixes must be added to CSS files locally and committed as part of a theme
upvoted 0 times
...
Alonso
9 months ago
B) CSS vendor prefixes must be added to CSS files locally and committed as part of a theme
upvoted 0 times
...
...
Lenna
10 months ago
But could it also be D) The custom command was run before static assets were transferred into the init directory?
upvoted 0 times
...
Marylin
10 months ago
Hmm, I think the answer is D. The custom command was run before the static assets were transferred into the init directory. Seems like a case of premature optimization!
upvoted 0 times
Sheldon
9 months ago
Good idea, let's test that out and see if it resolves the problem with the CSS prefixes.
upvoted 0 times
...
Kayleigh
9 months ago
Maybe we should try running the custom command after the static assets are transferred to see if that fixes the issue.
upvoted 0 times
...
Glynda
9 months ago
That makes sense, it could be a timing issue with when the custom command was executed.
upvoted 0 times
...
Burma
10 months ago
I think the answer is D. The custom command was run before the static assets were transferred into the init directory.
upvoted 0 times
...
...
Janet
10 months ago
I agree with Brock, because the prefixes are added during deployment, after static assets are generated.
upvoted 0 times
...
Brock
10 months ago
I think the answer is C) The static assets were not generated yet when the grunt command ran.
upvoted 0 times
...

Save Cancel