Free Practice Questions for the IBM Certified Administrator C1000-182 Exam (2026 Updated)

myFileGateway 2.0 is a modern web application that talks to the Sterling B2B Integrator and Sterling File Gateway REST APIs, and those APIs are hosted on a WebSphere Liberty server. When a partner downloads a file, the Liberty server handles the transfer, and the largest file that can be downloaded is limited by the RAM of the computer and the heap size of the JVM running that server. Large downloads that fail are therefore a capacity problem on the Liberty server and not a product limit set in a property. IBM's documented workaround is to increase the RAM of the machine and then raise the JVM heap by editing the jvm.options file of the Liberty server, using -Xmx for the maximum heap and -Xms for the minimum. The server must be restarted for the change to take effect, and the change should be tested in a non-production environment first, because it can affect uploads and other clients. Adding overrides to customer_overrides.properties or changing sandbox.cfg does not alter Liberty's memory, and hosting the application on an HTTP server adapter only determines how it is exposed, not how much data the API server can buffer.

Sterling File Gateway raises an event, identified by an event code, at each significant point in a file's life, for example when a file arrives, is routed, delivered or fails. Some of these events can trigger email notifications to subscribers. Users manage their own subscriptions from Profile > Notifications, where they choose the events they want, and partners using myFileGateway can do the same through the Event Subscription permission. When a subscribed event occurs, the system sends an email to the address stored on the user account, subject to the event's permissions and to the notification settings of the community the partner belongs to. Administrators can also control which events are available for subscription and can edit the email templates, such as FgRouteEventEmailNotification, used for administrative and partner messages. Removing the Event Subscription permission stops a user from adding subscriptions, but existing subscriptions continue to deliver notifications. Because the capability is built in, no routing channel change or custom business process is needed, and the B2B dashboard's user news is a general announcement feature rather than a mechanism for file event alerts.

Data privacy regulations such as GDPR require organisations to protect personal data with appropriate technical and organisational measures, and to keep those measures effective over time. For a file transfer platform like Sterling File Gateway, which handles business documents that may contain personal information, this means treating security as a continuing process. Administrators should periodically review how the platform is secured, including user and partner access, password and certificate policies, encryption of data in transit and at rest, audit and event retention, and patch levels, then close any gaps identified and strengthen controls where necessary. IBM's security guidance recommends this regular assessment, together with keeping the product at current fixes, because new vulnerabilities and requirements appear continually. High availability, backups and performance tuning are valuable operational practices that support resilience and efficiency, but they do not demonstrate that personal data is being protected, and they are not what privacy law specifically asks for. The key compliance activity is therefore the ongoing assessment of security practices and the upgrading of controls wherever they fall short, which is the description given in statement C.

Sterling File Gateway controls access to its screens through the permissions inherited from user groups. The File Gateway Integration Architects group and the File Gateway Route Provisioners group each inherit the Dash AFT Theme permission, and that permission gives access to the Sterling File Gateway user interface, including Participants > Partners and Participants > Communities, where these personas can view and edit records. System Administrators have unlimited access to all resources and therefore do not need a separate permission. The File Gateway Partner Users group is a different construct. It carries the myFileGateway permissions, such as login, file upload, file download, activity, reports and event subscription, and it gives partner users no access to the Sterling File Gateway administrative interface, so it cannot be used to create or edit partners or communities. IBM also advises not to modify the shipped groups, because changes can be overwritten by later builds, and to create a custom group if a different permission mix is required. A permission described as Provisional Trading Partners or Dashboard users is not the permission that grants partner and community maintenance in this interface. Dash AFT Theme is the correct answer.

ARCHIVE_INFO holds lifespan information for all business processes and document storage in the system. The archive and purge services read it to decide when data is eligible to be archived and when it can be purged; for example, the purge service scans the table in batches. Administrators therefore query it to find workflows and documents whose purge date is unusually far in the future. A well-known case is data with a ten-year lifespan. Messages placed in a mailbox are given a default lifespan of ten years, and the associated business process and documents inherit that lifespan. Backup can archive the data, but the purge service will not remove it until the date is reached. Running the index business process resets the lifespan to the value configured in Archive Manager, and scheduling the mailbox delete service prevents the buildup. Failed File Gateway transfers are tracked in File Gateway activity and visibility data, workflow execution steps are stored in the workflow context tables, and communication sessions are held in session tables. None of those are described by ARCHIVE_INFO, so option B is correct.

