IBM C1000-182 IBM Sterling File Gateway v6.2 Administration Exam Practice Test

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 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 records the creation, modification and deletion of administrative resources in the AUDIT_ADMIN table. Each entry holds the date and time of the operation, the resource name and type, the action performed and the user ID of the person who performed it. The table also captures when a user obtains or releases a lock on a resource through the Lock Manager. This information is presented through the Admin Audit report, which is run from Operations > Reports by selecting the Admin Audit type. Two report sources are provided: AdminAuditByObjectType, which groups changes by resource type, and AdminAuditByPrincipal, which groups them by user ID. Both show when something changed and who changed it, so they support change tracking, accountability and compliance reviews. The System Health Report describes the condition of the platform and does not record who modified a resource. Resource Change Log and User Activity Report are not the product's report names for this purpose. Because audit data is stored in a database table, it is also subject to the archive and purge settings that govern how long audit records remain available.

When a thread becomes runaway, blocked or is consuming excessive resources, the administrator can end it from the Thread Monitor, which is reached by selecting Operations > System > Threads. Each running thread is listed with its state and the activity it is performing, and two actions are available. Interrupt thread asks the thread to terminate, and Stop thread ends it forcibly. They act directly on the thread and do not wait for the current processing step to finish, which makes them the right tools when delay would risk an out-of-memory condition or a crash. Because the business process that was using the thread may be left incomplete, it should be reviewed afterwards and recovered if required. Stopping the business process from the Business Process Manager does not necessarily end a thread that is stuck inside a service call. The Controllers screen reports the status of system controllers and allows them to be refreshed, but it does not manage individual threads. Database Usage presents pool and connection information, and it offers no way to stop a thread. Stopping or interrupting the thread in the Threads screen is therefore the correct method.

In Sterling File Gateway, a routing channel template defines the pattern for a class of routes, including the permitted producer and consumer groups, the file structure, and how files are identified and delivered. A template can also declare provisioning facts, which are named parameters that cannot be fixed in advance because they differ from one partner relationship to the next, for example, a target directory, a remote file name or a custom value used by a delivery business process. The template only states that these facts exist. The actual values are supplied by the Route Provisioner when an individual routing channel is created from the template, so they are entered and stored in the Routing Channel configuration. This design lets Integration Architects build one reusable template while provisioners tailor each channel without editing the template. The values become part of the channel and are available to the processing business processes at run time. The producer, consumer and type sections of the template describe structure and are not where values are entered.

User exits are points at which customers or partners can link their own Java code into predefined product operations. In Sterling B2B Integrator and Sterling File Gateway, the mailbox component exposes user exits that are hooked into message add, message delete and message extract operations, and these were introduced during the 5.2 release stream. A class that implements the relevant Java interface is registered in MailboxUserExits.xml in the properties directory, under the matching user exit bean. The code then runs whenever a message is placed in a mailbox through the Mailbox Add service. This lets an implementer add custom logic such as allowing or blocking file extensions, checking file names or upload times, or starting a business process immediately when a message arrives instead of waiting for the scheduled routing rule evaluation. The WebSphereMQ Suite Put Service and the JMS Send Service are transport services that hand messages to external queues. They do not expose a comparable user exit hook. The Message Add Service is also not the documented user exit point, so the Mailbox Add Service is the correct choice.

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.

Sterling B2B Integrator writes its logs through a logging framework whose behaviour is defined in the logging configuration. Settings can be applied at two scopes. Global settings apply to every log, and they set defaults such as the log level, the rollover behaviour and the number of files to retain. Individual settings apply to a specific log, such as the one for a particular adapter, service or component, and they override the global values for that log only. This allows an administrator to raise detail for a single component while troubleshooting, without flooding the file system with debug output from the whole system. The properties are normally maintained in customer_overrides.properties, using the logService prefix, so the settings remain in place after upgrades. Rollover interval and verbosity are individual settings that control how a log behaves and are not scopes. System is a category of log, for example the system log, and not a level at which configuration is applied. Debug logging should be enabled only for the duration of an investigation and then returned to the default level to limit performance impact and disk consumption.

Sterling B2B Integrator stores transactional, reference and history data in its database, and the size of that database settles only when the volume of data removed matches the volume added. Removal is governed by the lifespans configured in Archive Manager for business processes and documents, together with the archive and purge schedules. If retention periods are set too high, data that is no longer needed stays in tables such as WORKFLOW_CONTEXT, DOCUMENT and ARCHIVE_INFO for longer than necessary, and the database eventually reaches capacity. IBM therefore recommends lowering retention periods, confirming that the backup, index and purge services run, and reviewing the DBStats report to see which data is accumulating. A few errors in business processes do not cause a database to fill, since they generate comparatively little data. Failing to rebuild indexes affects query speed and may increase fragmentation, but it is a performance concern rather than the cause of reaching capacity. A functioning Control service sending notifications is normal operation and unrelated to storage growth. Excessive retention is therefore the correct cause.

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.

The Perimeter Servers area of the System Troubleshooting page lists every perimeter server configuration known to Sterling B2B Integrator, whether local or remote, together with its name, its enabled or disabled state, the On/Off setting and its last activity. Beyond viewing status, an administrator can use the On/Off control to disable a perimeter server. When the entry is disabled, Sterling B2B Integrator stops contacting that perimeter server, so the connections that depend on it are stopped. The same control is used to enable the server again. This makes the screen useful during maintenance, when a DMZ server must be taken out of service without editing adapter configurations. The screen does not provide a restart function, because starting and stopping the perimeter server process itself is done on the host where it runs. It is also not limited to perimeter servers that adapters use; IBM has acknowledged that it does not identify servers without an associated adapter. The last activity value shows the most recent activity and is not a history reaching back to installation. Option D is therefore the accurate statement.

