A.Custom services that are created using an API that implements the provision, deprovision, bind, and unbind functionality of a service.

B.Services created by developers that are not available in the marketplace. Once created, they behave like service instances created through the marketplace.

C.A service instance provisioned from the marketplace.

D.Services created by developers that are not available in the marketplace. They behave differently than service instances created through the marketplace.

A.cf bind-security-group

B.cf unbind-staging-security-group

C.cf bind-staging-security-group

D.cf unbind-running-security-group

A.Execute cf logs my-app

B.Execute cf logs my-app --resent

C.Execute cf app my-app

D.cf events my-app

A.cf market

B.cf marketplace

C.cf available-services

D.cf services

A.Because of the ephemeral nature of apps in Cloud Foundry, you need to create a mounted volume for your app and write all logs to that mount.

B.Logs should be written to the local files system in /var/log and accessed by executing cf ssh APP_NAME -c tail /var/log/log_name.

C.The logs should be routed to a syslog server in your application.

D.Logging is handled as an event stream. All logs should be written to stdout and stderr.