The library card-renewal API Gateway has no events in Logging yet. What must the developer do so the service starts writing those events?
Select an answer to reveal the explanation.
Short Explanation
Until you flip the service’s log category on and park the log in a log group, the service is silent in Logging. Categories are per service—Object Storage’s labels do not transfer to API Gateway.
Full Explanation
Service logs do not appear until you enable them for that resource. For the library card-renewal API Gateway, the developer must enable the gateway’s own service log category, place the resulting log in a log group that lives in a compartment, and give the log a name. Only then does the service start writing those events into OCI Logging. Categories are service-specific; they are not portable labels you copy from another product.
Copying an Object Storage read/write logging category onto the gateway unchanged fails because categories do not transfer across services—Object Storage’s labels are not API Gateway’s. Creating only an APM domain sets up tracing storage; it does not flip Logging service categories on for the gateway. Disabling Audit logs so service logs can "take their place" is both unnecessary and wrong: Audit remains the public-API trail and is not swapped for service logs.
Exam caveat: Audit continues independently; enabling service logs adds a category stream—it does not replace or require turning Audit off. Operational check: after enablement, generate renewals through the gateway and verify new events in the named log/group via Logging Search; if the group is empty, recheck category, compartment, and that traffic actually hit that gateway deployment.