Document encryption adds a layer of protection for payloads stored in the database or on the file system. It relies on a system certificate, and the product supplies a predefined certificate named doccrypto for this purpose. The encryption behaviour is defined in the security properties, where the ENC_DECR_DOCS setting controls whether documents are encrypted in the file system, the database or both, and the CERT_NAME setting names the system certificate that is used. If an organisation creates its own document encryption certificate, such as doccrypto2, the CERT_NAME value must reference it. Following IBM's practice for property changes, the edit is made through customer_overrides.properties using the security. prefix, so that the change survives upgrades, and the system is restarted for it to take effect. The shipped definitions belong to security.properties, which makes it the correct file for this question. propertyEncryption.properties concerns the encryption of sensitive values stored in property files, such as passwords. sandbox.cfg holds installation and environment settings such as ports and JVM options. jdbc.properties defines database connection pools. None of them manages document encryption.

IBM documents a fixed procedure for changing the look of the Sterling B2B Integrator interface, and the order matters because each step depends on the previous one. First, the administrator edits skins.properties_style_ext, the extension file that holds site-specific style values, leaving the shipped skins.properties file untouched so that the customisation survives upgrades. Second, the deployer script, deployer.sh on UNIX and Linux or deployer.cmd on Windows, is run so the web application resources are rebuilt to include the changed style settings. Editing the file alone has no effect until it has been deployed. Third, Sterling B2B Integrator is restarted so that the deployed application loads the new configuration. Finally, users clear or refresh their browser cache, since browsers retain style sheets and images and would otherwise keep showing the previous appearance until the cached copies expire. The sequence is therefore edit, deploy, restart and refresh, which corresponds to D, C, A and B. Following it in this order avoids the common situation in which a change appears to be ignored because it was never deployed or was hidden by cached content.

Sterling B2B Integrator offers several security-related services, and they differ in how much of the protection process they cover. PGP, which implements the OpenPGP standard, supports the complete set of operations. A document can be encrypted with the recipient's public key and decrypted with the matching private key, which gives confidentiality, and it can be signed with the sender's private key and verified with the sender's public key, which gives integrity and authentication. The same package can be configured for both in one step, so sending a file that is signed and encrypted requires only one service. In Sterling File Gateway, PGP processing is commonly performed with the built-in PGP service or through the Command Line 2 adapter with an external PGP implementation, and an adapter group can be used to balance high volumes. By contrast, the XML Digital Signature services, shown here as xmIDSig and ebXMLDSig, are designed only for signing and verifying XML content, and the XML Encryptor service is concerned with encryption and decryption of XML elements. None of those three provides both families of operations, so PGP is the correct choice.

Sterling B2B Integrator protects the integrity of its configuration objects, including business processes, maps, services and schedules, through resource locking. When a user opens a resource for modification, or the system is processing it, the resource is locked automatically so that nobody else can change it at the same time. This prevents one administrator's edits from silently overwriting another's, and it avoids a definition being altered while a process is running with it. The lock is released when the edit is completed or cancelled, or when the session or processing ends. If a lock remains after an interrupted session, it can be cleared by an administrator through the resource management functions, and this should be done with care, so that in-progress work is not lost. Merely viewing a resource does not change it, so it does not need to be locked, and the same is true of exporting a copy or marking an item as a favourite, which are read operations that do not interfere with the stored definition. Locking therefore applies when a resource is being edited or processed, as stated in option C.

Sterling File Gateway ships with preconfigured user groups that follow the principle of least privilege. The File Gateway Operators group is intended for support and operations staff. Its members can search for and view file transfer activity, examine arrived file and delivery events, use the Activity Snapshot, run reports, and perform recovery actions such as redelivering or replaying files that failed. Operators do not receive the Dash AFT Theme permission that opens the configuration screens, so they cannot create or edit partners, communities or routing channel templates. Integration Architects hold that configuration authority for communities, partners, partner groups and routing channel templates, which is more access than this engineer needs. Route Provisioners create and maintain routing channels for partners, and that also goes beyond monitoring and redelivery. Partner Users is a different category altogether: it grants access to myFileGateway for a trading partner's own files and carries no operational monitoring rights across partners. IBM advises leaving the shipped groups unchanged, because modifications can be overwritten by later builds, and creating a custom group when a different combination of permissions is required. Operators fit the described responsibilities exactly.