The Cache Usage page of the System Troubleshooter is a read-only monitoring view. It lists the caches that Sterling B2B Integrator currently maintains in memory, such as those for configuration objects, certificates, business process definitions and other frequently used data, and for each one it reports statistics, including the number of requests made and the number of those requests that were satisfied from the cache, which are the hits. From these figures an administrator can calculate a hit ratio and judge whether a cache is effective. A low ratio, or a cache that is continually refilled, suggests that its size or lifetime is not appropriate for the workload and that the system is repeating database reads, which slows processing. The screen does not change anything. Cache sizes and related behaviour are tuned separately, by setting the appropriate properties in customer_overrides.properties, followed by a restart. The page also has no function to detect or report corrupted caches, so statements A, C and D describe capabilities that it lacks. Statement B accurately describes its purpose, which is to inform tuning decisions made elsewhere.

The JDBC adapter lets a business process work with any JDBC-compliant database. Through its associated services, a business process can submit ordinary SQL statements such as select, insert, update and delete, call stored procedures, and invoke stored functions, and then use the returned result sets or output parameters in later steps. Connection details, including the driver, URL and credentials, come from a JDBC connection pool defined for the adapter, while the statement itself is supplied by the business process. This flexibility is why the adapter is used to read reference data from an external system, write transaction results back to an application database, or run database-side logic as part of a workflow. The adapter is therefore not limited to queries that are tied to a translation map, and it does not offer only a fixed set of predefined queries. It also does not restrict a business process to update statements. Because statements run with the privileges of the configured database account, administrators should grant only the access the business process requires and should avoid placing credentials in business process definitions.

Sterling File Gateway installs a default partner group named All Partners, and every partner that is created, imported or migrated is automatically associated with it. This is also why an administrative account must not be tied to an identity that belongs to All Partners, since membership in a partner group prevents login as an administrator. Partner groups are collections of partners that share characteristics and are managed by Integration Architects. Their purpose is to define the producers and consumers that a routing channel template may serve. When a template names a producer group and a consumer group, only partners in those groups can be used in routing channels created from it, and broadcast groups let one file reach many consumers. Statement B is incorrect because a community is a separate concept: communities define the protocols and options available to partners, which is the role described in statement C. Partner groups should also not be confused with user groups, which assign permissions to users. Statement D is unreliable because a group that is referenced by a routing channel template cannot simply be removed. Statements A and E are therefore the accurate pair.

The Node Status screen under Operations > System > Cluster gives a consolidated view of the health of a clustered Sterling B2B Integrator and File Gateway installation. It presents the status of each node, including the application server nodes, and of the adapter containers that are deployed separately from them. Adapter containers are independent JVMs that host communication adapters, so their availability is directly important to file transfer, and displaying them alongside the nodes lets an operator see at a glance whether the containers are running, and which node or container needs attention. This is especially useful during maintenance, when engine nodes and adapter containers are stopped and started at different times, and after failures, when it identifies which part of the platform has gone down. For details of the workload inside a node, administrators use other screens, such as QueueWatch, the Thread Monitor and the Troubleshooter. System controllers are viewed on their own Controllers page, and the workflow engine and activity engine are internal components that are not listed as separate resources on Node Status. Adapter Containers are the resource shown in addition to nodes.

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 can be extended with custom protocols. The definition of a custom protocol is held in AFTExtensionsCustomer.xml, which names the protocol, references the business process that implements it through the bp attribute, and declares its fields. The text shown to users, such as the labels and descriptions for those fields, comes from AFTExtensionsCustomer.properties. IBM instructs administrators to use the shipped AFTExtensions.properties file only as a guide, copy the pattern, and never edit AFTExtensions.properties or AFTExtensions.xml directly. The new properties file is placed in the aft application's WEB-INF/classes/resources directory under the installation directory. The element type shown for each field is set with the htmlType attribute, which can be text, password or select. After the files are saved, the administrator stops Sterling File Gateway, runs setupfiles.sh and deployer.sh, and restarts so that the extra protocol appears when communities and partners are created. The value of the bp attribute cannot be changed once set, because the product does not reread it at run time, so a new protocol name must be created for a different business process. The properties file is therefore the one that holds field descriptions.

An SSH/SFTP remote trading partner profile describes how Sterling B2B Integrator connects to a partner's SSH server, including authentication, algorithms and compression. The Compression field accepts two values. NONE sends data without compression, which is the usual choice when the files are already compressed or when processor use must be minimised. ZLIB applies zlib compression to the SSH data stream, which can reduce the transfer time for text and other compressible data over slower links, at the cost of additional processing. Both partners must agree on the setting, because compression is negotiated during the SSH handshake, so an administrator should confirm the partner's server support before selecting ZLIB. The other options belong to different categories of SSH settings. AES is an encryption cipher that protects the confidentiality of the session and is chosen in the cipher fields. MD5 and SHA1 are hash algorithms used by message authentication codes to check the integrity of the transferred data, and they are chosen in the MAC fields. Because none of those three describes how data is compressed, they are not valid for the Compression field, and ZLIB and NONE are the correct pair.