Q: 13
In ABAP Cloud, you try to reference an SAP API that is not released for cloud use. What is the outcome?
Options
Discussion
B seen this in both the official SAP guides and practice tests. Helps to check the latest ABAP Cloud development documentation too.
Nah, I don’t think A fits here. B is correct, since the syntax check stops you before ATC even runs. A’s more of a trap for classic scenarios. Pretty sure about B but maybe someone’s seen edge cases?
Quick one, that's B. If an API isn't released for cloud dev, syntax check fails right away.
Option B is correct, syntax error right away if it's not released for cloud. Trap answer is A-ATC checks do extra validation, but this fails earlier at syntax. Would it change if “cloud-ready” is about on-prem extensions and not strict ABAP Cloud?
B , syntax error hits as soon as you use an unreleased API in ABAP Cloud. Classic SAP guardrail for cloud stability. Unless something changed recently, I think B is it.
Option D. seen a similar question in practice exams, I'd review official SAP doc too.
B , these SAP cloud restrictions are so strict. If the API isn’t released for ABAP Cloud, you get a syntax error instantly at compile time. Sometimes wish they were a bit more flexible but pretty sure B is right here.
B imo. In ABAP Cloud, the compiler blocks you right away if the API isn't released for cloud use, it's a syntax error before activation. Not like on-prem where some stuff slips by. Pretty sure that's what SAP wants here.
B
Be respectful. No spam.