Explanation
Two cross-cutting mechanisms within SysML that can be used to establish traceability between the systems model and a UML software model are allocations and stereotypes. Allocations are dependencies that indicate a relationship between elements in different models or domains. Stereotypes are extensions of existing metaclasses that add additional information or semantics to model elements. By using allocations and stereotypes, different aspects of the systems model and the software model can be linked and traced.
References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htmhttps://www.omg.org/spec/SysML/1.6/PDF

Explanation
For a system with stringent real-time requirements and power-consumption constraints, the concern that would lead the designer to employ the MARTE profile is ensuring that the structure could be precisely modeled and that analysis was supported. MARTE provides concepts and annotations for modeling the structure of real-time and embedded systems in terms of components, ports, connectors, flows, etc., as well as for modeling their behavior in terms of state machines, activities, etc. MARTE also provides concepts and annotations for performing analysis of system properties, such as schedulability, performance, power consumption, etc., using various methods and tools. References:
https://www.omg.org/ocsmp/ocsmp-adv-exam.htmhttps://www.omg.org/spec/MARTE/1.2/About-MARTE/

Explanation
The kind of models that can be exchanged using XMI are instances of MOF models. MOF (Meta-Object Facility) is a standard that defines a metamodeling architecture and a set of metamodels for creating and manipulating models. A metamodel is a model that defines the abstract syntax and semantics of another model. A model is an instance of a metamodel that conforms to its rules and constraints. XMI (XML Metadata Interchange) is a format specification that enables the interchange of objects and models through an XML formatted file. It is based on a metamodel that defines the mapping of MOF concepts to XML concepts. By using XMI, any model that is an instance of a MOF metamodel can be serialized and deserialized in terms of XML elements and attributes. This includes UML, SysML, and other modeling languages that are defined as MOF metamodels. References:
https://www.omg.org/ocsmp/ocsmp-adv-exam.htmhttps://www.omg.org/spec/XMI/2.5.1/About-XMI/

Explanation
A best practice to provide the MARTE information to the engineers who require it is to define a viewpoint and conform views for the engineers. A viewpoint is a specification of a perspective on a model that addresses a set of stakeholder concerns. A view is a representation of a model that conforms to a viewpoint. By defining a viewpoint and conform views for the engineers, the MARTE information can be presented in a way that is relevant and understandable for them. References:
https://www.omg.org/ocsmp/ocsmp-adv-exam.htmhttps://www.omg.org/spec/MARTE/1.2/About-MARTE/

Explanation
The best way to share the profile is to define it as a model library and import it into the other model. A model library is a package with the stereotype <<modelLibrary>> applied to it. It contains reusable model elements that can be imported into other models by using an "import" relationship. Option B shows this approach.
References: https://www.omg.org/ocsmp/ocsmp-adv-exam.htmhttps://www.omg.org/spec/SysML/1.6/PDF