Integrasi dan Perpindahan Data
Juga tersedia dalam 19 bahasa
English · Español · 日本語 · Português (Brasil) · Français · Deutsch · Italiano · 한국어 · 简体中文 · Português (Portugal) · 繁體中文 · Türkçe · Polski · Tiếng Việt · ไทย · Українська · Español (México) · Français (Canada) · Deutsch (Schweiz)
Panduan belajar untuk bab 9 kursus Data Architect. Baca dulu empat modulnya; halaman ini membantu Anda memeriksa apa yang sudah melekat.
Tentang panduan belajar ini. Panduan ini disusun hanya dari konten kursus ini sendiri dan daftar tujuan yang tercantum dalam panduan ujian resmi Salesforce. Panduan ini tidak pernah didasarkan pada soal ujian yang sebenarnya, dan tidak mengklaim tahu apa yang keluar di ujian. Jika Anda sudah mengikuti ujiannya, mohon jangan kirimkan soal-soalnya kepada saya: perjanjian sertifikasi melarang membagikannya, dan menghafal jawaban memang cara yang salah untuk menjadi arsitek.
Panduan ujian menyatakan bahwa ujian tidak menguji konfigurasi alat integrasi, dan bab ini adalah piring cicip untuk arsitek data, bukan kursus Integration Architect. Yang memang dipedulikan ujian adalah apa yang dilakukan integrasi terhadap data Anda: kunci, otoritas tulis, volume dan kelengkapan, serta data yang berpindah antar-org. Angka-angka platform berubah, jadi periksa angka terkini sebelum mengandalkannya.
Untuk Ujian
Section titled “Untuk Ujian ”Centang satu per satu sambil berjalan. Setiap poin bertaut ke tempat ia diajarkan.
Sebelum panah (mendukung LDV-1 dan SDM-2)
- I zoom out to the landscape, then zoom in on one arrow and ask its data questions: initiator, direction, freshness, volume and shape, key, write authority, and who proves it arrived. (Zoom In on One Arrow) ⟲
- Saya memisahkan siapa yang memulai dari ke mana data mengalir, dan saya tahu hanya klien yang melihat seluruh perjalanan pulang-pergi. (Siapa yang Memulai Bukanlah ke Mana Data Bergerak)
- I treat freshness as a requirement, not a default, and match the timing to the mechanism: a synchronous call when the caller waits, platform events for fire and forget, Change Data Capture to keep another system in step, the Bulk API for large scheduled loads. (How Current Does It Need to Be?) ⟲
- I know a database stores; a process calls: polling needs a process, often middleware, and polling for nothing is waste. Change Data Capture has a daily delivery allocation, counted per subscriber. (Asking Every Minute) ⟲
- I know Salesforce’s guidance for pulling changes on a schedule:
getUpdated()andgetDeleted()for intervals over 5 minutes; more often than that, let Salesforce send the change. (Asking Every Minute) ⟲ - I know the three traffic shapes, singles, sets and bulk; that more than 2,000 records is a good candidate for Bulk API 2.0, fewer for bulkified synchronous calls such as Composite; and to send only the fields that changed. (The Number of Zeros Applies to Integrations Too) ⟲
- I know integration volume becomes data volume: ownership, automation, sharing and storage. (Integration Volume Becomes Data Volume) ⟲
Kunci dan otoritas tulis (mendukung SDM-2, SDM-4, dan MDM-2)
- I carry an external system’s key in an External ID field marked Unique, one-to-one, and upsert on it: no match creates, one match updates, more than one fails. (One Record, One Key) ⟲
- When one customer has several external records, I add records, not fields (a hierarchy, peers or a child object), never a key field per ERP. (When the Customer Is in Two ERPs, chapter 6: One Customer, Two ERPs) ⟲
- I know one key field with the source in the value is still one key per record, and a new partner is a new value, not a new field. (Steve Trucking: One Field, the Source in the Value) ⟲
- Saya tahu kunci yang stabil membuat coba ulang aman (awal idempotensi). (Kunci Membuat Coba Ulang Aman)
- I know a key isn’t authority, and enforce write authority in the org: record types, read-only fields for users, and an integration user with only the access its contract needs. (A Key Isn’t Authority) ⟲
- I know two-way movement still has one owner per field, and how unclear authority causes loops. (Two-Way Movement, One Owner per Field) ⟲
- Saya tahu record ID dari satu org Salesforce bukan kunci perusahaan di org lain: dua org adalah dua sistem. (Kunci Juga Punya Siklus Hidup)
Proof of delivery (supports MIG-1 and MIG-2) ⟲
- I know the client owns the conversation, and whoever knows what should arrive proves that it did; the server keeps its own promises and reports what it received. (Who Proves It Arrived?) ⟲
- I know “no errors” isn’t completeness: reconcile counts and, where it matters, control totals. (“No Errors” Isn’t Completeness) ⟲
- I design for restart and safe retries, and log every call: request ID, endpoint, response code and duration. (Know Where You Are, and Restart Gracefully, Log Every Call, Retries Are Normal; Make Them Safe) ⟲
- I know platform events and Change Data Capture events stay on the bus for 72 hours, subscribers resume by Replay ID, duplicates can happen, and proof needs my own return receipt. (The Return Receipt) ⟲
- I know the soft landing for partial failure, and I send the increment, not the universe. (Partial Failure, and the Soft Landing, Send the Increment, Not the Universe) ⟲
- I know the four shapes: request and reply, fire and forget, batch and events, and where each recovers. (Four Shapes of Integration) ⟲
- I know outbound messaging is supported but gets no further investment, and since Spring ‘26 sends no session ID. (Outbound Messaging: Know It, Don’t Start There) ⟲
Kontrak data integrasi (mendukung SDM-4)
- I can write an integration data contract for an arrow, eleven lines: initiator, direction, freshness, volume and shape, key, write authority, pattern, mechanism, proof of delivery, sensitivity and travel, and change. (An Arrow Needs More Than a Label) ⟲
- I go requirement, then pattern, then mechanism. (Requirements, Then Pattern, Then Mechanism) ⟲
- I know when to give another team a custom Apex REST endpoint instead of the standard APIs (one stable interface, my own logging and orchestration) and what it costs (code to maintain; API and Apex limits still apply). (A Contract Between Teams) ⟲
- I count every place the data rests on its way, logs and retry queues included, when it has to stay in a country. (Make Each Line Specific) ⟲
- For multiple orgs, I start with a contract per movement, and sometimes the contract says don’t move it (chapter 14). (Multiple Orgs, and “Don’t Move It”) ⟲
Where the rest lives. This chapter is about moving data. Not moving it (Salesforce Connect, mashups, data brought in on demand, zero copy: exam objective LDV-3) is chapter 14, Virtualization, Federation, and Zero-Copy (coming soon). Loading and extracting at volume is chapter 10, Migration and Synchronization. ⟲
Di Luar Ujian
Section titled “Di Luar Ujian ”Ujian adalah batas bawah, bukan batas atas. Inilah kebiasaan dari bab ini yang dibutuhkan seorang arsitek, entah ada pertanyaan ujian tentangnya atau tidak.
- Zoom out, then zoom in. Start with the landscape; then take one arrow at a time. ⟲
- Pahami lalu lintas yang akan datang, bahkan ketika orang lain yang merancang integrasinya.
- Pilih mekanismenya setelah Anda memahami perpindahannya.
- A database stores; a process calls. Someone has to own the process. ⟲
- Perpindahan data tidak gratis. Setiap salinan adalah satu tempat lagi untuk dikelola.
- Add records, not fields. ⟲
- Kenali rekamannya. Kenali pemiliknya. Lalu biarkan integrasi menulis.
- Whoever knows what should arrive proves that it did. ⟲
- Jika ia bisa gagal diam-diam, ia belum selesai. Integrasi yang berhenti adalah masalah kualitas data.
- Izin berkata bisa; arsitektur berkata seharusnya.
- Decide the interface between teams in the first weeks: the standard API or a wrapper you own. ⟲
- Kontraknya bertahan lebih lama dari teknologinya.
- Perlakukan setiap tindakan agen sebagai integrasi, dengan kunci, otoritas, idempotensi, dan keteramatan.
Istilah Penting
Section titled “Istilah Penting ”| Istilah | Dalam satu baris |
|---|---|
| Pemrakarsa | Sistem yang memulai percakapan (klien) |
| Arah data | Ke mana data bisnis bergerak, siapa pun yang memulainya |
| Freshness | How current the data must be |
| Polling | Asking on a schedule whether anything changed |
| Satuan, kelompok, massal | Satu rekaman sekali kirim, kelompok kecil, atau volume besar dalam satu job |
| ID Eksternal | Kunci sistem lain yang disimpan pada rekaman Salesforce, dipakai untuk pencocokan |
| Upsert | Perbarui rekaman yang cocok jika ada, buat jika tidak |
| Idempotensi | Mengulang sebuah operasi tanpa efek tambahan yang tidak diinginkan |
| Watermark / checkpoint | Catatan sejauh mana sebuah integrasi sudah berjalan dengan aman |
| Rekonsiliasi | Membandingkan apa yang dimaksud dengan apa yang tiba |
| Proof of delivery | Evidence, held by the side that knows what should arrive, that it did |
| Return receipt | An acknowledgment sent back to say a message was received and processed |
| Request and reply | The client sends and waits for the answer |
| Fire and forget | The client sends without waiting for the outcome |
| Platform event | Pesan yang diterbitkan di event bus Salesforce untuk para subscriber |
| Change Data Capture | Event yang diterbitkan Salesforce ketika rekaman berubah |
| Replay ID | Posisi yang dipakai subscriber untuk melanjutkan membaca event |
| Custom Apex REST | Your own REST endpoint in Salesforce, written in Apex, in front of your objects |
| Kontrak data integrasi | Catatan singkat tentang apa yang boleh dilakukan sebuah integrasi terhadap data |
Uji Diri
Section titled “Uji Diri ”Skenario singkat dengan gaya kursus ini. Tentukan jawaban Anda sebelum membukanya.
1. Salesforce memanggil ERP untuk mendapatkan status kredit pelanggan. Ke mana data mengalir, dan siapa pemrakarsanya?
Salesforce yang memulai; datanya mengalir ERP → Salesforce. Pemrakarsa dan arah adalah pertanyaan yang terpisah, dan pemrakarsa (klien) adalah pihak yang melihat seluruh perjalanan pulang-pergi. Baca lagi Siapa yang Memulai Bukanlah ke Mana Data Bergerak.
2. Tim mengusulkan membuat rekaman Salesforce untuk setiap pembacaan GPS: 200.000 sehari. Apa yang Anda tanyakan pertama kali?
Mengapa memasukkan 73 juta pembacaan setahun ke model transaksional? Itu keputusan arsitektur data sebelum menjadi keputusan integrasi; org mungkin hanya butuh posisi terakhir. Baca lagi Volume Integrasi Menjadi Volume Data.
3. A warehouse team says, "Snowflake will just poll Salesforce every minute." What's missing?
⟲A database stores; a process calls. Something has to run the polling (usually an integration layer), with its own credentials, schedule and failures, and 1,440 calls a day mostly find nothing. Ask how current the data must be, then consider letting Salesforce send the changes (Change Data Capture), and count the events. Reread Asking Every Minute.
4. An external system needs Salesforce's changes about every hour, including deletions. What does Salesforce's own guidance suggest?
⟲For intervals over 5 minutes, the SOAP API’s getUpdated() and getDeleted() return what changed and what was deleted in a window, instead of a full extract. More often than that, let Salesforce send the change. Reread Asking Every Minute.
5. The ERP retries a "create customer" call after a timeout and Salesforce ends up with two accounts. How should it have been designed?
⟲Upsert on the ERP’s customer number in an External ID field marked unique, so a retry matches the existing record instead of inserting a duplicate. Reread Keys Make Retries Safe.
6. The customer exists in two ERPs, and someone proposes `NA_ERP_ID__c` and `EMEA_ERP_ID__c` on the Account. Your view?
⟲That’s a key field per ERP: an anti-pattern. It hides repeating structure in fields and turns every new ERP into a schema change. Add records, not fields: child accounts, peer accounts, or a child object per ERP record, each with one key. Reread When the Customer Is in Two ERPs.
7. The integration log shows zero errors, but finance totals don't match. What happened, and who should have caught it?
⟲Zero errors isn’t completeness: maybe fewer records were sent than intended, or values changed in transit. The side that knows what should have arrived proves it did: it reconciles counts and control totals against what it meant to send. Reread Who Proves It Arrived?.
8. A subscriber to platform events was down for a day. Can it catch up?
⟲Yes, within the 72-hour retention: it resumes from its last Replay ID. It must also handle duplicates, because the same event can arrive twice. Reread The Return Receipt.
9. The requirement says "we need a REST integration for credit holds." What's wrong with that?
⟲REST is a mechanism, not a requirement. The requirement is something like “agents see a credit hold within five minutes of the ERP change.” Start there, choose the pattern, then the mechanism, and write the contract. Reread Requirements, Then Pattern, Then Mechanism.
10. A partner's middleware team will send orders that touch four objects, and your data model changes every release. Standard API or custom Apex REST?
⟲It depends on the team. If they know Salesforce deeply and can change quickly, the standard APIs work. If not, a custom Apex REST endpoint gives them one stable interface, lets Salesforce orchestrate the four writes and log every call, and absorbs your changes inside. The cost is code you maintain, inside Salesforce’s API and Apex limits. Decide in the first weeks. Reread A Contract Between Teams.
Jelajahi
Section titled “Jelajahi ”- Salesforce Certified Platform Data Architect Exam Guide (terbuka di tab baru), Salesforce Help (checked 2026-11-01): the official list of objectives and their weights. Always check the current version before you book the exam. ⟲
- Salesforce, Best Practices for Deployments with Large Data Volumes (terbuka di tab baru), Winter ‘27 (last updated September 18, 2026), checked 2026-11-01: the guide behind the exam’s Large Data Volumes section. Its integration rules are in module 1; its mashups are in chapter 14. ⟲
- Bagian Jelajahi di setiap modul mencantumkan dokumentasi Salesforce di balik fakta-faktanya, beserta tanggal pengecekannya.