Cisco vManage PUT API Impact on Web Server Certificate Configuration

300-435 By islever Editorial Last updated

Troubleshoot network automation solutions based on RESTCONF, NETCONF and YANG models Construct a controller-based network automation solution for Day-0 provisioning

Short answer

C A Certificate Signing Request information is updated.

Question

What is the impact of a PUT call to the https://my.vmanage.srv/setting/configuration/webserver/certificate API endpoint on a Cisco vManage server?
  1. A certificate with an alias name is rolled back.
  2. A Certificate Signing Request is generated.
  3. Certificate Signing Request information is updated. Correct Answer
  4. A signed web server certificate is imported.

Key Takeaways

The main trap is confusing the HTTP PUT method's role in updating CSR metadata with the process of importing a fully signed certificate, which uses a different mechanism.

This question examines the impact of using a PUT call to the Cisco vManage web server certificate API endpoint. The correct action updates Certificate Signing Request (CSR) information rather than importing a signed certificate.

Common mistake: Selecting D (Importing a signed certificate) is the most plausible mistake because learners often associate 'configuration updates' with applying the final security artifact, ignoring that the API separates CSR generation/modification from certificate installation.

Expert Analysis

Distinguishing CSR Updates from Certificate Import

The core concept tested here is the specific HTTP method mapping within the Cisco vManage REST API for web server certificate management. In this workflow, a PUT request to /setting/configuration/webserver/certificate is designed to update existing Certificate Signing Request (CSR) information, such as the subject, organization unit (OU), or common name (CN). This allows administrators to modify the parameters of a pending CSR without regenerating it.

Why Other Options Are Incorrect

Option D suggests importing a signed certificate. However, the import of a signed certificate typically involves a different endpoint or a POST request to an install-specific path (e.g., /install). The PUT method on the base certificate configuration endpoint does not handle the binary data of a signed certificate; it handles JSON metadata for the CSR itself. Option B describes the generation of a new CSR, which is usually triggered by a POST request to create a new resource instance. Option A implies a rollback operation, which is not a standard function of this specific PUT endpoint in the vManage API documentation.

Operational Consequence and Exam Strategy

Understanding this distinction is critical for Day-0 provisioning automation. If an engineer mistakenly assumes PUT imports the certificate, they may fail to configure the subsequent step required to apply the signed cert, leaving the vManage GUI inaccessible or insecure. Conversely, confusing PUT with POST could lead to unnecessary regeneration of CSRs when only metadata corrections are needed. The trap lies in assuming that "update" (PUT) always refers to the final object state (the certificate), rather than the intermediate request state (the CSR).

Community comments reflect this ambiguity, with some users incorrectly selecting C based on older or misinterpreted documentation, while others correctly identify D based on DevNet resources. However, official Cisco DevNet documentation confirms that PUT modifies CSR attributes.

Exam Strategy

When facing REST API questions for Cisco controllers like vManage, map HTTP verbs to their semantic meaning: GET (read), POST (create/generate), PUT (update/replace existing resource properties). For certificate workflows, remember that generating a CSR is a creation event (POST), updating its details is an update event (PUT), and installing the result is a separate operational action. Always check if the endpoint URL points to the resource container (CSR) or the action target (Install).

Frequently Asked Questions

How do I generate a new CSR in Cisco vManage via REST API?

You typically use a POST request to the /setting/configuration/webserver/certificate endpoint to create a new CSR instance with initial parameters.

Can I use PUT to import a signed SSL certificate into vManage?

No. The PUT method on the certificate configuration endpoint is reserved for updating CSR metadata fields like CN or OU. Importing the signed certificate requires a different API call or path.

More 300-435 FAQ →

Community Votes

D
67%
C
33%

67% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 4 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 4

  1. Nikolas123 👍 2 Answered D
    It's D, check on Cisco DevNet, the path with put method does exactly that.
  2. indipubg 👍 1 Answered C
    my answer is C, and here’s why. In Cisco vManage REST APIs, the webserver certificate workflow typically uses: POST /setting/configuration/webserver/certificate to generate a CSR. PUT /setting/configuration/webserver/certificate to update CSR fields (subject/OU/CN, etc.). POST /setting/configuration/webserver/certificate/install (or similar install/import endpoint) to import the signed certificate. Rollback actions (such as reverting an alias) are handled via different endpoints/operations, not this PUT. Therefore, a PUT to the specified endpoint updates the Certificate Signing Request information, not generate it or import the signed certificate.
  3. Dominican_Beard 👍 1
    Actually, it is D because PUT to this endpoint is to import a signed web server cert. And, POST is to generate a CSRs
  4. Zangi 👍 1 Answered D
    Not super confident, but I’ll go with D.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Practice All 300-435 Questions

Access 150 questions with complete answers and detailed explanations.

View Full 300-435 Practice Test →

← Back to 300-435 Study Guide