Which of the following Cisco APIC configuration methods should not be mixed with other configuration methods?

A. NX-OS CLI
B. APIC REST API

C. APIC GUI in Advanced mode

D. APIC GUI in Basic mode

Explanation:

The Cisco Application Policy Infrastructure Controller (APIC) graphical user interface (GUI) in Advanced mode method of configuring a Cisco APIC should not be mixed with other configuration methods. The Cisco APIC is a means of managing the Cisco Application Centric Infrastructure (ACI). By using the APIC, administrators can deploy policies and monitor the health of the infrastructure. The APIC GUI has two modes: Advanced and Basic. Advanced mode is intended for large-scale infrastructures and uses different objects than the other methods.
The Cisco APIC GUI in Basic mode configuration method and the NX-OS command-line interface (CLI) configuration method can be mixed. Configuration changes that are made in the Cisco APIC’s NX-OS CLI are typically reflected in the Cisco APIC GUI in Basic mode. In addition, changes made in the APIC GUI in Basic mode are more accurately reflected in the NX-OS CLI. The APIC GUI in Basic mode is typically used to deploy more common ACI workflows. However, Cisco recommend not using the NX-OS CLI or Cisco APIC GUI in Basic mode prior to using the CISCO APIC GUI in Advanced mode; the former modes create objects that Advanced mode does not use and that cannot be deleted from the configuration.
The APIC representational state transfer (REST) application programming interface (API) is not itself an APIC configuration method. Instead, the APIC REST API is responsible for facilitating communication between the APIC and configuration methods or automation tools. By default, the APIC REST API relies on Hypertext Transfer Protocol Secure (HTTPS) to accept queries and return either JavaScript Object Notation (JSON) or Extensible Markup Language (XML) data.

Reference:

Cisco: Cisco APIC Basic Configuration Guide, Release 2.x: About ACI/APIC Interfaces.