SAP C-ADBTP-2601 Value Pack (Frequently Bought Together)

SIMULATION
Enable a Cloud Foundry Environment
Task 2: Enable and Configure a Cloud Foundry Environment
In your SAP BTP cockpit, in the EU HCM Dev subaccount, enable the Cloud Foundry environment in the cf-eu10-004 landscape. Set the instance name to cf-eu-hcm-dev and the org name to btpops####-eu-hcm-dev.
In the EU HCM Dev subaccount, create a space with the name activity-recording.
In the EU HCM Dev subaccount, create a space quota with the name half-org-quot a. Halve the available org quota for memory, routes, service, and instance memory for an unlimited number of app instances. Assign the space quota to activity-recording.

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 specifically in EU HCM Dev. SAP documents that Cloud Foundry is enabled at subaccount level, and the system creates a Cloud Foundry org linked to that subaccount.
Part 1 - Enable the Cloud Foundry environment
Step 1 - Open the subaccount overview
In EU HCM Dev, go to Overview.
Explanation:
SAP Help describes the cockpit flow for enabling Cloud Foundry from the subaccount Overview page.
What to verify
You should see a Cloud Foundry section on the overview page.
Step 2 - Start enabling Cloud Foundry
In the Cloud Foundry section, click Enable Cloud Foundry.
Explanation:
This starts creation of the Cloud Foundry organization for the subaccount. SAP notes that when you enable Cloud Foundry in a subaccount, the system automatically creates a Cloud Foundry org for it.
Step 3 - Enter the required Cloud Foundry values
In the enablement dialog, enter:
Landscape: cf-eu10-004
Instance Name: cf-eu-hcm-dev
Org Name: btpops####-eu-hcm-dev
Then confirm by clicking Create or Enable.
Explanation:
The task gives you the exact landscape and naming values to use. SAP documentation shows that enabling Cloud Foundry in the cockpit requires naming the Cloud Foundry instance and org.
What to verify
After the process completes, the subaccount should show Cloud Foundry as enabled, with the org created for EU HCM Dev.


Part 2 - Create the space
Step 4 - Open Spaces
In EU HCM Dev, after Cloud Foundry is enabled, open:
Cloud Foundry
Spaces
Explanation:
SAP Help shows that spaces are created from the Spaces area after Cloud Foundry is enabled in the subaccount.

Step 5 - Create the space
Click Create Space.
Enter:
Space Name: activity-recording
Confirm by clicking Create.

Explanation:
This creates the required Cloud Foundry space inside the org for EU HCM Dev. SAP's cockpit documentation and setup guides show this as the standard next step after enabling the environment.
What to verify
You should now see:
activity-recording
in the list of Cloud Foundry spaces.
Part 3 - Create the space quota
Step 6 - Open Cloud Foundry Space Quotas
In EU HCM Dev, open:
Cloud Foundry
Space Quotas
Explanation:
SAP Help states that, in the Cloud Foundry environment, the quotas allocated to a subaccount can be further distributed by creating space quota plans, and these are managed from the Cloud Foundry Space Quotas area.
Step 7 - Create a new space quota
Click Create Space Quota or New Space Quota.
Enter the quota name:
half-org-quota
Explanation:
This creates a quota plan that you will assign to the required space. SAP Help describes creating space quota plans in the subaccount and then assigning them to spaces.
Step 8 - Set quota values to half of the org quota
In the quota form, set the values to half of the available org quota for:
Memory
Routes
Services
Instance Memory
For App Instances, set:
Unlimited
Then save the quota.

Explanation:
The simulation asks you to halve the available org quota for those four dimensions. SAP Help confirms that space quotas are used to limit resource consumption inside the org by defining values such as memory, routes, and service instances, and that these plans can then be assigned to spaces.
How to calculate "half"
Use the current org quota values shown in the Cloud Foundry quota screens and divide each by 2 before entering it.
Examples:
If org memory = 2 GB, enter 1 GB
If routes = 20, enter 10
If services = 200, enter 100
If instance memory = 2 GB, enter 1 GB
What to verify
The new quota plan should exist as:
half-org-quota
with the reduced values saved.

Part 4 - Assign the quota to the space
Step 9 - Assign the quota to activity-recording
Open the newly created quota:
half-org-quota
Choose Assign Spaces or Assign to Spaces
Select:
activity-recording
Save the assignment
Explanation:
SAP Help states that after creating a space quota, you assign it to one or more spaces from the space quota management flow.
What to verify
The quota half-org-quota should now be assigned to:
activity-recording



Final expected result
Inside EU HCM Dev:
Cloud Foundry is enabled
landscape is cf-eu10-004
instance name is cf-eu-hcm-dev
org name is btpops####-eu-hcm-dev
space activity-recording exists
space quota half-org-quota exists
memory, routes, services, and instance memory are each set to half of the available org quota app instances are unlimited quota half-org-quota is assigned to activity-recording Common mistakes to avoid Enabling Cloud Foundry in the wrong subaccount; it must be EU HCM Dev.
Using the wrong landscape; the task explicitly requires cf-eu10-004.
Typing the wrong org name; use exactly btpops####-eu-hcm-dev.
Forgetting to create the space before assigning the quota.
Entering full org quota instead of half.
Limiting app instances to a number instead of leaving them unlimited.
Creating the quota but not assigning it to activity-recording.