Refer to the exhibit.

The question marks indicate that the title block contains labels referencing custom shared parameters, but the project does not contain the corresponding parameter bindings needed to supply their values. The parameters must be added to the project and associated with the appropriate category—principally Project Information when the value must be common to all sheets. Once the same shared-parameter definitions are bound correctly, users can enter the values through Project Information and the title block labels will display them.

Loading a title block family containing shared-parameter labels does not automatically establish every required project-level parameter binding. The family carries the label definition, but the project must also expose the parameter in the correct data context. The shared parameter’s identity must remain consistent so the label and project parameter reference the same underlying definition.

Option B is inconsistent with the scenario because the family already contains functioning parameter labels. If ordinary text had been used instead of labels, the fields would display fixed text rather than unresolved question marks. Overwriting standard Sheet or Project Information fields would not explain why custom parameter labels remain unresolved.

Reference topics: Shared parameters; title block families; Project Information parameters; category binding; label creation; client content standards.

===============