Online Access Free C-ADBTP-2601 Exam Questions

See the Explanation below for complete solution.
Explanation:
Before you start
Log in to SAP BTP Cockpit.
Open the correct Global Account.
Go to Directories.
Open Human Resources.
Open the EU HCM Dev subaccount.
This matters because the task must be completed in EU HCM Dev, and the service instance must be created in the specific Cloud Foundry space activity-recording. SAP Help also confirms that the HTML5 Application Repository is used in the Cloud Foundry environment and that the app-host plan is the host service used to store HTML5 application content.
Step 1 - Open the Cloud Foundry space
In EU HCM Dev, go to:
Cloud Foundry
Spaces
Select the space:
activity-recording
SAP Help describes creating Cloud Foundry service instances by first navigating to the subaccount, opening Cloud Foundry Spaces, selecting the target space, and then using that space's Services > Service Instances are a.
Step 2 - Open Service Instances in the space
Inside the activity-recording space, go to:
Services
Service Instances
This is the Cloud Foundry-space-level location used for creating service instances in that space.
Step 3 - Start creating the new instance
Click Create.

A wizard opens for the new service instance. SAP Help describes this as the standard cockpit flow for creating service instances in Cloud Foundry spaces.
Step 4 - Choose the required service
In the service selection, choose:
HTML5 Application Repository Service
SAP Help documents the HTML5 Application Repository as the service used for centrally storing HTML5 applications' static content on SAP BTP in the Cloud Foundry environment.

Step 5 - Choose the required service plan
Select the service plan:
app-host
SAP Help states that the app-host service plan is used to deploy applications to the HTML5 Application Repository.
Step 6 - Enter the instance name
Set the service instance name to:
html5-eu-hcm-dev
Then continue and confirm creation.
SAP Help recommends using a CLI-friendly name for service instances, and the task gives the exact required name.

Step 7 - Verify the space is correct
Before final confirmation, verify the target Cloud Foundry space is:
activity-recording
This is important because Cloud Foundry service instances are created within a specific space, not only at the subaccount level.
Step 8 - Create and confirm
Click Create or Finish.
Wait for the status to change from in-progress to created.
SAP Help notes that after creation, the instance appears in the service instances table and its status can be checked there.
Final expected result
Inside EU HCM Dev, in Cloud Foundry space activity-recording, you should have a service instance with:
Service: HTML5 Application Repository Service
Plan: app-host
Instance Name: html5-eu-hcm-dev
Common mistakes to avoid
Creating the instance in the wrong subaccount; it must be EU HCM Dev.
Creating it in the wrong Cloud Foundry space; it must be activity-recording.
Choosing the wrong service; use HTML5 Application Repository Service.
Choosing the wrong plan; use app-host. SAP Help specifically links app-host with hosting deployed HTML5 app content.
Typing the wrong instance name; use exactly html5-eu-hcm-dev.

See the Explanation below for complete solution.
Explanation:
Before you start
Log in to SAP BTP Cockpit.
Open your correct Global Account.
Go to the Shared Services directory.
Open the SH Dev subaccount.
This matters because all three required actions must be done inside SH Dev, not in the directory and not in another subaccount.
Part 1 - Entitle the service in SH Dev
Step 1 - Open the subaccount
In the cockpit, choose Directories.
Open Shared Services.
Select SH Dev.
You should now be on the SH Dev subaccount page.

Step 2 - Open Entitlements
In SH Dev, choose Entitlements.
SAP documents that service plans and quotas for a subaccount are added in the subaccount's Entitlements are a.
Step 3 - Add the required service plan
Click Configure Entitlements or Add Service Plans.
Search for SAP Build Work Zone, advanced edition.
Select the service.
Choose the plan standard (Application).
Set the quantity to 1 if a quota/amount field is shown.
Save the entitlement changes.

This task explicitly asks for one standard (Application) service plan. SAP Help also notes that SAP Build Work Zone usage depends on the correct entitlement being available in the subaccount first.
Verify
Under Entitlements, you should now see:
SAP Build Work Zone, advanced edition
plan: standard (Application)
quantity: 1 if shown
Part 2 - Establish trust to the identity provider
Step 4 - Open Trust Configuration
In SH Dev, go to Security.
Choose Trust Configuration.
SAP Help states that trust to a custom identity provider is established from Security > Trust Configuration in the SAP BTP cockpit.
Step 5 - Create the trust
Click Establish Trust.
Enter or select the identity provider:
agvlamkzw.accounts.ondemand.com
Continue through the wizard.
Save the trust configuration.
SAP documents that to use a custom identity provider, the subaccount must have a trust relationship to that provider. SAP also highlights that apps such as SAP Build Work Zone rely on SAP Cloud Identity Services trust configuration.

Verify
On the Trust Configuration page, you should see:
agvlamkzw.accounts.ondemand.com
as a trusted identity provider.

Part 3 - Create the subscription
Step 6 - Open Instances and Subscriptions
In SH Dev, go to Services.
Choose Instances and Subscriptions.
Step 7 - Create the subscription
Click Create.
Choose Subscription if the cockpit asks for a type.
Search for SAP Build Work Zone, advanced edition.
Select the service.
Choose the plan standard.
Confirm the creation.
SAP Help for SAP Build Work Zone scenarios indicates that the subaccount needs the correct entitlements and subscription flow to expose and use SAP Build Work Zone content.
Step 8 - Confirm subscription status
Stay on Instances and Subscriptions.
Check that the new subscription appears and is active.
Verify
You should see:
SAP Build Work Zone, advanced edition
plan: standard
subscription created successfully

Final expected result
Inside SH Dev:
the entitlement for SAP Build Work Zone, advanced edition exists
the entitled plan is standard (Application)
trust is established to agvlamkzw.accounts.ondemand.com
a subscription exists for SAP Build Work Zone, advanced edition
the subscription uses the standard plan
Common mistakes to avoid
Doing the entitlement in Shared Services directory instead of SH Dev
Choosing SAP Build Work Zone, standard edition instead of advanced edition Choosing the wrong plan; the entitlement must be standard (Application) Forgetting the trust step to agvlamkzw.accounts.ondemand.com Trying to subscribe before the entitlement exists