A county security developer must create and delete network objects using the platform named in DEVCOR task 3.2. Which product and API family is correct?
Select an answer to reveal the explanation.
Short Explanation
Task 3.2 is the manager living on the firewall itself—Firepower Device Manager—not the separate FMC product. Different badge, different API family.
Full Explanation
DEVCOR task 3.2’s create/delete network-object work targets the on-box manager for a threat-defense device: Firepower Device Manager, reached through /api/fdm/… paths on that host. FDM is the device-local manager API family for labs and deployments that are not driven exclusively through a central management center, and the token plus /object/networks resources live in that family.
Using Secure Firewall Management Center (FMC) central API exclusively fails the task naming when the blueprint points at FDM: FMC is a different product surface with different URLs and object models, even though both relate to Secure Firewall. Cisco DNA Center Intent API for fabric wireless underlay objects fails by domain—DNA Center intent addresses campus fabric/wireless controllers, not FDM network objects on a threat-defense appliance. Intersight SaaS policy classes for compute PhysicalSummaries writes fail similarly: Intersight retrieve/write for compute inventory is a separate Cisco platforms story, not FDM object CRUD.
Exam caveat: FMC versus FDM is a deliberate distractor pair; read whether the stem says device manager on the threat-defense host versus central management.
Operational check: confirm base URL reaches the threat-defense FDM HTTPS endpoint, successfully POST /api/fdm/…/fdm/token, and see /object/networks under that same /api/fdm tree before coding create/delete.