C_ADBTP sample questions & answers

A Nordic maritime logistics and port operator headquartered in Oslo runs its vessel-scheduling extension on SAP Business Technology Platform. As part of standing up the production landscape, the platform administration team assigned the relevant service plan from the global account down to the "Port-Operations-Prod" subaccount, and the cockpit shows that the right to use the plan now appears under that subaccount with the expected quantity. The team's runbook calls for a validation step in which a developer confirms the extension can actually consume the service before the change is signed off. A developer in the berth-planning squad opens the subaccount, attempts to bind the vessel-scheduling extension to the service, and reports that no usable service binding can be created and the service does not appear as a consumable resource for the application. The administrator re-checks the subaccount, the global-account assignment figures, and the developer's project-level access, and finds them all in order, with the cockpit reporting no errors against the subaccount. Leadership wants the binding available and validated before the next scheduling window opens, so a wrong corrective step that wastes the window is not acceptable. As the platform administrator, you must determine why the service is still not consumable inside the subaccount and what action restores the developer's ability to bind the extension.

Which action correctly addresses why the service cannot yet be bound inside the "Port-Operations-Prod" subaccount?

At the same Oslo-based port operator, the terminal-automation team has onboarded a new operations engineer who must administer workloads in a Cloud Foundry-based runtime within the "Terminal-Ops" subaccount. Following the onboarding checklist, the administrator assigned the engineer a role collection at the subaccount level that aggregates the platform roles the team uses, and trust to the corporate identity provider is established so the engineer can authenticate with corporate credentials. The expected end state is that the engineer can both open the subaccount and operate the applications running in its Cloud Foundry runtime. The engineer signs in to the cockpit successfully and can see the subaccount and its general settings. However, when the engineer tries to view and manage the running applications inside the Cloud Foundry runtime, the actions are refused and the application list cannot be opened. The administrator verifies that the engineer authenticates correctly, that the subaccount-level role collection is assigned exactly as for working colleagues, and that no platform-level errors are logged. Other engineers who were onboarded earlier do not hit this refusal at all. You must determine why platform-level access did not extend into the runtime and what action lets the engineer manage the applications.

Which action correctly explains the refusal and restores the engineer's ability to manage applications in the Cloud Foundry runtime?

The customs-clearance integration team at the Oslo port operator exposes an on-premise declaration system to a cloud application running on SAP BTP so that vessel manifests can be filed automatically. During the cutover, a destination was configured in the "Customs-Integration" subaccount pointing at the declaration system's internal host name, with the correct authentication type set. The Cloud Connector was installed in the on-premise network and connected to the subaccount, and its tunnel to the platform shows as established and healthy. The expected result is that calls from the cloud application traverse the connector and reach the backend. The cloud application nonetheless fails to reach the backend: calls through the destination return an unreachable-host result, even though the on-premise system is healthy and responding normally to local clients on the same network. The administrator confirms that the destination's authentication, the subaccount assignment, and the application's binding to the destination are all correct, and that the Cloud Connector tunnel remains up throughout. A clearance batch is queued behind this path and the team needs reachability restored without a trial-and-error guess. You must determine why the destination cannot reach the backend and what corrective action makes the on-premise system reachable from the cloud application.

Which corrective action makes the on-premise declaration system reachable through the destination?

The platform governance lead at the Oslo port operator is restructuring how SAP BTP subaccounts are organized as the fleet-analytics, berth-planning, and customs programs scale. Today, ten production subaccounts sit directly under the global account with no intermediate structure, and applying consistent administrative settings and governance policies across related subaccounts has become repetitive and error-prone, with settings drifting apart between teams. The lead proposes introducing a grouping layer so that subaccounts belonging to the same program can be managed together and share common configuration from a single place. Finance, however, has stated firmly that contract and billing accountability must continue to roll up to the existing global-account commercial entity and must not move, because the annual entitlement contract is anchored there. A junior administrator worries that adding any grouping layer will change where entitlement and billing accountability sit and reopen the commercial agreement. The change is scheduled for an upcoming maintenance window, so the chosen approach must be settled in advance. As the platform administrator advising the governance lead, you must recommend how to introduce the grouping structure while preserving the existing entitlement source and commercial boundary.

Which recommendation correctly introduces the grouping structure while preserving where entitlements and commercial accountability reside?

The platform engineering team at the Oslo port operator provisions its non-production SAP BTP landscape with Terraform, treating the configuration as version-controlled infrastructure-as-code so that environments can be rebuilt predictably. The team's working agreement is that every change to a managed resource flows through code review and the pipeline. During an urgent test, however, an administrator opened the cockpit and manually changed a managed resource in the "Analytics-Test" subaccount to unblock a colleague, intending to tidy it up later. On the next pipeline run, the Terraform plan reports an unexpected difference for that resource and proposes reverting it to the committed configuration, surprising the team who expected a clean, no-change run. On investigation, the committed Terraform code itself was not edited, the provider configuration is valid, and the state file is intact and reachable. The team wants future runs to be predictable and to stop the recurring surprises without abandoning their infrastructure-as-code practice or freezing the cockpit entirely. You must determine why the plan now shows the unexpected difference and recommend how the team should handle the situation going forward.

Which explanation and corrective practice correctly addresses the unexpected plan difference?

The reliability team at the Oslo port operator is establishing how it will monitor SAP BTP across several subaccounts that host the fleet-tracking and gate-control applications used to run the terminal. One engineer has already set up monitoring within a single application's runtime and can view that application's logs and metrics there in detail. Leadership, however, wants a cross-landscape picture so operations can correlate health and usage across all of the program's subaccounts from one vantage point during incidents, rather than logging into each environment separately. During a design review, the team debates whether the per-application monitoring already in place is sufficient or whether a different category of tooling is required to meet the cross-landscape goal, and there is pressure to avoid throwing away the work already done. The administrator must align the team with BTP's observability approach, which distinguishes between tools that operate within a single environment or application and tools intended to provide a consolidated, cross-landscape view. You must recommend how to satisfy the cross-landscape monitoring requirement without discarding the value of the existing per-application setup.

Which recommendation correctly satisfies the cross-landscape monitoring requirement?