When developing a custom USD schema, what statements are true regarding API schemas versus typed...

API schemas and typed schemas serve different modeling roles in OpenUSD. NVIDIA’s Learn OpenUSD schema guidance states that IsA, or typed, schemas define what a prim fundamentally is by assigning a typeName, while API schemas define what capabilities a prim has by adding optional properties or behaviors to an already-typed prim. API schemas do not assign a typeName; instead, they are list-edited through the apiSchemas metadata and queried with HasAPI. ( docs.nvidia.com )

Option A is correct because API schemas can be applied across different prim types, while a typed schema defines a specific prim type such as Mesh, Camera, or Xform. Option B is also correct because one prim has a single typed schema identity, but multiple API schemas can be applied to enrich that prim with additional behaviors. NVIDIA further notes that API schemas may be single-apply or multiple-apply, where multiple-apply schemas can be applied more than once to the same prim using different instance names. ( docs.nvidia.com )

Option C is incorrect because API schemas can define attributes and relationships. Option D is incorrect because Python binding policy is not the distinguishing factor between API and typed schemas. This aligns with Customizing USD → Schemas, IsA Schemas, API Schemas, typeName, apiSchemas Metadata .