350-901 · Question #99
350-901 Question #99: Real Exam Question with Answer & Explanation
The correct answer is C: DELETE /api/fmc_config/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/object/fqdns/005056BB-0B24-0ED3-0000-858993545263. The Cisco FMC REST API follows standard REST URL conventions where a specific resource is addressed by appending its UUID directly as the final path segment.
Question
Refer to the exhibit. Which API call does an engineer use to delete the FQDN object?
Options
- ADELETE /api/fmc_config/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/id=005056BB-0B24-0ED3-0000-858993545263/object/fqdns
- BDELETE /api/fmc_config/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/object/fqdns/id=005056BB-0B24-0ED3-0000-858993545263
- CDELETE /api/fmc_config/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f/object/fqdns/005056BB-0B24-0ED3-0000-858993545263
- DDELETE /api/fmc_confio/v1/domain/e276abec-e0f2-11e3-8169-6d9ed49b625f
Explanation
The Cisco FMC REST API follows standard REST URL conventions where a specific resource is addressed by appending its UUID directly as the final path segment.
Common mistakes.
- A. The UUID is incorrectly placed before the resource collection name 'fqdns' rather than after it, reversing the required path hierarchy, and 'id=' is not valid REST path syntax.
- B. Although the path order is closer to correct, the 'id=' prefix is not valid REST path parameter syntax - UUIDs must appear as bare path segments, not as key=value pairs.
- D. This URL omits both the object collection type 'fqdns' and the specific object UUID entirely, making it an incomplete domain-level endpoint that cannot target a specific FQDN object for deletion.
Concept tested. Cisco FMC REST API DELETE request URL structure
Reference. https://developer.cisco.com/docs/firepower-management-center-nio/api-quick-start/
Topics
Community Discussion
No community discussion yet for this question.