MENU
Assuming the Apache Web Server Identification Rule (CI Identifier) is configured as shown with the following
Criterion attributes:
Class
Configuration file
Version
Yesterday, an Apache Web Server CI was discovered as part of Service Mapping. Today, the application owner upgraded the Apache Web Server to a different version and reran discovery of the service. What will happen in the CMDB?
Suggested Answer: A
Get Premium CIS-SM Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
EL
Eloisa
12 months ago
Definitely not a reclassification, that's for sure!
MA
Maurine
12 months ago
Really? I thought that would cause a duplication error.
TR
Tracie
1 year ago
I think it will reconcile and update the version.
KA
Katina
1 year ago
No way, it should just update the existing one!
JE
Jenifer
1 year ago
I'm pretty sure a new CI gets created with a version change.
AL
Alayna
1 year ago
I feel like if the CI is already in the CMDB, it should just update instead of creating a new one. So, I think C makes the most sense here.
SA
Sabra
1 year ago
I’m a bit confused about the reclassification part. Does upgrading the version really change the classification of the CI?
RE
Renea
1 year ago
I think I practiced a question similar to this, and it mentioned that the existing CI would be updated with the new version. So, I’m leaning towards option C.
LA
Lavonne
1 year ago
I remember something about how version changes can affect CI reconciliation, but I'm not entirely sure if it leads to a duplication error or an update.
CA
Carey
1 year ago
Okay, let's see. The key seems to be that the processor used data collected for a different purpose, so that's likely a breach. I think I'll go with option C - the processor needs to notify the controller so they can report it.
MI
Mila
1 year ago
Okay, I think I've got this. The key is using Synchronized Data Source to sync the Sales Cloud data, and then using SQL Query Activities to create a sendable data extension.
ST
Stephane
1 year ago
I'm a bit unsure about some of these choices. I'll need to review my notes on Multi-Org to make sure I understand the capabilities.
LA
Lawrence
1 year ago
I bet the application owner is wishing they had a crystal ball to see the future and know which version of Apache to upgrade to. But hey, at least the CMDB is there to save the day with option C. It's like the CI version control superhero, keeping everything in check.
LO
Loreen
1 year ago
Ah, the age-old question of the Apache Web Server CI. Of course, option C is the correct answer. The CMDB is like a digital librarian, keeping track of all the different versions and reconciling the changes. I just hope the application owner didn't accidentally upgrade to the 'Spicy Salsa' version of Apache instead of the 'Mild Guacamole' one.
BR
Bronwyn
1 year ago
The CMDB is like a digital librarian indeed, keeping everything organized and up to date.
JO
Jordan
1 year ago
Haha, 'Spicy Salsa' version of Apache sounds interesting. Hopefully, the application owner upgraded to the right version!
DO
Domonique
1 year ago
I agree, option C is definitely the correct answer. The CMDB will reconcile the changes and update the version.
ER
Erick
2 years ago
This is a tricky one, but I think C is the right answer. The CMDB should be able to handle the version upgrade and update the existing CI. Although, I'm curious if the application owner used the 'Upgrade to the Latest Version' button or if they did a manual update. Either way, the CMDB should be on top of it.
ER
Erinn
1 year ago
Yes, the CMDB should be able to recognize the updated version and update the existing CI accordingly.
CH
Cherrie
1 year ago
I think so too. As long as the CMDB is properly configured, it should be able to handle the version update without creating duplicates.
CA
Cassandra
1 year ago
I agree, C seems like the most logical option. The CMDB should reconcile the existing CI with the upgraded version.
CA
Carri
2 years ago
Hmm, I was thinking the new version would create a duplicate, but option C makes sense. The CMDB is smart enough to reconcile the changes and update the existing CI. Though I wonder if the application owner remembered to clear the cache before running the discovery again...
CO
Colene
1 year ago
It's important to clear the cache to ensure accurate results in the CMDB.
HY
Hyun
1 year ago
I hope the application owner cleared the cache before rerunning the discovery.
FR
Franklyn
1 year ago
I agree, the CMDB is designed to handle updates like this.
GE
Genevieve
1 year ago
Option C is correct. The CMDB will reconcile the changes and update the existing CI.
NA
Natalya
1 year ago
Yes, the reconciliation process is crucial for maintaining data integrity in the CMDB.
MI
Mitsue
1 year ago
It's important to keep the CMDB accurate and up to date.
JO
Johnna
1 year ago
Hopefully the application owner did remember to clear the cache before rerunning the discovery.
JE
Jestine
1 year ago
I agree, option C seems like the most logical outcome.
CA
Catherin
2 years ago
Ah, I see. The key here is that the application owner upgraded the Apache Web Server to a different version and reran discovery. So option C is correct - the existing Apache Web Server CI will be reconciled with the upgraded version, and its version will be updated.
MI
Micah
2 years ago
I'm not sure, but I think a duplication error might occur if the CI is not properly reconciled.
KA
Kayleigh
2 years ago
I agree with Salina. It makes sense to update the version instead of creating a new CI.
SA
Salina
2 years ago
I think the existing Apache Web Server CI will be reconciled with the upgraded version.