Sterling B2B Integrator uses internal connection pooling so that connections to the database server are reused instead of created for each request. Every JVM that runs part of the product, such as the application server nodes, the adapter container nodes and the operations server, creates its own connection pools. A pool holds a number of connections up to its configured maximum size, and when all pools are in use the system may request additional connections up to the buffer size. In a cluster, the database therefore sees the combined demand of every pool in every JVM. The total number of connections is the sum of the connections in all those pools, and it grows as nodes or pools are added. This is the reason capacity planning must multiply pool sizes by the number of JVMs and compare the result with the maximum number of sessions the database allows. If the total exceeds that limit, new connection attempts fail. A pool is not equal to a single connection, and a pool does not use one connection regardless of the number of JVMs. The total is also clearly dependent on the pools, which is why option D is correct.

A set of scheduled business processes keeps Sterling B2B Integrator healthy, and the System Troubleshooter is where an administrator checks that they are active. Backup (Schedule_BackupService) archives business process and document data that has reached its lifespan. The index service (Schedule_IndexBusinessProcessService) assigns lifespans and archive dates to business processes and documents, and the purge service (Schedule_PurgeService) removes data that has been archived and has expired. BPRecovery restarts or resumes business processes that were interrupted, which supports recovery after a failure, and BPLinkagePurgeService cleans up linkage records between processes. If any of these schedules is disabled or fails, data accumulates in the database, the database grows, and performance declines, as the weekly database maintenance check and the DBStats report would later reveal. Monitoring them is therefore a routine operational task. The File Gateway route processes are important for file routing, but they are part of Sterling File Gateway's routing flow and not the core system maintenance schedules asked about here. DBHeartbeat and SystemAlertsNotifications are single items and do not represent the group of critical maintenance processes.

FTP uses two connections: a control connection for commands and a separate data connection for file content and directory listings. Active and Passive modes differ in which side opens the data connection. In Active mode, the client sends a PORT command and the server connects back to the client, which can be blocked by firewalls. In Passive mode, the server announces an address and port, in a 227 response, and the client opens the connection. Because a data connection is created for each transfer command, the choice is made on the services that perform transfers, and the Sterling B2B Integrator FTP Client services allow the mode to be set as a parameter in the business process. The same parameter appears on the PUT and GET services, so option A is the best match. The Begin Session service opens the control session and defines the host, port and credentials, and it does not decide how each data connection is opened. The FTP Client adapter supplies perimeter server and port range settings, and ftp.properties holds general settings rather than the per-transfer mode.

The 4 Eyed Principle is switched on through the enable.4eyedPrinciple property. Once it is active, a change to a protected resource such as a business process is not applied immediately. It is captured as a request that a Super User must approve or reject before the change takes effect. Because requests are held separately from the live resource, an editor can raise several edit requests against the same business process while earlier requests are still pending, which makes statement C correct. Installation, upgrade and patch procedures update business processes and other system resources automatically. The approval workflow would intercept those updates and stall them, so IBM directs administrators to turn the property off before the procedure and enable it again once the work is complete, which makes statement D correct. Statement E contradicts the purpose of the control, which is to enforce separation of duties: the person who raises a change cannot also be the person who approves it. Statements A and B describe behaviour that the feature does not provide, and neither matches IBM's documented handling of pending requests or of the resources placed under approval control.

A mailbox in Sterling B2B Integrator is a repository for messages exchanged with trading partners, and access to it is controlled by permissions that can be granted to individual users or to user groups. When a mailbox is assigned to a group, every member of that group inherits the same access, so administrators avoid granting rights user by user. Members can sign in to the Mailbox Browser Interface and both add files to the mailbox and extract files from it, and they can do so through protocol adapters such as FTP and SFTP when the same rights are in place. The rights are not limited to a single action: it is not true that members can only view, only add or only extract. Within Sterling File Gateway, similar permissions are granted automatically to partner users for the mailboxes created for their routing channels, and View and Execute rights on intermediate mailboxes allow traversal of the mailbox tree. Using groups also simplifies auditing and offboarding, because removing a user from the group immediately removes the mailbox access. Statement D matches the documented behaviour of group assignment.