What basic steps are required to extend the dimension in your custom subject area by adding new attributes from another data source?

What basic steps are required to extend the dimension in your custom subject area by adding new attributes from another data source?

• A. Create a sandbox and edit an existing logical star; After editing, modify an existing subject area to expose the required customized elements.
• B. Directly modify the production environment.
• C. Create a new schema in ADW.
• D. Use only data augmentation.

Answer: (A)

When you want to extend a dimension in your custom subject area by bringing in attributes from another data source, you work in a safe, isolated development space first and then expand the model. Start by using a sandbox to keep changes separate from production, so you can build and test without affecting live reports. Next, update the existing logical star to include the new attributes from the other data source. This means adding or mapping those attributes into the dimension in the logical layer, ensuring the joins and keys align so the attributes are properly associated with the dimension. Finally, modify the subject area to expose these newly added elements so end users and reports can access them. This approach preserves governance and allows testing before deployment. Directly editing production bypasses safeguards, creating a new schema in ADW isn’t needed for this subject-area extension, and data augmentation alone doesn’t integrate the new attributes into the logical model and the subject area.

When you want to extend a dimension in your custom subject area by bringing in attributes from another data source, you work in a safe, isolated development space first and then expand the model. Start by using a sandbox to keep changes separate from production, so you can build and test without affecting live reports. Next, update the existing logical star to include the new attributes from the other data source. This means adding or mapping those attributes into the dimension in the logical layer, ensuring the joins and keys align so the attributes are properly associated with the dimension. Finally, modify the subject area to expose these newly added elements so end users and reports can access them.

This approach preserves governance and allows testing before deployment. Directly editing production bypasses safeguards, creating a new schema in ADW isn’t needed for this subject-area extension, and data augmentation alone doesn’t integrate the new attributes into the logical model and the subject area.