Setup38% of the exam
Installed Package API integrations and SFTP
How to choose and configure an Installed Packages API integration (Server-to-Server, Web App or Public App), where the client ID and secret come from, how token requests use v2/token, scope and account_id, and how the Marketing Cloud Engagement SFTP server, SFTP accounts, SSH keys and file locations work, with their limits.
Given a scenario, determine how to configure integrations.
~7 min read · 19 practice questions ·
What the exam expects
- Choose the Installed Packages integration type (Server-to-Server, Web App, Public App) from whether a user is present and whether the app can keep a secret.
- Explain where the client ID and secret come from and what a token request needs: v2/token on the Authorization Base URI, scope, account_id, and a 20-minute token that is reused.
- Configure SFTP: port, separate credentials, connection and lockout limits, folders, retention, filename rules, SSH keys and account limits.
- Tell SFTP Accounts (the Engagement-hosted server) from Authorizing File Locations (external storage).
- Key terms: installed package (a bundle of components such as an API integration); client credentials (grant with no user); authorization code (grant where a user logs in); Authorization Base URI (tenant-specific auth endpoint); MID (a business unit's account ID).
Key facts
Unattended integration
- Detail
- Server-to-Server, client_credentials grant
User-authorized integration
- Detail
- Web App or Public App, authorization code grant
Client ID and secret
- Detail
- Generated when the API integration is created in Installed Packages
Token endpoint
- Detail
- v2/token on the Authorization Base URI
Token lifetime
- Detail
- 20 minutes, reusable; refresh two minutes early
Child business unit
- Detail
- account_id set to the unit's MID
SFTP port and lockout
- Detail
- Port 22; 30-minute block after too many bad passwords
SFTP retention
- Detail
- At least 21 days
SFTP users
- Detail
- Up to 10 active per MID
External S3 bucket
- Detail
- Authorizing File Locations
Sources for this section (6)
- Access Token for S2Sdeveloper.salesforce.com (opens in a new tab)
- Web and Public App Integrationsdeveloper.salesforce.com (opens in a new tab)
- S2S Client Credentialsdeveloper.salesforce.com (opens in a new tab)
- SFTP Accountshelp.salesforce.com (opens in a new tab)
- Create SFTP User Accountshelp.salesforce.com (opens in a new tab)
- Authorizing File Locationshelp.salesforce.com (opens in a new tab)
- Why must a single-page app use a Public App integration?
- When does a token request work in a business unit other than the one that created the integration?
- Why save the client secret as soon as the component is created?
- Which Automation Studio activities work with the SFTP server?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Marketing Cloud Engagement Administrator pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 20 lessons of the Marketing Cloud Engagement Administrator guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Inline practice questions and one-click topic practice (19 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Unlimited timed practice exams