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-E706 Topic 10 Question 35 Discussion

Actual exam question for Adobe's AD0-E706 exam
Question #: 35
Topic #: 10
[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

Contribute your Thoughts:

Gladys
2 months ago
This is a tricky one. I'm leaning towards D, but I'm not 100% sure. Maybe they should try running the grunt command after the static assets are transferred to the init directory?
upvoted 0 times
...
Jeannetta
2 months ago
Haha, the prefixes missing reminds me of that time I forgot to put my socks on in the morning. Talk about a fashion disaster! Anyway, I'm going with C. The static assets were not generated yet when the grunt command ran.
upvoted 0 times
Carmela
1 days ago
I agree with you, C seems like the most logical option.
upvoted 0 times
...
Myra
2 days ago
I guess we'll have to make sure the timing is right for those prefixes to be added.
upvoted 0 times
...
Tyisha
9 days ago
Yeah, it seems like the static assets weren't ready when the grunt command ran.
upvoted 0 times
...
Matthew
27 days ago
I agree with you, I think C makes the most sense.
upvoted 0 times
...
...
Kimberlie
2 months ago
That makes sense, the custom command might have been run before static assets were transferred.
upvoted 0 times
...
Kathryn
2 months ago
I believe the answer could also be D.
upvoted 0 times
...
Alaine
2 months ago
I agree with Kimberlie, the static assets were not generated yet when the grunt command ran.
upvoted 0 times
...
Maile
2 months ago
I'm going with B. The CSS vendor prefixes need to be added to the CSS files locally and committed as part of the theme. The build process shouldn't be responsible for that.
upvoted 0 times
Solange
1 months ago
I agree with you. It makes sense that the prefixes were missing because the assets were not generated at that point.
upvoted 0 times
...
Cassie
1 months ago
I think C is the correct answer. The static assets were not generated yet when the grunt command ran.
upvoted 0 times
...
Tegan
1 months ago
B
upvoted 0 times
...
Naomi
1 months ago
C
upvoted 0 times
...
Remona
2 months ago
A
upvoted 0 times
...
...
Kimberlie
2 months ago
I think the answer is C.
upvoted 0 times
...
Leila
2 months ago
Hmm, I think the answer is D. The custom command was run before the static assets were transferred into the init directory. The question says the prefixes are missing after deployment, so it must be an issue with the deployment process.
upvoted 0 times
Arminda
2 months ago
D) The custom command was run before static assets were transferred into the init directory
upvoted 0 times
...
Ruth
2 months ago
A) Custom commands can be run only on the deploy phase
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