What should you do to make sure that the XSD schema can have promoted properties and can be referenced by the orchestrations in both projects?

You work in an international company which is named TXTWIN. And you’re in charge of the company network and use Microsoft BizTalk Server 2006 R2.
And you’re developing a solution. You have two projects each of which has one orchestration. An XSD schema is created. What should you do to make sure that the XSD schema can have promoted properties and can be referenced by the orchestrations in both projects?

You work in an international company which is named TXTWIN. And you’re in charge of the company network and use Microsoft BizTalk Server 2006 R2.
And you’re developing a solution. You have two projects each of which has one orchestration. An XSD schema is created. What should you do to make sure that the XSD schema can have promoted properties and can be referenced by the orchestrations in both projects?

A.
First, you should add the XSD schema to the new project that you should create.
Second, in both orchestration projects, you reference the XSD schema project.

B.
First, the XSD schema should be added to one of the orchestration projects.
Second, the root-level fields of the schema should be promoted.
Third, you reference the Property schema that is created when you promote the fields.

C.
First, the XSD schema should be added to the new project that you create.
Second, the root-level fields of the schema should be promoted.
Third, you reference the Property schema that is created when you promote the fields.

D.
First, the schema should be created as a strongly typed DataSet in a C# project.
Second, the assembly for this C# project should be added to the global assembly cache (GAC).
Third, the assembly should be referenced in both orchestration projects.

Explanation:
BURGOS: mnemo: “XSD schema can have promoted” = “new project … both orchestration”



Leave a Reply 0

Your email address will not be published. Required fields are marked *