ThingWorx Developer Associate Certification Exam

Exam name: ThingWorx Developer Associate

Exam Duration: 90 minutes
Exam Price: $6000 INR
Exam length: 60 questions
Pass/Fail mark: 75%
(subject to change)

Test Formats:

 Multiple Choice (one correct answer)

 Multi-select (must select all correct options to receive points)
 Matching Style
 Scenario based (all multiple choice)

Sample Question

Description
This exam is intended for all ThingWorx users and partners who perform application development. It is a
mandatory pre-requisite exam for all users in the following roles who plan to complete professional
level certification:

 Application Developers
 Device Engineers
 Application Model Developers
 Architects
The ThingWorx Developer Associate Certification exam validates a candidate’s ability to model a
ThingWorx application using Thing Templates and Things. Candidates apply core ThingWorx Composer
functionality to correctly respond to scenario based questions on how to create a user interface to view
and edit entities in the application. Candidates must be able to secure a ThingWorx application and
define the best connectivity technology, given a use case.

Task Based Performance Objectives

This exam measures the following performance objectives:

 Define the following key ThingWorx concepts: (Exam Coverage 12%)

o Properties
o Services
o Events
o Subscriptions
o Thing Templates
o Data Shapes
o Things
o Mashups
o ThingWorx Organization
o Application Keys
o Resources
o Subsystems
o Remote Thing
o Virtual Thing
o Info Tables

 Identify the following: (Exam Coverage 5%)

o ThingWorx connectivity technologies
o ThingWorx extensions
 Navigate the ThingWorx Composer User Interface (Exam Coverage 5%)
 Create Thing Templates (Exam Coverage 2%)
o Use predefined Things such as Timer Things
 Use Thing Templates to create Things (Exam Coverage: 3%)
 Work with ThingWorx entities and data by doing the following: (Exam Coverage 7%)
o Applying model tags to ThingWorx Entities
o Exporting ThingWorx Entities and Data
o Importing ThingWorx Entities
  Create Mashups by doing the following: (Exam Coverage 18%)
o Configure Widgets
o Determine when to use a Responsive versus Static mashup
o Read the Connections panel of the mashup builder
o Add Services to a mashup
o Use dynamic entities in a mashup
o Use entities to populate widget properties
o Use widgets to populate entitity input parameters
o Use the Layout widget
o Use the Workspace tab
o Use Data Entry widgets
o Use List and Grid widgets
o Use the visibility parameter in widgets
o Test a mashup as the administrator

 Secure a ThingWorx application by doing the following: (Exam Coverage 13%)

o Create a ThingWorx group.
o Define a ThingWorx organization and sub-units.
o Apply security to an organization.
o Create an application key.
o Set security for Entities
o Set security for Services.
 Bind Edge devices to the platform by doing the following: (Exam Coverage 2%)
o Identify when the platform has access to an unbound thing.
o Bind a virtual thing to a remote thing.
 Add the following to things: (Exam Coverage 9%)
o Properties
o Services
o Events
o Subscriptions
 Do the following with Services: (Exam Coverage 2%)
o Create InfoTables in Services
o Manipulate InfoTables in Services
 Work with repositories by doing the following: (Exam Coverage 4%)
o Define Platform File Repositories
o Define Remote File Repositories
o Transfer files from the client to a platform repository
o Download files from repository
o Transfer files between remote and platform repositories

Integrate file transfers into a mashup

 Work with ThingWorx extensions by doing the following: (Exam Coverage 4%)
o Import ThingWorx extensions
o Locate extensions on the ThingWorx marketplace
 o Use Templates from ThingWorx Model Extensions
o Use Widgets from ThingWorx Extensions
 Use ThingWorx data structures, including the following: (Exam Coverage 14%)
o Log values to value streams
o Display value streams in a mashup
o Create ThingWorx Streams
o Create ThingWorx Data Tables
o Tag data in streams and data tables
o Identify persistence provider options