SFMC Developer Exam Questions Answered Correctly Rated A+
SOAP API - Answers - Core functionality with Email, Tracking and Data Extensions
- Most comprehensive API functionality
REST API - Answers - New functionality with Mobile, Journey Builder, and Content Builder
- Selective support for core functionality including Email and Data Extensions
SOAP API for transactional message - Answers Available via the TriggeredSend object using the Create
method
REST API for transactional messaget - Answers Route for sending: /messageDefinitionSends
AMPScript for transactional message - Answers - Available via the TriggeredSend object using the
InvokeCreate function
- Used for landing pages on the Marketing Cloud
Components of a triggered send - Answers Definition + API Request
Where is the triggered send definition? - Answers In the UI under Email Studio > Interactions > Triggered
Emails
or via API (uncommon)
What does the triggered send definition do? - Answers - Provides common data for sending:
- Form Details
- Email Template
- Subscriber Management
- Differentiates sends for tracking purposes
- Allow for pausing/queuing messages (can pause triggered send, update email and then resume)
Creating a Triggered Send Definition - Answers Fields:
- Name
- Key Identifier (CustomerKey = ExternalKey)
,- Classification
- Email
- List for Subscriber Management
- Misc Options
- CC/BCC
- Multipart MIME
- Send Loggins
Triggered Send Def best practices - Answers - Create new definition for unique send types
- Password reset versus Receipt
- Make sure you start your definition
- Publish anytime you make changes
- Pause + Start != Publish
- Always select a list under subscriber management
- Provides better visibility into subscriber status
SOAP/REST API - which supports username and password? - Answers SOAP API
- Also supports OATH for a short-lived token
Web App - Answers Web Apps make API requests in the context of an end user. These integrations are
issued a client ID and client secret because they can maintain the confidentiality of a client secret.
Public App - Answers Public Apps, such as single-page or mobile applications, make API requests in the
context of an end user. These integrations are issued only a client ID because they cannot maintain the
confidentiality of a client secret.
Server-Server - Answers A server-to-server integration performs tasks on behalf of the integration,
without an end-user context, user interaction, or user interface.They make API requests in the context
, of a service account instead of a user account. These integrations are issued a client ID and client secret
to use with the Client Credentials grant type.
Access Tokens for Server-to-Server Integrations - Answers In the client credentials flow, your client
application uses this client ID and client secret to request an access token from the Marketing Cloud
authorization server. The access token gives your application access to Marketing Cloud's REST and
SOAP services. (The client credentials grant type doesn't have refresh tokens.)
Access Tokens for Server-to-Server Integrations- how it works - Answers 1. Your application requests an
access token by providing the client ID and secret that was generated for the package you created in
Marketing Cloud.
2. The Marketing Cloud authorization server returns an access token for your application to extract.
3. Your application uses the access token to access Marketing Cloud resources and the REST or SOAP
base URLs returned as part of the token response.
how does your application request the access token for the server-to-server integration? - Answers
Construct a static endpoint for your request by appending v2/token to the Authorization Base URI
provided to you when you created the API integration in Installed Packages. Request an access token by
providing the client ID and secret that you received when you created the API integration in Installed
Packages.
How long is the lifetime of an access token? - Answers 20 minutes
Here's an example request:
Host: https://YOUR_SUBDOMAIN.auth.marketingcloudapis.com
POST /v2/token
Content-Type: application/json
{
"grant_type": "client_credentials",
"client_id": "7a9j47upktedde30uedl822p",
"client_secret": "1955278925675241571",
"scope": "list_and_subscribers_write audiences_write",
"account_id": "12345"
SOAP API - Answers - Core functionality with Email, Tracking and Data Extensions
- Most comprehensive API functionality
REST API - Answers - New functionality with Mobile, Journey Builder, and Content Builder
- Selective support for core functionality including Email and Data Extensions
SOAP API for transactional message - Answers Available via the TriggeredSend object using the Create
method
REST API for transactional messaget - Answers Route for sending: /messageDefinitionSends
AMPScript for transactional message - Answers - Available via the TriggeredSend object using the
InvokeCreate function
- Used for landing pages on the Marketing Cloud
Components of a triggered send - Answers Definition + API Request
Where is the triggered send definition? - Answers In the UI under Email Studio > Interactions > Triggered
Emails
or via API (uncommon)
What does the triggered send definition do? - Answers - Provides common data for sending:
- Form Details
- Email Template
- Subscriber Management
- Differentiates sends for tracking purposes
- Allow for pausing/queuing messages (can pause triggered send, update email and then resume)
Creating a Triggered Send Definition - Answers Fields:
- Name
- Key Identifier (CustomerKey = ExternalKey)
,- Classification
- List for Subscriber Management
- Misc Options
- CC/BCC
- Multipart MIME
- Send Loggins
Triggered Send Def best practices - Answers - Create new definition for unique send types
- Password reset versus Receipt
- Make sure you start your definition
- Publish anytime you make changes
- Pause + Start != Publish
- Always select a list under subscriber management
- Provides better visibility into subscriber status
SOAP/REST API - which supports username and password? - Answers SOAP API
- Also supports OATH for a short-lived token
Web App - Answers Web Apps make API requests in the context of an end user. These integrations are
issued a client ID and client secret because they can maintain the confidentiality of a client secret.
Public App - Answers Public Apps, such as single-page or mobile applications, make API requests in the
context of an end user. These integrations are issued only a client ID because they cannot maintain the
confidentiality of a client secret.
Server-Server - Answers A server-to-server integration performs tasks on behalf of the integration,
without an end-user context, user interaction, or user interface.They make API requests in the context
, of a service account instead of a user account. These integrations are issued a client ID and client secret
to use with the Client Credentials grant type.
Access Tokens for Server-to-Server Integrations - Answers In the client credentials flow, your client
application uses this client ID and client secret to request an access token from the Marketing Cloud
authorization server. The access token gives your application access to Marketing Cloud's REST and
SOAP services. (The client credentials grant type doesn't have refresh tokens.)
Access Tokens for Server-to-Server Integrations- how it works - Answers 1. Your application requests an
access token by providing the client ID and secret that was generated for the package you created in
Marketing Cloud.
2. The Marketing Cloud authorization server returns an access token for your application to extract.
3. Your application uses the access token to access Marketing Cloud resources and the REST or SOAP
base URLs returned as part of the token response.
how does your application request the access token for the server-to-server integration? - Answers
Construct a static endpoint for your request by appending v2/token to the Authorization Base URI
provided to you when you created the API integration in Installed Packages. Request an access token by
providing the client ID and secret that you received when you created the API integration in Installed
Packages.
How long is the lifetime of an access token? - Answers 20 minutes
Here's an example request:
Host: https://YOUR_SUBDOMAIN.auth.marketingcloudapis.com
POST /v2/token
Content-Type: application/json
{
"grant_type": "client_credentials",
"client_id": "7a9j47upktedde30uedl822p",
"client_secret": "1955278925675241571",
"scope": "list_and_subscribers_write audiences_write",
"account_id": "12345"
