A page uses a block named hero. Under standard EDS conventions, where are its implementation assets typically located?

Where are styles specific to an EDS block commonly defined?

When adopting AEM Edge Delivery Services, what is a major early decision for a project team?

Where is Edge Delivery Services project code commonly stored?

What configuration identifies the repository location from which EDS reads content?

What are section metadata rows commonly used for in document-based EDS authoring?

What supports querying and filtering content returned by an EDS index?

Which authoring approach uses documents or spreadsheets as page sources?

What JavaScript pattern is used to enhance a rendered EDS block?

What converts recognized document patterns into EDS blocks during processing?

What event commonly triggers deployment of EDS code changes?

In an Edge Delivery Services project, what does fstab.yaml primarily describe?

What EDS action processes newly published source content for delivery?

What browser tool provides preview, publish, and editing actions for EDS authors?

What command-line tooling is commonly used to run an EDS project locally?

Why use Preview before Publish in EDS?

Why is the self-contained block model valuable in Edge Delivery Services?

What is the primary purpose of an EDS block library?

Which tool is commonly used to assess web performance metrics for an EDS site?

In Edge Delivery Services, a block is best understood as: