Which two criteria can an endpoint be classified statically into an application EPG?

4 thoughts on “Which two criteria can an endpoint be classified statically into an application EPG?”

1. I vote also for AE.

   Reply

2. I think the wording is really off. It only makes sense to me if the wording is more along the terms of “Which two criteria are used to statically bind an endpoint into an EPG.” Thus indicating that both criteria have to be selected before the endpoint can be assigned to a specific EPG. If we take the wording as this, the answer would be A and E as Raja suggests.

   My reasoning behind this would be that the other three criteria simply don’t fit when we’re talking about static binding. This is called out in all the documents I’ve looked at so far. The VM Name, DNS name, OS, or other VM attributes are used to dynamic assignment. Which makes way more sense as those objects are going to be rather fluid in the environment.

   So, A and E

   Reply

3. Probably the answer is AD

   EPG Usage

   EPGs are designed to abstract the instantiation of network policy and forwarding from basic network constructs (VLANs and subnets.) This allows applications to be deployed on the network in a model consistent with their development and intent. Endpoints assigned to an EPG can be defined in several ways. Endpoints can be defined by virtual port, physical port, IP address, DNS name, and in the future through identification methods such as IP address plus Layer 4 port and others

   https://www.cisco.com/c/en/us/solutions/collateral/data-center-virtualization/application-centric-infrastructure/white-paper-c11-731630.html

   Reply

4. I think the answer should be …

   A & E

   Reply