無料でクラウドストレージから最新のCertShiken Integration-Architect PDFダンプをダウンロードする：https://drive.google.com/open?id=1AW5_fXGEYxiwodlnY7giSknep88DEGHb
Integration-Architectテスト資料を購入したすべてのお客様を大切にしています。お客様との協力を継続したいと考えています。 Integration-Architectテストの質問は常に更新および改善されているため、必要な情報を入手してより良い体験を得ることができます。 Integration-Architectのテストの質問は、デジタル化のペースに従い、絶えず改装し、新しいものを追加しています。 Integration-Architect試験準備がお客様に誠実に役立つことを実感していただければ幸いです。また、Integration-Architectトレーニングガイドの合格率は99％から100％であり、Integration-Architect試験に高いスコアで合格することができます。
Salesforce Integration-Architect 認定は、Salesforce 統合に特化したプロフェッショナルにとって貴重な資格です。複雑な統合ソリューションを設計し、実装する能力を検証し、スケーラブルで安全でパフォーマンスに最適化された統合ソリューションの専門知識を証明できます。Salesforce Integration Architect としてのキャリアを向上させたい場合、この認定試験はあなたの目標達成に役立ちます。
Salesforce Certified Integration Architect認定は、自己のキャリアを向上させたい専門家にとって名誉ある資格であり、価値のあるものです。これは、Salesforceの統合ソリューションのエキスパートレベルの知識と、ビジネスの成功を達成するためにどのように活用できるかを証明します。この試験に合格するためには、データおよびアプリケーションアーキテクチャの経験と知識、さらにはSalesforceの統合能力のエキスパートレベルの知識が必要です。この資格を持つ個人は、エキスパートレベルの統合スキルを必要とするさまざまな高収入の職種を追求することができます。
>> Integration-Architect復習教材 <<
SalesforceのIntegration-Architect認定試験はIT業界の中でとても普遍的な試験になります。試験の準備は時間とエネルギーがかかります。時は金なり社会に時間を無駄しないようによいツルを探し出されるのはみんなの希望です。CertShikenのSalesforceのIntegration-Architect認証試験の問題集は君の20時間だけかかりますよ。
Salesforce Integration-Architect認定試験に合格するには、候補者はさまざまな統合パターン、フレームワーク、およびベストプラクティスに関する知識を証明する必要があります。また、SalesforceプラットフォームとそのさまざまなAPIについて深い理解を持っている必要があります。この試験は60の多肢選択問題から構成され、105分間続きます。合格点は63％で、試験費用は400ドルです。試験に合格すると、候補者は業界で認められ、尊敬されるSalesforce Certified Integration Architect資格を取得できます。
質問 # 17
Northern Trail Outfitters' (NTO) Salesforce org usually goes through 8k-10k batches a day to synch data from external sources. NTO's Integration Architect has received requirements for a new custom object, FooBarc, for which 90M records will need to be loaded into the org. Once complete, 20GB (about 30M records) needs to be extracted to an external auditing system.
What should the architect recommend using to meet these requirements in a day?
正解：A
解説：
Answer D is valid because using Bulk API 2.0 for both inserting and querying data can meet the requirements of loading and extracting large volumes of data in a day. Bulk API 2.0 is a RESTful API that allows creating, updating, deleting, or querying millions of records asynchronously by uploading or downloading CSV or JSON files. Bulk API 2.0 has several advantages over Bulk API 1.0, such as:
It does not count against the daily limit of 5,000 batches per rolling 24-hour period.
It supports PK Chunking for queries, which automatically splits large data sets into manageable chunks based on the primary key.
It simplifies the job lifecycle and reduces the number of API calls needed to perform a bulk operation.
Answer A is not valid because using Bulk API 2.0 for inserting data and REST API for querying data is not an optimal solution for handling large volumes of data in a day. REST API is a synchronous API that allows creating, updating, deleting, or querying individual records or small batches of records using HTTP methods. REST API has several limitations and drawbacks for this use case, such as:
It counts against the daily limit of 15,000 API requests per 24-hour period.
It does not support PK Chunking for queries, which means that large data sets may exceed the query timeout or heap size limits.
It requires more API calls and processing time to perform a bulk operation than Bulk API 2.0.
Answer B is not valid because using Bulk API 1.0 for both inserting and querying data is not a feasible solution for handling large volumes of data in a day. Bulk API 1.0 is a SOAP-based API that allows creating, updating, deleting, or querying millions of records asynchronously by uploading or downloading XML or CSV files. Bulk API 1.0 has several limitations and drawbacks compared to Bulk API 2.0, such as:
It counts against the daily limit of 5,000 batches per rolling 24-hour period, which may not be enough to load and extract 90M and 30M records respectively.
It does not support JSON format for data files, which may not be compatible with some external systems or applications.
It requires more API calls and complexity to manage the job lifecycle and handle errors or retries than Bulk API 2.0.
Answer C is not valid because using Bulk API 1.0 for inserting data and REST API for querying data is not a suitable or reliable solution for handling large volumes of data in a day. As explained above, both Bulk API 1.0 and REST API have limitations and drawbacks that may affect the performance, efficiency, and scalability of the integration.
質問 # 18
A company's security assessment noted vulnerabilities on the un managed packages in their Salesforce orgs, notably secrets that are easily accessible and in plain text, such as usernames, passwords, and OAuth tokens used in callouts from Salesforce.
Which two persistence mechanisms should an integration architect require to be used to ensure that secrets are protected from deliberate or inadvertent exposure?
Choose 2 answers
正解：B、D
解説：
Explanation
Named Credentials and Protected Custom Settings are two persistence mechanisms that can be used to ensure that secrets are protected from deliberate or inadvertent exposure. Named Credentials allow you to specify the URL of a callout endpoint and its required authentication parameters in one definition. Salesforce manages all the authentication for Apex callouts that specify a named credential as the callout endpoint, and you don't have to add more authentication logic in your Apex code. Named Credentials can be defined to provide a secure and convenient way of setting up authenticated callouts, and they can also be used in Lightning components, Visualforce pages, and flows1.
Protected Custom Settings are a type of custom settings that store application-specific data that is hidden from subscribers. They are only accessible by the managed package that created them, and they can be used to store secrets such as encryption keys, passwords, or tokens. Protected Custom Settings can be accessed by Apex code, formulas, or validation rules within the same namespace as the settings2.
Encrypted Custom Fields are not a suitable mechanism for storing secrets, because they are not designed to prevent unauthorized access to sensitive data. Encrypted Custom Fields allow you to encrypt text fields using a standard encryption scheme. The encrypted data is masked in reports, list views, and search results, but it can still be viewed by users who have the "View Encrypted Data" permission. Encrypted Custom Fields are intended to protect data from unauthorized access by users within your organization, not from external threats or malicious code3.
Protected Custom Metadata Types are another type of custom metadata types that store application-specific data that is hidden from subscribers. They are similar to Protected Custom Settings, but they have some advantages such as being deployable using change sets or Metadata API, being accessible by SOQL queries, and being able to reference other metadata types or settings. However, Protected Custom Metadata Types cannot be used to store secrets, because they do not support encryption or masking of sensitive data. Protected Custom Metadata Types are intended to store configuration data that is specific to your managed package, not secrets that need to be secured.
Therefore, the correct answer is B and D, because Named Credentials and Protected Custom Settings are the only persistence mechanisms that can be used to securely store secrets in Salesforce.
References: 1: Named Credentials | Apex Developer Guide | Salesforce Developers 2: Custom Settings | Apex Developer Guide | Salesforce Developers 3: Encrypted Fields | Salesforce Help : [Protected Custom Metadata Types | ISVforce Guide | Salesforce Developers]
質問 # 19
Northern Trail Outfitters (NTO) use Salesforce to track leads, opportunities, and to capture order details. However, Salesforce isn't the system that holds or processes orders. After the order details are captured in Salesforce, an order must be created in the remote system, which manages the orders lifecylce. The Integration Architect for the project is recommending a remote system that will subscribe to the platform event defined in Salesforce.
Which integration pattern should be used for this business use case?
正解：B
質問 # 20
A company's security assessment noted vulnerabilities on the unmanaged packages in its Salesforce orgs; notably, secrets that are easily accessible and in plain text, such as usernames, passwords, and OAuth tokens used in callouts from Salesforce. Which persistence mechanisms should an integration architect require to be used to ensure that secrets are protected from deliberate or inadvertent exposure?
正解：B
解説：
The scenario highlights vulnerabilities in unmanaged packages where secrets (usernames, passwords, OAuth tokens) are stored in plain text and easily accessible. The goal is to protect these secrets from exposure in callouts, especially in unpackaged or unmanaged code contexts.
Why A (Protected Custom Metadata Types and Named Credentials)?
Named Credentials is the primary Salesforce-recommended mechanism for securely storing authentication details (including passwords, tokens, and secrets) for HTTP callouts. Secrets are encrypted, not visible in debug logs, and Salesforce handles authentication without exposing them in Apex code.
However, in Named Credentials, admins with "Customize Application" permission can view/edit the secrets.
To further protect secrets (e.g., hide them completely from admins or in packaged scenarios), use Protected Custom Metadata Types (preferably in a managed package). These allow Apex code in the same namespace
/package to access the secrets while hiding them from users, API queries, or subscriber orgs.
This combination addresses both standard callouts (via Named Credentials) and cases needing maximum obfuscation (via Protected Custom Metadata), directly mitigating plain-text exposure in unmanaged packages.
Why not B (Encrypted Custom Fields and Protected Custom Settings)?
Encrypted Custom Fields are suitable for sensitive data like PII (e.g., credit cards, SSNs) but explicitly not recommended for storing authentication secrets or credentials used in callouts (per Salesforce Secure Coding guidelines).
Protected Custom Settings offer similar protection to Protected Custom Metadata but are less preferred for configuration-like data (secrets are configuration). Custom Metadata is deployable as metadata, better for packaging and migrations.
Why not C (Named Credentials and Protected Custom Settings)?
While Named Credentials are ideal, pairing with Protected Custom Settings is valid but suboptimal.
Salesforce documentation and Trailhead modules favor Protected Custom Metadata Types over Custom Settings for secret storage due to better deployability, caching, and metadata API support.
This aligns with Salesforce Trailhead ("Securely Store Secrets with Salesforce Features") and secure coding guidelines, emphasizing Named Credentials for callouts and Protected Custom Metadata for high-security secret storage in packages. For unmanaged code vulnerabilities, migrating to these mechanisms (ideally with packaging) prevents exposure.
質問 # 21
A company uses Customer Community for course registration. The payment gateway takes more than 30 seconds to process transactions. Students want results in real time to retry if errors occur. What is the recommended integration approach?
正解：C
解説：
Standard synchronous Apex callouts have a timeout limit, and more importantly, Salesforce limits the number of long-running requests (those lasting longer than 5 seconds) that can execute concurrently. If a payment gateway consistently takes 30 seconds, a few simultaneous users could easily exhaust the org's concurrent request limit, causing the entire system to stop responding.
The Continuation pattern (Option C) is designed specifically for this "long-wait" scenario. It allows the Apex request to be suspended while waiting for the external service to respond, freeing up the Salesforce worker thread to handle other users. Once the gateway responds, the suspended process resumes and returns the result to the student's browser. This provides the "real-time" experience required for the student to retry immediately without the risk of bringing down the entire community due to thread exhaustion.
質問 # 22
......
Integration-Architect勉強時間: https://www.certshiken.com/Integration-Architect-shiken.html
BONUS！！！ CertShiken Integration-Architectダンプの一部を無料でダウンロード：https://drive.google.com/open?id=1AW5_fXGEYxiwodlnY7giSknep88DEGHb