Why did you check the box for CommunityMap but not Parks in step 4?

• A. Dynamic writing does not work for MITAB datasets.
• B. Selecting Parks will cause an error because there are conflicting schema definitions for the same feature type.
• C. We want the written Parks data to take its schema from the CommunityMap geodatabase, not the Parks MITAB file.
• D. We want to ensure compatibility with all data sources.

Answer: (C)

This question hinges on how FME handles schema when writing data from multiple sources. In step 4 you want the Parks data to conform to a single, authoritative schema—the one defined by the CommunityMap geodatabase. By letting the written Parks data take its schema from the CommunityMap geodatabase, you ensure all features share the same field names, data types, and geometry rules that the writer expects. This avoids mismatches that can occur if Parks were written using the Parks MITAB file’s own schema, which might have different fields or types.

If you relied on the Parks MITAB schema, there’s a risk of conflicts or missing definitions because the two sources may define attributes differently. Choosing the CommunityMap schema provides a consistent target structure for the write operation, creating a compatible, stable output.