Adobe Exam AD0-E706 Topic 5 Question 39 Discussion

Actual exam question for Adobe's AD0-E706 exam

Question #: 39
Topic #: 5

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?

ACustom commands can be run only on the deploy phase

BCSS vendor prefixes must be added to CSS files locally and committed as part of a theme

CThe static assets were not generated yet when the grunt command ran

DThe custom command was run before static assets were transferred into the init directory

Show Suggested 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

10 months ago

A) Custom commands can be run only on the deploy phase

upvoted 0 times

...

Leonor

10 months ago

C) The static assets were not generated yet when the grunt command ran

upvoted 0 times

...

Gwenn

10 months ago

C) The static assets were not generated yet when the grunt command ran

upvoted 0 times

...

Nichelle

10 months ago

B) CSS vendor prefixes must be added to CSS files locally and committed as part of a theme

upvoted 0 times

...

Alonso

10 months ago

B) CSS vendor prefixes must be added to CSS files locally and committed as part of a theme

upvoted 0 times

...

Lenna

11 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

11 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

10 months ago

Good idea, let's test that out and see if it resolves the problem with the CSS prefixes.

upvoted 0 times

...

Kayleigh

10 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

10 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

11 months ago

I agree with Brock, because the prefixes are added during deployment, after static assets are generated.

upvoted 0 times

...

Brock

11 months ago

I think the answer is C) The static assets were not generated yet when the grunt command ran.

upvoted 0 times

...