A developer is creating an entity for home inspections that contains a field for the...

Guidewire'sMetadata Naming Conventionsare strictly enforced to ensure that customer code remains distinct from Guidewire's base product code, which is essential for seamless platform upgrades.

When creating abrand-new entity, the developer must use the.eti (Entity Interface)extension. Following Cloud Delivery Standards, the entity name itself must include the_Extsuffix. Therefore, HomeInspection_Ext.eti is the correct file structure. Regarding the fieldswithinthat custom entity, Guidewire best practices recommend applying the_Extsuffix to custom columns as well (Option B), even if the entity itself is custom. This provides a consistent visual indicator in Gosu code that the developer is interacting with an extension rather than a base product element.

Option A and C use the .etx extension, which is reserved forextending existing base entities(e.g., adding a field to Claim). Option D is incorrect because it lacks the mandatory suffix on the entity name. Option E uses an invalid file naming format. Following the convention in Option B ensures the data model is compliant with Guidewire's automated quality gates.